public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: Jon Loeliger <jdl@jdl•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: "linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>
Subject: Re: [PATCH] Remove CPU_FTR_NEED_COHERENT for 7448.
Date: Fri, 04 May 2007 10:16:29 -0500	[thread overview]
Message-ID: <E1HjzWH-0001Wg-Ps@jdl.com> (raw)
In-Reply-To: Your message of "Fri, 04 May 2007 07:36:48 +1000." <1178228208.6353.55.camel@localhost.localdomain>

So, like, the other day Benjamin Herrenschmidt mumbled:
> 
> I still maintain it should be a runtime thing tho :-)
> 
> Ben.

So, could you comment on my proposed solution doing
things exactly this way?  Speifically, would folks
prefer the dynamic 

    number_of_cpus() == 1 

and possibly checking the device tree or SMP map, or the 

    #ifndef SMP

test guarding the removal of the CPU_FTR_NEED_COHERENT bit?

Thanks,
jdl

next prev parent reply	other threads:[~2007-05-04 15:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 21:34 [PATCH] Remove CPU_FTR_NEED_COHERENT for 7448 Jon Loeliger
2007-05-03 10:17 ` Adrian Cox
2007-05-03 10:53   ` Benjamin Herrenschmidt
2007-05-03 16:13   ` Jon Loeliger
2007-05-03 17:07     ` Adrian Cox
2007-05-03 17:38       ` Jon Loeliger
2007-05-03 21:36     ` Benjamin Herrenschmidt
2007-05-04 15:16       ` Jon Loeliger [this message]
2007-05-04 22:25         ` Benjamin Herrenschmidt
2007-05-05 13:25           ` Adrian Cox
2007-05-07 17:31           ` Loeliger Jon-LOELIGER
2007-05-04 20:19   ` Kumar Gala
2007-05-03 11:02 ` Paul Mackerras
2007-05-03 16:04   ` Jon Loeliger
2007-05-03 23:34     ` Paul Mackerras
2007-05-04 15:13       ` Jon Loeliger
2007-05-10 16:17 ` Kumar Gala
2007-05-10 16:44   ` Jon Loeliger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1HjzWH-0001Wg-Ps@jdl.com \
    --to=jdl@jdl$(echo .)com \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox