From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Tamas K Lengyel <tamas.lengyel@zentific.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>
Subject: Re: [PATCH V2] xen/vm_event: Clean up control-register-write vm_events
Date: Thu, 14 May 2015 21:06:44 +0300 [thread overview]
Message-ID: <5554E434.2070400@bitdefender.com> (raw)
In-Reply-To: <CAErYnsg=3iPP_bVMq-AtR+=QhMwKHcNEVah7QUJwA7P7pqtysA@mail.gmail.com>
On 05/14/2015 08:31 PM, Tamas K Lengyel wrote:
> On Thu, May 14, 2015 at 7:11 PM, Razvan Cojocaru
> <rcojocaru@bitdefender.com> wrote:
>> On 05/14/2015 07:55 PM, Tamas K Lengyel wrote:
>>>> diff --git a/xen/include/asm-x86/domain.h b/xen/include/asm-x86/domain.h
>>>> index 45b5283..1dd49dd 100644
>>>> --- a/xen/include/asm-x86/domain.h
>>>> +++ b/xen/include/asm-x86/domain.h
>>>> @@ -341,19 +341,13 @@ struct arch_domain
>>>>
>>>> /* Monitor options */
>>>> struct {
>>>> - uint16_t mov_to_cr0_enabled : 1;
>>>> - uint16_t mov_to_cr0_sync : 1;
>>>> - uint16_t mov_to_cr0_onchangeonly : 1;
>>>> - uint16_t mov_to_cr3_enabled : 1;
>>>> - uint16_t mov_to_cr3_sync : 1;
>>>> - uint16_t mov_to_cr3_onchangeonly : 1;
>>>> - uint16_t mov_to_cr4_enabled : 1;
>>>> - uint16_t mov_to_cr4_sync : 1;
>>>> - uint16_t mov_to_cr4_onchangeonly : 1;
>>>> - uint16_t mov_to_msr_enabled : 1;
>>>> - uint16_t mov_to_msr_extended : 1;
>>>> - uint16_t singlestep_enabled : 1;
>>>> - uint16_t software_breakpoint_enabled : 1;
>>>> + uint32_t write_ctrlreg_enabled : 8;
>>>> + uint32_t write_ctrlreg_sync : 8;
>>>> + uint32_t write_ctrlreg_onchangeonly : 8;
>>>
>>> Any particular reason why you have these bitmaps 8-bits wide? There
>>> are only 4 events defined at the moment that would use these.
>>
>> ARM control registers have been mentioned, so I thought I would leave
>> some space for a few more events. Other than that, they don't _need_ to
>> be 8-bits wide. If compactness matters more I'll change them to 4.
>>
>>
>> Thanks,
>> Razvan
>
> IMHO it's better to widen the field when there is an actual need for
> it. For now I think 4 would be appropriate.
Fair enough. I'll change it to 4 and we'll just have to be careful when
patches touching these events come in.
Thanks,
Razvan
prev parent reply other threads:[~2015-05-14 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 8:40 [PATCH V2] xen/vm_event: Clean up control-register-write vm_events Razvan Cojocaru
2015-05-14 8:57 ` Tim Deegan
2015-05-14 16:55 ` Tamas K Lengyel
2015-05-14 17:11 ` Razvan Cojocaru
2015-05-14 17:31 ` Tamas K Lengyel
2015-05-14 18:06 ` 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=5554E434.2070400@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.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=stefano.stabellini@eu.citrix.com \
--cc=tamas.lengyel@zentific.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.