From: Palmer Dabbelt <palmerdabbelt@google.com>
To: Anup Patel <Anup.Patel@wdc.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, pbonzini@redhat.com,
Atish Patra <Atish.Patra@wdc.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
anup@brainfault.org, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, Anup Patel <Anup.Patel@wdc.com>
Subject: Re: [PATCH 0/3] RISC-V KVM preparation
Date: Mon, 04 May 2020 13:01:28 -0700 (PDT) [thread overview]
Message-ID: <mhng-be6b9ad5-d81c-4ae1-9eed-9b2d63600b37@palmerdabbelt-glaptop1> (raw)
In-Reply-To: <20200424045928.79324-1-anup.patel@wdc.com>
On Thu, 23 Apr 2020 21:59:25 PDT (-0700), Anup Patel wrote:
> This patch series is factored-out from the KVM RISC-V v11 series and is
> based upon Linux-5.7-rc2.
>
> These patches are mostly preparatory changes in Linux RISC-V kernel which
> we require for KVM RISC-V implementation. Also, most of these patches are
> already reviewed as part of original KVM RISC-V series.
>
> Anup Patel (3):
> RISC-V: Export riscv_cpuid_to_hartid_mask() API
> RISC-V: Add bitmap reprensenting ISA features common across CPUs
> RISC-V: Remove N-extension related defines
>
> arch/riscv/include/asm/csr.h | 3 --
> arch/riscv/include/asm/hwcap.h | 22 +++++++++
> arch/riscv/kernel/cpufeature.c | 83 ++++++++++++++++++++++++++++++++--
> arch/riscv/kernel/smp.c | 2 +
> 4 files changed, 104 insertions(+), 6 deletions(-)
These are on fixes.
prev parent reply other threads:[~2020-05-04 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 4:59 [PATCH 0/3] RISC-V KVM preparation Anup Patel
2020-04-24 4:59 ` [PATCH 1/3] RISC-V: Export riscv_cpuid_to_hartid_mask() API Anup Patel
2020-04-24 4:59 ` [PATCH 2/3] RISC-V: Add bitmap reprensenting ISA features common across CPUs Anup Patel
2020-04-24 4:59 ` [PATCH 3/3] RISC-V: Remove N-extension related defines Anup Patel
2020-05-04 20:01 ` Palmer Dabbelt [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=mhng-be6b9ad5-d81c-4ae1-9eed-9b2d63600b37@palmerdabbelt-glaptop1 \
--to=palmerdabbelt@google.com \
--cc=Alistair.Francis@wdc.com \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@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).