WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Hypercalls in Intel-VT

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Hypercalls in Intel-VT
From: "Ashish Bijlani" <ashish.bijlani@xxxxxxxxx>
Date: Thu, 25 Oct 2007 21:13:39 -0400
Delivery-date: Thu, 25 Oct 2007 18:14:39 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=RbiKmBMn0Pp3dpBsuDjST0Ln7xJILa/nus4pk/SM7dk=; b=WM6ypejGGGQMy6vIj+AbOQ7sGzW76jz5XVzrDR88bCId9JL45CBsuVl/khPO6FhVsXu8p8NOWJ/LC9mWWOtKOgsRJ1rOWb3Y0MVY9qZpv+e2GE2jtlEG7TVvQcwa1nlxFwsfKQmNdHTmcYJ9X1CHj0X8ocR/N7lYxbw5Wp+vbDo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=KtdIvSwEGMyy71ZV5kDzZHm49E0aLfphkzC+KRJOJOt6ufht5FMDvoAubO3amJ6EzMD6ZuQkDuV++jGI4tN2s9sLINh2wcz5s8SI5R+x0zThwrfPiKSzDdV3Ay8klZAEBLgR7Dsxj/WuM3pnqgEGHdPE5jACoYnYqdou5KDI4co=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <FE7BBCFBB500984A9A7922EBC95F516E70F4DD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <ec55b17e0710251603w41333364oa499101cdb64af5b@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E70F4DA@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <ec55b17e0710251644p1c5e47a7k53810b6d34fdecb8@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E70F4DC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <ec55b17e0710251719n126bf13dk7990357d19fa5d9e@xxxxxxxxxxxxxx> <FE7BBCFBB500984A9A7922EBC95F516E70F4DD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
how does dom0 on intel-vt gets privileges to access the hardware devices? i mean does it get these privileges through superpages?

On 10/25/07, Cui, Dexuan <dexuan.cui@xxxxxxxxx> wrote:
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ashish Bijlani
> Sent: 2007年10月26日 8:20
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Hypercalls in Intel-VT

>
> could there be a way to make a transition into xen without a vmexit upon executing an iret inside a guest os krnl?
I think we are talking about VMX guest -- the answer it NO...  For an VMX guest to return to Xen, a VMexit is a must. You can refert to Intel Software Developer Manual 3B for details.

-- Dexuan



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