From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Kaushik Barde" <Kaushik_Barde@Phoenix.com>
Subject: RE: EPS Signature
Date: Sun, 11 Feb 2007 18:36:56 -0800
Message-ID: <0EF82802ABAA22479BC1CE8E2F60E8C30164B688@scl-exch2k3.phoenix.com>
References: <C1F56C33.182A%Keir.Fraser@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-class: urn:content-classes:message
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, Xen devel list <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org



But is the usage HYPERVISOR_update_descriptor(...) appropriate? =20

-Kaushik

-----Original Message-----
From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]=20
Sent: Sunday, February 11, 2007 4:58 PM
To: Kaushik Barde; Ian Pratt; Xen devel list
Subject: Re: [Xen-devel] EPS Signature=20

On 11/2/07 23:39, "Kaushik Barde" <Kaushik_Barde@Phoenix.com> wrote:

> gdt_table  =3D get_cpu_gdt_table(cpu);
> l_entry_ma =3D virt_to_bus(&(gdt_table[l_Request.entryNum]));
> l_desc_64  =3D *( (u64 *) &l_Desc);

This should be fine, assuming gdt_table is a normal kernel virtual
address
(e.g., returned by kmalloc()). I/O memory is a different matter in Xen,
in
that virt_to_bus() won't work. In fact the same restriction holds in
native
Linux as well (I/O memory shouldn't be virt_to_bus()ed).

 -- Keir