From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
eddie.dong@intel.com, xen-devel@lists.xen.org,
jun.nakajima@intel.com, ian.jackson@eu.citrix.com
Subject: Re: [PATCH RFC V6 5/5] xen: Handle resumed instruction based on previous mem_event reply
Date: Tue, 12 Aug 2014 18:43:29 +0300 [thread overview]
Message-ID: <53EA3621.7020906@bitdefender.com> (raw)
In-Reply-To: <53EA4CEA020000780002BB82@mail.emea.novell.com>
On 08/12/2014 06:20 PM, Jan Beulich wrote:
>>>> On 11.08.14 at 17:08, <rcojocaru@bitdefender.com> wrote:
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> @@ -1699,6 +1699,18 @@ static void vmx_enable_msr_exit_interception(struct domain *d)
>> vmx_enable_intercept_for_msr(v, msrs[i], MSR_TYPE_W);
>> }
>>
>> +static bool_t vmx_exited_by_nested_pagefault(void)
>> +{
>> + unsigned long exit_qualification;
>> +
>> + __vmread(EXIT_QUALIFICATION, &exit_qualification);
>> +
>> + if ( (exit_qualification & EPT_GLA_FAULT) == 0 )
>> + return 0;
>> +
>> + return 1;
>> +}
>
> As (I think) said on the previous version already - this would apparently
> benefit from being based on Tamas's recent work (slated to go in once
> the series got suitably acked).
I agree, that would be great. In the meantime, I just thought that the
patches should be self-sufficient.
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2014-08-12 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 15:08 [PATCH RFC V6 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-08-11 15:08 ` [PATCH RFC V6 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-08-12 15:01 ` Jan Beulich
2014-08-11 15:08 ` [PATCH RFC V6 3/5] xen, libxc: Force-enable relevant MSR events Razvan Cojocaru
2014-08-12 15:06 ` Jan Beulich
2014-08-12 15:09 ` Razvan Cojocaru
2014-08-11 15:08 ` [PATCH RFC V6 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-08-12 15:16 ` Jan Beulich
2014-08-12 15:42 ` Razvan Cojocaru
2014-08-12 16:03 ` Jan Beulich
2014-08-11 15:08 ` [PATCH RFC V6 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-08-12 15:20 ` Jan Beulich
2014-08-12 15:43 ` Razvan Cojocaru [this message]
2014-08-12 14:57 ` [PATCH RFC V6 1/5] xen: Emulate with no writes Jan Beulich
2014-08-12 15:08 ` Razvan Cojocaru
2014-08-12 15:27 ` Jan Beulich
2014-08-12 15:49 ` 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=53EA3621.7020906@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=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=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.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.