linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wen Xiong <wenxiong@us.ibm.com>
To: Pingfan Liu <piliu@redhat.com>, Michael Ellerman <mpe@ellerman.id.au>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Hari Bathini <hbathini@linux.ibm.com>,
	Pingfan Liu <kernelfans@gmail.com>,
	Ming Lei <ming.lei@redhat.com>
Subject: RE: [RFC PATCH 5/5] powerpc/smp: Remap boot CPU onto core 0 if >= nr_cpu_ids
Date: Tue, 13 Feb 2024 20:16:55 +0000	[thread overview]
Message-ID: <BL0PR1501MB203368E0F789B454F8B94DECF04F2@BL0PR1501MB2033.namprd15.prod.outlook.com> (raw)
In-Reply-To: <CAF+s44QfT+m1hL=Z-wevFhWff=O6DNK=WRxcdjK+p-rK5J=LKQ@mail.gmail.com>

>>And loop in Wen Xiong and Ming Lei, who care for this issue too.


Hi Pingfan, Thanks for your email!

Hi Michael,

Thanks for your new patchset!

In past month, Our several test team have modified /etc/sysconfig/kdump file with nr_cpus=1, triggered kdump over the following IO devices and  kdump works fine with generating vmcore file.

Test kernel:  the latest upstream kernel + your patchset
                      the latest rhel94 kernel + backport of your patchset

Test hardware: Nvme drives, FC adapter, NVmf-over-FC

Test device drivers: nvme, lpfc, nvme-fc

Thanks for your work! Please consideration for inclusion in upstream kernel.

Thanks for your help!
Wendy

> the problems that have been seen. I've tested this fairly thoroughly 
> with a qemu script, and also a few boots on a real machine.
>
> If you can test it with your setups that would be great. Hopefully 
> there isn't some obscure case I've missed.
>
> cheers
>


  reply	other threads:[~2024-02-13 20:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 12:01 [RFC PATCH 1/5] powerpc/smp: Adjust nr_cpu_ids to cover all threads of a core Michael Ellerman
2023-12-29 12:01 ` [RFC PATCH 2/5] powerpc/smp: Increase nr_cpu_ids to include the boot CPU Michael Ellerman
2023-12-29 12:01 ` [RFC PATCH 3/5] powerpc/smp: Lookup avail once per device tree node Michael Ellerman
2023-12-29 12:01 ` [RFC PATCH 4/5] powerpc/smp: Factor out assign_threads() Michael Ellerman
2024-01-02  4:34   ` Aneesh Kumar K.V
2024-02-14 13:10     ` Michael Ellerman
2023-12-29 12:01 ` [RFC PATCH 5/5] powerpc/smp: Remap boot CPU onto core 0 if >= nr_cpu_ids Michael Ellerman
2023-12-29 12:07   ` Michael Ellerman
2024-01-02  0:51     ` Pingfan Liu
2024-02-13 20:16       ` Wen Xiong [this message]
2024-01-02  4:46   ` Aneesh Kumar K.V
2024-02-09 15:56     ` Jiri Bohac
2024-02-14 13:12       ` Michael Ellerman
2024-02-15 13:00 ` [RFC PATCH 1/5] powerpc/smp: Adjust nr_cpu_ids to cover all threads of a core Michael Ellerman
2024-02-16  2:42   ` Pingfan Liu

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=BL0PR1501MB203368E0F789B454F8B94DECF04F2@BL0PR1501MB2033.namprd15.prod.outlook.com \
    --to=wenxiong@us.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=kernelfans@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ming.lei@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=piliu@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).