All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "Magenheimer,
	Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Essay on an important Xen decision (long)
Date: Wed, 11 Jan 2006 10:25:08 -0600	[thread overview]
Message-ID: <43C53164.2070308@us.ibm.com> (raw)
In-Reply-To: <ca704ea5ca30b98dca4508cd6bfdf581@cl.cam.ac.uk>

Hi Keir,

Keir Fraser wrote:

>
> On an architecture where VP is cheaper to implement than on x86, it 
> may well make sense to do that in preference to P2M. As you say, it 
> makes certain future extensions less of a pain to implement.

Is VP on x86 expensive in terms of performance or complexity?

I imagine that you would have to always have shadow paging enable but 
you could still do bulk updates ala writable page tables so the 
performance cost should be minimal I would think.

Trying to understand the memory system in more details so any additional 
info is much appreciate :-)

Thanks,

Anthony Liguori

> If ia64 does decide to back off from the P==M route then I suspect VP 
> is the way to go (which is I think how ia64 domU's currently work 
> anyway).
>
>  -- Keir
>
>

  reply	other threads:[~2006-01-11 16:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 19:26 Essay on an important Xen decision (long) Magenheimer, Dan (HP Labs Fort Collins)
2006-01-10 19:34 ` Mark Williamson
2006-01-10 19:55 ` Anthony Liguori
2006-01-11  9:33   ` Gerd Hoffmann
2006-01-11 16:22     ` Anthony Liguori
2006-01-11 10:08   ` Keir Fraser
2006-01-11 16:25     ` Anthony Liguori [this message]
2006-01-11 16:22       ` Mark Williamson
2006-01-11 16:41         ` Anthony Liguori
2006-01-11 21:16         ` Hollis Blanchard
2006-01-11 16:38       ` Keir Fraser
2006-01-11 10:46   ` Tristan Gingold
2006-01-10 23:02 ` Hollis Blanchard
2006-01-11 13:37 ` Harry Butterworth
  -- strict thread matches above, loose matches on Subject: below --
2006-01-11  0:13 Magenheimer, Dan (HP Labs Fort Collins)
2006-01-11  0:22 Magenheimer, Dan (HP Labs Fort Collins)
2006-01-11  0:39 Magenheimer, Dan (HP Labs Fort Collins)
2006-01-11 21:36 ` Hollis Blanchard
2006-01-11  7:56 Tian, Kevin
2006-01-11 17:20 Ian Pratt
2006-01-11 17:38 ` Anthony Liguori
2006-01-12  0:48 Magenheimer, Dan (HP Labs Fort Collins)
2006-01-12  2:44 Tian, Kevin
2006-01-16 15:52 ` Mark Williamson
2006-01-16 22:56 Magenheimer, Dan (HP Labs Fort Collins)
2006-01-17  2:47 ` Mark Williamson
2006-01-17  3:03 Magenheimer, Dan (HP Labs Fort Collins)
2006-01-17  3:16 ` Mark Williamson
2006-01-17  4:11 Tian, Kevin

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=43C53164.2070308@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=dan.magenheimer@hp.com \
    --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.