From: guoren@kernel.org
To: xianting.tian@linux.alibaba.com, palmer@dabbelt.com,
heiko@sntech.de, guoren@kernel.org, conor.dooley@microchip.com
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, liaochang1@huawei.com,
mick@ics.forth.gr, jszhang@kernel.org,
Guo Ren <guoren@linux.alibaba.com>
Subject: [PATCH V2 0/2] riscv: kexec: Fixup crash_save percpu and machine_kexec_mask_interrupts
Date: Wed, 17 Aug 2022 12:12:56 -0400 [thread overview]
Message-ID: <20220817161258.748836-1-guoren@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
Current riscv kexec can't crash_save percpu states and disable
interrupts properly. The patch series fix them, make kexec work correct.
Changes in v2:
- Add Fixes tags
- Remove extern from bool smp_crash_stop_failed(void)
v1: https://lore.kernel.org/linux-riscv/20220816012701.561435-1-guoren@kernel.org/
Guo Ren (2):
riscv: kexec: Disable all interrupts in kexec crash path
riscv: kexec: Fixup crash_smp_send_stop with percpu crash_save_cpu
arch/riscv/include/asm/smp.h | 6 +++
arch/riscv/kernel/machine_kexec.c | 44 +++++++++++----
arch/riscv/kernel/smp.c | 89 ++++++++++++++++++++++++++++++-
3 files changed, 126 insertions(+), 13 deletions(-)
--
2.36.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-08-17 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 16:12 guoren [this message]
2022-08-17 16:12 ` [PATCH V2 1/2] riscv: kexec: Disable all interrupts in kexec crash path guoren
2022-08-18 4:38 ` Xianting Tian
2022-08-17 16:12 ` [PATCH V2 2/2] riscv: kexec: Fixup crash_smp_send_stop with percpu crash_save_cpu guoren
2022-08-18 4:38 ` Xianting Tian
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=20220817161258.748836-1-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--cc=liaochang1@huawei.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=xianting.tian@linux.alibaba.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).