From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
Shuang Qiu <shuang.qiu@intel.com>,
SongtaoX Liu <songtaox.liu@intel.com>,
Xiantao Zhang <xiantao.zhang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: use tasklet to handle init/sipi?
Date: Thu, 28 Mar 2013 20:02:29 +0000 [thread overview]
Message-ID: <CD7A5255.4EDB4%keir.xen@gmail.com> (raw)
In-Reply-To: <51546FFF02000078000C95C2@nat28.tlf.novell.com>
On 28/03/2013 15:29, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> On 28.03.13 at 12:48, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 28/03/2013 06:39, "Qiu, Shuang" <shuang.qiu@intel.com> wrote:
>>> We've patched the enclosed file on xen-unstable and tested on qemu.git and
>>> qemu-upstream-unstable.git as backends.
>>> In both cases, your patch works.
>>
>> Thanks for the testing! I have now committed my patch.
>
> Question now is - do we want this on the stable trees (once it
> passed the push gate of course), despite APIC virtualization
> (which triggered this) isn't in anything pre-4.3?
There are possibly other ways in which an INIT or SIPI could be
broadcast/multicast and not be properly handled -- hvm_x2apic_msr_write()?
vlapic_ipi() via the Viridian MSRs?
I think it's fairly theoretical risk though!
Overall I would be inclined not to backport.
-- Keir
> Jan
>
prev parent reply other threads:[~2013-03-28 20:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 5:31 use tasklet to handle init/sipi? Zhang, Yang Z
2013-03-25 6:29 ` Keir Fraser
2013-03-25 6:55 ` Zhang, Yang Z
2013-03-25 8:05 ` Keir Fraser
2013-03-25 12:16 ` Zhang, Yang Z
2013-03-25 12:38 ` Jan Beulich
2013-03-25 12:39 ` Keir Fraser
2013-03-26 3:15 ` Zhang, Yang Z
2013-03-26 6:07 ` Keir Fraser
2013-03-26 6:14 ` Zhang, Yang Z
2013-03-26 7:00 ` Keir Fraser
2013-03-26 7:11 ` Keir Fraser
2013-03-26 7:17 ` Zhang, Yang Z
2013-03-26 7:38 ` Keir Fraser
2013-03-26 7:41 ` Zhang, Yang Z
2013-03-26 7:55 ` Keir Fraser
2013-03-26 8:02 ` Keir Fraser
2013-03-28 1:18 ` Zhang, Yang Z
2013-03-28 6:39 ` Qiu, Shuang
2013-03-28 11:48 ` Keir Fraser
2013-03-28 15:29 ` Jan Beulich
2013-03-28 20:02 ` Keir Fraser [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=CD7A5255.4EDB4%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=shuang.qiu@intel.com \
--cc=songtaox.liu@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.