From: Andrew Jones <ajones@ventanamicro.com>
To: Fei Wu <fei2.wu@intel.com>
Cc: palmer@dabbelt.com, alistair.francis@wdc.com,
bin.meng@windriver.com, liweiwei@iscas.ac.cn,
dbarboza@ventanamicro.com, zhiwei_liu@linux.alibaba.com,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
Andrei Warkentin <andrei.warkentin@intel.com>
Subject: Re: [PATCH] hw/riscv: split RAM into low and high memory
Date: Thu, 3 Aug 2023 18:07:03 +0300 [thread overview]
Message-ID: <20230803-3855259bbabb934c247c5607@orel> (raw)
In-Reply-To: <20230731015317.1026996-1-fei2.wu@intel.com>
On Mon, Jul 31, 2023 at 09:53:17AM +0800, Fei Wu wrote:
> riscv virt platform's memory started at 0x80000000 and
> straddled the 4GiB boundary. Curiously enough, this choice
> of a memory layout will prevent from launching a VM with
> a bit more than 2000MiB and PCIe pass-thru on an x86 host, due
> to identity mapping requirements for the MSI doorbell on x86,
> and these (APIC/IOAPIC) live right below 4GiB.
>
> So just split the RAM range into two portions:
> - 1 GiB range from 0x80000000 to 0xc0000000.
> - The remainder at 0x100000000
>
> ...leaving a hole between the ranges.
Can you elaborate on the use case? Maybe provide details of the host
system and the QEMU command line? I'm wondering why we didn't have
any problems with the arm virt machine type. Has nobody tried this
use case with that? Is the use case something valid for riscv, but
not arm?
Thanks,
drew
next prev parent reply other threads:[~2023-08-03 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 1:53 [PATCH] hw/riscv: split RAM into low and high memory Fei Wu
2023-07-31 22:46 ` Daniel Henrique Barboza
2023-08-01 2:34 ` Wu, Fei
2023-08-03 0:45 ` Wu, Fei
2023-09-07 3:17 ` Alistair Francis
2023-09-07 15:57 ` Anup Patel
2023-09-07 15:46 ` Anup Patel
2023-09-08 0:16 ` Wu, Fei
2023-08-03 15:07 ` Andrew Jones [this message]
2023-08-04 9:15 ` Wu, Fei
2023-09-07 7:16 ` Philippe Mathieu-Daudé
2023-09-07 9:10 ` Eric Auger
2023-09-07 10:04 ` Wu, Fei
2023-09-07 13:49 ` Eric Auger
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=20230803-3855259bbabb934c247c5607@orel \
--to=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=andrei.warkentin@intel.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=fei2.wu@intel.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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).