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] expandable grant table bug?

To: Kasai Takanori <kasai.takanori@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] expandable grant table bug?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 25 May 2007 07:48:07 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 24 May 2007 23:44:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <37a201c79e64$cf072a60$dab2220a@VF03007L>
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: AceemKaP5T8AzwqLEdy5nQAWy6hiGQ==
Thread-topic: [Xen-devel] expandable grant table bug?
User-agent: Microsoft-Entourage/11.3.3.061214
On 25/5/07 01:36, "Kasai Takanori" <kasai.takanori@xxxxxxxxxxxxxx> wrote:

>> Fix grant_table_op to be callable from HVM guests.
> 
> It is not necessary to use all functions of grant_table_op from hvm domain.
> It is necessary only to acquire the query size.
> Is the method of acquiring the query size by HYPERCALL of hvm_op better?

Some people do want to be able to do grant_table_ops in the near future. So
working around that doesn't really make sense.

 -- Keir



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

<Prev in Thread] Current Thread [Next in Thread>