From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Ziqiao Kong <ziqiaokong@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
alistair.francis@wdc.com, richard.henderson@linaro.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 1/1] target/riscv: fix endless translation loop on big endian systems
Date: Mon, 14 Apr 2025 19:38:03 +0200 [thread overview]
Message-ID: <c566eed5-605f-4aeb-8841-dae4e591fcb3@linaro.org> (raw)
In-Reply-To: <CAM0BWND3dr=_nZHXSoV2jzkXPXd=hViX6vM0cUMZ2Uru+TD6GQ@mail.gmail.com>
Hi,
On 14/4/25 18:59, Ziqiao Kong wrote:
> Hello Philippe,
>
> Any further concern regarding this series? I certainly would like to investigate
> and help =).
Short term I can't keep looking because I'm busy with other stuffs and
tagged this patch for another review, because there is some endianness
code smell in get_physical_address(). I understand your change fixes
your issue, but I'm skeptical about it, in part because there are no
such use in the whole code base. My change suggestion is just a starting
point, more is needed.
>
> Bests,
> Ziqiao
>
> On Mon, Apr 14, 2025 at 7:17 PM Ziqiao Kong <ziqiaokong@gmail.com> wrote:
>>
>> On Mon, Apr 14, 2025 at 6:41 PM Philippe Mathieu-Daudé
>> <philmd@linaro.org> wrote:
>>>
>>> Hi,
>>>
>>> On 14/4/25 05:46, Ziqiao Kong wrote:
>>>> On big endian systems, pte and updated_pte hold big endian host data
>>>> while pte_pa points to little endian target data. This means the branch
>>>> at cpu_helper.c:1669 will be always satisfied and restart translation,
>>>> causing an endless translation loop.
>>>>
>>>
>>> Cc: qemu-stable@nongnu.org
>>> Fixes: 0c3e702aca7 ("RISC-V CPU Helpers")
>>>
>>>> Signed-off-by: Ziqiao Kong <ziqiaokong@gmail.com>
>>>> ---
>>>> target/riscv/cpu_helper.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c
>>>> index 6c4391d96b..bc146771c8 100644
>>>> --- a/target/riscv/cpu_helper.c
>>>> +++ b/target/riscv/cpu_helper.c
>>>> @@ -1662,9 +1662,9 @@ static int get_physical_address(CPURISCVState *env, hwaddr *physical,
>>>> target_ulong *pte_pa = qemu_map_ram_ptr(mr->ram_block, addr1);
>>>> target_ulong old_pte;
>>>> if (riscv_cpu_sxl(env) == MXL_RV32) {
>>>> - old_pte = qatomic_cmpxchg((uint32_t *)pte_pa, pte, updated_pte);
>>>> + old_pte = qatomic_cmpxchg((uint32_t *)pte_pa, cpu_to_le32(pte), cpu_to_le32(updated_pte));
>>>> } else {
>>>> - old_pte = qatomic_cmpxchg(pte_pa, pte, updated_pte);
>>>> + old_pte = qatomic_cmpxchg(pte_pa, cpu_to_le64(pte), cpu_to_le64(updated_pte));
>>>> }
>>>> if (old_pte != pte) {
>>>> goto restart;
>>>
>>> If PTEs are always stored in LE order, maybe what we want is earlier:
>>>
>>> -- >8 --
>>> diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c
>>> index 619c76cc001..b6ac2800240 100644
>>> --- a/target/riscv/cpu_helper.c
>>> +++ b/target/riscv/cpu_helper.c
>>> @@ -1464,5 +1464,5 @@ static int get_physical_address(CPURISCVState
>>> *env, hwaddr *physical,
>>> if (riscv_cpu_mxl(env) == MXL_RV32) {
>>> - pte = address_space_ldl(cs->as, pte_addr, attrs, &res);
>>> + pte = address_space_ldl_le(cs->as, pte_addr, attrs, &res);
>>> } else {
>>> - pte = address_space_ldq(cs->as, pte_addr, attrs, &res);
>>> + pte = address_space_ldq_le(cs->as, pte_addr, attrs, &res);
>>
>> Unfortunately, this doesn't work in two ways:
>>
>> 1. Note pte is used in the following code and that means pte must hold
>> a correct value from the
>> view of host endian (in my case, big endian not little endian).
>> 2. address_space_ldq_le will dispatch to ldq_le_p, while
>> address_space_leq will dispatch to ldq_p.
>> However, on little endian targets, ldq_p is an alias of ldq_le_p so
>> making no effects.
>>
>> Per my testing, this patch doesn't have any effect indeed. To have a
>> brief view what is happening,
>> see the logs just before atomic_cmpxchg:
>>
>> pte_pa 0xf14000000000000 == pte 0x140f ? updated_pte 0x144f
>>
>>> }
>>> ---
next prev parent reply other threads:[~2025-04-14 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 3:46 [PATCH v2 0/1] Fix endless translation loop of riscv Ziqiao Kong
2025-04-14 3:46 ` [PATCH v2 1/1] target/riscv: fix endless translation loop on big endian systems Ziqiao Kong
2025-04-14 10:41 ` Philippe Mathieu-Daudé
2025-04-14 11:17 ` Ziqiao Kong
2025-04-14 16:59 ` Ziqiao Kong
2025-04-14 17:38 ` Philippe Mathieu-Daudé [this message]
[not found] ` <CAM0BWNBNrjJ6UuF+TRtkuEesLatnY1pzSjyaiPVDeKSMF8no-A@mail.gmail.com>
2025-04-15 7:04 ` Ziqiao Kong
2025-04-15 7:15 ` Philippe Mathieu-Daudé
2025-04-15 7:19 ` Ziqiao Kong
2025-04-15 7:22 ` Ziqiao Kong
2025-04-15 7:40 ` Ziqiao Kong
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=c566eed5-605f-4aeb-8841-dae4e591fcb3@linaro.org \
--to=philmd@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=ziqiaokong@gmail.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).