linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 12/15] powerpc: Do not use op_model_cell under LPAR
Date: Wed, 13 Dec 2006 09:51:11 +1100	[thread overview]
Message-ID: <1165963871.21287.3.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <200612122055.59698.arnd@arndb.de>

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

On Tue, 2006-12-12 at 20:55 +0100, Arnd Bergmann wrote:
> On Tuesday 12 December 2006 05:13, Michael Ellerman wrote:
> >   On Tue, 2006-12-12 at 13:02 +0900, Ishizaki Kou wrote:
> > > op_model_cell supports native Cell processor. Under LPAR environment,
> > > it cannot work.
> > > 
> > > Signed-off-by: Kou Ishizaki <kou.ishizaki.co.jp>
> 
> Acked-by: Arnd Bergmann <arnd.bergmann@de.ibm.com>
> 
> > 
> > Is FW_FEATURE_LPAR is the right switch to use here, I'm not sure.
> 
> Yes, I think it is. The code accesses I/O memory areas that can not
> work under any hypervisor, so FW_FEATURE_LPAR makes perfect sense
> to me.

Yeah it's good enough.

But to be pedantic, P (LPAR) implies Q (HV), but !P does not imply !Q :)

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-12-12 22:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  4:02 [PATCH 12/15] powerpc: Do not use op_model_cell under LPAR Ishizaki Kou
2006-12-12  4:13 ` Michael Ellerman
2006-12-12  4:53   ` Benjamin Herrenschmidt
2006-12-12  4:55     ` Michael Ellerman
2006-12-12 11:49       ` Ishizaki Kou
2006-12-12 19:55   ` Arnd Bergmann
2006-12-12 22:51     ` Michael Ellerman [this message]

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=1165963871.21287.3.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).