From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian.Jackson@eu.citrix.com
Cc: "Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>,
"Wang, Yong Y" <yong.y.wang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"Wang, Wei W" <wei.w.wang@intel.com>,
"JBeulich@suse.com" <JBeulich@suse.com>,
"Hu, Robert" <robert.hu@intel.com>
Subject: Re: Is: Fixes for xl pci-attach for Xen 4.5 confirmed to fix by Intel.Was:Re: [TestDay] VMX test report for Xen 4.5.0-rc1
Date: Mon, 05 Jan 2015 10:54:02 -0500 [thread overview]
Message-ID: <54AAB39A.3070204@oracle.com> (raw)
In-Reply-To: <20150105152758.GA11661@l.oracle.com>
On 01/05/2015 10:27 AM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 05, 2015 at 12:48:16PM +0000, George Dunlap wrote:
>> On Thu, Dec 18, 2014 at 4:55 AM, Hu, Robert <robert.hu@intel.com> wrote:
>>>> For this specific problem though I think
>>>>
>>>> http://lists.xen.org/archives/html/xen-devel/2014-11/msg01342.html
>>> We verified this on RC4, it works.
>>> Will your patch get in Xen 4.5 release? Otherwise hotplug vt-d device with a running guest will not work properly.
>> It looks like IanJ's patch (referenced above) has not been applied.
>> It's clearly a bug fix, so it probably should be...
> <nods>
>
> Ian, were you waiting on Boris to repost the patches?
I wasn't planning on resending them. They (or, more likely, it) need to
be reworked to use async notifications and I haven't done this.
Ian's fix is independent of what I need to do.
-boris
next prev parent reply other threads:[~2015-01-05 15:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 6:58 [TestDay] VMX test report for Xen 4.5.0-rc1 Hu, Robert
2014-11-12 9:49 ` Jan Beulich
2014-11-12 10:53 ` Hu, Robert
2014-11-12 11:05 ` Jan Beulich
2014-11-12 13:23 ` Ian Campbell
2014-11-12 9:59 ` Fabio Fantoni
2014-11-13 2:40 ` Hu, Robert
2014-11-14 7:50 ` Hu, Robert
2014-11-14 9:42 ` Ian Campbell
2014-11-14 9:59 ` Wei Liu
2014-11-14 10:14 ` Hu, Robert
2014-11-14 10:38 ` Fabio Fantoni
2014-11-14 11:04 ` Wei Liu
2014-11-14 11:28 ` Ian Campbell
2014-11-19 1:41 ` Hu, Robert
2014-11-26 9:15 ` Robert Hu
2014-11-12 11:07 ` Wei Liu
2014-11-13 1:22 ` Hu, Robert
2014-11-13 9:39 ` Ian Campbell
2014-11-13 9:54 ` Wei Liu
2014-11-12 12:38 ` Boris Ostrovsky
2014-11-24 7:43 ` Hu, Robert
2014-11-24 14:54 ` Is: Fixes for xl pci-attach for Xen 4.5 confirmed to fix by Intel.Was:Re: " Konrad Rzeszutek Wilk
2014-11-24 15:13 ` Boris Ostrovsky
2014-12-18 4:55 ` Hu, Robert
2015-01-05 12:48 ` George Dunlap
2015-01-05 15:27 ` Konrad Rzeszutek Wilk
2015-01-05 15:54 ` Boris Ostrovsky [this message]
2015-01-05 15:56 ` Ian Jackson
2015-01-05 16:34 ` [PATCH for-4.5] libxl: Fix if{} nesting in do_pci_remove Ian Jackson
2015-01-05 16:38 ` Ian Campbell
2015-01-05 16:39 ` Konrad Rzeszutek Wilk
2015-01-05 16:46 ` [PATCH for-4.5] libxl: Fix if{} nesting in do_pci_remove [and 1 more messages] Ian Jackson
2014-11-12 16:06 ` [TestDay] VMX test report for Xen 4.5.0-rc1 Konrad Rzeszutek Wilk
2014-11-12 22:29 ` Konrad Rzeszutek Wilk
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=54AAB39A.3070204@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=robert.hu@intel.com \
--cc=wei.w.wang@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=yong.y.wang@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.