All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: Alistair Francis <alistair.francis@wdc.com>,
	qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Igor Mammedov" <imammedo@redhat.com>
Subject: [PATCH v2 0/6] hw/riscv: Use MachineState::ram and MachineClass::default_ram_id in all machines
Date: Wed, 20 Oct 2021 09:41:06 +0800	[thread overview]
Message-ID: <20211020014112.7336-1-bmeng.cn@gmail.com> (raw)

As of today, all RISC-V machines (except virt) are still using memory_region_init_ram()
to initilize the sysytem RAM, which can't possibly handle vhost-user, and can't
work as expected with '-numa node,memdev' options.

Change to use MachineState::ram instead of manually initializing RAM memory
region, as well as by providing MachineClass::default_ram_id to opt in to
memdev scheme.

Changes in v2:
- split RAM into low and high regions using aliases to machine->ram
- rename mc->default_ram_id to "microchip.icicle.kit.ram"
- opentitan: add RAM size check
- opentitan: assign mc->default_ram_size
- sifive_e: add RAM size check
- sifive_e: assign mc->default_ram_size

Bin Meng (6):
  hw/riscv: microchip_pfsoc: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: opentitan: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: shakti_c: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: sifive_e: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: sifive_u: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: spike: Use MachineState::ram and
    MachineClass::default_ram_id

 hw/riscv/microchip_pfsoc.c | 36 ++++++++++++++++++++----------------
 hw/riscv/opentitan.c       | 16 ++++++++++++----
 hw/riscv/shakti_c.c        |  6 ++----
 hw/riscv/sifive_e.c        | 16 ++++++++++++----
 hw/riscv/sifive_u.c        |  6 ++----
 hw/riscv/spike.c           |  6 ++----
 6 files changed, 50 insertions(+), 36 deletions(-)

-- 
2.25.1



WARNING: multiple messages have this Message-ID (diff)
From: Bin Meng <bmeng.cn@gmail.com>
To: Alistair Francis <alistair.francis@wdc.com>,
	qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: "Igor Mammedov" <imammedo@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH v2 0/6] hw/riscv: Use MachineState::ram and MachineClass::default_ram_id in all machines
Date: Wed, 20 Oct 2021 09:41:06 +0800	[thread overview]
Message-ID: <20211020014112.7336-1-bmeng.cn@gmail.com> (raw)

As of today, all RISC-V machines (except virt) are still using memory_region_init_ram()
to initilize the sysytem RAM, which can't possibly handle vhost-user, and can't
work as expected with '-numa node,memdev' options.

Change to use MachineState::ram instead of manually initializing RAM memory
region, as well as by providing MachineClass::default_ram_id to opt in to
memdev scheme.

Changes in v2:
- split RAM into low and high regions using aliases to machine->ram
- rename mc->default_ram_id to "microchip.icicle.kit.ram"
- opentitan: add RAM size check
- opentitan: assign mc->default_ram_size
- sifive_e: add RAM size check
- sifive_e: assign mc->default_ram_size

Bin Meng (6):
  hw/riscv: microchip_pfsoc: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: opentitan: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: shakti_c: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: sifive_e: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: sifive_u: Use MachineState::ram and
    MachineClass::default_ram_id
  hw/riscv: spike: Use MachineState::ram and
    MachineClass::default_ram_id

 hw/riscv/microchip_pfsoc.c | 36 ++++++++++++++++++++----------------
 hw/riscv/opentitan.c       | 16 ++++++++++++----
 hw/riscv/shakti_c.c        |  6 ++----
 hw/riscv/sifive_e.c        | 16 ++++++++++++----
 hw/riscv/sifive_u.c        |  6 ++----
 hw/riscv/spike.c           |  6 ++----
 6 files changed, 50 insertions(+), 36 deletions(-)

-- 
2.25.1



             reply	other threads:[~2021-10-20  1:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  1:41 Bin Meng [this message]
2021-10-20  1:41 ` [PATCH v2 0/6] hw/riscv: Use MachineState::ram and MachineClass::default_ram_id in all machines Bin Meng
2021-10-20  1:41 ` [PATCH v2 1/6] hw/riscv: microchip_pfsoc: Use MachineState::ram and MachineClass::default_ram_id Bin Meng
2021-10-20  1:41   ` Bin Meng
2021-10-20 23:06   ` Alistair Francis
2021-10-20 23:06     ` Alistair Francis
2021-10-21  8:48   ` Igor Mammedov
2021-10-21  8:48     ` Igor Mammedov
2021-10-20  1:41 ` [PATCH v2 2/6] hw/riscv: opentitan: " Bin Meng
2021-10-20  1:41   ` Bin Meng
2021-10-20 13:01   ` Philippe Mathieu-Daudé
2021-10-20 23:10   ` Alistair Francis
2021-10-20 23:10     ` Alistair Francis
2021-10-21  8:44   ` Igor Mammedov
2021-10-21  8:44     ` Igor Mammedov
2021-10-20  1:41 ` [PATCH v2 3/6] hw/riscv: shakti_c: " Bin Meng
2021-10-20  1:41   ` Bin Meng
2021-10-20 23:11   ` Alistair Francis
2021-10-20 23:11     ` Alistair Francis
2021-10-20  1:41 ` [PATCH v2 4/6] hw/riscv: sifive_e: " Bin Meng
2021-10-20  1:41   ` Bin Meng
2021-10-20 13:02   ` Philippe Mathieu-Daudé
2021-10-20 23:12   ` Alistair Francis
2021-10-20 23:12     ` Alistair Francis
2021-10-21  8:43   ` Igor Mammedov
2021-10-21  8:43     ` Igor Mammedov
2021-10-20  1:41 ` [PATCH v2 5/6] hw/riscv: sifive_u: " Bin Meng
2021-10-20  1:41   ` Bin Meng
2021-10-20 23:12   ` Alistair Francis
2021-10-20 23:12     ` Alistair Francis
2021-10-20  1:41 ` [PATCH v2 6/6] hw/riscv: spike: " Bin Meng
2021-10-20  1:41   ` Bin Meng
2021-10-20 23:13   ` Alistair Francis
2021-10-20 23:13     ` Alistair Francis
2021-10-21 21:58 ` [PATCH v2 0/6] hw/riscv: Use MachineState::ram and MachineClass::default_ram_id in all machines Alistair Francis
2021-10-21 21:58   ` Alistair Francis

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=20211020014112.7336-1-bmeng.cn@gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=imammedo@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.