| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
 Re: [Xen-devel] [PATCH V7] xen/vm_event: Clean up control-register-write vm_events and add XCR0 event
 
To: Jan Beulich <JBeulich@xxxxxxxx>, Tamas Lengyel <tlengyel@xxxxxxxxxxx>From: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>Date: Fri, 29 May 2015 16:47:20 +0300Cc: tim@xxxxxxx, kevin.tian@xxxxxxxxx, wei.liu2@xxxxxxxxxx,	eddie.dong@xxxxxxxxx,	Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>,	andrew.cooper3@xxxxxxxxxx, ian.jackson@xxxxxxxxxxxxx,	xen-devel@xxxxxxxxxxxxx, Jun Nakajima <jun.nakajima@xxxxxxxxx>,	keir@xxxxxxx, Ian Campbell <ian.campbell@xxxxxxxxxx>Comment: DomainKeys? See http://domainkeys.sourceforge.net/Delivery-date: Fri, 29 May 2015 13:47:28 +0000Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com;	b=JC9f3502IhwJg2vl2q9S9fmrAn/cZAIPtbCzKtu4kh0O7Q12RRBiXAiqqhnDJEpPEbz4bbCTdN3gqxziXFz/W8YBVzRCut4mL3RVEbjQ4ZN+BsiJBSbIX8gVUf6i2o9OyIqjcLTAHudls1o+xponHZQ6yr+yN3v0PAqZVVAZUoc6Y/QFwdu0wBRuFBl2kNXKyxDPokuFXlpNDYG82tsPT+FS2kTcNDArqDLBAo9iA7M1tLqWTiJ92atVMCYuKJQRpo6PZjYIzSdoOf/hy+cqd1n7D2eRe8kKNdXvlJEv/xl87/gkzB+05Gn0f/JB4neTOR/9G/zfx5uInrwhUrKK1A==;	h=Received:Received:Received:Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-BitDefender-Scanner:X-BitDefender-Spam:X-BitDefender-SpamStamp:X-BitDefender-CF-Stamp;List-id: Xen developer discussion <xen-devel.lists.xen.org> 
 On 05/29/2015 12:12 PM, Jan Beulich wrote:
>>>> On 28.05.15 at 18:32, <rcojocaru@xxxxxxxxxxxxxxx> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
 
 |