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] Why using hypercall_page ?

To: Li Yaqiong <liyaq04@xxxxxxxxxx>
Subject: Re: 答复: [Xen-devel] Why using hypercall_page ?
From: Wu Bingzheng <wubingzheng@xxxxxxxxx>
Date: Thu, 23 Oct 2008 09:46:26 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Oct 2008 18:47:02 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=LLU92MPHa0DMwOBDOLvjelG0HqnQEiSXMmh6QaVFqDI=; b=OFbrry+bA60zy45D+9LPuqgGIe3vGefeREkuNZjNpBy65IVz/OUakjpQ7w12p0bgZe VXpW3zPxQbIhiwMNsf4oDfeTvZxx/v/tHI2rdZQhtDcCBMuM7u7uopgIfy8xbLu/0JSY YjN5DOYzKUA+0UYjnpjj3Iqk9hXzs67Ge1JaU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=itL/cuOqV4jOpYr6WhaGlfBtI9pT3t1R0RWZ3DsDRF+7DZmybGADT9pK49+gXc6kJ+ dCHh85kwK5VMEghrSJVrdBZKmrZLOBAP3XkWm4xKLGclzZbfRBX3Sc1lfALw7ROq5vss ynd3XW2jiCo5Nl15FX+7a5S40nkrPdT3bZ6ZE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC88FCA8B5E43A994773AA7A161DF1C@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC88FCA8B5E43A994773AA7A161DF1C@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I think that's the reason too. 

Thank you very much.

Wu

在 2008-10-23四的 09:31 +0800,Li Yaqiong写道:
> As you know, the old Intel/AMD x86 cpus use INT to invoke kernel's
> service. But the newer CPUs introduce two instruction pairs:
> syscall/sysret, syscenter/sysexit. So, because the hypercall page is
> filled by Xen, it can hide the difference of this two types. Guest OS
> only take one uniform format to invoke a hypercall.
> I gusee this is the reason.
> 
> -Techie
> 
> -----邮件原件-----
> 发件人: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] 代表 Wu Bingzheng
> 发送时间: 2008年10月23日 9:18
> 收件人: xen-devel@xxxxxxxxxxxxxxxxxxx
> 主题: [Xen-devel] Why using hypercall_page ?
> 
> Hello,
> 
> I am studing Xen hypercall now. I found that hypercall is invoked via
> hypercall_page, which is only filled with (in
> no-hypervisor-kernel-mode ):
> 
> mov $i, %eax
> int $0x82
> ret
> 
> Why not invoked the hypercall directly by "int $0x82" ? What's the
> advantage of using hypercall_page?
> 
> Thanks,
> Wu
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 


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