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

[Xen-devel] Re: Hypercall by DomU Application

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Hypercall by DomU Application
From: Srujan Kotikela <ksrujandas@xxxxxxxxx>
Date: Tue, 25 Oct 2011 20:18:20 -0500
Delivery-date: Tue, 25 Oct 2011 18:19:31 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=5NP38TDTMs+tJ+S/G8We9wBkhX+lsddc/B6b7pLqcG4=; b=F0e0McetJeSauccGjryV/1LZaXHbhVoY3s91ajDJ/w/QIrmxpv9KanFP5rQzL7Zcsb YuOVRk5ZQ5x+gLbv7y4DvXY/BUTJig5UrkVAKz1iDnIEy7FtwaLIQjHbfUYzWlZiUBk1 vEzbiKGRTtoK+iZIZfaH30x7QJ2cWkP7HAzYk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAKLFbfyTc-Q4ao44suwBC_XQi7KLaGpfS0=kH=iL2CoQzjQXbQ@xxxxxxxxxxxxxx>
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: <CAKLFbfyTc-Q4ao44suwBC_XQi7KLaGpfS0=kH=iL2CoQzjQXbQ@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On Tue, Oct 25, 2011 at 8:16 PM, Srujan Kotikela <ksrujandas@xxxxxxxxx> wrote:
Hi,

I am working on a security architecture. In this architecture, the application in DomU has to communicate directly with the hypervisor. But as I can see, the xen architecture allows only DomU kernel to raise a hypercall. I am planning to enable application to communicate with xen directly. I am assuming, setting up a trap gate with Ring-3 access should do the trick. I have few questions regarding this.

Is my idea feasible? ==> (  _set_gate(idt_table+HYPERCALL_VECTOR, 15, 3, &hypercall); )

Are there any security/performance/functional implications with this approach?

Thanks and regards,
SDK.



In the proposed security architecture, please note that, it is essential to NOT involve DomU kernel in the process of invoking the hypercall.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>