Re: [PATCH v5 7/8] iommu/amd: Don't update domain info to dte entry at iommu init stage

2016-09-21 Thread Baoquan He
On 09/20/16 at 02:50pm, Joerg Roedel wrote: > On Thu, Sep 15, 2016 at 11:03:25PM +0800, Baoquan He wrote: > > AMD iommu creates protection domain and assign each device to it during > > iommu driver initialization stage. This happened just after system pci > > bus scanning stage, and much earlier

Re: [PATCH v5 5/8] iommu/amd: copy old trans table from old kernel

2016-09-21 Thread Baoquan He
On 09/20/16 at 02:40pm, Joerg Roedel wrote: > On Thu, Sep 15, 2016 at 11:03:23PM +0800, Baoquan He wrote: > > Here several things need be done: > > 1) If iommu is pre-enabled in a normal kernel, just disable it and print > >warning. > > 2) If failed to copy dev table of old kernel, continue to

Re: [PATCH v5 4/8] iommu/amd: Add function copy_dev_tables

2016-09-21 Thread Baoquan He
Hi Joerg, Thanks for your reviewing and great suggestion! On 09/20/16 at 01:58pm, Joerg Roedel wrote: > Hi Baoquan, > > On Thu, Sep 15, 2016 at 11:03:22PM +0800, Baoquan He wrote: > > +static int copy_dev_tables(void) > > +{ > > + u64 entry; > > + u32 lo, hi, devid; > > + phys_addr_t

Re: [PATCH v5 8/8] iommu/amd: Update domain into to dte entry during device driver init

2016-09-21 Thread Baoquan He
On 09/20/16 at 02:53pm, Joerg Roedel wrote: > On Thu, Sep 15, 2016 at 11:03:26PM +0800, Baoquan He wrote: > > All devices are supposed to reset themselves at device driver initialization > > stage. At this time if in kdump kernel those on-flight DMA will be stopped > > because of device reset.

Re: [PATCH v5 6/8] iommu/amd: Do not re-enable dev table entries in kdump

2016-09-21 Thread Baoquan He
On 09/20/16 at 02:42pm, Joerg Roedel wrote: > On Thu, Sep 15, 2016 at 11:03:24PM +0800, Baoquan He wrote: > > This enabling should have been done in normal kernel. It's unnecessary > > to enable it again in kdump kernel. > > > > And clean up the function comments of init_device_table_dma. > >

Re: [PATCH v5 7/8] iommu/amd: Don't update domain info to dte entry at iommu init stage

2016-09-21 Thread Baoquan He
On 09/21/16 at 06:26pm, Baoquan He wrote: > On 09/20/16 at 02:50pm, Joerg Roedel wrote: > > On Thu, Sep 15, 2016 at 11:03:25PM +0800, Baoquan He wrote: > > > AMD iommu creates protection domain and assign each device to it during > > > iommu driver initialization stage. This happened just after

[PATCH v6 2/3] arm64: Add arm64 kexec support

2016-09-21 Thread Geoff Levand
Add kexec reboot support for ARM64 platforms. Signed-off-by: Geoff Levand --- configure.ac| 3 + kexec/Makefile | 1 + kexec/arch/arm64/Makefile | 40 +++ kexec/arch/arm64/crashdump-arm64.c | 21

[PATCH v6 1/3] kexec: Add common device tree routines

2016-09-21 Thread Geoff Levand
Common device tree routines that can be shared between all arches that have device tree support. Signed-off-by: Geoff Levand --- kexec/Makefile | 4 ++ kexec/dt-ops.c | 145 + kexec/dt-ops.h | 13 ++ 3 files

[PATCH v6 0/3] arm64 kexec-tools patches

2016-09-21 Thread Geoff Levand
This series adds the core support for kexec re-boot on ARM64. Linux kernel support for ARM64 kexec reboot has been merged in v4.8-rc1 with the expectation that it will be included in the v4.8 stable kernel release. For ARM64 kdump support see Takahiro's latest kdump patches [1]. [1]

[PATCH v6 3/3] arm64: Add support for binary image files

2016-09-21 Thread Geoff Levand
From: Pratyush Anand Signed-off-by: Pratyush Anand [Reworked and cleaned up] Signed-off-by: Geoff Levand --- kexec/arch/arm64/kexec-image-arm64.c | 49 1 file changed, 44 insertions(+), 5

Re: [PATCH v26 0/7] arm64: add kdump support

2016-09-21 Thread AKASHI Takahiro
James, On Fri, Sep 16, 2016 at 05:04:34PM +0100, James Morse wrote: > (Cc: Ard), > > Mark, Ard, how does/will reserved-memory work on an APCI only system? > > > On 07/09/16 05:29, AKASHI Takahiro wrote: > > v26-specific note: After a comment from Rob[0], an idea of adding > >

Re: [PATCH v26 0/7] arm64: add kdump support

2016-09-21 Thread AKASHI Takahiro
On Mon, Sep 19, 2016 at 05:05:48PM +0100, James Morse wrote: > On 16/09/16 21:17, Ard Biesheuvel wrote: > > On 16 September 2016 at 17:04, James Morse wrote: > >> Mark, Ard, how does/will reserved-memory work on an APCI only system? > > > > It works by accident, at the

RE: [PATCH v3 1/3] open_dump_bitmap: open bitmap file in non-cyclic case

2016-09-21 Thread Atsushi Kumagai
Hello Martin, >The logic of set_bitmap() requires that a bitmap fd exists in the >non-cyclic case. > >Signed-off-by: Martin Wilck I'll merge this version into v1.6.1, thanks for your work. Regards, Atsushi Kumagai >--- > makedumpfile.c | 2 +- > 1 file changed, 1 insertion(+),