All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: dfeustel@mindspring.com
Cc: xen-devel@lists.xensource.com
Subject: Re: xen 3.0 for AMD Pacifica
Date: Tue, 25 Oct 2005 14:24:11 -0500	[thread overview]
Message-ID: <435E865B.50909@us.ibm.com> (raw)
In-Reply-To: <200510251320.47925.dfeustel@verizon.net>

Dave Feustel wrote:

>On Tuesday 25 October 2005 09:53, Anthony Liguori wrote:
>  
>
>>Dave Feustel wrote:
>>
>>    
>>
>>>>We intend to add support for x86 h/w virtualization extensions 
>>>>as information about them becomes available.
>>>>   
>>>>
>>>>        
>>>>
>>>What information is needed beyond the Pacifica documentation already
>>>provided by AMD and the Vanderpool docs provided by Intel?
>>> 
>>>
>>>      
>>>
>>I don't know where you're quoting from, but both specs are out publicly.
>>    
>>
>
>I know. I have both. What I was asking is whether the info in those documents
>is sufficient to make Xen work with  the hardware of both chips, or is additional 
>info needed (and still not available)?
>
Sorry, then yes, theoritically, all you should need are those specs.

>>Both VT and Pacifica are pretty similiar in the basic idea that they 
>>allow the processor to be put in a mode where 30 or so events that 
>>normally don't trap actually do trap.
>>    
>>
>
>Pacifica has a new paging mode (paged real mode) made possible by the 
>Opteron on-chip memory controller. This feature is not present in VT.
>  
>
Yes, there are considerable differences.  Pacifica has paged real mode 
whereas VT requires vm86 mode to be used for real mode emulation.  
Pacifica also has (optional) support for hardware shadow page tables, 
TLB tagging, and DMA memory protection.  They also have different models 
for dealing with the VMCS/VMCB.  I would categorize this stuff mostly as 
optimizations though since none of it's required to meet the 
Popek/Goldberg requirements.

Just enough differences to make things interesting :-)

Regards,

Anthony Liguori

>>Just having the processor trap though doesn't get you virtualization 
>>:-)  Each of those events has to be handled, and often emulated.  Throw 
>>in shadow paging and IO emulation and it's all rather complicated.
>>
>>Plus, there's not much that can be done without having the hardware at 
>>this point.
>>
>>    
>>
>>>Is there any possibility of setting up a mailing list directed specifically at
>>>xen 3.0 hardware supported virtualization?
>>> 
>>>
>>>      
>>>
>>There are an awful lot of Xen mailing lists at this point.  What would 
>>be *really* useful is having some content on the wiki that went into 
>>more depth about VT/Pacifica.
>>
>>Regards,
>>
>>Anthony Liguori
>>
>>    
>>
>>>Thanks,
>>>Dave Feustel
>>>
>>>
>>> 
>>>
>>>      
>>>
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>
>>    
>>
>
>  
>

      parent reply	other threads:[~2005-10-25 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 13:59 xen 3.0 for AMD Pacifica Dave Feustel
2005-10-25 14:37 ` Mark Williamson
2005-10-25 14:53 ` Anthony Liguori
2005-10-25 18:20   ` Dave Feustel
2005-10-25 18:54     ` Mark Williamson
2005-10-25 19:24     ` Anthony Liguori [this message]

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=435E865B.50909@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=dfeustel@mindspring.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.