Hi Baoquan,
On Thu, Jul 20, 2017 at 09:17:43PM +0800, Baoquan He wrote:
> I have rebased the amd iommu fix patches of kdump kernel on the latest
> upstream kernel, can I send them to you to have a look? Or just send to
> iommu and lkml mailing list?
Please send them to me and Cc iommu and lkml.
Hi Baoquan,
On Thu, Jul 20, 2017 at 09:17:43PM +0800, Baoquan He wrote:
> I have rebased the amd iommu fix patches of kdump kernel on the latest
> upstream kernel, can I send them to you to have a look? Or just send to
> iommu and lkml mailing list?
Please send them to me and Cc iommu and lkml.
Hi Joerg,
On 06/26/17 at 12:07pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Fri, Jun 23, 2017 at 07:43:10PM +0800, Baoquan He wrote:
> > Do you think whether it's necessary to continue my kdump fix of amd iommu
> > patchset? Seems my last post was in Jan this year. I know you are very
> > busy on
Hi Joerg,
On 06/26/17 at 12:07pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Fri, Jun 23, 2017 at 07:43:10PM +0800, Baoquan He wrote:
> > Do you think whether it's necessary to continue my kdump fix of amd iommu
> > patchset? Seems my last post was in Jan this year. I know you are very
> > busy on
On 06/26/17 at 12:07pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Fri, Jun 23, 2017 at 07:43:10PM +0800, Baoquan He wrote:
> > Do you think whether it's necessary to continue my kdump fix of amd iommu
> > patchset? Seems my last post was in Jan this year. I know you are very
> > busy on fixing
On 06/26/17 at 12:07pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Fri, Jun 23, 2017 at 07:43:10PM +0800, Baoquan He wrote:
> > Do you think whether it's necessary to continue my kdump fix of amd iommu
> > patchset? Seems my last post was in Jan this year. I know you are very
> > busy on fixing
Hi Baoquan,
On Fri, Jun 23, 2017 at 07:43:10PM +0800, Baoquan He wrote:
> Do you think whether it's necessary to continue my kdump fix of amd iommu
> patchset? Seems my last post was in Jan this year. I know you are very
> busy on fixing bugs and reviewing tons of patches. Without your
> guidance
Hi Baoquan,
On Fri, Jun 23, 2017 at 07:43:10PM +0800, Baoquan He wrote:
> Do you think whether it's necessary to continue my kdump fix of amd iommu
> patchset? Seems my last post was in Jan this year. I know you are very
> busy on fixing bugs and reviewing tons of patches. Without your
> guidance
Hi Joerg,
On 06/23/17 at 04:57pm, Baoquan He wrote:
> Hi dear Joerg,
>
> On 06/16/17 at 10:15am, Joerg Roedel wrote:
> > From: Joerg Roedel
> >
> > When booting into a kdump kernel, suppress IO_PAGE_FAULTs by
> > default for all devices. But allow the faults again when a
> >
Hi Joerg,
On 06/23/17 at 04:57pm, Baoquan He wrote:
> Hi dear Joerg,
>
> On 06/16/17 at 10:15am, Joerg Roedel wrote:
> > From: Joerg Roedel
> >
> > When booting into a kdump kernel, suppress IO_PAGE_FAULTs by
> > default for all devices. But allow the faults again when a
> > domain is assigned
Hi dear Joerg,
On 06/16/17 at 10:15am, Joerg Roedel wrote:
> From: Joerg Roedel
>
> When booting into a kdump kernel, suppress IO_PAGE_FAULTs by
> default for all devices. But allow the faults again when a
> domain is assigned to a device.
I have two bugs at hand reported by
Hi dear Joerg,
On 06/16/17 at 10:15am, Joerg Roedel wrote:
> From: Joerg Roedel
>
> When booting into a kdump kernel, suppress IO_PAGE_FAULTs by
> default for all devices. But allow the faults again when a
> domain is assigned to a device.
I have two bugs at hand reported by customer, saying
From: Joerg Roedel
When booting into a kdump kernel, suppress IO_PAGE_FAULTs by
default for all devices. But allow the faults again when a
domain is assigned to a device.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 3 ++-
From: Joerg Roedel
When booting into a kdump kernel, suppress IO_PAGE_FAULTs by
default for all devices. But allow the faults again when a
domain is assigned to a device.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 3 ++-
drivers/iommu/amd_iommu_init.c | 9 +
14 matches
Mail list logo