From: Julien Grall <julien.grall@arm.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"tamas@tklengyel.com" <tamas@tklengyel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH V5] x86/vm_event: Added support for VM_EVENT_REASON_INTERRUPT
Date: Tue, 13 Dec 2016 12:53:18 +0000 [thread overview]
Message-ID: <29a29e02-6679-532b-594d-df0bb550ecdd@arm.com> (raw)
In-Reply-To: <5a4197b4-f475-2a7c-1e7f-b37390031959@bitdefender.com>
Hi Razvan,
On 13/12/16 09:14, Razvan Cojocaru wrote:
> On 12/13/2016 11:09 AM, Jan Beulich wrote:
>>>>> On 13.12.16 at 09:50, <rcojocaru@bitdefender.com> wrote:
>>> On 11/17/2016 07:11 AM, Tian, Kevin wrote:
>>>>> From: Razvan Cojocaru [mailto:rcojocaru@bitdefender.com]
>>>>> Sent: Wednesday, November 16, 2016 3:49 PM
>>>>>
>>>>> On 11/16/2016 09:22 AM, Tian, Kevin wrote:
>>>>>> Looks not working with APICv virtual interrupt delivery...
>>>>>
>>>>> It's only meant to work with "regular" injections (we'd like to be able
>>>>> to tell if xc_hvm_inject_trap() can succeed). APICv support could be a
>>>>> later patch, if desirable (AFAICT, the two types shouldn't collide, i.e.
>>>>> impede trap delivery as done by the xc_hvm_inject_trap() hypercall).
>>>>>
>>>>>
>>>>
>>>> OK then. Acked-by: Kevin Tian <kevin.tian@intel.com>
>>>
>>> AFAIK this has been acked by everyone a while back,
>>
>> Has it? I've meant to apply it the other day, but couldn't find
>> any ARM or AMD SVM maintainer acks.
>
> Oh I see. At one point Julien came into the conversation but it was just
> a friendly discussion about spelling somewhere - I've misremembered that
> as an ack, I now see.
Thank you for reminding me:
Acked-by: Julien Grall <julien.grall@arm.com>
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-13 12:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 16:09 [PATCH V5] x86/vm_event: Added support for VM_EVENT_REASON_INTERRUPT Razvan Cojocaru
2016-11-11 16:31 ` Jan Beulich
2016-11-16 7:22 ` Tian, Kevin
2016-11-16 7:48 ` Razvan Cojocaru
2016-11-17 5:11 ` Tian, Kevin
2016-12-13 8:50 ` Razvan Cojocaru
2016-12-13 9:09 ` Jan Beulich
2016-12-13 9:14 ` Razvan Cojocaru
2016-12-13 12:53 ` Julien Grall [this message]
2016-12-13 10:34 ` Suravee Suthikulpanit
2016-12-13 13:18 ` Jan Beulich
2016-12-13 13:42 ` Razvan Cojocaru
2016-12-13 14:17 ` Razvan Cojocaru
2016-12-13 14:53 ` build issue on staging (was Re: [PATCH V5] x86/vm_event: Added support for VM_EVENT_REASON_INTERRUPT) Jan Beulich
2016-12-13 17:15 ` Roger Pau Monne
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=29a29e02-6679-532b-594d-df0bb550ecdd@arm.com \
--to=julien.grall@arm.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=sstabellini@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=tamas@tklengyel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).