All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Razvan Cojocaru <rzvncj@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Writes to guests' page table pages + mem_events
Date: Mon, 4 Nov 2013 17:40:50 +0000	[thread overview]
Message-ID: <5277DC22.9060005@citrix.com> (raw)
In-Reply-To: <5277DA22.4090600@gmail.com>

On 04/11/13 17:32, Razvan Cojocaru wrote:
> Hello,
>
> looking at pages 6 and 7 of this document:
>
> http://www-archive.xenproject.org/files/summit_3/XenSummit_Shadow2.pdf
>
> I see that instructions writing to the page table pages of a guest are
> emulated by Xen.
>
> Does this mean that, assuming that I make a page table page read-only, I
> will _not_ receive a mem_event if the guest tries to write to said page?
>
>
> Thanks.

A PV guest never has write access to its pagetables.  A PV guest able to
modify its own pagetables without audit from Xen would be a serious
security vulnerability.

An HVM guest completely controls its own pagetables, and protection is
provided by HAP.  Shadow is a little more awkward where a guest has
pagetables which it believes it owns but doesn't.  A shadow guest will
fault on pagetable access but Xen will fix up.

~Andrew

>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2013-11-04 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 17:32 Writes to guests' page table pages + mem_events Razvan Cojocaru
2013-11-04 17:40 ` Andrew Cooper [this message]
2013-11-04 18:27 ` Tim Deegan
     [not found] <mailman.13959.1383588010.32487.xen-devel@lists.xen.org>
2013-11-04 18:05 ` Andres Lagar-Cavilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5277DC22.9060005@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=rzvncj@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.