From: Xu Lu <luxu.kernel@bytedance.com>
To: Andrea Parri <parri.andrea@gmail.com>
Cc: linux-riscv@lists.infradead.org, kvm-riscv@lists.infradead.org,
devicetree@vger.kernel.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
conor.dooley@microchip.com, anup@brainfault.org,
atishp@atishpatra.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
christoph.muellner@vrull.eu, heiko@sntech.de,
charlie@rivosinc.com, David.Laight@aculab.com
Subject: Re: [External] Re: [RFC v2 0/2] riscv: Idle thread using Zawrs extension
Date: Fri, 21 Jun 2024 20:09:10 +0800 [thread overview]
Message-ID: <CAPYmKFuS-wJTfZBeVo_AS9PscLC7zSiEDZnRU9NDB5+LYxjNSw@mail.gmail.com> (raw)
In-Reply-To: <ZnVhIi0Jre77i3RN@andrea>
On Fri, Jun 21, 2024 at 7:17 PM Andrea Parri <parri.andrea@gmail.com> wrote:
>
> > This is the second version of idle thread based on Zawrs extension. We
> > rebased our code on Andrew's patch series[1] which provides basic
> > support for Zawrs as well as optimization for spinlock.
>
> There's some feedback on Andrew's v2 [1] which seems to equally apply
> to the later, mentioned series/submission, and hence to the series in
> question (although only indirectly admittedly).
>
> As an additional comment, please do add linux-kernel@vger.kernel.org
> (the LKML) to your Cc: list on patch submission (again, this applies
> to both Andrew's and the present submissions).
>
> Andrea
>
> [1] https://lore.kernel.org/linux-riscv/ZiWCP6f6zZ3dKXfN@andrea/
Hi Andrea,
Thanks a lot for your reminder. I will check the feedback and add this
email in the next patch series!
Xu Lu
prev parent reply other threads:[~2024-06-21 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 9:32 [RFC v2 0/2] riscv: Idle thread using Zawrs extension Xu Lu
2024-06-21 9:32 ` [RFC v2 1/2] riscv: process: Introduce idle " Xu Lu
2024-06-21 9:32 ` [RFC v2 2/2] riscv: Use Zawrs to accelerate IPI to idle cpu Xu Lu
2024-06-21 11:16 ` [RFC v2 0/2] riscv: Idle thread using Zawrs extension Andrea Parri
2024-06-21 11:24 ` Andrea Parri
2024-06-21 12:09 ` Xu Lu [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=CAPYmKFuS-wJTfZBeVo_AS9PscLC7zSiEDZnRU9NDB5+LYxjNSw@mail.gmail.com \
--to=luxu.kernel@bytedance.com \
--cc=David.Laight@aculab.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=charlie@rivosinc.com \
--cc=christoph.muellner@vrull.eu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=parri.andrea@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@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 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).