From: Andrew Jones <andrew.jones@linux.dev>
To: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org
Cc: atishp@rivosinc.com, cade.richard@berkeley.edu, jamestiotio@gmail.com
Subject: Re: [kvm-unit-tests PATCH 0/3] riscv: Improve on-cpu and IPI support
Date: Tue, 3 Sep 2024 15:41:12 +0200 [thread overview]
Message-ID: <20240903-97ba8bde2c3c7c1ca97d3bdc@orel> (raw)
In-Reply-To: <20240830101221.2202707-5-andrew.jones@linux.dev>
On Fri, Aug 30, 2024 at 12:12:22PM GMT, Andrew Jones wrote:
> The first two patches improve general library support for cpumasks and
> the on-cpus API. on-cpus can now take cpumasks for input. The last patch
> improves support for sending IPIs on riscv using the SBI IPI extension
> by supporting a nicer interface of cpuids and cpumasks.
>
> Andrew Jones (3):
> lib/cpumask: Fix and simplify a few functions
> lib/on-cpus: Introduce on_cpumask and on_cpumask_async
> riscv: Introduce SBI IPI convenience functions
>
> lib/cpumask.h | 47 +++++++++++++++++----------------------------
> lib/on-cpus.c | 35 +++++++++++++++++++++++++--------
> lib/on-cpus.h | 3 +++
> lib/riscv/asm/sbi.h | 3 +++
> lib/riscv/sbi.c | 43 +++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 94 insertions(+), 37 deletions(-)
>
> --
> 2.45.2
Queued on riscv/sbi, https://gitlab.com/jones-drew/kvm-unit-tests/-/commits/riscv%2Fsbi
prev parent reply other threads:[~2024-09-03 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 10:12 [kvm-unit-tests PATCH 0/3] riscv: Improve on-cpu and IPI support Andrew Jones
2024-08-30 10:12 ` [kvm-unit-tests PATCH 1/3] lib/cpumask: Fix and simplify a few functions Andrew Jones
2024-08-30 10:12 ` [kvm-unit-tests PATCH 2/3] lib/on-cpus: Introduce on_cpumask and on_cpumask_async Andrew Jones
2024-08-30 10:12 ` [kvm-unit-tests PATCH 3/3] riscv: Introduce SBI IPI convenience functions Andrew Jones
2024-08-30 11:01 ` [kvm-unit-tests PATCH 4/3] riscv: Provide helpers for IPIs Andrew Jones
2024-09-03 13:41 ` Andrew Jones [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=20240903-97ba8bde2c3c7c1ca97d3bdc@orel \
--to=andrew.jones@linux.dev \
--cc=atishp@rivosinc.com \
--cc=cade.richard@berkeley.edu \
--cc=jamestiotio@gmail.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.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