From: Alistair Francis <alistair23@gmail.com>
To: Anup Patel <anup.patel@wdc.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Anup Patel <anup@brainfault.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Atish Patra <atish.patra@wdc.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH 0/4] RISC-V multi-socket support
Date: Tue, 19 May 2020 14:20:25 -0700 [thread overview]
Message-ID: <CAKmqyKNURMfx+ONV02DLiJxkMaX7_FCdoNjnUhtqnsvKpty8PA@mail.gmail.com> (raw)
In-Reply-To: <20200516063746.18296-1-anup.patel@wdc.com>
On Fri, May 15, 2020 at 11:40 PM Anup Patel <anup.patel@wdc.com> wrote:
>
> This series adds multi-socket support for RISC-V virt machine and
> RISC-V spike machine. The multi-socket support will help us improve
> various RISC-V operating systems, firmwares, and bootloader to
> support RISC-V NUMA systems.
>
> These patch can be found in riscv_multi_socket_v1 branch at:
> https://github.com/avpatel/qemu.git
>
> To try this patches, we will need:
> 1. OpenSBI multi-PLIC and multi-CLINT support which can be found in
> multi_plic_clint_v1 branch at:
> https://github.com/avpatel/opensbi.git
> 2. Linux multi-PLIC improvements support which can be found in
> plic_imp_v1 branch at:
> https://github.com/avpatel/linux.git
>
> Anup Patel (4):
> hw/riscv: Allow creating multiple instances of CLINT
> hw/riscv: spike: Allow creating multiple sockets
> hw/riscv: Allow creating multiple instances of PLIC
> hw/riscv: virt: Allow creating multiple sockets
Can you make sure all the patches pass checkpatch?
Alistair
>
> hw/riscv/sifive_clint.c | 20 +-
> hw/riscv/sifive_e.c | 4 +-
> hw/riscv/sifive_plic.c | 24 +-
> hw/riscv/sifive_u.c | 4 +-
> hw/riscv/spike.c | 210 ++++++++------
> hw/riscv/virt.c | 495 ++++++++++++++++++--------------
> include/hw/riscv/sifive_clint.h | 7 +-
> include/hw/riscv/sifive_plic.h | 12 +-
> include/hw/riscv/spike.h | 8 +-
> include/hw/riscv/virt.h | 12 +-
> 10 files changed, 458 insertions(+), 338 deletions(-)
>
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2020-05-19 21:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 6:37 [PATCH 0/4] RISC-V multi-socket support Anup Patel
2020-05-16 6:37 ` [PATCH 1/4] hw/riscv: Allow creating multiple instances of CLINT Anup Patel
2020-05-19 21:21 ` Alistair Francis
2020-05-21 20:16 ` Palmer Dabbelt
2020-05-16 6:37 ` [PATCH 2/4] hw/riscv: spike: Allow creating multiple sockets Anup Patel
2020-05-21 20:16 ` Palmer Dabbelt
2020-05-22 10:09 ` Anup Patel
2020-05-27 0:38 ` Alistair Francis
2020-05-27 2:54 ` Anup Patel
2020-05-27 3:30 ` Alistair Francis
2020-05-27 3:59 ` Anup Patel
2020-05-16 6:37 ` [PATCH 3/4] hw/riscv: Allow creating multiple instances of PLIC Anup Patel
2020-05-21 20:16 ` Palmer Dabbelt
2020-05-21 21:59 ` Alistair Francis
2020-05-16 6:37 ` [PATCH 4/4] hw/riscv: virt: Allow creating multiple sockets Anup Patel
2020-05-21 20:16 ` Palmer Dabbelt
2020-05-16 11:58 ` [PATCH 0/4] RISC-V multi-socket support no-reply
2020-05-19 21:20 ` Alistair Francis [this message]
2020-05-20 8:50 ` Anup Patel
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=CAKmqyKNURMfx+ONV02DLiJxkMaX7_FCdoNjnUhtqnsvKpty8PA@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=anup.patel@wdc.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=palmer@dabbelt.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).