[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Read-only locking of Guest Memory pages

  • To: Srujan Kotikela <ksrujandas@xxxxxxxxx>
  • 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
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.