From: Ian Campbell <ian.campbell@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: kevin.tian@intel.com, keir@xen.org, jun.nakajima@intel.com,
stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
tim@xen.org, xen-devel@lists.xen.org, eddie.dong@intel.com,
jbeulich@suse.com, andrew.cooper3@citrix.com,
wei.liu2@citrix.com
Subject: Re: [PATCH V9] xen/vm_event: Clean up control-register-write vm_events and add XCR0 event
Date: Wed, 3 Jun 2015 12:45:39 +0100 [thread overview]
Message-ID: <1433331939.7108.74.camel@citrix.com> (raw)
In-Reply-To: <1433331352-18287-1-git-send-email-rcojocaru@bitdefender.com>
On Wed, 2015-06-03 at 14:35 +0300, Razvan Cojocaru wrote:
> As suggested by Andrew Cooper, this patch attempts to remove
> some redundancy and allow for an easier time when adding vm_events
> for new control registers in the future, by having a single
> VM_EVENT_REASON_WRITE_CTRLREG vm_event type, meant to serve CR0,
> CR3, CR4 and (newly introduced) XCR0. The actual control register
> will be deduced by the new .index field in vm_event_write_ctrlreg
> (renamed from vm_event_mov_to_cr).
>
> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
> Acked-by: Jan Beulich <jbeulich@suse.com>
> Acked-by: Kevin Tian <kevin.tian@intel.com>
>
> ---
> Changes since V8:
> - Removed the additional CR3 test code from xen-access.c.
=> Acked-by: Ian Campbell <ian.campbell@citrix.com> (for both ARM and
tools)
next prev parent reply other threads:[~2015-06-03 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 11:35 [PATCH V9] xen/vm_event: Clean up control-register-write vm_events and add XCR0 event Razvan Cojocaru
2015-06-03 11:45 ` Ian Campbell [this message]
2015-06-03 13:29 ` Lengyel, Tamas
2015-06-03 13:48 ` Razvan Cojocaru
2015-06-03 14:19 ` Lengyel, Tamas
2015-06-03 14:37 ` Razvan Cojocaru
2015-06-04 13:53 ` Tim Deegan
2015-06-04 18:49 ` Lengyel, Tamas
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=1433331939.7108.74.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.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=wei.liu2@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.