Re: [PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2014-01-14 Thread HATAYAMA Daisuke
(2013/12/10 23:49), Vivek Goyal wrote: On Wed, Dec 04, 2013 at 05:10:58PM +0900, HATAYAMA Daisuke wrote: This patch set is to allow kdump 2nd kernel to wake up multiple CPUs, a continueing work from: [PATCH v3 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP https://lkml.org/lkml

Re: [PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2014-01-14 Thread HATAYAMA Daisuke
(2013/12/10 23:49), Vivek Goyal wrote: On Wed, Dec 04, 2013 at 05:10:58PM +0900, HATAYAMA Daisuke wrote: This patch set is to allow kdump 2nd kernel to wake up multiple CPUs, a continueing work from: [PATCH v3 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP https://lkml.org/lkml

[RESEND PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apicid kernel parameter

2014-01-14 Thread HATAYAMA Daisuke
, disabled_cpu_apicid kernel parameter doesn't work well for apicids of APs. Fixing the wrong handling of boot_cpu_physical_apicid requires some reviews and tests beyond some platforms and it could take some time. The fix here is a kind of workaround to focus on the main topic of this patch. Signed-off-by: HATAYAMA

Re: [PATCH v2] vmcore: copy fractional pages into buffers in the kdump 2nd kernel

2013-12-12 Thread HATAYAMA Daisuke
(2013/12/13 1:42), Vivek Goyal wrote: On Mon, Dec 09, 2013 at 05:06:06PM +0900, HATAYAMA Daisuke wrote: This is a patch for fixing mmap failure due to fractional page issue. This patch might be still a bit too large as a single patch and might need to split. If you think patch refactoring

Re: [PATCH v2] vmcore: copy fractional pages into buffers in the kdump 2nd kernel

2013-12-12 Thread HATAYAMA Daisuke
(2013/12/13 1:42), Vivek Goyal wrote: On Mon, Dec 09, 2013 at 05:06:06PM +0900, HATAYAMA Daisuke wrote: This is a patch for fixing mmap failure due to fractional page issue. This patch might be still a bit too large as a single patch and might need to split. If you think patch refactoring

[PATCH v2] vmcore: copy fractional pages into buffers in the kdump 2nd kernel

2013-12-09 Thread HATAYAMA Daisuke
t;From fd6b0aca54caf7f0b5fd3841ef9e5ff081121ab8 Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke Date: Mon, 9 Dec 2013 09:12:32 +0900 Subject: [PATCH] vmcore: copy fractional pages into buffers in the kdump 2nd kernel As Vivek reported in https://lkml.org/lkml/2013/11/13/439, in real world there's platform that allocates Syst

[PATCH v2] vmcore: copy fractional pages into buffers in the kdump 2nd kernel

2013-12-09 Thread HATAYAMA Daisuke
fd6b0aca54caf7f0b5fd3841ef9e5ff081121ab8 Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com Date: Mon, 9 Dec 2013 09:12:32 +0900 Subject: [PATCH] vmcore: copy fractional pages into buffers in the kdump 2nd kernel As Vivek reported in https://lkml.org/lkml/2013/11/13/439, in real world there's platform

Re: [PATCH] vmcore: call remap_pfn_range() separately for respective partial pages

2013-12-04 Thread HATAYAMA Daisuke
(2013/12/04 0:12), Vivek Goyal wrote: On Tue, Dec 03, 2013 at 02:16:35PM +0900, HATAYAMA Daisuke wrote: [..] Even if copying partial pages into the 2nd kernel, we need to use ioremap() once on them, and I think the ioremap() is exactly similar to remap_pfn_range() for a single page

[PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-12-04 Thread HATAYAMA Daisuke
7d323b3ce95481be Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke Date: Tue, 3 Dec 2013 09:21:56 +0900 Subject: [PATCH] x86, apic, kexec, Documentation: Add disable_cpu_apicid kernel parameter Add disable_cpu_apicid kernel parameter. To use this kernel parameter, specify an initial APIC ID of

[PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-12-04 Thread HATAYAMA Daisuke
2001 From: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com Date: Tue, 3 Dec 2013 09:21:56 +0900 Subject: [PATCH] x86, apic, kexec, Documentation: Add disable_cpu_apicid kernel parameter Add disable_cpu_apicid kernel parameter. To use this kernel parameter, specify an initial APIC ID of the corresponding

Re: [PATCH] vmcore: call remap_pfn_range() separately for respective partial pages

2013-12-04 Thread HATAYAMA Daisuke
(2013/12/04 0:12), Vivek Goyal wrote: On Tue, Dec 03, 2013 at 02:16:35PM +0900, HATAYAMA Daisuke wrote: [..] Even if copying partial pages into the 2nd kernel, we need to use ioremap() once on them, and I think the ioremap() is exactly similar to remap_pfn_range() for a single page

Re: [PATCH v9] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-12-03 Thread HATAYAMA Daisuke
(2013/12/04 12:08), HATAYAMA Daisuke wrote: (2013/12/04 0:25), Vivek Goyal wrote: On Tue, Dec 03, 2013 at 10:32:26AM +0900, HATAYAMA Daisuke wrote: [..] diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 50680a5..dd77bec 100644 --- a/Documentation

Re: [PATCH v9] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-12-03 Thread HATAYAMA Daisuke
(2013/12/04 0:25), Vivek Goyal wrote: On Tue, Dec 03, 2013 at 10:32:26AM +0900, HATAYAMA Daisuke wrote: [..] diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 50680a5..dd77bec 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-12-03 Thread HATAYAMA Daisuke
are necessary for sanity check, how will > you prepare such values ? > (Get them from kernel source and hard-code them in makedumpfile ?) > >> Unlike diskdump, we no longer need to care about kernel/hardware level data >> integrity >> outside of user-land, but we still c

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-12-03 Thread HATAYAMA Daisuke
to deal with them by carefully handling dump data against makedumpfile's runtime data structure, e.g., buffer size. Is it OK to consider this is a policy of makedumpfile for data corruption? -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line unsubscribe linux-kernel

Re: [PATCH v9] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-12-03 Thread HATAYAMA Daisuke
(2013/12/04 0:25), Vivek Goyal wrote: On Tue, Dec 03, 2013 at 10:32:26AM +0900, HATAYAMA Daisuke wrote: [..] diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 50680a5..dd77bec 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation

Re: [PATCH v9] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-12-03 Thread HATAYAMA Daisuke
(2013/12/04 12:08), HATAYAMA Daisuke wrote: (2013/12/04 0:25), Vivek Goyal wrote: On Tue, Dec 03, 2013 at 10:32:26AM +0900, HATAYAMA Daisuke wrote: [..] diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 50680a5..dd77bec 100644 --- a/Documentation

Re: [PATCH] vmcore: call remap_pfn_range() separately for respective partial pages

2013-12-02 Thread HATAYAMA Daisuke
(2013/12/03 10:18), HATAYAMA Daisuke wrote: (2013/12/03 0:27), Vivek Goyal wrote: On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote: Hello Vivek, Here is a patch set for mmap failure for /proc/vmcore. Could you try to use this on the problematic system? This patch doesn't copy

[PATCH v9] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-12-02 Thread HATAYAMA Daisuke
n case of acpi and MP table - tested disable_cpu_apicid= to disable both AP and BSP >From 2cd100eb618a36a82bae2db98f0f4b7d3c1dfe89 Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke Date: Tue, 3 Dec 2013 09:21:56 +0900 Subject: [PATCH] x86, apic, kexec, Documentation: Add disable_cpu_apic

Re: [PATCH] vmcore: call remap_pfn_range() separately for respective partial pages

2013-12-02 Thread HATAYAMA Daisuke
(2013/12/03 0:27), Vivek Goyal wrote: On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote: Hello Vivek, Here is a patch set for mmap failure for /proc/vmcore. Could you try to use this on the problematic system? This patch doesn't copy partial pages to the 2nd kernel, only

Re: [PATCH] vmcore: call remap_pfn_range() separately for respective partial pages

2013-12-02 Thread HATAYAMA Daisuke
(2013/12/03 0:27), Vivek Goyal wrote: On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote: Hello Vivek, Here is a patch set for mmap failure for /proc/vmcore. Could you try to use this on the problematic system? This patch doesn't copy partial pages to the 2nd kernel, only

[PATCH v9] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-12-02 Thread HATAYAMA Daisuke
- tested disable_cpu_apicid=n to disable both AP and BSP From 2cd100eb618a36a82bae2db98f0f4b7d3c1dfe89 Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com Date: Tue, 3 Dec 2013 09:21:56 +0900 Subject: [PATCH] x86, apic, kexec, Documentation: Add disable_cpu_apicid kernel

Re: [PATCH] vmcore: call remap_pfn_range() separately for respective partial pages

2013-12-02 Thread HATAYAMA Daisuke
(2013/12/03 10:18), HATAYAMA Daisuke wrote: (2013/12/03 0:27), Vivek Goyal wrote: On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote: Hello Vivek, Here is a patch set for mmap failure for /proc/vmcore. Could you try to use this on the problematic system? This patch doesn't copy

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-28 Thread HATAYAMA Daisuke
For example, if the corrupted value were a huge number, wide range of pages after buddy page would be filtered falsely. So, actually we should sanity check data in crash dump before using them for application level feature. I've picked up order contained in page descriptor, so there would be other data used in makedumpfile that are not checked. Unlike diskdump, we no longer need to care about kernel/hardware level data integrity outside of user-land, but we still care about data its own integrity. On the other hand, if we do it, we might face some difficulty, for example, hardness of maintenance or performance bottleneck; it might be the reason why we don't see sanity check in makedumpfile now. -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-28 Thread HATAYAMA Daisuke
rder of >> huge page is hard in some way, right? > > The maximum order will be gotten from HUGETLB_PAGE_ORDER or HPAGE_PMD_ORDER, > so I don't say it's hard. However, the carrying over method doesn't depend on > such kernel symbols, so I think it's robuster. > Then, it's better

[PATCH] vmcore: call remap_pfn_range() separately for respective partial pages

2013-11-28 Thread HATAYAMA Daisuke
. >From c8323be2a2972dcb3f252598c39abfa23078 Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke Date: Thu, 28 Nov 2013 14:51:22 +0900 Subject: [PATCH] vmcore: call remap_pfn_range() separately for respective partial pages Acording to the report by Vivek in https://lkml.org/lkml/2013/11/13/

[PATCH] vmcore: call remap_pfn_range() separately for respective partial pages

2013-11-28 Thread HATAYAMA Daisuke
. From c8323be2a2972dcb3f252598c39abfa23078 Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com Date: Thu, 28 Nov 2013 14:51:22 +0900 Subject: [PATCH] vmcore: call remap_pfn_range() separately for respective partial pages Acording to the report by Vivek in https://lkml.org

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-28 Thread HATAYAMA Daisuke
say it's hard. However, the carrying over method doesn't depend on such kernel symbols, so I think it's robuster. Then, it's better to remove check_cyclic_buffer_overrun() and rewrite part of free page filtering in __exclude_unnecessary_pages(). Could you do that too? -- Thanks. HATAYAMA

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-28 Thread HATAYAMA Daisuke
, hardness of maintenance or performance bottleneck; it might be the reason why we don't see sanity check in makedumpfile now. -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-27 Thread HATAYAMA Daisuke
(2013/11/28 16:08), Atsushi Kumagai wrote: > On 2013/11/22 16:18:20, kexec wrote: >> (2013/11/07 9:54), HATAYAMA Daisuke wrote: >>> (2013/11/06 11:21), Atsushi Kumagai wrote: >>>> (2013/11/06 5:27), Vivek Goyal wrote: >>>>> On Tue, Nov 0

[PATCH v8] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-11-27 Thread HATAYAMA Daisuke
nly; I don't have any x86 processor without local apic. - Add __init annotation to boot_cpu_is_bsp_init(). Test - tested x86_64 in case of acpi and MP table - tested disable_cpu_apicid= to disable both AP and BSP >From a8bd546408ca06d844eda1af9ed1b34d12519eab Mon Sep 17 00:00:00 2001 From

Re: [PATCH v7 1/2] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-27 Thread HATAYAMA Daisuke
(2013/11/28 0:10), Vivek Goyal wrote: On Wed, Nov 27, 2013 at 11:00:48AM +0900, HATAYAMA Daisuke wrote: Add disable_cpu_apicid kernel parameter. To use this kernel parameter, specify an initial APIC ID of the corresponding CPU you want to disable. This is mostly used for the kdump 2nd kernel

Re: [PATCH v7 1/2] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-27 Thread HATAYAMA Daisuke
(2013/11/28 0:10), Vivek Goyal wrote: On Wed, Nov 27, 2013 at 11:00:48AM +0900, HATAYAMA Daisuke wrote: Add disable_cpu_apicid kernel parameter. To use this kernel parameter, specify an initial APIC ID of the corresponding CPU you want to disable. This is mostly used for the kdump 2nd kernel

[PATCH v8] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

2013-11-27 Thread HATAYAMA Daisuke
processor without local apic. - Add __init annotation to boot_cpu_is_bsp_init(). Test - tested x86_64 in case of acpi and MP table - tested disable_cpu_apicid=n to disable both AP and BSP From a8bd546408ca06d844eda1af9ed1b34d12519eab Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke d.hatay

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-27 Thread HATAYAMA Daisuke
(2013/11/28 16:08), Atsushi Kumagai wrote: On 2013/11/22 16:18:20, kexec kexec-boun...@lists.infradead.org wrote: (2013/11/07 9:54), HATAYAMA Daisuke wrote: (2013/11/06 11:21), Atsushi Kumagai wrote: (2013/11/06 5:27), Vivek Goyal wrote: On Tue, Nov 05, 2013 at 09:45:32PM +0800, Jingbai Ma

[PATCH v7 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-26 Thread HATAYAMA Daisuke
local apic-present case only; I don't have any x86 processor without local apic. - Add __init annotation to boot_cpu_is_bsp_init(). Test - built with and without CONFIG_LOCAL_APIC - tested x86_64 in case of acpi and MP table - tested disable_cpu_apicid= to disable both AP and BSP --- H

[PATCH v7 1/2] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-26 Thread HATAYAMA Daisuke
are required. As a workaround, we directly update boot_cpu_physical_apicid by read_apic_id(). Signed-off-by: HATAYAMA Daisuke --- arch/x86/kernel/apic/apic.c | 49 +++ 1 file changed, 49 insertions(+) diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86

[PATCH v7 2/2] Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter

2013-11-26 Thread HATAYAMA Daisuke
Add disable_cpu_apicid kernel parameter to disable the CPU with the specified number of initial APIC ID, mostly used for the kdump 2nd kernel to disable BSP to wake up multiple CPUs without causing system reset or hang due to sending INIT from AP to BSP. Signed-off-by: HATAYAMA Daisuke

[PATCH v7 2/2] Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter

2013-11-26 Thread HATAYAMA Daisuke
Add disable_cpu_apicid kernel parameter to disable the CPU with the specified number of initial APIC ID, mostly used for the kdump 2nd kernel to disable BSP to wake up multiple CPUs without causing system reset or hang due to sending INIT from AP to BSP. Signed-off-by: HATAYAMA Daisuke d.hatay

[PATCH v7 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-26 Thread HATAYAMA Daisuke
; I don't have any x86 processor without local apic. - Add __init annotation to boot_cpu_is_bsp_init(). Test - built with and without CONFIG_LOCAL_APIC - tested x86_64 in case of acpi and MP table - tested disable_cpu_apicid=n to disable both AP and BSP --- HATAYAMA Daisuke (2): x86

[PATCH v7 1/2] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-26 Thread HATAYAMA Daisuke
are required. As a workaround, we directly update boot_cpu_physical_apicid by read_apic_id(). Signed-off-by: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com --- arch/x86/kernel/apic/apic.c | 49 +++ 1 file changed, 49 insertions(+) diff --git a/arch/x86/kernel

Re: /proc/vmcore mmap() failure issue

2013-11-25 Thread HATAYAMA Daisuke
(2013/11/25 23:41), Vivek Goyal wrote: On Mon, Nov 25, 2013 at 06:01:37PM +0900, HATAYAMA Daisuke wrote: [..] I agree to avoid this issue by fixing makedumpfile as workaround while to fix kernel is so tough and risky. However, it sounds strange to me to fix userspace side elaborately

Re: /proc/vmcore mmap() failure issue

2013-11-25 Thread HATAYAMA Daisuke
(2013/11/25 17:10), Atsushi Kumagai wrote: > On 2013/11/22 1:53:14, kexec wrote: >> On Thu, Nov 21, 2013 at 05:31:46PM +0900, HATAYAMA Daisuke wrote: >> >> [..] >>>> So I think the patch I sent is enough, the policy will be simpler as >>>> "Don

Re: /proc/vmcore mmap() failure issue

2013-11-25 Thread HATAYAMA Daisuke
(2013/11/25 17:10), Atsushi Kumagai wrote: On 2013/11/22 1:53:14, kexec kexec-boun...@lists.infradead.org wrote: On Thu, Nov 21, 2013 at 05:31:46PM +0900, HATAYAMA Daisuke wrote: [..] So I think the patch I sent is enough, the policy will be simpler as Don't use mmap() for buggy kernels

Re: /proc/vmcore mmap() failure issue

2013-11-25 Thread HATAYAMA Daisuke
(2013/11/25 23:41), Vivek Goyal wrote: On Mon, Nov 25, 2013 at 06:01:37PM +0900, HATAYAMA Daisuke wrote: [..] I agree to avoid this issue by fixing makedumpfile as workaround while to fix kernel is so tough and risky. However, it sounds strange to me to fix userspace side elaborately

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-21 Thread HATAYAMA Daisuke
(2013/11/07 9:54), HATAYAMA Daisuke wrote: (2013/11/06 11:21), Atsushi Kumagai wrote: (2013/11/06 5:27), Vivek Goyal wrote: On Tue, Nov 05, 2013 at 09:45:32PM +0800, Jingbai Ma wrote: This patch set intend to exclude unnecessary hugepages from vmcore dump file. This patch requires the kernel

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-21 Thread HATAYAMA Daisuke
(2013/11/07 9:54), HATAYAMA Daisuke wrote: (2013/11/06 11:21), Atsushi Kumagai wrote: (2013/11/06 5:27), Vivek Goyal wrote: On Tue, Nov 05, 2013 at 09:45:32PM +0800, Jingbai Ma wrote: This patch set intend to exclude unnecessary hugepages from vmcore dump file. This patch requires the kernel

[PATCH v6 3/3] Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter

2013-11-20 Thread HATAYAMA Daisuke
Add disable_cpu_apicid kernel parameter to disable the CPU with the specified number of initial APIC ID, mostly used for the kdump 2nd kernel to disable BSP to wake up multiple CPUs without causing system reset or hang due to sending INIT from AP to BSP. Signed-off-by: HATAYAMA Daisuke

[PATCH v6 2/3] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-20 Thread HATAYAMA Daisuke
-off-by: HATAYAMA Daisuke --- arch/x86/kernel/apic/apic.c | 29 + 1 file changed, 29 insertions(+) diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c index cff8d71..77fd68d 100644 --- a/arch/x86/kernel/apic/apic.c +++ b/arch/x86/kernel/apic/apic.c

[PATCH v6 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-20 Thread HATAYAMA Daisuke
to disable both AP and BSP --- HATAYAMA Daisuke (3): x86, apic: add bios_bsp_physical_apicid x86, apic: Add disable_cpu_apicid kernel parameter Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter Documentation/kernel-parameters.txt|9 arch/

[PATCH v6 1/3] x86, apic: add bios_bsp_physical_apicid

2013-11-20 Thread HATAYAMA Daisuke
even if it exists on some system, e.g. some cluster system. Signed-off-by: HATAYAMA Daisuke --- arch/x86/include/asm/mpspec.h |1 + arch/x86/kernel/acpi/boot.c|8 arch/x86/kernel/apic/apic.c|9 + arch/x86/kernel/mpparse.c

[PATCH v6 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-20 Thread HATAYAMA Daisuke
and BSP --- HATAYAMA Daisuke (3): x86, apic: add bios_bsp_physical_apicid x86, apic: Add disable_cpu_apicid kernel parameter Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter Documentation/kernel-parameters.txt|9 arch/x86/include/asm

[PATCH v6 1/3] x86, apic: add bios_bsp_physical_apicid

2013-11-20 Thread HATAYAMA Daisuke
even if it exists on some system, e.g. some cluster system. Signed-off-by: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com --- arch/x86/include/asm/mpspec.h |1 + arch/x86/kernel/acpi/boot.c|8 arch/x86/kernel/apic/apic.c|9 + arch/x86/kernel

[PATCH v6 3/3] Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter

2013-11-20 Thread HATAYAMA Daisuke
Add disable_cpu_apicid kernel parameter to disable the CPU with the specified number of initial APIC ID, mostly used for the kdump 2nd kernel to disable BSP to wake up multiple CPUs without causing system reset or hang due to sending INIT from AP to BSP. Signed-off-by: HATAYAMA Daisuke d.hatay

[PATCH v6 2/3] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-20 Thread HATAYAMA Daisuke
-off-by: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com --- arch/x86/kernel/apic/apic.c | 29 + 1 file changed, 29 insertions(+) diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c index cff8d71..77fd68d 100644 --- a/arch/x86/kernel/apic/apic.c +++ b/arch

Re: /proc/vmcore mmap() failure issue

2013-11-19 Thread HATAYAMA Daisuke
(2013/11/20 14:27), Atsushi Kumagai wrote: > On 2013/11/19 18:56:21, kexec wrote: >> (2013/11/18 9:51), Atsushi Kumagai wrote: >>> (2013/11/15 23:26), Vivek Goyal wrote: >>>> On Fri, Nov 15, 2013 at 06:41:52PM +0900, HATAYAMA Daisuke wrote: >>>> >

Re: /proc/vmcore mmap() failure issue

2013-11-19 Thread HATAYAMA Daisuke
(2013/11/18 9:51), Atsushi Kumagai wrote: > (2013/11/15 23:26), Vivek Goyal wrote: >> On Fri, Nov 15, 2013 at 06:41:52PM +0900, HATAYAMA Daisuke wrote: >> >> [..] >>>> Given the fact that hpa does not like fixing it in kernel. We are left >>>>

[PATCH] sysfs, acpi, tables: Set file size for each ACPI table

2013-11-19 Thread HATAYAMA Daisuke
00 00 00 00 01 00 00 00 ...@ 00A0: 00 00 00 00 00 00 00 00 Signed-off-by: HATAYAMA Daisuke --- drivers/acpi/sysfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/sysfs.c b/drivers/acpi/sysfs.c index 05306a5

[PATCH] sysfs, acpi, tables: Set file size for each ACPI table

2013-11-19 Thread HATAYAMA Daisuke
00 00 00 00 01 00 00 00 ...@ 00A0: 00 00 00 00 00 00 00 00 Signed-off-by: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com --- drivers/acpi/sysfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/sysfs.c b/drivers/acpi

Re: /proc/vmcore mmap() failure issue

2013-11-19 Thread HATAYAMA Daisuke
(2013/11/18 9:51), Atsushi Kumagai wrote: (2013/11/15 23:26), Vivek Goyal wrote: On Fri, Nov 15, 2013 at 06:41:52PM +0900, HATAYAMA Daisuke wrote: [..] Given the fact that hpa does not like fixing it in kernel. We are left with option of fixing it in following places. - Drop partial pages

Re: /proc/vmcore mmap() failure issue

2013-11-19 Thread HATAYAMA Daisuke
(2013/11/20 14:27), Atsushi Kumagai wrote: On 2013/11/19 18:56:21, kexec kexec-boun...@lists.infradead.org wrote: (2013/11/18 9:51), Atsushi Kumagai wrote: (2013/11/15 23:26), Vivek Goyal wrote: On Fri, Nov 15, 2013 at 06:41:52PM +0900, HATAYAMA Daisuke wrote: [..] Given the fact that hpa

Re: /proc/vmcore mmap() failure issue

2013-11-15 Thread HATAYAMA Daisuke
(2013/11/15 0:13), Vivek Goyal wrote: On Thu, Nov 14, 2013 at 07:31:37PM +0900, HATAYAMA Daisuke wrote: [..] BTW, I previously found a part of makedumpfile that truncates the first and last pages if they are not aligned in page size. Discussing with Kumagai-san, the truncation is performed

Re: /proc/vmcore mmap() failure issue

2013-11-15 Thread HATAYAMA Daisuke
(2013/11/15 0:13), Vivek Goyal wrote: On Thu, Nov 14, 2013 at 07:31:37PM +0900, HATAYAMA Daisuke wrote: [..] BTW, I previously found a part of makedumpfile that truncates the first and last pages if they are not aligned in page size. Discussing with Kumagai-san, the truncation is performed

Re: [PATCH v5 1/3] x86, apic: add bsp_physical_apicid

2013-11-14 Thread HATAYAMA Daisuke
Hello HPA, I have another question relevant to http://lkml.org/lkml/2013/11/12/311. (2013/11/12 18:51), HATAYAMA Daisuke wrote: @@ -2589,3 +2593,14 @@ static int __init lapic_insert_resource(void) * that is using request_resource */ late_initcall(lapic_insert_resource); + +void __init

Re: [PATCH v5 2/3] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-14 Thread HATAYAMA Daisuke
(2013/11/12 19:44), Borislav Petkov wrote: On Tue, Nov 12, 2013 at 06:51:58PM +0900, HATAYAMA Daisuke wrote: Add disable_cpu_apicid kernel parameter. To use this kernel parameter, specify an initial APIC ID of the corresponding CPU you want to disable. This is mostly used for the kdump 2nd

Re: /proc/vmcore mmap() failure issue

2013-11-14 Thread HATAYAMA Daisuke
above commit or not since makedumpfile fails on some kind of system as you reported. -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.o

Re: /proc/vmcore mmap() failure issue

2013-11-14 Thread HATAYAMA Daisuke
or not to revert the above commit or not since makedumpfile fails on some kind of system as you reported. -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http

Re: [PATCH v5 2/3] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-14 Thread HATAYAMA Daisuke
(2013/11/12 19:44), Borislav Petkov wrote: On Tue, Nov 12, 2013 at 06:51:58PM +0900, HATAYAMA Daisuke wrote: Add disable_cpu_apicid kernel parameter. To use this kernel parameter, specify an initial APIC ID of the corresponding CPU you want to disable. This is mostly used for the kdump 2nd

Re: [PATCH v5 1/3] x86, apic: add bsp_physical_apicid

2013-11-14 Thread HATAYAMA Daisuke
Hello HPA, I have another question relevant to http://lkml.org/lkml/2013/11/12/311. (2013/11/12 18:51), HATAYAMA Daisuke wrote: cut @@ -2589,3 +2593,14 @@ static int __init lapic_insert_resource(void) * that is using request_resource */ late_initcall(lapic_insert_resource); + +void

Re: [tip:x86/bsp-hotplug] x86, apic: Disable BSP if boot cpu is AP

2013-11-12 Thread HATAYAMA Daisuke
(2013/11/12 4:54), H. Peter Anvin wrote: On 10/12/2013 10:42 AM, Ingo Molnar wrote: * H. Peter Anvin wrote: On 10/09/2013 04:16 PM, tip-bot for HATAYAMA Daisuke wrote: Commit-ID: 1d79e607332d67d9132c176d99b5e7fabe1b6b7f Gitweb: http://git.kernel.org/tip

Re: [PATCH v4 1/3] x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU

2013-11-12 Thread HATAYAMA Daisuke
(2013/11/12 9:40), HATAYAMA Daisuke wrote: (2013/11/12 1:52), Vivek Goyal wrote: On Mon, Nov 11, 2013 at 11:52:30AM +0900, HATAYAMA Daisuke wrote: [..] Looking at my past investigation, kernel/mpparse.c, mm/amdtopology.c and platform/visws/visws_quirks.c assumes that boot_cpu_physical_apicid

[PATCH v5 2/3] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-12 Thread HATAYAMA Daisuke
-off-by: HATAYAMA Daisuke --- arch/x86/kernel/apic/apic.c | 29 + 1 file changed, 29 insertions(+) diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c index b60ad92..075bf23 100644 --- a/arch/x86/kernel/apic/apic.c +++ b/arch/x86/kernel/apic/apic.c

[PATCH v5 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-12 Thread HATAYAMA Daisuke
ve any x86 processor without local apic. - Add __init annotation to boot_cpu_is_bsp_init(). Test - built with and without CONFIG_LOCAL_APIC, CONFIG_SMP and CONFIG_X86_UP_APIC. - tested x86_64 in case of acpi and MP table - tested disable_cpu_apicid= to disable both AP and BSP --- HATAYAMA Daisuke (3

[PATCH v5 3/3] Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter

2013-11-12 Thread HATAYAMA Daisuke
Add disable_cpu_apicid kernel parameter to disable the CPU with the specified number of initial APIC ID, mostly used for the kdump 2nd kernel to disable BSP to wake up multiple CPUs without causing system reset or hang due to sending INIT from AP to BSP. Signed-off-by: HATAYAMA Daisuke

[PATCH v5 1/3] x86, apic: add bsp_physical_apicid

2013-11-12 Thread HATAYAMA Daisuke
from MP table or MADT. This covers the above MP table related codes with no functional change. Initialize boot_cpu_data.initial_apicid in early_identify_cpu() since currently it is initialized after logical cpu number assignment is performed. Signed-off-by: HATAYAMA Daisuke --- arch/x86/include

[PATCH v5 1/3] x86, apic: add bsp_physical_apicid

2013-11-12 Thread HATAYAMA Daisuke
from MP table or MADT. This covers the above MP table related codes with no functional change. Initialize boot_cpu_data.initial_apicid in early_identify_cpu() since currently it is initialized after logical cpu number assignment is performed. Signed-off-by: HATAYAMA Daisuke d.hatay

[PATCH v5 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-12 Thread HATAYAMA Daisuke
without local apic. - Add __init annotation to boot_cpu_is_bsp_init(). Test - built with and without CONFIG_LOCAL_APIC, CONFIG_SMP and CONFIG_X86_UP_APIC. - tested x86_64 in case of acpi and MP table - tested disable_cpu_apicid=n to disable both AP and BSP --- HATAYAMA Daisuke (3): x86

[PATCH v5 3/3] Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter

2013-11-12 Thread HATAYAMA Daisuke
Add disable_cpu_apicid kernel parameter to disable the CPU with the specified number of initial APIC ID, mostly used for the kdump 2nd kernel to disable BSP to wake up multiple CPUs without causing system reset or hang due to sending INIT from AP to BSP. Signed-off-by: HATAYAMA Daisuke d.hatay

[PATCH v5 2/3] x86, apic: Add disable_cpu_apicid kernel parameter

2013-11-12 Thread HATAYAMA Daisuke
-off-by: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com --- arch/x86/kernel/apic/apic.c | 29 + 1 file changed, 29 insertions(+) diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c index b60ad92..075bf23 100644 --- a/arch/x86/kernel/apic/apic.c +++ b/arch

Re: [PATCH v4 1/3] x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU

2013-11-12 Thread HATAYAMA Daisuke
(2013/11/12 9:40), HATAYAMA Daisuke wrote: (2013/11/12 1:52), Vivek Goyal wrote: On Mon, Nov 11, 2013 at 11:52:30AM +0900, HATAYAMA Daisuke wrote: [..] Looking at my past investigation, kernel/mpparse.c, mm/amdtopology.c and platform/visws/visws_quirks.c assumes that boot_cpu_physical_apicid

Re: [tip:x86/bsp-hotplug] x86, apic: Disable BSP if boot cpu is AP

2013-11-12 Thread HATAYAMA Daisuke
(2013/11/12 4:54), H. Peter Anvin wrote: On 10/12/2013 10:42 AM, Ingo Molnar wrote: * H. Peter Anvin h...@zytor.com wrote: On 10/09/2013 04:16 PM, tip-bot for HATAYAMA Daisuke wrote: Commit-ID: 1d79e607332d67d9132c176d99b5e7fabe1b6b7f Gitweb: http://git.kernel.org/tip

Re: [PATCH v4 1/3] x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU

2013-11-11 Thread HATAYAMA Daisuke
(2013/11/12 1:52), Vivek Goyal wrote: On Mon, Nov 11, 2013 at 11:52:30AM +0900, HATAYAMA Daisuke wrote: [..] Looking at my past investigation, kernel/mpparse.c, mm/amdtopology.c and platform/visws/visws_quirks.c assumes that boot_cpu_physical_apicid has initial apicid of the BSP

Re: [PATCH v4 1/3] x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU

2013-11-11 Thread HATAYAMA Daisuke
(2013/11/12 1:52), Vivek Goyal wrote: On Mon, Nov 11, 2013 at 11:52:30AM +0900, HATAYAMA Daisuke wrote: [..] Looking at my past investigation, kernel/mpparse.c, mm/amdtopology.c and platform/visws/visws_quirks.c assumes that boot_cpu_physical_apicid has initial apicid of the BSP

Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-10 Thread HATAYAMA Daisuke
(2013/11/07 4:02), jerry.hoem...@hp.com wrote: On Wed, Oct 23, 2013 at 12:01:18AM +0900, HATAYAMA Daisuke wrote: This patch set is to allow kdump 2nd kernel to wake up multiple CPUs even if 1st kernel crashs on some AP, a continueing work from: [PATCH v3 0/2] x86, apic, kdump: Disable BSP

Re: [PATCH v4 1/3] x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU

2013-11-10 Thread HATAYAMA Daisuke
(2013/11/09 1:08), Vivek Goyal wrote: On Wed, Oct 23, 2013 at 12:01:24AM +0900, HATAYAMA Daisuke wrote: If crash occurs on some AP, then kdump 2nd kernel is booted up on the AP. Therefore, it is not always correct that the CPU that is currently booting up the kernel is BSP. It's wrong

Re: [PATCH v4 1/3] x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU

2013-11-10 Thread HATAYAMA Daisuke
(2013/11/09 1:08), Vivek Goyal wrote: On Wed, Oct 23, 2013 at 12:01:24AM +0900, HATAYAMA Daisuke wrote: If crash occurs on some AP, then kdump 2nd kernel is booted up on the AP. Therefore, it is not always correct that the CPU that is currently booting up the kernel is BSP. It's wrong

Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-10 Thread HATAYAMA Daisuke
(2013/11/07 4:02), jerry.hoem...@hp.com wrote: On Wed, Oct 23, 2013 at 12:01:18AM +0900, HATAYAMA Daisuke wrote: This patch set is to allow kdump 2nd kernel to wake up multiple CPUs even if 1st kernel crashs on some AP, a continueing work from: [PATCH v3 0/2] x86, apic, kdump: Disable BSP

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-07 Thread HATAYAMA Daisuke
magai-san, please correct me, if I'm wrong. > > Yes, my patch treats all allocated hugetlbfs pages as user pages, > doesn't distinguish whether the pages are actually used or not. > I made so because I guess it's enough for almost all users. > > We can introduce new dump level after it's needed actually, > but I don't think now is the time. To introduce it without > demand will make this tool just more complex. > Typically, users would allocate huge pages as much as actually they use only, in order not to waste system memory. So, this design seems reasonable. -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-07 Thread HATAYAMA Daisuke
rrupts can be broken. The other cpus except for the crashing cpu are no longer guaranteed to be running sanely. Migrating cpu from the crashing cpu to cpu0 reduces reliability of kdump. -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in t

Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-07 Thread HATAYAMA Daisuke
. The other cpus except for the crashing cpu are no longer guaranteed to be running sanely. Migrating cpu from the crashing cpu to cpu0 reduces reliability of kdump. -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-07 Thread HATAYAMA Daisuke
as actually they use only, in order not to waste system memory. So, this design seems reasonable. -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-06 Thread HATAYAMA Daisuke
n info->bufsize_cyclic with larger one in check_cyclic_buffer_overrun(). -- Thanks. HATAYAMA, Daisuke -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[tip:x86/cpu] x86/cpu: Always print SMP information in /proc/ cpuinfo

2013-11-06 Thread tip-bot for HATAYAMA Daisuke
Commit-ID: a477c8594bee3bff639739c48258a8c737ab721e Gitweb: http://git.kernel.org/tip/a477c8594bee3bff639739c48258a8c737ab721e Author: HATAYAMA Daisuke AuthorDate: Tue, 5 Nov 2013 02:15:48 +0900 Committer: Ingo Molnar CommitDate: Wed, 6 Nov 2013 08:13:56 +0100 x86/cpu: Always print

[tip:x86/cpu] x86/cpu: Always print SMP information in /proc/ cpuinfo

2013-11-06 Thread tip-bot for HATAYAMA Daisuke
Commit-ID: a477c8594bee3bff639739c48258a8c737ab721e Gitweb: http://git.kernel.org/tip/a477c8594bee3bff639739c48258a8c737ab721e Author: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com AuthorDate: Tue, 5 Nov 2013 02:15:48 +0900 Committer: Ingo Molnar mi...@kernel.org CommitDate: Wed, 6 Nov 2013

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-06 Thread HATAYAMA Daisuke
to the current cyclic range. If maximum value of compound_order is larger than maximum value of CONFIG_FORCE_MAX_ZONEORDER, which makedumpfile obtains by ARRAY_LENGTH(zone.free_area), it's necessary to align info-bufsize_cyclic with larger one in check_cyclic_buffer_overrun(). -- Thanks. HATAYAMA

[RESEND][PATCH] x86, procfs: always print MP information in /proc/cpuinfo

2013-11-04 Thread HATAYAMA Daisuke
, on which guest, MP information is not displayed in /proc/cpuinfo. I saw this situation on VMWare guest environment, too. To fix this issue, this patch simply removes the condition because this information is useful even if there's only 1 thread. Signed-off-by: HATAYAMA Daisuke --- arch/x86/kernel/cpu

[RESEND][PATCH] x86, procfs: always print MP information in /proc/cpuinfo

2013-11-04 Thread HATAYAMA Daisuke
, on which guest, MP information is not displayed in /proc/cpuinfo. I saw this situation on VMWare guest environment, too. To fix this issue, this patch simply removes the condition because this information is useful even if there's only 1 thread. Signed-off-by: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com

Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-03 Thread HATAYAMA Daisuke
only. I'd like anyone to post patches if necessary... BTW, what's the status of this patch set? I've redesigned this so as to be done with kernel parameter in order not to depend on platform specific BIOS table. Due to the redesign, I think now ACK is needed again. -- Thanks. HATAYAMA, Daisuke

Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-11-03 Thread HATAYAMA Daisuke
only. I'd like anyone to post patches if necessary... BTW, what's the status of this patch set? I've redesigned this so as to be done with kernel parameter in order not to depend on platform specific BIOS table. Due to the redesign, I think now ACK is needed again. -- Thanks. HATAYAMA, Daisuke

Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

2013-10-30 Thread HATAYAMA Daisuke
(2013/10/31 9:58), jerry.hoem...@hp.com wrote: On Wed, Oct 23, 2013 at 09:05:06AM +0900, HATAYAMA Daisuke wrote: - Rebased on top of v3.12-rc6 - Basic design has been changed. Now users need to figure out initial APIC ID of BSP in the 1st kernel and configures kernel parameter

<    1   2   3   4   5   6   7   8   >