[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] backport requests for 4.x-testing

  • To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Wed, 07 Mar 2012 09:18:40 +0000
  • Delivery-date: Wed, 07 Mar 2012 09:19:21 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Acz8Q0i5kMtfAANbqEOZdPsBt0Dygg==
  • Thread-topic: [Xen-devel] backport requests for 4.x-testing

All applied, except:

On 06/03/2012 10:13, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> 24535 (x86/vMSI: miscellaneous fixes)

Applied to 4.1, but does not easily apply to 4.0. You'll need to provide a
patch against 4.0-testing.

> 24888 (passthrough: release assigned PCI devices earlier during domain
> shutdown)

This one applied, but I see a bug in the original xen-unstable patch. In
XEN_DOMCTL_assign_device you break on d->is_dying, but do not put_domain(d).
You should go fix that in xen-unstable.

> 24156 (x86/IRQ: prevent vector sharing within IO-APICs, requiring
>             23900 [kzalloc])

Doesn't easily apply. Need a patch against 4.1-testing.

> 24527 (iommu: Move IOMMU faults handling into softirq for AMD-Vi)

Depends on other xen-unstable patches which refactor AMD IOMMU event
handling. You'd need to provide a manual backport of this for 4.1-testing.

> 24690 (x86: avoid deadlock after a PCI SERR NMI)

There is no PCI SERR NMI handling in 4.0-testing. It would also need

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.