From: Baoquan He <bhe@redhat.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, piliu@redhat.com,
linux-sh@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, ebiederm@xmission.com,
loongarch@lists.linux.dev, linux-riscv@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, akpm@linux-foundation.org,
linux-arm-kernel@lists.infradead.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v2 00/14] Split crash out from kexec and clean up related config items
Date: Wed, 21 Feb 2024 21:44:04 +0800 [thread overview]
Message-ID: <ZdX+JMKsQWheE0B0@MiWiFi-R3L-srv> (raw)
In-Reply-To: <559f2595-1477-4ef0-80e4-85ae8b426de7@linux.ibm.com>
On 02/21/24 at 11:15am, Hari Bathini wrote:
> Hi Baoquan,
>
> On 04/02/24 8:56 am, Baoquan He wrote:
> > > > Hope Hari and Pingfan can help have a look, see if
> > > > it's doable. Now, I make it either have both kexec and crash enabled, or
> > > > disable both of them altogether.
> > >
> > > Sure. I will take a closer look...
> > Thanks a lot. Please feel free to post patches to make that, or I can do
> > it with your support or suggestion.
>
> Tested your changes and on top of these changes, came up with the below
> changes to get it working for powerpc:
>
>
> https://lore.kernel.org/all/20240213113150.1148276-1-hbathini@linux.ibm.com/
>
> Please take a look.
I added a comment to the patch 1 consulting if the "struct crash_mem" is
appropriate to cover other cases except of kdump memory regions. I am
wondering if its name need be adjusted, or other kind of memory you
mentioned can use other structures or create a new one.
If it's has to be done like that, it's fine.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, piliu@redhat.com,
linux-sh@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, ebiederm@xmission.com,
loongarch@lists.linux.dev, linux-riscv@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, akpm@linux-foundation.org,
linux-arm-kernel@lists.infradead.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v2 00/14] Split crash out from kexec and clean up related config items
Date: Wed, 21 Feb 2024 21:44:04 +0800 [thread overview]
Message-ID: <ZdX+JMKsQWheE0B0@MiWiFi-R3L-srv> (raw)
In-Reply-To: <559f2595-1477-4ef0-80e4-85ae8b426de7@linux.ibm.com>
On 02/21/24 at 11:15am, Hari Bathini wrote:
> Hi Baoquan,
>
> On 04/02/24 8:56 am, Baoquan He wrote:
> > > > Hope Hari and Pingfan can help have a look, see if
> > > > it's doable. Now, I make it either have both kexec and crash enabled, or
> > > > disable both of them altogether.
> > >
> > > Sure. I will take a closer look...
> > Thanks a lot. Please feel free to post patches to make that, or I can do
> > it with your support or suggestion.
>
> Tested your changes and on top of these changes, came up with the below
> changes to get it working for powerpc:
>
>
> https://lore.kernel.org/all/20240213113150.1148276-1-hbathini@linux.ibm.com/
>
> Please take a look.
I added a comment to the patch 1 consulting if the "struct crash_mem" is
appropriate to cover other cases except of kdump memory regions. I am
wondering if its name need be adjusted, or other kind of memory you
mentioned can use other structures or create a new one.
If it's has to be done like that, it's fine.
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, piliu@redhat.com,
linux-sh@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, ebiederm@xmission.com,
loongarch@lists.linux.dev, linux-riscv@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, akpm@linux-foundation.org,
linux-arm-kernel@lists.infradead.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v2 00/14] Split crash out from kexec and clean up related config items
Date: Wed, 21 Feb 2024 21:44:04 +0800 [thread overview]
Message-ID: <ZdX+JMKsQWheE0B0@MiWiFi-R3L-srv> (raw)
In-Reply-To: <559f2595-1477-4ef0-80e4-85ae8b426de7@linux.ibm.com>
On 02/21/24 at 11:15am, Hari Bathini wrote:
> Hi Baoquan,
>
> On 04/02/24 8:56 am, Baoquan He wrote:
> > > > Hope Hari and Pingfan can help have a look, see if
> > > > it's doable. Now, I make it either have both kexec and crash enabled, or
> > > > disable both of them altogether.
> > >
> > > Sure. I will take a closer look...
> > Thanks a lot. Please feel free to post patches to make that, or I can do
> > it with your support or suggestion.
>
> Tested your changes and on top of these changes, came up with the below
> changes to get it working for powerpc:
>
>
> https://lore.kernel.org/all/20240213113150.1148276-1-hbathini@linux.ibm.com/
>
> Please take a look.
I added a comment to the patch 1 consulting if the "struct crash_mem" is
appropriate to cover other cases except of kdump memory regions. I am
wondering if its name need be adjusted, or other kind of memory you
mentioned can use other structures or create a new one.
If it's has to be done like that, it's fine.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, piliu@redhat.com,
linux-sh@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, ebiederm@xmission.com,
loongarch@lists.linux.dev, linux-riscv@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, akpm@linux-foundation.org,
linux-arm-kernel@lists.infradead.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v2 00/14] Split crash out from kexec and clean up related config items
Date: Wed, 21 Feb 2024 21:44:04 +0800 [thread overview]
Message-ID: <ZdX+JMKsQWheE0B0@MiWiFi-R3L-srv> (raw)
In-Reply-To: <559f2595-1477-4ef0-80e4-85ae8b426de7@linux.ibm.com>
On 02/21/24 at 11:15am, Hari Bathini wrote:
> Hi Baoquan,
>
> On 04/02/24 8:56 am, Baoquan He wrote:
> > > > Hope Hari and Pingfan can help have a look, see if
> > > > it's doable. Now, I make it either have both kexec and crash enabled, or
> > > > disable both of them altogether.
> > >
> > > Sure. I will take a closer look...
> > Thanks a lot. Please feel free to post patches to make that, or I can do
> > it with your support or suggestion.
>
> Tested your changes and on top of these changes, came up with the below
> changes to get it working for powerpc:
>
>
> https://lore.kernel.org/all/20240213113150.1148276-1-hbathini@linux.ibm.com/
>
> Please take a look.
I added a comment to the patch 1 consulting if the "struct crash_mem" is
appropriate to cover other cases except of kdump memory regions. I am
wondering if its name need be adjusted, or other kind of memory you
mentioned can use other structures or create a new one.
If it's has to be done like that, it's fine.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-21 13:44 UTC|newest]
Thread overview: 150+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 14:52 [PATCH v2 00/14] Split crash out from kexec and clean up related config items Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 01/14] kexec: split crashkernel reservation code out from crash_core.c Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-02-21 17:29 ` Sourabh Jain
2024-02-21 17:29 ` Sourabh Jain
2024-02-21 17:29 ` Sourabh Jain
2024-02-21 17:29 ` Sourabh Jain
2024-02-21 17:29 ` Sourabh Jain
2024-02-21 20:12 ` Andrew Morton
2024-02-21 20:12 ` Andrew Morton
2024-02-21 20:12 ` Andrew Morton
2024-02-21 20:12 ` Andrew Morton
2024-02-21 20:12 ` Andrew Morton
2024-01-19 14:52 ` [PATCH v2 02/14] crash: split vmcoreinfo exporting " Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-02-21 17:37 ` Sourabh Jain
2024-02-21 17:37 ` Sourabh Jain
2024-02-21 17:37 ` Sourabh Jain
2024-02-21 17:37 ` Sourabh Jain
2024-02-21 17:37 ` Sourabh Jain
2024-02-22 7:57 ` Baoquan He
2024-02-22 7:57 ` Baoquan He
2024-02-22 7:57 ` Baoquan He
2024-02-22 7:57 ` Baoquan He
2024-02-22 7:57 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 03/14] crash: remove dependency of FA_DUMP on CRASH_DUMP Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 04/14] crash: split crash dumping code out from kexec_core.c Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 05/14] crash: clean up kdump related config items Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 06/14] x86, crash: wrap crash dumping code into crash related ifdefs Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 07/14] arm64, " Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 08/14] ppc, crash: enforce KEXEC and KEXEC_FILE to select CRASH_DUMP Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 09/14] s390, crash: wrap crash dumping code into crash related ifdefs Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 10/14] sh, " Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 11/14] arm, " Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-20 12:13 ` kernel test robot
2024-01-20 12:13 ` kernel test robot
2024-01-20 12:13 ` kernel test robot
2024-01-20 12:13 ` kernel test robot
2024-01-20 12:13 ` kernel test robot
2024-01-21 1:55 ` Baoquan He
2024-01-21 1:55 ` Baoquan He
2024-01-21 1:55 ` Baoquan He
2024-01-21 1:55 ` Baoquan He
2024-01-21 1:55 ` Baoquan He
2024-01-20 13:58 ` kernel test robot
2024-01-20 13:58 ` kernel test robot
2024-01-20 13:58 ` kernel test robot
2024-01-20 13:58 ` kernel test robot
2024-01-20 13:58 ` kernel test robot
2024-01-19 14:52 ` [PATCH v2 12/14] mips, " Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 13/14] riscv, " Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` [PATCH v2 14/14] loongarch, " Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-01-19 14:52 ` Baoquan He
2024-02-02 5:23 ` [PATCH v2 00/14] Split crash out from kexec and clean up related config items Hari Bathini
2024-02-02 5:23 ` Hari Bathini
2024-02-02 5:23 ` Hari Bathini
2024-02-02 5:23 ` Hari Bathini
2024-02-02 5:23 ` Hari Bathini
2024-02-04 3:26 ` Baoquan He
2024-02-04 3:26 ` Baoquan He
2024-02-04 3:26 ` Baoquan He
2024-02-04 3:26 ` Baoquan He
2024-02-04 3:26 ` Baoquan He
2024-02-21 5:45 ` Hari Bathini
2024-02-21 5:45 ` Hari Bathini
2024-02-21 5:45 ` Hari Bathini
2024-02-21 5:45 ` Hari Bathini
2024-02-21 13:44 ` Baoquan He [this message]
2024-02-21 13:44 ` Baoquan He
2024-02-21 13:44 ` Baoquan He
2024-02-21 13:44 ` Baoquan He
2024-02-21 20:57 ` Andrew Morton
2024-02-21 20:57 ` Andrew Morton
2024-02-21 20:57 ` Andrew Morton
2024-02-21 20:57 ` Andrew Morton
2024-02-21 20:57 ` Andrew Morton
2024-02-22 5:17 ` Hari Bathini
2024-02-22 5:17 ` Hari Bathini
2024-02-22 5:17 ` Hari Bathini
2024-02-22 5:17 ` Hari Bathini
2024-02-22 21:29 ` Andrew Morton
2024-02-22 21:29 ` Andrew Morton
2024-02-22 21:29 ` Andrew Morton
2024-02-22 21:29 ` Andrew Morton
2024-02-23 5:41 ` Hari Bathini
2024-02-23 5:41 ` Hari Bathini
2024-02-23 5:41 ` Hari Bathini
2024-02-23 5:41 ` Hari Bathini
2024-02-22 7:07 ` Baoquan He
2024-02-22 7:07 ` Baoquan He
2024-02-22 7:07 ` Baoquan He
2024-02-22 7:07 ` Baoquan He
2024-02-22 7:07 ` Baoquan He
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=ZdX+JMKsQWheE0B0@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=piliu@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--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.