From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: "Tian, Kevin" <kevin.tian@intel.com>, Jan Beulich <JBeulich@suse.com>
Cc: "Dong, Eddie" <eddie.dong@intel.com>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"tim@xen.org" <tim@xen.org>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>
Subject: Re: [PATCH RFC V8 5/5] xen: Handle resumed instruction based on previous mem_event reply
Date: Thu, 28 Aug 2014 10:30:07 +0300 [thread overview]
Message-ID: <53FEDA7F.9020701@bitdefender.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D126050235@SHSMSX101.ccr.corp.intel.com>
On 08/28/2014 12:06 AM, Tian, Kevin wrote:
>> From: Jan Beulich [mailto:JBeulich@suse.com]
>> Sent: Wednesday, August 27, 2014 8:52 AM
>>
>>>>> On 27.08.14 at 16:01, <rcojocaru@bitdefender.com> wrote:
>>> +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 )
>>
>> It just occurred to me - Is this a valid check for any but
>> EXIT_REASON_EPT_VIOLATION? I didn't think the bits here carry
>> the same meaning regardless of exit kind...
>>
>
> You're right. GLA bit definition is only for EPT violation.
I'll check the exit reason as well.
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2014-08-28 7:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 14:01 [PATCH RFC V8 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-08-27 14:01 ` [PATCH RFC V8 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-08-27 14:01 ` [PATCH RFC V8 3/5] xen, libxc: Force-enable relevant MSR events Razvan Cojocaru
2014-08-27 15:44 ` Jan Beulich
2014-08-27 20:25 ` Tian, Kevin
2014-08-28 7:40 ` Razvan Cojocaru
2014-08-28 8:25 ` Jan Beulich
2014-08-28 8:26 ` Razvan Cojocaru
2014-08-28 21:27 ` Tian, Kevin
2014-08-27 14:01 ` [PATCH RFC V8 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-08-27 15:46 ` Jan Beulich
2014-08-27 16:04 ` Razvan Cojocaru
2014-08-27 20:59 ` Tian, Kevin
2014-08-28 7:54 ` Razvan Cojocaru
2014-08-28 21:22 ` Tian, Kevin
2014-08-27 14:01 ` [PATCH RFC V8 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-08-27 15:52 ` Jan Beulich
2014-08-27 21:06 ` Tian, Kevin
2014-08-28 7:30 ` Razvan Cojocaru [this message]
2014-08-27 15:40 ` [PATCH RFC V8 1/5] xen: Emulate with no writes Jan Beulich
2014-08-27 15:42 ` 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=53FEDA7F.9020701@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=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 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.