From: "Jan Beulich" <JBeulich@suse.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: kevin.tian@intel.com, keir@xen.org, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
eddie.dong@intel.com, tim@xen.org, jun.nakajima@intel.com,
xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com
Subject: Re: [PATCH V4 5/5] xen: Handle resumed instruction based on previous mem_event reply
Date: Mon, 08 Sep 2014 16:50:02 +0100 [thread overview]
Message-ID: <540DEC4A02000078000322A8@mail.emea.novell.com> (raw)
In-Reply-To: <1409911297-3360-6-git-send-email-rcojocaru@bitdefender.com>
>>> On 05.09.14 at 12:01, <rcojocaru@bitdefender.com> wrote:
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -1695,6 +1695,21 @@ static void vmx_enable_msr_exit_interception(struct domain *d)
> MSR_TYPE_W);
> }
>
> +static bool_t vmx_exited_by_nested_pagefault(void)
> +{
> + unsigned long exit_qualification, exit_reason;
> +
> + __vmread(VM_EXIT_REASON, &exit_reason);
> + ASSERT(exit_reason == EXIT_REASON_EPT_VIOLATION);
> +
> + __vmread(EXIT_QUALIFICATION, &exit_qualification);
> +
> + if ( (exit_qualification & EPT_GLA_FAULT) == 0 )
> + return 0;
> +
> + return 1;
> +}
So I said a number of times that I think this new function can go
away with the recent changes introducing struct npfec, making
the interesting bit of information already available to
p2m_mem_access_check() if I'm not mistaken. And the previous
excuse of that code not being committed yet is no longer valid.
Jan
next prev parent reply other threads:[~2014-09-08 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 10:01 [PATCH V4 0/5] Basic guest memory introspection support Razvan Cojocaru
2014-09-05 10:01 ` [PATCH V4 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-09-05 10:01 ` [PATCH V4 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-09-05 10:01 ` [PATCH V4 3/5] xen, libxc: Force-enable relevant MSR events Razvan Cojocaru
2014-09-05 10:01 ` [PATCH V4 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-09-05 16:46 ` Tian, Kevin
2014-09-08 15:47 ` Jan Beulich
2014-09-08 16:21 ` Razvan Cojocaru
2014-09-09 9:08 ` Jan Beulich
2014-09-09 10:31 ` Razvan Cojocaru
2014-09-05 10:01 ` [PATCH V4 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-09-08 15:50 ` Jan Beulich [this message]
2014-09-08 15:53 ` Razvan Cojocaru
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=540DEC4A02000078000322A8@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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 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).