From: patchwork-bot+linux-riscv@kernel.org
To: yunhui cui <cuiyunhui@bytedance.com>
Cc: linux-riscv@lists.infradead.org, apatel@ventanamicro.com,
atishp@rivosinc.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
samuel.holland@sifive.com, alexghiti@rivosinc.com,
jassisinghbrar@gmail.com, takakura@valinux.co.jp,
valentina.fernandezalanis@microchip.com, ruanjinjie@huawei.com,
charlie@rivosinc.com, conor.dooley@microchip.com,
haibo1.xu@intel.com, andybnac@gmail.com, ke.zhao@shingroup.cn,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: print hartid on bringup
Date: Thu, 03 Apr 2025 16:20:41 +0000 [thread overview]
Message-ID: <174369724199.2563936.8945479042100583382.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250303083424.14309-1-cuiyunhui@bytedance.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Mon, 3 Mar 2025 16:34:24 +0800 you wrote:
> Firmware randomly releases cores, so CPU numbers don't linearly map
> to hartids. When the system has an exception, we care more about hartids.
> Adding "dyndbg="file smpboot.c +p" loglevel=8" to the cmdline can output
> the hartid.
>
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
>
> [...]
Here is the summary with links:
- [v2] riscv: print hartid on bringup
https://git.kernel.org/riscv/c/a3313375e88e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-04-03 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 8:34 [PATCH v2] riscv: print hartid on bringup Yunhui Cui
2025-03-25 9:59 ` Alexandre Ghiti
2025-04-03 16:20 ` patchwork-bot+linux-riscv [this message]
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=174369724199.2563936.8945479042100583382.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=charlie@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=cuiyunhui@bytedance.com \
--cc=haibo1.xu@intel.com \
--cc=jassisinghbrar@gmail.com \
--cc=ke.zhao@shingroup.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ruanjinjie@huawei.com \
--cc=samuel.holland@sifive.com \
--cc=takakura@valinux.co.jp \
--cc=tglx@linutronix.de \
--cc=valentina.fernandezalanis@microchip.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