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] EPS Signature

To: Kaushik Barde <Kaushik_Barde@xxxxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] EPS Signature
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 12 Feb 2007 07:43:39 +0000
Delivery-date: Sun, 11 Feb 2007 23:43:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <0EF82802ABAA22479BC1CE8E2F60E8C30164B688@xxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdG/Nc6FhN5E7LwEduJCgAX8io7RQAASYugAHRDoLABK2G7PwASBzjWABqxFWAABFzWSwABtIdQAAxyPiI=
Thread-topic: [Xen-devel] EPS Signature
User-agent: Microsoft-Entourage/11.3.3.061214
It doesn't appear obviously incorrect.

 K.


On 12/2/07 02:36, "Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx> wrote:

> 
> 
> But is the usage HYPERVISOR_update_descriptor(...) appropriate?
> 
> -Kaushik
> 
> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
> Sent: Sunday, February 11, 2007 4:58 PM
> To: Kaushik Barde; Ian Pratt; Xen devel list
> Subject: Re: [Xen-devel] EPS Signature
> 
> On 11/2/07 23:39, "Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx> wrote:
> 
>> gdt_table  = get_cpu_gdt_table(cpu);
>> l_entry_ma = virt_to_bus(&(gdt_table[l_Request.entryNum]));
>> l_desc_64  = *( (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
> 
> 



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