All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Bhupesh Sharma <bhsharma@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org, x86@kernel.org,
	Mark Rutland <mark.rutland@arm.com>,
	Kazuhito Hagio <k-hagio@ab.jp.nec.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Boris Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>,
	bhupesh.linux@gmail.com, Will Deacon <will@kernel.org>,
	Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
	Dave Anderson <anderson@redhat.com>
Subject: Re: [PATCH v6 1/2] crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS' to vmcoreinfo
Date: Thu, 2 Jul 2020 12:00:20 +0100	[thread overview]
Message-ID: <20200702110003.GC22241@gaia> (raw)
In-Reply-To: <1589395957-24628-2-git-send-email-bhsharma@redhat.com>

On Thu, May 14, 2020 at 12:22:36AM +0530, Bhupesh Sharma wrote:
> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> index 9f1557b98468..18175687133a 100644
> --- a/kernel/crash_core.c
> +++ b/kernel/crash_core.c
> @@ -413,6 +413,7 @@ static int __init crash_save_vmcoreinfo_init(void)
>  	VMCOREINFO_LENGTH(mem_section, NR_SECTION_ROOTS);
>  	VMCOREINFO_STRUCT_SIZE(mem_section);
>  	VMCOREINFO_OFFSET(mem_section, section_mem_map);
> +	VMCOREINFO_NUMBER(MAX_PHYSMEM_BITS);
>  #endif
>  	VMCOREINFO_STRUCT_SIZE(page);
>  	VMCOREINFO_STRUCT_SIZE(pglist_data);

I can queue this patch via the arm64 tree (together with the second one)
but I'd like an ack from the kernel/crash_core.c maintainers. They don't
seem to have been cc'ed either (only the kexec list).

Thanks.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Bhupesh Sharma <bhsharma@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Kazuhito Hagio <k-hagio@ab.jp.nec.com>,
	Will Deacon <will@kernel.org>,
	x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	James Morse <james.morse@arm.com>, Boris Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	bhupesh.linux@gmail.com, linuxppc-dev@lists.ozlabs.org,
	Ingo Molnar <mingo@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Dave Anderson <anderson@redhat.com>
Subject: Re: [PATCH v6 1/2] crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS' to vmcoreinfo
Date: Thu, 2 Jul 2020 12:00:20 +0100	[thread overview]
Message-ID: <20200702110003.GC22241@gaia> (raw)
In-Reply-To: <1589395957-24628-2-git-send-email-bhsharma@redhat.com>

On Thu, May 14, 2020 at 12:22:36AM +0530, Bhupesh Sharma wrote:
> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> index 9f1557b98468..18175687133a 100644
> --- a/kernel/crash_core.c
> +++ b/kernel/crash_core.c
> @@ -413,6 +413,7 @@ static int __init crash_save_vmcoreinfo_init(void)
>  	VMCOREINFO_LENGTH(mem_section, NR_SECTION_ROOTS);
>  	VMCOREINFO_STRUCT_SIZE(mem_section);
>  	VMCOREINFO_OFFSET(mem_section, section_mem_map);
> +	VMCOREINFO_NUMBER(MAX_PHYSMEM_BITS);
>  #endif
>  	VMCOREINFO_STRUCT_SIZE(page);
>  	VMCOREINFO_STRUCT_SIZE(pglist_data);

I can queue this patch via the arm64 tree (together with the second one)
but I'd like an ack from the kernel/crash_core.c maintainers. They don't
seem to have been cc'ed either (only the kexec list).

Thanks.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Bhupesh Sharma <bhsharma@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Kazuhito Hagio <k-hagio@ab.jp.nec.com>,
	Will Deacon <will@kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	James Morse <james.morse@arm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Boris Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>,
	bhupesh.linux@gmail.com, linuxppc-dev@lists.ozlabs.org,
	Ingo Molnar <mingo@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Dave Anderson <anderson@redhat.com>
Subject: Re: [PATCH v6 1/2] crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS' to vmcoreinfo
Date: Thu, 2 Jul 2020 12:00:20 +0100	[thread overview]
Message-ID: <20200702110003.GC22241@gaia> (raw)
In-Reply-To: <1589395957-24628-2-git-send-email-bhsharma@redhat.com>

On Thu, May 14, 2020 at 12:22:36AM +0530, Bhupesh Sharma wrote:
> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> index 9f1557b98468..18175687133a 100644
> --- a/kernel/crash_core.c
> +++ b/kernel/crash_core.c
> @@ -413,6 +413,7 @@ static int __init crash_save_vmcoreinfo_init(void)
>  	VMCOREINFO_LENGTH(mem_section, NR_SECTION_ROOTS);
>  	VMCOREINFO_STRUCT_SIZE(mem_section);
>  	VMCOREINFO_OFFSET(mem_section, section_mem_map);
> +	VMCOREINFO_NUMBER(MAX_PHYSMEM_BITS);
>  #endif
>  	VMCOREINFO_STRUCT_SIZE(page);
>  	VMCOREINFO_STRUCT_SIZE(pglist_data);

I can queue this patch via the arm64 tree (together with the second one)
but I'd like an ack from the kernel/crash_core.c maintainers. They don't
seem to have been cc'ed either (only the kexec list).

Thanks.

-- 
Catalin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Bhupesh Sharma <bhsharma@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Kazuhito Hagio <k-hagio@ab.jp.nec.com>,
	Will Deacon <will@kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	James Morse <james.morse@arm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Boris Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>,
	bhupesh.linux@gmail.com, linuxppc-dev@lists.ozlabs.org,
	Ingo Molnar <mingo@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Dave Anderson <anderson@redhat.com>
Subject: Re: [PATCH v6 1/2] crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS' to vmcoreinfo
Date: Thu, 2 Jul 2020 12:00:20 +0100	[thread overview]
Message-ID: <20200702110003.GC22241@gaia> (raw)
In-Reply-To: <1589395957-24628-2-git-send-email-bhsharma@redhat.com>

On Thu, May 14, 2020 at 12:22:36AM +0530, Bhupesh Sharma wrote:
> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> index 9f1557b98468..18175687133a 100644
> --- a/kernel/crash_core.c
> +++ b/kernel/crash_core.c
> @@ -413,6 +413,7 @@ static int __init crash_save_vmcoreinfo_init(void)
>  	VMCOREINFO_LENGTH(mem_section, NR_SECTION_ROOTS);
>  	VMCOREINFO_STRUCT_SIZE(mem_section);
>  	VMCOREINFO_OFFSET(mem_section, section_mem_map);
> +	VMCOREINFO_NUMBER(MAX_PHYSMEM_BITS);
>  #endif
>  	VMCOREINFO_STRUCT_SIZE(page);
>  	VMCOREINFO_STRUCT_SIZE(pglist_data);

I can queue this patch via the arm64 tree (together with the second one)
but I'd like an ack from the kernel/crash_core.c maintainers. They don't
seem to have been cc'ed either (only the kexec list).

Thanks.

-- 
Catalin

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2020-07-02 11:00 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 18:52 [PATCH v6 0/2] Append new variables to vmcoreinfo (TCR_EL1.T1SZ for arm64 and MAX_PHYSMEM_BITS for all archs) Bhupesh Sharma
2020-05-13 18:52 ` Bhupesh Sharma
2020-05-13 18:52 ` Bhupesh Sharma
2020-05-13 18:52 ` Bhupesh Sharma
2020-05-13 18:52 ` [PATCH v6 1/2] crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS' to vmcoreinfo Bhupesh Sharma
2020-05-13 18:52   ` Bhupesh Sharma
2020-05-13 18:52   ` Bhupesh Sharma
2020-05-13 18:52   ` Bhupesh Sharma
2020-07-02 11:00   ` Catalin Marinas [this message]
2020-07-02 11:00     ` Catalin Marinas
2020-07-02 11:00     ` Catalin Marinas
2020-07-02 11:00     ` Catalin Marinas
2020-07-02 12:08     ` Dave Young
2020-07-02 12:08       ` Dave Young
2020-07-02 12:08       ` Dave Young
2020-07-02 12:08       ` Dave Young
2020-07-02 16:55       ` Catalin Marinas
2020-07-02 16:55         ` Catalin Marinas
2020-07-02 16:55         ` Catalin Marinas
2020-07-02 16:55         ` Catalin Marinas
2020-05-13 18:52 ` [PATCH v6 2/2] arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Bhupesh Sharma
2020-05-13 18:52   ` Bhupesh Sharma
2020-05-13 18:52   ` Bhupesh Sharma
2020-06-03 11:20   ` Kamlakant Patel
2020-06-03 11:20     ` Kamlakant Patel
2020-06-03 11:20     ` Kamlakant Patel
2020-06-03 20:34     ` Bhupesh Sharma
2020-06-03 20:34       ` Bhupesh Sharma
2020-06-03 20:34       ` Bhupesh Sharma
2020-06-04  4:49       ` [EXT] " Kamlakant Patel
2020-06-04  4:49         ` Kamlakant Patel
2020-06-04  4:49         ` Kamlakant Patel
2020-06-04  7:19       ` Will Deacon
2020-06-04  7:19         ` Will Deacon
2020-06-04  7:19         ` Will Deacon
2020-07-01  8:04   ` Amit Kachhap
2020-07-01  8:04     ` Amit Kachhap
2020-07-01  8:04     ` Amit Kachhap
2020-07-01 11:59   ` James Morse
2020-07-01 11:59     ` James Morse
2020-07-01 11:59     ` James Morse
2020-06-02  5:24 ` [PATCH v6 0/2] Append new variables to vmcoreinfo (TCR_EL1.T1SZ for arm64 and MAX_PHYSMEM_BITS for all archs) Bhupesh Sharma
2020-06-02  5:24   ` Bhupesh Sharma
2020-06-02  5:24   ` Bhupesh Sharma
2020-06-02  5:24   ` Bhupesh Sharma
2020-06-15 19:11   ` Bhupesh Sharma
2020-06-15 19:11     ` Bhupesh Sharma
2020-06-15 19:11     ` Bhupesh Sharma
2020-06-15 19:11     ` Bhupesh Sharma
2020-07-02 17:14 ` Catalin Marinas
2020-07-02 17:14   ` Catalin Marinas
2020-07-02 17:14   ` Catalin Marinas
2020-07-02 17:14   ` Catalin Marinas
2020-07-02 18:43   ` Bhupesh Sharma
2020-07-02 18:43     ` Bhupesh Sharma
2020-07-02 18:43     ` Bhupesh Sharma
2020-07-02 18:43     ` Bhupesh Sharma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200702110003.GC22241@gaia \
    --to=catalin.marinas@arm.com \
    --cc=anderson@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=bhsharma@redhat.com \
    --cc=bhupesh.linux@gmail.com \
    --cc=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=k-hagio@ab.jp.nec.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.