From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
xen-devel@lists.xensource.com, Alexander Graf <agraf@suse.de>,
Laurent Vivier <Laurent@vivier.eu>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 00/10] xen: pv domain support.
Date: Mon, 06 Apr 2009 13:44:29 -0700 [thread overview]
Message-ID: <49DA69AD.6050700@goop.org> (raw)
In-Reply-To: <49D9A6CD.30602@redhat.com>
Gerd Hoffmann wrote:
> Hmm. I suspect xen's direct paging mode makes that quite intrusive as
> the kvm mmu code would have to know about this extra p2m translation
> step to get the shadow/ept/ntp tables right. Given that this most
> likely would be a odd and rarely tested use case I don't think this
> would be a good idea ...
>
That's mostly encapsulated in the normal pagetable manipulation
routines, so if kvm can be convinced to use those to manage its shadow
tables, it will all Just Work. That doesn't work well with a non-PAE
32-bit host with kvm's PAE shadow pagetables, but Xen doesn't support
non-PAE anyway.
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
xen-devel@lists.xensource.com, Alexander Graf <agraf@suse.de>,
Laurent Vivier <Laurent@vivier.eu>
Subject: Re: Re: [Qemu-devel] [PATCH 00/10] xen: pv domain support.
Date: Mon, 06 Apr 2009 13:44:29 -0700 [thread overview]
Message-ID: <49DA69AD.6050700@goop.org> (raw)
In-Reply-To: <49D9A6CD.30602@redhat.com>
Gerd Hoffmann wrote:
> Hmm. I suspect xen's direct paging mode makes that quite intrusive as
> the kvm mmu code would have to know about this extra p2m translation
> step to get the shadow/ept/ntp tables right. Given that this most
> likely would be a odd and rarely tested use case I don't think this
> would be a good idea ...
>
That's mostly encapsulated in the normal pagetable manipulation
routines, so if kvm can be convinced to use those to manage its shadow
tables, it will all Just Work. That doesn't work well with a non-PAE
32-bit host with kvm's PAE shadow pagetables, but Xen doesn't support
non-PAE anyway.
J
next prev parent reply other threads:[~2009-04-06 20:44 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 21:39 [Qemu-devel] [PATCH 00/10] xen: pv domain support Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 01/10] xen: groundwork for xen support Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-02 16:37 ` [Qemu-devel] " Blue Swirl
2009-04-02 16:37 ` Blue Swirl
2009-04-03 19:58 ` [Qemu-devel] " Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 02/10] xen: backend driver core Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-02 16:49 ` [Qemu-devel] " Blue Swirl
2009-04-02 16:49 ` Blue Swirl
2009-04-03 19:59 ` [Qemu-devel] " Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 03/10] xen: add console backend driver Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 04/10] xen: add framebuffer " Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-02 16:57 ` [Qemu-devel] " Blue Swirl
2009-04-02 16:57 ` Blue Swirl
2009-04-01 21:39 ` [Qemu-devel] [PATCH 05/10] xen: add block device " Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-02 17:02 ` [Qemu-devel] " Christoph Hellwig
2009-04-03 20:11 ` Gerd Hoffmann
2009-04-05 13:49 ` Anthony Liguori
2009-04-06 12:38 ` Christoph Hellwig
2009-04-07 10:22 ` Gerd Hoffmann
2009-04-07 15:51 ` Christoph Hellwig
2009-04-01 21:39 ` [Qemu-devel] [PATCH 06/10] xen: add net " Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 07/10] xen: blk & nic configuration via cmd line Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 08/10] xen: pv domain builder Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-02 17:06 ` [Qemu-devel] " Blue Swirl
2009-04-02 17:06 ` Blue Swirl
2009-04-01 21:39 ` [Qemu-devel] [PATCH 09/10] simplify vga selection Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-01 21:39 ` [Qemu-devel] [PATCH 10/10] xen: add -vga xenfb option, configure xenfb Gerd Hoffmann
2009-04-01 21:39 ` Gerd Hoffmann
2009-04-01 23:41 ` [Qemu-devel] [PATCH 00/10] xen: pv domain support Anthony Liguori
2009-04-02 15:32 ` Ian Jackson
2009-04-02 21:14 ` Laurent Vivier
2009-04-02 21:14 ` Laurent Vivier
2009-04-03 20:24 ` [Qemu-devel] " Gerd Hoffmann
2009-04-03 23:04 ` Alexander Graf
2009-04-03 23:04 ` Alexander Graf
2009-04-05 8:48 ` [Qemu-devel] " Avi Kivity
2009-04-05 11:17 ` Alexander Graf
2009-04-05 11:17 ` Alexander Graf
2009-04-05 11:37 ` [Qemu-devel] " Avi Kivity
2009-04-05 12:10 ` Alexander Graf
2009-04-05 12:10 ` Alexander Graf
2009-04-05 12:33 ` [Qemu-devel] " Avi Kivity
2009-04-06 7:39 ` Gerd Hoffmann
2009-04-06 13:56 ` [Xen-devel] " Stefano Stabellini
2009-04-06 13:56 ` Stefano Stabellini
2009-04-06 7:10 ` Gerd Hoffmann
2009-04-06 6:53 ` Gerd Hoffmann
2009-04-06 20:44 ` Jeremy Fitzhardinge [this message]
2009-04-06 20:44 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2009-04-21 12:19 Gerd Hoffmann
2009-04-22 15:52 ` Anthony Liguori
2009-04-22 16:54 ` [Xen-devel] " Stefano Stabellini
2009-04-23 9:55 ` Gerd Hoffmann
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=49DA69AD.6050700@goop.org \
--to=jeremy@goop.org \
--cc=Laurent@vivier.eu \
--cc=agraf@suse.de \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.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.