From: "Wu, Fei" <fei2.wu@intel.com>
To: <rick@andestech.com>, <ycliang@andestech.com>,
<bmeng.cn@gmail.com>, <sjg@chromium.org>, <pali@kernel.org>,
<u-boot@lists.denx.de>, <andrei.warkentin@intel.com>,
<sunilvl@ventanamicro.com>, <xypron.glpk@gmx.de>
Subject: Re: [PATCH] riscv: enable multi-range memory layout
Date: Wed, 13 Sep 2023 10:23:14 +0800 [thread overview]
Message-ID: <92e300b3-d4d5-4965-4ed4-ae3974fba279@intel.com> (raw)
In-Reply-To: <20230905100935.428120-1-fei2.wu@intel.com>
On 9/5/2023 6:09 PM, Fei Wu wrote:
> In order to enable PCIe passthrough on qemu riscv, the physical memory
> range between 3GB and 4GB is reserved. Therefore if guest has 4GB ram,
> two ranges are created as [2G, 3G) and [4G, 7G), currently u-boot sets
> ram_top to 4G - 1 if the gd->ram_top is above 4G in
> board_get_usable_ram_top(), but that address is not backed by ram. This
> patch selects the lowest range instead.
>
I think multi-range memory layout is a common requirement, PCIe
passthrough happens to be the first one to require it. Could anyone
please take a look at this patch and give your comments?
Thanks,
Fei.
> Signed-off-by: Fei Wu <fei2.wu@intel.com>
> ---
> arch/riscv/cpu/generic/dram.c | 2 +-
> configs/qemu-riscv64_smode_defconfig | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/riscv/cpu/generic/dram.c b/arch/riscv/cpu/generic/dram.c
> index 44e11bd56c..fb53a57b4e 100644
> --- a/arch/riscv/cpu/generic/dram.c
> +++ b/arch/riscv/cpu/generic/dram.c
> @@ -13,7 +13,7 @@ DECLARE_GLOBAL_DATA_PTR;
>
> int dram_init(void)
> {
> - return fdtdec_setup_mem_size_base();
> + return fdtdec_setup_mem_size_base_lowest();
> }
>
> int dram_init_banksize(void)
> diff --git a/configs/qemu-riscv64_smode_defconfig b/configs/qemu-riscv64_smode_defconfig
> index 1d0f021ade..de08a49dab 100644
> --- a/configs/qemu-riscv64_smode_defconfig
> +++ b/configs/qemu-riscv64_smode_defconfig
> @@ -1,6 +1,6 @@
> CONFIG_RISCV=y
> CONFIG_SYS_MALLOC_LEN=0x800000
> -CONFIG_NR_DRAM_BANKS=1
> +CONFIG_NR_DRAM_BANKS=2
> CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y
> CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x80200000
> CONFIG_ENV_SIZE=0x20000
next prev parent reply other threads:[~2023-09-13 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 10:09 [PATCH] riscv: enable multi-range memory layout Fei Wu
2023-09-13 2:23 ` Wu, Fei [this message]
2023-09-13 5:05 ` Heinrich Schuchardt
2023-09-13 5:59 ` Wu, Fei
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=92e300b3-d4d5-4965-4ed4-ae3974fba279@intel.com \
--to=fei2.wu@intel.com \
--cc=andrei.warkentin@intel.com \
--cc=bmeng.cn@gmail.com \
--cc=pali@kernel.org \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=sunilvl@ventanamicro.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=ycliang@andestech.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