From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
eddie.dong@intel.com, xen-devel@lists.xen.org,
jun.nakajima@intel.com, ian.jackson@eu.citrix.com
Subject: Re: [PATCH RFC V4 4/5] xen, libxc: Request page fault injection via libxc
Date: Tue, 05 Aug 2014 11:48:43 +0300 [thread overview]
Message-ID: <53E09A6B.4080500@bitdefender.com> (raw)
In-Reply-To: <53E0B46A0200007800029561@mail.emea.novell.com>
On 08/05/2014 11:39 AM, Jan Beulich wrote:
>>>> On 05.08.14 at 10:09, <rcojocaru@bitdefender.com> wrote:
>> On 08/04/2014 06:20 PM, Jan Beulich wrote:
>>>>>> On 04.08.14 at 17:00, <rcojocaru@bitdefender.com> wrote:
>>>> On 08/04/2014 05:26 PM, Jan Beulich wrote:
>>>>>>>> On 04.08.14 at 13:30, <rcojocaru@bitdefender.com> wrote:
>>>>>> + __vmread(VM_ENTRY_INTR_INFO, &ev);
>>>>>> +
>>>>>> + if ( (ev & INTR_INFO_VALID_MASK) &&
>>>>>> + hvm_event_needs_reinjection((ev >> 8) & 7, ev & 0xff) )
>>>>>
>>>>> Are there no manifest constants for all these plain numbers?
>>>>
>>>> If there are, vmx_vmcs_save() in vmx.c (line 416) doesn't use them. I've
>>>> copied that part verbatim.
>>>
>>> And that's precisely the problem: As long as there's exactly one use
>>> site, the need for manifest constants is questionable (i.e. largely
>>> cosmetic). As soon as there are multiple places, connecting them
>>> together is largely impossible without naming these numbers - only
>>> that way you have a reasonable chance to find the clone of the
>>> original should the original be found to need tweaking.
>>
>> I'll gladly add #defines for those magic constants, but could you please
>> recommend names for them and a header (or at least, category of headers)
>> to put them in, in the interest of minimizing the number of RFC versions
>> for this series?
>
> Did you even make an attempt to locate a proper place, or
> to check whether such constants already exist? Simply looking
> for INTR_INFO_VALID_MASK would have turned up
>
> #define INTR_INFO_VECTOR_MASK 0xff /* 7:0 */
> #define INTR_INFO_INTR_TYPE_MASK 0x700 /* 10:8 */
>
> i.e. all you need is there, you just need to make use of them
> (and please also - perhaps in an initial cleanup patch - for the
> original you cloned from). And just to avoid a needless further
> intermediate round: While there is no #define for the shift count
> used, you also don't need one if you make use of MASK_EXTR().
I did, obviously, but you can only turn up so much when grepping for "7"
in a large, mostly undocumented codebase. Thanks for your quick answer,
I'll use those and modify the original code as well.
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2014-08-05 8:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 11:30 [PATCH RFC V4 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-08-04 11:30 ` [PATCH RFC V4 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-08-04 14:16 ` Jan Beulich
2014-08-04 14:43 ` Razvan Cojocaru
2014-08-04 11:30 ` [PATCH RFC V4 3/5] xen: Force-enable relevant MSR events; optimize the number of sent MSR events Razvan Cojocaru
2014-08-04 11:30 ` [PATCH RFC V4 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-08-04 11:51 ` Ian Campbell
2014-08-04 14:26 ` Jan Beulich
2014-08-04 15:00 ` Razvan Cojocaru
2014-08-04 15:20 ` Jan Beulich
2014-08-05 8:09 ` Razvan Cojocaru
2014-08-05 8:39 ` Jan Beulich
2014-08-05 8:48 ` Razvan Cojocaru [this message]
2014-08-05 9:59 ` Razvan Cojocaru
2014-08-04 15:11 ` Razvan Cojocaru
2014-08-04 15:21 ` Jan Beulich
[not found] ` <53DFA537.70105@bitdefender.com>
2014-08-04 15:23 ` Razvan Cojocaru
2014-08-04 11:30 ` [PATCH RFC V4 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-08-04 14:33 ` Jan Beulich
2014-08-06 14:00 ` Razvan Cojocaru
2014-08-04 14:09 ` [PATCH RFC V4 1/5] xen: Emulate with no writes Jan Beulich
2014-08-04 14:25 ` Razvan Cojocaru
2014-08-04 14:42 ` Jan Beulich
2014-08-05 15:16 ` Razvan Cojocaru
2014-08-05 15:27 ` Razvan Cojocaru
2014-08-05 15:43 ` Jan Beulich
2014-08-06 8:42 ` Razvan Cojocaru
2014-08-06 8:50 ` Jan Beulich
2014-08-28 11:53 ` Tim Deegan
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=53E09A6B.4080500@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=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.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.