From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org, michael@ellerman•id.au
Cc: paulus@samba•org
Subject: Re: [PATCH 12/15] powerpc: Do not use op_model_cell under LPAR
Date: Tue, 12 Dec 2006 20:55:59 +0100 [thread overview]
Message-ID: <200612122055.59698.arnd@arndb.de> (raw)
In-Reply-To: <1165896791.14839.7.camel@concordia.ozlabs.ibm.com>
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.
Arnd <><
next prev parent reply other threads:[~2006-12-12 19:56 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 [this message]
2006-12-12 22:51 ` Michael Ellerman
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=200612122055.59698.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=michael@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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