xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Colp <pjcolp@cs.ubc.ca>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Olaf Hering <olaf@aepfle.de>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xenpaging crashes xen in is_iomem_page()
Date: Mon, 26 Jul 2010 11:23:23 -0400	[thread overview]
Message-ID: <AANLkTimAnkJbTRE8DyOa7rZo4ePaAvLAKqBqHMHjU9Gy@mail.gmail.com> (raw)
In-Reply-To: <20100726145807.GU13291@whitby.uk.xensource.com>

On 26 July 2010 10:58, Tim Deegan <Tim.Deegan@citrix.com> wrote:
> Hi,
>
> At 15:39 +0100 on 26 Jul (1280158794), Patrick Colp wrote:
>> On 26 July 2010 10:08, Olaf Hering <olaf@aepfle.de> wrote:
>> > Is there a portable way to check for the EPT flag in xenpaging?
>>
>> Yeah, this can be added. Probably not a bad idea, really. I actually
>> have some code to test if a machine has EPT enabled or not (by
>> borrowing some of the Xen start-up code which checks for things like
>> EPT)
>
> Good idea.  From inside Xen you should be checking hap_enabled(d) (since
> even on an EPT machine the tools can request shadow pagetables for
> individual domains).  Outside Xen I'm not sure there's a reliable way of
> detecting HAP; maybe the xenpaging hypercalls should return an error?

Right, checks against hap_enabled make sense too. From outside Xen, I
can detect if EPT is enabled for the machine. This doesn't guarantee
it's enabled for a given guest nor if it returns "EPT disabled" does
it mean the machine doesn't have EPT (it just means that EPT isn't
enabled at the time). However, it might be better to just put the
checks in Xen and return an error through the domctls if HAP isn't
enabled, as you suggest.


Patrick

  reply	other threads:[~2010-07-26 15:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 11:58 xenpaging crashes xen in is_iomem_page() Olaf Hering
2010-07-26 13:15 ` Patrick Colp
2010-07-26 14:08   ` Olaf Hering
2010-07-26 14:39     ` Patrick Colp
2010-07-26 14:58       ` Tim Deegan
2010-07-26 15:23         ` Patrick Colp [this message]
2010-07-27 15:20   ` Olaf Hering
2010-07-27 15:46     ` Patrick Colp
2010-07-27 18:25       ` Olaf Hering
2010-07-27 18:39         ` Patrick Colp
2010-07-28 15:26           ` Olaf Hering
2010-07-28 16:22             ` Patrick Colp
2010-08-06 11:16       ` Olaf Hering
2010-08-09 13:30         ` Patrick Colp
2010-08-09 17:39           ` Olaf Hering
2010-08-09 18:23             ` Patrick Colp
2010-08-10 14:19               ` Olaf Hering
2010-08-10 15:02                 ` Patrick Colp
2010-08-10 15:06                   ` Olaf Hering

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=AANLkTimAnkJbTRE8DyOa7rZo4ePaAvLAKqBqHMHjU9Gy@mail.gmail.com \
    --to=pjcolp@cs.ubc.ca \
    --cc=Tim.Deegan@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).