From: "Jan Beulich" <JBeulich@suse.com>
To: Julien Grall <julien.grall@arm.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Xudong Hao <xudong.hao@intel.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>
Cc: Lars Kurth <lars.kurth@citrix.com>, Quan Xu <quan.xu0@gmail.com>,
Wei Liu <wei.liu2@citrix.com>,
PengtaoX Zhang <pengtaox.zhang@intel.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Luwei Kang <luwei.kang@intel.com>
Subject: Re: [BUG] win2008 guest cannot get ip through sriov
Date: Fri, 27 Oct 2017 02:37:36 -0600 [thread overview]
Message-ID: <59F30C70020000780018A881@prv-mh.provo.novell.com> (raw)
In-Reply-To: <B8376D2DEA074F45BA033984477C453E3B838AF3@shsmsx102.ccr.corp.intel.com>
>>> On 27.10.17 at 09:27, <xudong.hao@intel.com> wrote:
> This bug exist much long time, there are many discussion last year but not a
> solution then. I call out it now because there is a fix in qemu upstream:
> commit a8036336609d2e184fc3543a4c439c0ba7d7f3a2
> Author: Roger Pau Monne <roger.pau@citrix.com>
> Date: Thu Aug 24 16:07:03 2017 +0100
>
> xen/pt: allow QEMU to request MSI unmasking at bind time
>
> The fix is not in qemu-xen tree yet, when will qemu-xen sync this fix? Is it
> possible to catch Xen 4.10's qemu-xen?
Well, the question shouldn't have been directed at Quan or me -
at this point it would need to be sorted out between the qemu
maintainers (Stefano and Anthony) and the release manager
(Julien).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-27 8:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 9:04 [BUG] win2008 guest cannot get ip through sriov Zhang, PengtaoX
2016-05-27 10:39 ` Wei Liu
2016-05-27 12:16 ` Jan Beulich
2016-05-27 13:34 ` Wei Liu
2016-05-27 14:06 ` Jan Beulich
2016-06-02 7:31 ` Xu, Quan
2016-06-02 9:03 ` Jan Beulich
2016-06-02 10:22 ` Wei Liu
2016-06-02 10:38 ` Jan Beulich
2016-06-02 11:03 ` Wei Liu
2016-06-02 12:08 ` Jan Beulich
2016-06-02 13:05 ` Xu, Quan
2016-06-02 13:30 ` Jan Beulich
2016-06-02 14:02 ` Xu, Quan
2016-06-07 5:52 ` Xu, Quan
2016-06-07 6:07 ` Xu, Quan
2016-06-07 7:43 ` Jan Beulich
2016-06-07 7:49 ` Jan Beulich
2016-06-07 8:03 ` Xu, Quan
2016-06-07 8:08 ` Jan Beulich
2016-06-07 8:19 ` Xu, Quan
2016-06-08 9:12 ` Xu, Quan
2016-06-08 9:25 ` Jan Beulich
2017-10-27 7:27 ` Hao, Xudong
2017-10-27 8:37 ` Jan Beulich [this message]
2017-10-27 8:58 ` Hao, Xudong
2017-10-27 10:41 ` Julien Grall
2017-10-27 20:16 ` Stefano Stabellini
2017-11-02 13:49 ` Julien Grall
2017-11-03 1:10 ` Hao, Xudong
2017-11-03 11:23 ` Roger Pau Monné
2017-11-06 1:04 ` Hao, Xudong
2017-11-07 9:33 ` Roger Pau Monné
2017-11-09 0:22 ` Hao, Xudong
2017-11-09 9:27 ` Roger Pau Monné
2017-11-09 14:36 ` Julien Grall
2017-11-09 14:37 ` Julien Grall
2017-11-27 3:20 ` Hao, Xudong
2017-11-27 10:39 ` Julien Grall
2017-11-06 1:07 ` Hao, Xudong
2017-11-08 12:13 ` Anthony PERARD
2017-11-08 12:17 ` Julien Grall
2017-10-30 1:04 ` Hao, Xudong
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=59F30C70020000780018A881@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=luwei.kang@intel.com \
--cc=pengtaox.zhang@intel.com \
--cc=quan.xu0@gmail.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.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).