From: Wei Liu <wei.liu2@citrix.com>
To: "Wu, Feng" <feng.wu@intel.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Hao, Xudong" <xudong.hao@intel.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [BUG] Xen panic with VT-d PI
Date: Thu, 26 May 2016 11:26:36 +0100 [thread overview]
Message-ID: <20160526102636.GU22076@citrix.com> (raw)
In-Reply-To: <E959C4978C3B6342920538CF579893F0196F0225@SHSMSX103.ccr.corp.intel.com>
On Thu, May 26, 2016 at 01:56:28AM +0000, Wu, Feng wrote:
> The patch fixing this issue has already been sent to upstream.
>
> " [PATCH 0/3] VMX: Properly handle pi descriptor and per-cpu blocking list "
>
> v2 will be sent out soon.
>
I just went through that thread. There are some open questions. Also Jan
requested that you explore other possible options.
My current plan is to not block the release for this -- we're very close
to the anticipated release date, and posted-interrupt is either
technical preview or experimental, so bugs there are expected.
This issue will be listed as a known issue for PI. And you can continue
to develop a fix for it. Your fix will be integrated with next version
of Xen. Then you can request for backport to 4.7 if you want to.
What do you think about this plan?
Wei.
> Thanks,
> Feng
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-26 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 1:44 [BUG] Xen panic with VT-d PI Hao, Xudong
2016-05-26 1:56 ` Wu, Feng
2016-05-26 10:26 ` Wei Liu [this message]
2016-05-26 13:03 ` Wu, Feng
2016-05-26 13:46 ` Wei Liu
2016-05-26 16:10 ` Dario Faggioli
2016-05-31 10:03 ` Wu, Feng
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=20160526102636.GU22076@citrix.com \
--to=wei.liu2@citrix.com \
--cc=feng.wu@intel.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xudong.hao@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 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).