All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH V2 4/6] powerpc/44x: don't use tlbivax on AMP systems
Date: Thu, 3 Feb 2011 20:22:18 -0600	[thread overview]
Message-ID: <AANLkTimbE-zNH9UCxDjNx65gNgDVqOmKk0SKShqkJ4mS@mail.gmail.com> (raw)
In-Reply-To: <1296774957.14077.23.camel@shaggy-w500>

On Thu, Feb 3, 2011 at 5:15 PM, Dave Kleikamp <shaggy@linux.vnet.ibm.com> w=
rote:

>> Bit too short, I think. =A0I'd suggest either spelling out
>> 'asymmetric-multiprocessor' or 'cooperative-partition' (a more
>> accurate term, IMO).
>
> I could be wrong, but I thought the A stands for Asynchronous, not
> Asymmetric. =A0I thought Asymmetric means that different types of tasks
> run on the secondary processors, as on the Cell. =A0Anyway, going with
> 'cooperative-partition' would avoid that confusion.

Well, if we pretend that everyone already knows what the "A" stands
for, that's not going to avoid confusion.  Some people still are going
to be wrong.  It would be great if we could settle the matter once and
for all.

I've always thought the A stood for asymmetric, since you're running
multiple cores, but each OS is not aware of the others.  It doesn't
necessarily have to be two copies of Linux.  In fact, it usually
isn't.

As for "MPC8572DS-CAMP", I've always hated that.  A specific property
that defines an AMP environment is a much better idea.

--=20
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2011-02-04  2:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 18:48 [PATCH V2 0/6] powerpc: AMP support for 47x Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 1/6] powerpc: Move udbg_early_init() after early_init_devtree() Dave Kleikamp
2011-02-02 23:06   ` David Gibson
2011-02-03  0:00     ` Dave Kleikamp
2011-02-07  8:29       ` David Gibson
2011-03-02  3:37         ` Benjamin Herrenschmidt
2011-03-02 13:03           ` Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 2/6] powerpc/44x: allow override to hard-coded uart address Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 3/6] powerpc/47x: allow kernel to be loaded in higher physical memory Dave Kleikamp
2011-02-02  7:45   ` Kumar Gala
2011-02-09 22:59     ` Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 4/6] powerpc/44x: don't use tlbivax on AMP systems Dave Kleikamp
2011-02-02  7:48   ` Kumar Gala
2011-02-02 13:19     ` Dave Kleikamp
2011-02-02 23:08   ` David Gibson
2011-02-02 23:53     ` Dave Kleikamp
2011-02-03  5:03       ` David Gibson
2011-02-03 23:15         ` Dave Kleikamp
2011-02-04  2:22           ` Timur Tabi [this message]
2011-02-07  8:30           ` David Gibson
2011-02-04 13:56   ` Josh Boyer
2011-02-04 14:44     ` Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 5/6] powerpc/44x: boot wrapper: allow kernel to load into non-zero address Dave Kleikamp
2011-02-01 19:13   ` Scott Wood
2011-02-01 19:41     ` Dave Kleikamp
2011-02-04 14:07   ` Josh Boyer
2011-02-04 14:44     ` Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 6/6] powerpc/476: Create a dts files for two 476 AMP instances under ISS Dave Kleikamp
2011-02-02  2:43   ` David Gibson
2011-02-09 23:03     ` Dave Kleikamp

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=AANLkTimbE-zNH9UCxDjNx65gNgDVqOmKk0SKShqkJ4mS@mail.gmail.com \
    --to=timur@freescale.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=shaggy@linux.vnet.ibm.com \
    /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.