From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, Ian Campbell <ian.campbell@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>,
stefano.stabellini@citrix.com,
Tamas Lengyel <tlengyel@novetta.com>
Subject: Re: [PATCH v2] x86/vm_event: toggle singlestep from vm_event response
Date: Tue, 7 Jul 2015 09:26:23 +0300 [thread overview]
Message-ID: <559B710F.6040909@bitdefender.com> (raw)
In-Reply-To: <559B8BB5020000780008D166@mail.emea.novell.com>
On 07/07/2015 09:20 AM, Jan Beulich wrote:
>>>> On 06.07.15 at 19:03, <rcojocaru@bitdefender.com> wrote:
>> I don't mind just having the comment for now, so for what it's worth I
>> stand by my ack.
>>
>> Having said that (and with the understading that it is beyond the scope
>> of this patch), a way to validate things like these is a good idea. I
>> wonder if, in a future patch, we could not have ./configure detect these
>> things and simply disable the relevant VM_EVENT_FLAG constants with
>> #if(n)defs, for example. That way, you wouldn't be able to compile code
>> that wouldn't work silently on platforms where that is the case.
>
> I don't follow: Are you saying this assuming that everyone would
> configure and build on the target system? I.e. are you leaving
> distros completely out of consideration?
I was, as also pointed out by Andrew. Tamas has, in the meantime,
submitted a patch doing this the right way (adding the ability to query
hypervisor capabilities).
Thanks,
Razvan
next prev parent reply other threads:[~2015-07-07 6:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 14:11 [PATCH v2] x86/vm_event: toggle singlestep from vm_event response Tamas K Lengyel
2015-06-30 14:18 ` Andrew Cooper
2015-06-30 14:40 ` Lengyel, Tamas
2015-07-06 15:26 ` Jan Beulich
2015-07-06 15:35 ` Lengyel, Tamas
2015-07-06 15:54 ` Jan Beulich
2015-07-06 16:26 ` Lengyel, Tamas
2015-07-06 17:03 ` Razvan Cojocaru
2015-07-06 17:08 ` Lengyel, Tamas
2015-07-06 17:17 ` Andrew Cooper
2015-07-06 17:29 ` Razvan Cojocaru
2015-07-06 17:36 ` Lengyel, Tamas
2015-07-06 17:45 ` Andrew Cooper
2015-07-06 17:44 ` Andrew Cooper
2015-07-07 6:20 ` Jan Beulich
2015-07-07 6:26 ` Razvan Cojocaru [this message]
2015-07-07 9:27 ` Jan Beulich
2015-07-07 11:56 ` Lengyel, Tamas
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=559B710F.6040909@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@citrix.com \
--cc=tlengyel@novetta.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.