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) host
Date: Wed, 08 Jul 2009 08:19:56 +0000	[thread overview]
Message-ID: <1247041196.6066.177.camel@pasglop> (raw)
In-Reply-To: <1246976262-4826-1-git-send-email-agraf@suse.de>

On Wed, 2009-07-08 at 11:06 +0300, Avi Kivity wrote:
> 
> I don't see how the mmu structure matters.  All mmu notifiers does is 
> tell you when Linux wants to drop a pte, it's completely up to you how 
> to use this information.
> 
> There are three ways of dealing with the problem:
> 
> - ignore it (ia64, ppc)
> 
> Easy to implement, but you can't swap or do any fancy stuff like page 
> migration.  If you have a large tlb/shadow, you pin a lot of pages.

Hrm... with MOL we used to just patch into the low level hash
invalidate, which is called to invalidate the translation from the hash
table when Linux invalidates the PTE. I haven't quite figured out yet
what Alexander does. We could probably use an mmu_notifier for that
provided it's not too high level ie, we may want to stick to whacking
the hash code which does some fancy stuff... 

> - use mmu notifiers (x86)
> 
> Need reverse mapping to convert guest physical addresses to shadow/tlb 
> addresses.  Not difficult to implement but requires careful locking.

Well, as I said, we may want to implement that completely differently at
a lower level, purely at the hash level, and thus use a different
infrastructure. At least that's what MOL did and swap etc... worked just
fine. I need to get more familiar with Alex code to see how he does
things vs. the MMU, but we definitely need to think it through. 

> Can you explain your concerns?

Nothing really just yet. As I said, I need to get my head around Alex
code and figure before I take a position here. It might just be easier
for us to hook into the low level hash table invalidation code instead
and totally ignore the linux PTEs.

Cheers,
Ben.

 


  parent reply	other threads:[~2009-07-08  8:19 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
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 ` Benjamin Herrenschmidt [this message]
2009-07-08  8:28 ` 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=1247041196.6066.177.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.