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: Goetz Bock <bock@blacknet.de>,
	xen-devel@lists.xensource.com, xen-users@lists.xensource.com,
	monz@danbbs.dk
Subject: Re: Re: [Xen-devel] VMX Hardware
Date: Sun, 14 Aug 2005 13:09:53 -0500	[thread overview]
Message-ID: <42FF88F1.6050409@us.ibm.com> (raw)
In-Reply-To: <5e08dad6679ac1fb93d823ac85551efe@cl.cam.ac.uk>

Keir Fraser wrote:

>
> On 14 Aug 2005, at 13:23, Mogens Valentin wrote:
>
>> I assume by VMX, you're talking about cpu/hardware with HW-support 
>> for virtualisation, i.e. Intels Vanderbilt Technology (VT) and AMD' 
>> Pacifica. If so, it's clear to me that AMD will be leading, because 
>> of it's onchip memory controller, and hence reduced needs for 
>> software support to do the page switching, for which Intel needs 
>> quite a lot of software to emulate.
>
>
> Not sure what you mean. Both technologies require the hypervisor to 
> maintain shadow page tables.

The Pacifica spec does mention optional hardware support for "Nested 
Page Tables" which is essentially hardware shadow page tables.

Should be interesting to see the performance difference between 
software/hardware shadow page tables.

It's worth noting that AMD has just released a simulator for (SimNow) 
that has virtualization support.  Perhaps one of the AMD guys on the 
list can confirm whether SimNow has enough Pacifica support for Xen 
development?

Regards,

Anthony Liguori

>
>  -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2005-08-14 18:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 10:44 VMX Hardware Goetz Bock
2005-08-14 11:09 ` Keir Fraser
2005-08-14 12:23   ` Re: [Xen-devel] " Mogens Valentin
2005-08-14 13:27     ` [Xen-users] " Keir Fraser
2005-08-14 18:09       ` Anthony Liguori [this message]
2005-08-14 18:23         ` Keir Fraser
2005-08-16  2:36 ` David

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=42FF88F1.6050409@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=bock@blacknet.de \
    --cc=monz@danbbs.dk \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.