From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>, Tamas Lengyel <tlengyel@novetta.com>
Cc: tim@xen.org, kevin.tian@intel.com, wei.liu2@citrix.com,
eddie.dong@intel.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org, Jun Nakajima <jun.nakajima@intel.com>,
keir@xen.org, Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH V7] xen/vm_event: Clean up control-register-write vm_events and add XCR0 event
Date: Fri, 29 May 2015 16:47:20 +0300 [thread overview]
Message-ID: <55686DE8.7030206@bitdefender.com> (raw)
In-Reply-To: <556849A8020000780007EDF7@mail.emea.novell.com>
On 05/29/2015 12:12 PM, Jan Beulich wrote:
>>>> On 28.05.15 at 18:32, <rcojocaru@bitdefender.com> wrote:
>> the macro will probably go out the window (or the first parameter will
>> need to be changed to VM_EVENT_##what instead of VM_EVENT_X86_##what) as
>> soon as ARM control register write events will come into play.
>
> It's in an x86-specific header, so why should it need to be changed
> for ARM? If ARM will gain a similarly named function, the use sites
> will still all be architecture specific, and hence both declaration and
> whether or not to have a wrapper macro can remain a per-arch
> decision.
You're right. Submitted V8 with the proper header included.
Thanks,
Razvan
prev parent reply other threads:[~2015-05-29 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 5:33 [PATCH V7] xen/vm_event: Clean up control-register-write vm_events and add XCR0 event Razvan Cojocaru
2015-05-28 8:39 ` Jan Beulich
2015-05-28 10:56 ` Razvan Cojocaru
2015-05-28 12:09 ` Jan Beulich
2015-05-28 14:12 ` Lengyel, Tamas
2015-05-28 14:33 ` Razvan Cojocaru
2015-05-28 16:06 ` Lengyel, Tamas
2015-05-28 16:32 ` Razvan Cojocaru
2015-05-29 9:12 ` Jan Beulich
2015-05-29 13:47 ` Razvan Cojocaru [this message]
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=55686DE8.7030206@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=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=tlengyel@novetta.com \
--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.