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] Hypercall-page initialization

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Hypercall-page initialization
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Tue, 7 Feb 2006 19:04:46 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 07 Feb 2006 18:15:42 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=o+owxSRrvzRdOV0hQQbdSVANoxgcH9vDauOHmnIj0y/MBGyMJI343IFG6MI5SdU1LXKvMHbQrh3VAjFP6+N72lemVBWLGL8IskmsbQS0GWQfgWDeE5rCy3bgtLC80Mg7yNX0tngJDYXzvO6lgc4ezul6VQ5UvuvV2CCc3+gkTvI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <919bb30a9d2ec4dfa5f8bbfbb7371219@xxxxxxxxxxxx>
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: <e08041f30602070820r2602de2hcba5742e3104d3ba@xxxxxxxxxxxxxx> <919bb30a9d2ec4dfa5f8bbfbb7371219@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 2/7/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

> We can make the hypercall for filling the page one that can be executed
> by unpriv domains (i.e., make it not a dom0_op).

That would be fine with me, though I guess purists would argue that it
would remove some flexibility, e.g. int 0x82 (or another hardcoded
trap vector) would have always have to be supported.

> Or if you want to fill it in from within the domU, how about if we did
> something like reserve some space of MSRs for Xen use (e.g., hex
> Bxxxxxxx). Then we could say that, if the guest writes an MFN to a
> particular one of those MSRs, it gets filled with hypercall-page
> goodness. :-)

Hmm would that work in paravirt mode also? I guess Xen would trap the
exception and do the right thing? I suppose this has the advantage of
avoiding any hardcoded trap vectors.

>   -- Keir

Jacob

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

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