All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Josh Boyer <jwboyer@linux.vnet.ibm.com>,
	LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/3] powerpc/44x: don't use tlbivax on AMP systems
Date: Wed, 13 Jul 2011 15:57:03 +1000	[thread overview]
Message-ID: <20110713055703.GI20597@ozlabs.org> (raw)
In-Reply-To: <D1C71884-DD31-4F3C-8BF5-C6DB3BF4EC8F@kernel.crashing.org>

On Wed, Jul 13, 2011 at 12:48:21AM -0500, Kumar Gala wrote:
> 
> On Jul 4, 2011, at 11:38 PM, Tony Breeds wrote:
> 
> > +#ifdef CONFIG_PPC_47x
> > +void __init early_init_mmu_47x(void)
> > +{
> > +#ifdef CONFIG_SMP
> > +	unsigned long root = of_get_flat_dt_root();
> > +	if (of_get_flat_dt_prop(root, "cooperative-partition", NULL))
> > +		mmu_clear_feature(MMU_FTR_USE_TLBIVAX_BCAST);
> > +#endif /* CONFIG_SMP */
> > +}
> > +#endif /* CONFIG_PPC_47x */
> > +
> 
> Is this device tree prop spec'd anywhere?

I don't think this has been formally written up, but this was discussed in Feb.
this year http://patchwork.ozlabs.org/patch/81355/

Yours Tony

  reply	other threads:[~2011-07-13  5:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05  4:36 [PATCH 1/3] powerpc/47x: allow kernel to be loaded in higher physical memory Tony Breeds
2011-07-05  4:38 ` [PATCH 2/3] powerpc/44x: don't use tlbivax on AMP systems Tony Breeds
2011-07-13  5:48   ` Kumar Gala
2011-07-13  5:57     ` Tony Breeds [this message]
2011-07-05  4:38 ` [PATCH 3/3] powerpc/44x: boot wrapper: allow kernel to load into non-zero address Tony Breeds
2011-07-05  6:18 ` [PATCH 1/3] powerpc/47x: allow kernel to be loaded in higher physical memory Suzuki Poulose
2011-07-12 13:27   ` Josh Boyer
2011-07-12 20:22     ` Suzuki Poulose

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=20110713055703.GI20597@ozlabs.org \
    --to=tony@bakeyournoodle.com \
    --cc=galak@kernel.crashing.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.