Re: [PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-28 Thread Baoquan He
On 07/27/17 at 05:57pm, Joerg Roedel wrote: > On Fri, Jul 21, 2017 at 04:59:09PM +0800, Baoquan He wrote: > > When iommu is pre_enabled in kdump kernel, if a device is set up with > > guest translations (DTE.GV=1), then don't copy GCR3 table root pointer > > but move the device over to an empty

Re: [PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-28 Thread Baoquan He
On 07/27/17 at 05:57pm, Joerg Roedel wrote: > On Fri, Jul 21, 2017 at 04:59:09PM +0800, Baoquan He wrote: > > When iommu is pre_enabled in kdump kernel, if a device is set up with > > guest translations (DTE.GV=1), then don't copy GCR3 table root pointer > > but move the device over to an empty

Re: [PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-27 Thread Joerg Roedel
On Fri, Jul 21, 2017 at 04:59:09PM +0800, Baoquan He wrote: > When iommu is pre_enabled in kdump kernel, if a device is set up with > guest translations (DTE.GV=1), then don't copy GCR3 table root pointer > but move the device over to an empty guest-cr3 table and handle the > faults in the PPR log

Re: [PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-27 Thread Joerg Roedel
On Fri, Jul 21, 2017 at 04:59:09PM +0800, Baoquan He wrote: > When iommu is pre_enabled in kdump kernel, if a device is set up with > guest translations (DTE.GV=1), then don't copy GCR3 table root pointer > but move the device over to an empty guest-cr3 table and handle the > faults in the PPR log

Re: [PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-23 Thread Baoquan He
On 07/24/17 at 06:33am, kbuild test robot wrote: > Hi Baoquan, > > [auto build test WARNING on iommu/next] > [also build test WARNING on v4.13-rc1] > [cannot apply to next-20170721] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url:

Re: [PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-23 Thread Baoquan He
On 07/24/17 at 06:33am, kbuild test robot wrote: > Hi Baoquan, > > [auto build test WARNING on iommu/next] > [also build test WARNING on v4.13-rc1] > [cannot apply to next-20170721] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url:

Re: [PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-23 Thread kbuild test robot
Hi Baoquan, [auto build test WARNING on iommu/next] [also build test WARNING on v4.13-rc1] [cannot apply to next-20170721] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-23 Thread kbuild test robot
Hi Baoquan, [auto build test WARNING on iommu/next] [also build test WARNING on v4.13-rc1] [cannot apply to next-20170721] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-21 Thread Baoquan He
When iommu is pre_enabled in kdump kernel, if a device is set up with guest translations (DTE.GV=1), then don't copy GCR3 table root pointer but move the device over to an empty guest-cr3 table and handle the faults in the PPR log (which answer them with INVALID). After all these PPR faults are

[PATCH v8 11/13] iommu/amd: Don't copy GCR3 table root pointer

2017-07-21 Thread Baoquan He
When iommu is pre_enabled in kdump kernel, if a device is set up with guest translations (DTE.GV=1), then don't copy GCR3 table root pointer but move the device over to an empty guest-cr3 table and handle the faults in the PPR log (which answer them with INVALID). After all these PPR faults are