public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guo Ren <guoren@kernel.org>
To: wangruikang@iscas.ac.cn
Cc: alex@ghiti.fr, gaohan@iscas.ac.cn, guoren@kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	palmer@dabbelt.com, pjw@kernel.org
Subject: Re: Re: [PATCH] riscv: mm: Do not probe satp mode limit if known in FDT
Date: Sat, 25 Apr 2026 06:32:23 +0000	[thread overview]
Message-ID: <20260425063223.3329222-1-guoren@kernel.org> (raw)
In-Reply-To: <0e139862-d41b-4b46-92f6-a1eb5bffc863@iscas.ac.cn>

> Sorry for the trouble, it seems that some miscommunication has occurred.
> While I was able to reproduce this problem in an emulator, I do not have
> access to this hardware and had misunderstood the context and the nature
> of this platform.

I also found this issue in QEMU. It can be easily reproduced with the
following modification:

diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
index a1c323e66d..8c1d92c8dd 100644
--- a/hw/riscv/virt.c
+++ b/hw/riscv/virt.c
@@ -100,7 +100,7 @@ static const MemMapEntry virt_memmap[] = {
     [VIRT_IMSIC_S] =      { 0x28000000, VIRT_IMSIC_MAX_SIZE },
     [VIRT_PCIE_ECAM] =    { 0x30000000,    0x10000000 },
     [VIRT_PCIE_MMIO] =    { 0x40000000,    0x40000000 },
-    [VIRT_DRAM] =         { 0x80000000,           0x0 },
+    [VIRT_DRAM] =         { 0x800000000000,           0x0 },
 };

Best Regards
  GUO Ren

      reply	other threads:[~2026-04-25  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24  3:03 [PATCH] riscv: mm: Do not probe satp mode limit if known in FDT Vivian Wang
2026-04-25  2:02 ` Guo Ren
2026-04-25  5:23   ` Vivian Wang
2026-04-25  6:32     ` Guo Ren [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=20260425063223.3329222-1-guoren@kernel.org \
    --to=guoren@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=gaohan@iscas.ac.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=wangruikang@iscas.ac.cn \
    /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