From: Keir Fraser <keir.xen@gmail.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Yang Zhang <yang.z.zhang@intel.com>,
Jan Beulich <JBeulich@suse.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 0/5] Add posted interrupt supporting
Date: Wed, 17 Apr 2013 17:54:29 +0100 [thread overview]
Message-ID: <CD949255.21DF4%keir.xen@gmail.com> (raw)
In-Reply-To: <CAFLBxZao=A1Yu-BNnBnXqbaVaTQSHSRboxFoMEJBSc+JZPCZ5w@mail.gmail.com>
On 17/04/2013 13:53, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:
> On Wed, Apr 17, 2013 at 8:04 AM, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 17/04/2013 07:50, "Yang Zhang" <yang.z.zhang@intel.com> wrote:
>>
>>> From: Yang Zhang <yang.z.zhang@Intel.com>
>>
>> The whole series:
>>
>> Acked-by: Keir Fraser <keir@xen.org>
>
> Keir / Yang, any comments on risks to the release?
>
> Yang, what kinds of testing are you guys going to be doing of this
> between now and the 4.3 release?
>
> From a feature / risk of slip perspective, I think this is probably
> good. The key thing I think is making sure that if there is a bug, it
> will be caught before the release. I suspect that a lot of people
> won't have hardware to test this, so it will be up to Intel to make
> sure the code has "gone through its paces" and is ready for public
> consumption in 2 months' time.
Personally I think it should go in, if Intel can assure they have done
decent testing internally (and will continue to do so).
-- Keir
> -George
next prev parent reply other threads:[~2013-04-17 16:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 6:50 [PATCH v2 0/5] Add posted interrupt supporting Yang Zhang
2013-04-17 6:50 ` [PATCH v2 1/5] VMX: Detect posted interrupt capability Yang Zhang
2013-04-17 6:50 ` [PATCH v2 2/5] VMX: Turn on posted interrupt bit in vmcs Yang Zhang
2013-04-17 9:02 ` Jan Beulich
2013-04-17 12:21 ` Zhang, Yang Z
2013-04-17 6:51 ` [PATCH v2 3/5] VMX: Add posted interrupt supporting Yang Zhang
2013-04-17 9:14 ` Jan Beulich
2013-04-17 12:40 ` Zhang, Yang Z
2013-04-17 13:15 ` Jan Beulich
2013-04-17 13:19 ` Zhang, Yang Z
2013-04-17 6:51 ` [PATCH v2 4/5] Call vlapic_set_irq() to delivery virtual interrupt Yang Zhang
2013-04-17 6:51 ` [PATCH v2 5/5] VMX: Use posted interrupt to deliver virutal interrupt Yang Zhang
2013-04-17 9:17 ` Jan Beulich
2013-04-17 12:32 ` Zhang, Yang Z
2013-04-17 7:04 ` [PATCH v2 0/5] Add posted interrupt supporting Keir Fraser
2013-04-17 12:53 ` George Dunlap
2013-04-17 16:54 ` Keir Fraser [this message]
2013-04-18 0:19 ` Zhang, Yang Z
2013-04-18 8:43 ` George Dunlap
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=CD949255.21DF4%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.zhang@intel.com \
--cc=yang.z.zhang@intel.com \
/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.