From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: kevin.tian@intel.com, sstabellini@kernel.org,
wei.liu2@citrix.com, Jan Beulich <JBeulich@suse.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
andrew.cooper3@citrix.com, xen-devel@lists.xen.org,
julien.grall@arm.com, tamas@tklengyel.com,
jun.nakajima@intel.com
Subject: Re: [PATCH V9] vm_event: Allow subscribing to write events for specific MSR-s
Date: Wed, 1 Jun 2016 11:44:06 +0100 [thread overview]
Message-ID: <20160601104406.GF5160@citrix.com> (raw)
In-Reply-To: <22350.47980.710977.918770@mariner.uk.xensource.com>
On Wed, Jun 01, 2016 at 11:39:40AM +0100, Ian Jackson wrote:
> Razvan Cojocaru writes ("Re: [PATCH V9] vm_event: Allow subscribing to write events for specific MSR-s"):
> > On 05/13/2016 02:35 PM, Jan Beulich wrote:
> > >>>> On 06.05.16 at 16:33, <rcojocaru@bitdefender.com> wrote:
> > >> Previously, subscribing to MSR write events was an all-or-none
> > >> approach, with special cases for introspection MSR-s. This patch
> > >> allows the vm_event consumer to specify exactly what MSR-s it is
> > >> interested in, and as a side-effect gets rid of the
> > >> vmx_introspection_force_enabled_msrs[] special case.
> > >> The patch also introduces arch_monitor_init_domain() and
> > >> arch_monitor_cleanup_domain(), to do monitor-specific work
> > >> (as opposed to the previous way of doing all the setup in
> > >> vm_event_init_domain() / vm_event_cleanup_domain()).
> > >> This replaces the previously posted "xen: Filter out MSR write
> > >> events" patch.
> > >>
> > >> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
> > >> Acked-by: Wei Liu <wei.liu2@citrix.com>
> > >> Acked-by: Kevin Tian <kevin.tian@intel.com>
> > >
> > > Acked-by: Jan Beulich <jbeulich@suse.com>
> >
> > Does this patch require additional acks? Tamas' maybe?
>
> I assume it's not for 4.7. (If it were for 4.7 it would require a
> release ack, which (on the basis of the information provided so far) I
> think ought probably not to be granted.)
>
This is not for 4.7.
Wei.
> Thanks,
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-01 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 14:33 [PATCH V9] vm_event: Allow subscribing to write events for specific MSR-s Razvan Cojocaru
2016-05-13 11:35 ` Jan Beulich
2016-05-30 7:13 ` Razvan Cojocaru
2016-05-30 10:13 ` Jan Beulich
2016-05-30 18:03 ` Tamas K Lengyel
2016-06-01 10:39 ` Ian Jackson
2016-06-01 10:44 ` Wei Liu [this message]
2016-06-01 11:36 ` 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=20160601104406.GF5160@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.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.