All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 00/23] Add KVM support for PPC64 (970) hosts
Date: Wed, 08 Jul 2009 06:17:28 +0000	[thread overview]
Message-ID: <1247033848.6066.115.camel@pasglop> (raw)
In-Reply-To: <1246976262-4826-1-git-send-email-agraf@suse.de>

On Tue, 2009-07-07 at 17:44 +0200, Arnd Bergmann wrote:
> Most of the code is after 970 but does look generic enough to be
> usable
> on other powerpc64 implementations. How specific to 970 is it really?
> Maybe the files and identifiers could be renamed to ppc64?
> 
> You mentioned before that you could not get ppc32 guests to run on
> Cell hosts, but how about 970 or cell guests? Are there any problems
> that mean it cannot work on Power5/6/7 hosts, or was that just a
> matter of your priorities and available test hardware?

There is another problem I foresee which is the cache line size
difference.... That can not be emulated.

The cache line sizes vary between processors, that is, the problem is
not only classic 32 "32 bytes" vs. classic 64 "128 bytes", some CPUs
have 64 bytes cache line size for example too.

However, we can somewhat work around. At least 64-bit linux uses the
cache line size from the device-tree for example and overrides the
cputable content with that.

So if we manage to pass a "manufactures" device-tree down, we can cope
with the differences to some extent.

Things are going to be harder if the goal is to run some other OS, of
course, to the extent that we may not be able to sort it out completely
but at least for the linux-in-linux case it should work. For example, I
think MacOS uses the PVR and ignores the device-tree values...

Unfortunately, 32-bit linux does the same, though there is some work in
progress to change that, so it won't be a problem in the long run.

The patching technique Alexander does on executable pages is fun :-)
Though it's also both a bit slow and potentially dangerous (you don't
know for sure that what you are patching is actually an instruction).

Maybe it should be a configuration option to only be enabled when
needed.

Cheers,
Ben.




  parent reply	other threads:[~2009-07-08  6:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 14:17 [PATCH 00/23] Add KVM support for PPC64 (970) hosts Alexander Graf
2009-07-07 15:44 ` Arnd Bergmann
2009-07-07 15:49 ` Alexander Graf
2009-07-07 15:54 ` Avi Kivity
2009-07-07 15:56 ` Alexander Graf
2009-07-07 16:08 ` Avi Kivity
2009-07-08  6:17 ` Benjamin Herrenschmidt [this message]
2009-07-08  6:22 ` Benjamin Herrenschmidt
2009-07-08  6:42 ` Benjamin Herrenschmidt
2009-07-08  7:35 ` Alexander Graf
2009-07-08  8:01 ` Benjamin Herrenschmidt
2009-07-08  8:06 ` Avi Kivity
2009-07-08  8:19 ` [PATCH 00/23] Add KVM support for PPC64 (970) host Benjamin Herrenschmidt
2009-07-08  8:28 ` [PATCH 00/23] Add KVM support for PPC64 (970) hosts Alexander Graf
2009-07-08  8:43 ` [PATCH 00/23] Add KVM support for PPC64 (970) host Avi Kivity
2009-07-08  9:51 ` Benjamin Herrenschmidt
2009-07-08 10:04 ` Avi Kivity
2009-07-08 10:24 ` Benjamin Herrenschmidt
2009-07-08 11:10 ` [PATCH 00/23] Add KVM support for PPC64 (970) hosts Benjamin Herrenschmidt
2009-07-08 12:29 ` Alexander Graf
2009-07-08 21:40 ` Benjamin Herrenschmidt
2009-07-22 22:58 ` Olof Johansson
2009-07-22 23:02 ` Olof Johansson

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=1247033848.6066.115.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=kvm-ppc@vger.kernel.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.