All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: wangkefeng.wang@huawei.com, horms@verge.net.au,
	ard.biesheuvel@linaro.org, catalin.marinas@arm.com,
	will.deacon@arm.com, linux-kernel@vger.kernel.org,
	rppt@linux.ibm.com, linux-mm@kvack.org,
	takahiro.akashi@linaro.org, mingo@redhat.com, bp@alien8.de,
	ebiederm@xmission.com, kexec@lists.infradead.org,
	tglx@linutronix.de, akpm@linux-foundation.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c
Date: Wed, 10 Apr 2019 09:09:14 +0200	[thread overview]
Message-ID: <20190410070914.GA10935@gmail.com> (raw)
In-Reply-To: <20190409102819.121335-2-chenzhou10@huawei.com>


* Chen Zhou <chenzhou10@huawei.com> wrote:

> In preparation for supporting more than one crash kernel regions
> in arm64 as x86_64 does, move reserve_crashkernel_low() into
> kexec/kexec_core.c.
> 
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
> ---
>  arch/x86/include/asm/kexec.h |  3 ++
>  arch/x86/kernel/setup.c      | 66 +++++---------------------------------------
>  include/linux/kexec.h        |  1 +
>  kernel/kexec_core.c          | 53 +++++++++++++++++++++++++++++++++++
>  4 files changed, 64 insertions(+), 59 deletions(-)

No objections for this to be merged via the ARM tree, as long as x86 
functionality is kept intact.

Thanks,

	Ingo

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

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: wangkefeng.wang@huawei.com, horms@verge.net.au,
	ard.biesheuvel@linaro.org, catalin.marinas@arm.com,
	will.deacon@arm.com, linux-kernel@vger.kernel.org,
	rppt@linux.ibm.com, linux-mm@kvack.org,
	takahiro.akashi@linaro.org, mingo@redhat.com, bp@alien8.de,
	ebiederm@xmission.com, kexec@lists.infradead.org,
	tglx@linutronix.de, akpm@linux-foundation.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c
Date: Wed, 10 Apr 2019 09:09:14 +0200	[thread overview]
Message-ID: <20190410070914.GA10935@gmail.com> (raw)
In-Reply-To: <20190409102819.121335-2-chenzhou10@huawei.com>


* Chen Zhou <chenzhou10@huawei.com> wrote:

> In preparation for supporting more than one crash kernel regions
> in arm64 as x86_64 does, move reserve_crashkernel_low() into
> kexec/kexec_core.c.
> 
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
> ---
>  arch/x86/include/asm/kexec.h |  3 ++
>  arch/x86/kernel/setup.c      | 66 +++++---------------------------------------
>  include/linux/kexec.h        |  1 +
>  kernel/kexec_core.c          | 53 +++++++++++++++++++++++++++++++++++
>  4 files changed, 64 insertions(+), 59 deletions(-)

No objections for this to be merged via the ARM tree, as long as x86 
functionality is kept intact.

Thanks,

	Ingo

_______________________________________________
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: Ingo Molnar <mingo@kernel.org>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	ebiederm@xmission.com, rppt@linux.ibm.com,
	catalin.marinas@arm.com, will.deacon@arm.com,
	akpm@linux-foundation.org, ard.biesheuvel@linaro.org,
	horms@verge.net.au, takahiro.akashi@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	linux-mm@kvack.org, wangkefeng.wang@huawei.com
Subject: Re: [PATCH v3 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c
Date: Wed, 10 Apr 2019 09:09:14 +0200	[thread overview]
Message-ID: <20190410070914.GA10935@gmail.com> (raw)
In-Reply-To: <20190409102819.121335-2-chenzhou10@huawei.com>


* Chen Zhou <chenzhou10@huawei.com> wrote:

> In preparation for supporting more than one crash kernel regions
> in arm64 as x86_64 does, move reserve_crashkernel_low() into
> kexec/kexec_core.c.
> 
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
> ---
>  arch/x86/include/asm/kexec.h |  3 ++
>  arch/x86/kernel/setup.c      | 66 +++++---------------------------------------
>  include/linux/kexec.h        |  1 +
>  kernel/kexec_core.c          | 53 +++++++++++++++++++++++++++++++++++
>  4 files changed, 64 insertions(+), 59 deletions(-)

No objections for this to be merged via the ARM tree, as long as x86 
functionality is kept intact.

Thanks,

	Ingo


  reply	other threads:[~2019-04-10  7:09 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 10:28 [PATCH v3 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2019-04-09 10:28 ` Chen Zhou
2019-04-09 10:28 ` Chen Zhou
2019-04-09 10:28 ` [PATCH v3 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c Chen Zhou
2019-04-09 10:28   ` Chen Zhou
2019-04-09 10:28   ` Chen Zhou
2019-04-10  7:09   ` Ingo Molnar [this message]
2019-04-10  7:09     ` Ingo Molnar
2019-04-10  7:09     ` Ingo Molnar
2019-04-11 12:32     ` Chen Zhou
2019-04-11 12:32       ` Chen Zhou
2019-04-11 12:32       ` Chen Zhou
2019-04-12  7:00       ` Ingo Molnar
2019-04-12  7:00         ` Ingo Molnar
2019-04-12  7:00         ` Ingo Molnar
2019-04-09 10:28 ` [PATCH v3 2/4] arm64: kdump: support reserving crashkernel above 4G Chen Zhou
2019-04-09 10:28   ` Chen Zhou
2019-04-09 10:28   ` Chen Zhou
2019-04-09 10:28 ` [PATCH v3 3/4] arm64: kdump: support more than one crash kernel regions Chen Zhou
2019-04-09 10:28   ` Chen Zhou
2019-04-09 10:28   ` Chen Zhou
2019-04-10 13:09   ` Mike Rapoport
2019-04-10 13:09     ` Mike Rapoport
2019-04-10 13:09     ` Mike Rapoport
2019-04-11 12:17     ` Chen Zhou
2019-04-11 12:17       ` Chen Zhou
2019-04-11 12:17       ` Chen Zhou
2019-04-13  8:14       ` Chen Zhou
2019-04-13  8:14         ` Chen Zhou
2019-04-13  8:14         ` Chen Zhou
2019-04-14 12:10       ` Mike Rapoport
2019-04-14 12:10         ` Mike Rapoport
2019-04-14 12:10         ` Mike Rapoport
2019-04-15  2:05         ` Chen Zhou
2019-04-15  2:05           ` Chen Zhou
2019-04-15  2:05           ` Chen Zhou
2019-04-15  5:04           ` Mike Rapoport
2019-04-15  5:04             ` Mike Rapoport
2019-04-15  5:04             ` Mike Rapoport
2019-04-14 12:13   ` Mike Rapoport
2019-04-14 12:13     ` Mike Rapoport
2019-04-14 12:13     ` Mike Rapoport
2019-04-15  2:27     ` Chen Zhou
2019-04-15  2:27       ` Chen Zhou
2019-04-15  2:27       ` Chen Zhou
2019-04-15  4:55       ` Mike Rapoport
2019-04-15  4:55         ` Mike Rapoport
2019-04-15  4:55         ` Mike Rapoport
2019-04-09 10:28 ` [PATCH v3 4/4] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2019-04-09 10:28   ` Chen Zhou
2019-04-09 10:28   ` Chen Zhou

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=20190410070914.GA10935@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=chenzhou10@huawei.com \
    --cc=ebiederm@xmission.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=rppt@linux.ibm.com \
    --cc=takahiro.akashi@linaro.org \
    --cc=tglx@linutronix.de \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will.deacon@arm.com \
    /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.