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: Srujan Kotikela <ksrujandas@xxxxxxxxx>
Subject: Re: [Xen-devel] Read-only locking of Guest Memory pages
From: George Dunlap <dunlapg@xxxxxxxxx>
Date: Wed, 15 Jun 2011 10:34:36 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Delivery-date: Wed, 15 Jun 2011 02:35:27 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=VMPDUOL05H09MUJVCKFwHc8V70fcxdoi4/E45a7s93U=; b=LwfeFTihJMzB5iQNwwRNFHkoWl1yDT/gOBHi5NmZ5x9PkHXxXuhdAMyd2BsNRzvucO e6/l9Sf5a0XaFPwYbcnVbxBxcVTTgTWfs7YVPB+yqgjoXFoEsmZgIWzrZLQwShKsPs+z a/GDzi7g1a8qxvGqsbRqxoj8A44a2M/BaPQYQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=fD/1fQTg5bvXi9Ka2ndPtWAt2dtIzw5PS2iK37hr5GFitH/7OEV//sKGcP3vQ0y+MK 6zeWbP7lBUg2G2iN0cOGoj0hZ+Zqbn3B4R1cdifEYUYtY9MKcKjIMHvMKdZQJ+WR5MWk ztoB+V1klzW90TEf9vEXuIofBM9EYM91XkxG0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTimH2qgm0pfjPQ19kiOZE=0ngHg1wg@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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