On 07/27/17 at 05:58pm, Joerg Roedel wrote:
> On Fri, Jul 21, 2017 at 04:59:11PM +0800, Baoquan He wrote:
> > From: root
>
> You probaly need to reset the author on this one.
Oops, sorry. I made this patch on a testing machine. Will correct it.
Thanks a
On 07/27/17 at 05:58pm, Joerg Roedel wrote:
> On Fri, Jul 21, 2017 at 04:59:11PM +0800, Baoquan He wrote:
> > From: root
>
> You probaly need to reset the author on this one.
Oops, sorry. I made this patch on a testing machine. Will correct it.
Thanks a lot for all these comments and great
On Fri, Jul 21, 2017 at 04:59:11PM +0800, Baoquan He wrote:
> From: root
You probaly need to reset the author on this one.
>
> It's ok to disable iommu in normal kernel. While there's no need
> to disable it in kdump kernel after the on-flight dma issue
On Fri, Jul 21, 2017 at 04:59:11PM +0800, Baoquan He wrote:
> From: root
You probaly need to reset the author on this one.
>
> It's ok to disable iommu in normal kernel. While there's no need
> to disable it in kdump kernel after the on-flight dma issue has
> heen fixed.
>
> Signed-off-by:
From: root
It's ok to disable iommu in normal kernel. While there's no need
to disable it in kdump kernel after the on-flight dma issue has
heen fixed.
Signed-off-by: Baoquan He
---
drivers/iommu/amd_iommu_init.c | 3 ++-
1 file changed,
From: root
It's ok to disable iommu in normal kernel. While there's no need
to disable it in kdump kernel after the on-flight dma issue has
heen fixed.
Signed-off-by: Baoquan He
---
drivers/iommu/amd_iommu_init.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
6 matches
Mail list logo