From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: tim@xen.org, kevin.tian@intel.com, wei.liu2@citrix.com,
eddie.dong@intel.com, stefano.stabellini@eu.citrix.com,
andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org, jun.nakajima@intel.com, keir@xen.org,
ian.campbell@citrix.com
Subject: Re: [PATCH V7] xen/vm_event: Clean up control-register-write vm_events and add XCR0 event
Date: Thu, 28 May 2015 13:56:21 +0300 [thread overview]
Message-ID: <5566F455.40301@bitdefender.com> (raw)
In-Reply-To: <5566F079020000780007E699@mail.emea.novell.com>
On 05/28/2015 11:39 AM, Jan Beulich wrote:
>>>> On 28.05.15 at 07:33, <rcojocaru@bitdefender.com> wrote:
>> Changes since V6:
>> - Removed "Reviewed-by: Tim Deegan <tim@xen.org>", as the patch
>> went beyond cosmetic-only changes.
>> - Parenthesized hvm_event_cr in event.c, to prevent expansion of
>> the macro with the same name if event.h gets #included.
>
> I'm sorry, but I specifically said that you need to include the header
> declaring the function (and macro) in the file defining it, but ...
>
>> --- a/xen/arch/x86/hvm/event.c
>> +++ b/xen/arch/x86/hvm/event.c
>> @@ -21,6 +21,7 @@
>>
>> #include <xen/vm_event.h>
>> #include <xen/paging.h>
>> +#include <asm/monitor.h>
>> #include <public/vm_event.h>
>>
>> static void hvm_event_fill_regs(vm_event_request_t *req)
>
> ... you didn't (and you also didn't in a prereq patch, which would have
> been the alternative).
I see, sorry for the misunderstanding - I read your comment to mean that
in case the header gets included at a later time there might be
problems, which now won't happen. I will re-submit with the proper
header included.
Thanks,
Razvan
next prev parent reply other threads:[~2015-05-28 10:56 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 [this message]
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
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=5566F455.40301@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=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.