Hi Jerry,
On Wed, Dec 17, 2014 at 02:37:47PM -0700, Jerry Hoemann wrote:
> Before applying this change on a 3.18-rc7 kernel layered on a
> RHEL 7.0 root disk, I was able to reproduce the memory
> leak that Alex reported when powering on/off a VM w/ a PCI
> device assigned to it.
>
> After
Hi Jerry,
On Wed, Dec 17, 2014 at 02:37:47PM -0700, Jerry Hoemann wrote:
Before applying this change on a 3.18-rc7 kernel layered on a
RHEL 7.0 root disk, I was able to reproduce the memory
leak that Alex reported when powering on/off a VM w/ a PCI
device assigned to it.
After applying
On Wed, Dec 17, 2014 at 11:43:36AM +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Since commit 1196c2f a domain is only destroyed in the
> notifier path if it is hot-unplugged. This caused a
> domain leakage in iommu_attach_device when a driver was
> unbound from the device and bound to
From: Joerg Roedel
Since commit 1196c2f a domain is only destroyed in the
notifier path if it is hot-unplugged. This caused a
domain leakage in iommu_attach_device when a driver was
unbound from the device and bound to VFIO. In this case the
device is attached to a new domain and unlinked from
From: Joerg Roedel jroe...@suse.de
Since commit 1196c2f a domain is only destroyed in the
notifier path if it is hot-unplugged. This caused a
domain leakage in iommu_attach_device when a driver was
unbound from the device and bound to VFIO. In this case the
device is attached to a new domain and
On Wed, Dec 17, 2014 at 11:43:36AM +0100, Joerg Roedel wrote:
From: Joerg Roedel jroe...@suse.de
Since commit 1196c2f a domain is only destroyed in the
notifier path if it is hot-unplugged. This caused a
domain leakage in iommu_attach_device when a driver was
unbound from the device and
6 matches
Mail list logo
