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] Read-only locking of Guest Memory pages

To: George Dunlap <dunlapg@xxxxxxxxx>
Subject: Re: [Xen-devel] Read-only locking of Guest Memory pages
From: Srujan Kotikela <ksrujandas@xxxxxxxxx>
Date: Wed, 15 Jun 2011 07:14:57 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Jun 2011 05:15:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GIk9YMInBaZ1n5+XOV4gRyZ/9ik9mwSzoh9OJ2Gxa9k=; b=c3IVK+SBdAztTQPiB0ZySLQhLiDVXveXjYbojSZx9t9GtuVtDgdbY2XKbQqOrGcUoK kc/h/qi55kyIEhD2+GjKQb9o+f8fDapuWXWFSekbKRpOm4bPT1zLZdZwzhhMT900VmlR 3Fzj4+l4r+1mpyOH/g+8P3OKA1TI1yoMbvRD0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=vPmfyRx+5NQFT5g5jwEBGPSKkd0vQCApYOggXZYRR9Z3BHYE2DQxVD/cgIuSgJk9Q9 0i/DkEwHdlFNXkIE5I6HEdf5aDn8o1rye4jaQWdYDZagC3UPDSMAX4eVBAUIg6S6plms GJhcndzTcZvv5o8DdR8WV8OQKtvof232FctIw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTinDTQATF=hePQgA2ctmB5DZOzsrog@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: <BANLkTinp48h5866AcJXmRcmLK1XZ+L8Zpg@xxxxxxxxxxxxxx> <20110614081445.GB11702@xxxxxxxxxxxxxxxxxxxxxxx> <BANLkTimH2qgm0pfjPQ19kiOZE=0ngHg1wg@xxxxxxxxxxxxxx> <BANLkTinDTQATF=hePQgA2ctmB5DZOzsrog@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
In this case, the Guest OS is untrusted. We are trying to secure the process using Xen.
--
Srujan D. Kotikela


On Wed, Jun 15, 2011 at 4:34 AM, George Dunlap <dunlapg@xxxxxxxxx> wrote:
On Tue, Jun 14, 2011 at 5:38 PM, Srujan Kotikela <ksrujandas@xxxxxxxxx> wrote:
> Hi Tim,
>
> I am trying to implement a secure architecture where a process' (selected)
> memory pages have to be set as read-only. The process will send the virtual
> address of pages required (through a custom hypercall) to be set read-only.
> I need to compute the physical address of the pages and set them read-only.

The process can already ask the operating system to do that.  Why does
the hypervisor need to be involved?

 -George

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