From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH RFC 3/9] xen: Force-enable relevant MSR events; optimize the number of sent MSR events
Date: Wed, 23 Jul 2014 11:03:02 +0300 [thread overview]
Message-ID: <53CF6C36.6010503@bitdefender.com> (raw)
In-Reply-To: <53CF86C60200007800024F7D@mail.emea.novell.com>
On 07/23/2014 10:56 AM, Jan Beulich wrote:
>>>> On 09.07.14 at 10:02, <rcojocaru@bitdefender.com> wrote:
>> On 07/02/2014 06:43 PM, Jan Beulich wrote:
>>>>>> On 02.07.14 at 17:35, <andrew.cooper3@citrix.com> wrote:
>>>> On 02/07/14 14:33, Razvan Cojocaru wrote:
>>>>> @@ -700,6 +700,25 @@ void vmx_disable_intercept_for_msr(struct vcpu *v, u32
>> msr, int type)
>>>>> if ( msr_bitmap == NULL )
>>>>> return;
>>>>>
>>>>> + /* Filter out MSR-s needed by the memory introspection engine */
>>>>> + switch ( msr )
>>>>> + {
>>>>> + case MSR_IA32_SYSENTER_EIP:
>>>>> + case MSR_IA32_SYSENTER_ESP:
>>>>> + case MSR_IA32_SYSENTER_CS:
>>>>> + case MSR_IA32_MC0_CTL:
>>>>> + case MSR_STAR:
>>>>> + case MSR_LSTAR:
>>>>> +
>>>>
>>>> Given the performance implications of forcing interception of these
>>>> MSRs, it would be gated on mem_access being active for the domain.
>>>
>>> Absolutely.
>>
>> Unfortunately the call to vmx_disable_intercept_for_msr() happens _very_
>> early, and by the time our application gets to enable mem_access on the
>> domain, the interception for these MSRs has already been disabled, with
>> unacceptable consequences.
>>
>> I've tested this with an "if (
>> mem_event_check_ring(&d->mem_event->access) )" test.
>>
>> Also, ideally we'd like to be able to start monitoring an already
>> started domain, and in that case the mem_access test would be useless
>> even considering a workaround for the case above.
>
> All understood, but not penalizing non-monitored VMs has certainly
> higher priority.
Got it, I've already changed the code, but waiting on a few other things
before resubmitting the series. As far as this patch goes, the HV now
only refuses to disable interception for the interesting MSRs if
mem_access is active for the domain, and always enables interception for
them on XEN_DOMCTL_MEM_EVENT_OP_ACCESS in mem_event_domctl().
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2014-07-23 8:03 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 13:33 [PATCH RFC 1/9] xen: Emulate with no writes; compute current instruction length Razvan Cojocaru
2014-07-02 13:33 ` [PATCH RFC 2/9] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-07-02 15:31 ` Andrew Cooper
2014-07-07 14:50 ` Razvan Cojocaru
2014-07-10 8:05 ` Razvan Cojocaru
2014-07-10 8:17 ` Andrew Cooper
2014-07-10 8:23 ` Razvan Cojocaru
2014-07-10 11:57 ` Razvan Cojocaru
2014-07-10 12:16 ` Razvan Cojocaru
2014-07-10 13:01 ` Andrew Cooper
2014-07-02 15:37 ` Jan Beulich
2014-07-03 8:12 ` Razvan Cojocaru
2014-07-03 8:54 ` Jan Beulich
2014-07-02 13:33 ` [PATCH RFC 3/9] xen: Force-enable relevant MSR events; optimize the number of sent MSR events Razvan Cojocaru
2014-07-02 15:35 ` Andrew Cooper
2014-07-02 15:43 ` Jan Beulich
2014-07-09 8:02 ` Razvan Cojocaru
2014-07-23 7:56 ` Jan Beulich
2014-07-23 8:03 ` Razvan Cojocaru [this message]
2014-07-02 13:33 ` [PATCH RFC 4/9] xenctrl: Make the headers C++ friendly Razvan Cojocaru
2014-07-02 15:37 ` Andrew Cooper
2014-07-02 13:33 ` [PATCH RFC 5/9] xen: Support for VMCALL mem_events Razvan Cojocaru
2014-07-02 15:47 ` Jan Beulich
2014-07-02 15:54 ` Razvan Cojocaru
2014-07-02 16:11 ` Jan Beulich
2014-07-02 16:23 ` Razvan Cojocaru
2014-07-03 6:28 ` Jan Beulich
2014-07-03 7:29 ` Razvan Cojocaru
2014-07-02 15:54 ` Andrew Cooper
2014-07-02 15:59 ` Razvan Cojocaru
2014-07-02 13:33 ` [PATCH RFC 6/9] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-07-02 15:51 ` Jan Beulich
2014-07-02 16:00 ` Andrew Cooper
2014-07-02 16:58 ` Mihai Donțu
2014-07-02 17:07 ` Andrew Cooper
2014-07-03 8:23 ` Mihai Donțu
2014-07-03 9:32 ` Andrew Cooper
2014-07-03 9:40 ` Razvan Cojocaru
2014-07-02 16:06 ` Razvan Cojocaru
2014-07-02 16:13 ` Jan Beulich
2014-07-02 13:33 ` [PATCH RFC 7/9] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-07-02 15:56 ` Jan Beulich
2014-07-03 8:55 ` Razvan Cojocaru
2014-07-03 9:02 ` Jan Beulich
2014-07-03 9:12 ` Razvan Cojocaru
2014-07-03 9:18 ` Andrew Cooper
2014-07-03 9:22 ` Jan Beulich
2014-07-03 9:34 ` Razvan Cojocaru
2014-07-03 10:14 ` Jan Beulich
2014-07-02 13:34 ` [PATCH RFC 8/9] xen: Generic instruction re-execution mechanism for execute faults Razvan Cojocaru
2014-07-02 16:04 ` Andrew Cooper
2014-07-02 13:34 ` [PATCH RFC 9/9] mm: mark pages that have their permissions controlled by a domain Razvan Cojocaru
2014-07-03 10:19 ` Jan Beulich
2014-07-03 11:27 ` Razvan Cojocaru
2014-07-03 12:15 ` Jan Beulich
2014-07-02 15:20 ` [PATCH RFC 1/9] xen: Emulate with no writes; compute current instruction length Andrew Cooper
2014-07-03 7:42 ` Razvan Cojocaru
2014-07-02 15:21 ` Jan Beulich
2014-07-02 15:43 ` Razvan Cojocaru
2014-07-02 16:08 ` Jan Beulich
2014-07-02 16:18 ` Razvan Cojocaru
2014-07-03 6:24 ` Jan Beulich
2014-07-03 7:38 ` Razvan Cojocaru
2014-07-03 8:05 ` Jan Beulich
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=53CF6C36.6010503@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=tim@xen.org \
--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.