From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Michael Tokarev" <mjt@tls.msk.ru>,
"Song Gao" <gaosong@loongson.cn>,
"QEMU devel" <qemu-devel@nongnu.org>
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
qemu-stable@nongnu.org
Subject: Re: [PULL 10/10] hw/loongarch/virt: Fix FDT memory node address width
Date: Fri, 24 May 2024 11:54:02 +0100 [thread overview]
Message-ID: <c95587fd-ef45-406d-8e1d-1ce9f680cdaf@app.fastmail.com> (raw)
In-Reply-To: <a53378e3-658b-43b5-8714-9be5a1fec2f3@tls.msk.ru>
在2024年5月24日五月 上午11:10,Michael Tokarev写道:
> 23.05.2024 04:46, Song Gao wrote:
>> From: Jiaxun Yang <jiaxun.yang@flygoat.com>
>>
>> Higher bits for memory nodes were omitted at qemu_fdt_setprop_cells.
>>
>> Cc: qemu-stable@nongnu.org
>> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
>> Reviewed-by: Song Gao <gaosong@loongson.cn>
>> Message-Id: <20240520-loongarch-fdt-memnode-v1-1-5ea9be93911e@flygoat.com>
>> Signed-off-by: Song Gao <gaosong@loongson.cn>
>> ---
>> hw/loongarch/virt.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/loongarch/virt.c b/hw/loongarch/virt.c
>> index e3bdf085b5..3e6e93edf3 100644
>> --- a/hw/loongarch/virt.c
>> +++ b/hw/loongarch/virt.c
>> @@ -464,7 +464,8 @@ static void fdt_add_memory_node(MachineState *ms,
>> char *nodename = g_strdup_printf("/memory@%" PRIx64, base);
>>
>> qemu_fdt_add_subnode(ms->fdt, nodename);
>> - qemu_fdt_setprop_cells(ms->fdt, nodename, "reg", 0, base, 0, size);
>> + qemu_fdt_setprop_cells(ms->fdt, nodename, "reg", base >> 32, base,
>> + size >> 32, size);
>> qemu_fdt_setprop_string(ms->fdt, nodename, "device_type", "memory");
>>
>> if (ms->numa_state && ms->numa_state->num_nodes) {
>
> This commit changes exactly the same place as the previous commit,
> v9.0.0-274-gb11f981452, "hw/loongarch: Fix fdt memory node wrong 'reg'".
>
> Was it the wrong fix?
Yes, I believe previous commit is the wrong fix on the same problem.
>
> Note the previous commit isn't in any released version of qemu. So
> when picking up for any stable release, both needs to be picked up :)
Please go ahead!
Thanks
- Jiaxun
>
> Thanks,
>
> /mjt
> --
> GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
> New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD
> 3D98 ECDF 2C8E
> Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C
> E0A0 8044 65C5
> Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt
--
- Jiaxun
next prev parent reply other threads:[~2024-05-24 10:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 1:46 [PULL 00/10] loongarch-to-apply queue Song Gao
2024-05-23 1:46 ` [PULL 01/10] target/loongarch/kvm: Fix VM recovery from disk failures Song Gao
2024-05-24 10:00 ` Michael Tokarev
2024-05-27 1:54 ` gaosong
2024-05-23 1:46 ` [PULL 02/10] target/loongarch/kvm: fpu save the vreg registers high 192bit Song Gao
2024-05-23 1:46 ` [PULL 03/10] hw/loongarch: Add VM mode in IOCSR feature register in kvm mode Song Gao
2024-05-23 1:46 ` [PULL 04/10] hw/loongarch: Refine acpi srat table for numa memory Song Gao
2024-05-23 1:46 ` [PULL 05/10] hw/loongarch: Refine fadt memory " Song Gao
2024-05-23 1:46 ` [PULL 06/10] hw/loongarch: Refine fwcfg memory map Song Gao
2024-06-07 14:31 ` Peter Maydell
2024-06-11 1:57 ` maobibo
2024-05-23 1:46 ` [PULL 07/10] hw/loongarch: Refine system dram memory region Song Gao
2024-05-23 1:46 ` [PULL 08/10] hw/loongarch: Remove minimum and default memory size Song Gao
2024-05-23 1:46 ` [PULL 09/10] target/loongarch: Add loongarch vector property unconditionally Song Gao
2024-05-23 1:46 ` [PULL 10/10] hw/loongarch/virt: Fix FDT memory node address width Song Gao
2024-05-24 10:10 ` Michael Tokarev
2024-05-24 10:54 ` Jiaxun Yang [this message]
2024-05-23 16:44 ` [PULL 00/10] loongarch-to-apply queue Richard Henderson
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=c95587fd-ef45-406d-8e1d-1ce9f680cdaf@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=gaosong@loongson.cn \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.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 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).