From: Richard Henderson <richard.henderson@linaro.org>
To: gaosong <gaosong@loongson.cn>, qemu-devel@nongnu.org
Cc: maobibo@loongson.cn, philmd@linaro.org
Subject: Re: [PATCH 5/5] target/loongarch/tcg: Add hardware page table walker support
Date: Thu, 5 Sep 2024 12:39:53 -0700 [thread overview]
Message-ID: <2c81231c-4c99-4d6b-96d3-47c7c1e1e576@linaro.org> (raw)
In-Reply-To: <0cc6072a-d251-5d59-73e5-9009856e06a0@loongson.cn>
On 9/5/24 01:27, gaosong wrote:
> How about adding a variable to determine if tlb needs to be modified?
> like this:
>
> @@ -248,7 +250,7 @@ hwaddr loongarch_cpu_get_phys_page_debug(CPUState *cs, vaddr addr)
> int prot;
>
> if (get_physical_address(env, &phys_addr, &prot, addr, MMU_DATA_LOAD,
> - cpu_mmu_index(cs, false)) != 0) {
> + cpu_mmu_index(cs, false) != 0, false)) {
> return -1;
> }
Yes, that sort of thing. In other targets the flags is called 'debug'.
>>> + entry = ldq_phys(cs->as, tmp0) & TARGET_PHYS_MASK;
>>> +
>>> + if (entry == 0) {
>>> + return ret;
>>> + }
>>> +
>>> + /* Check entry, and do tlb modify. */
>>> + if ((tlb_error == TLBRET_INVALID) &&
>>> + (access_type == MMU_DATA_LOAD ||
>>> + access_type == MMU_INST_FETCH )) {
>>> + if (!(FIELD_EX64(entry, TLBENTRY, PRESENT))) {
>>> + break;
>>> + }
>>> + entry = FIELD_DP64(entry, TLBENTRY, V, 1);
>>> + } else if ((tlb_error == TLBRET_INVALID) &&
>>> + access_type == MMU_DATA_STORE) {
>>> + if (!((FIELD_EX64(entry, TLBENTRY, PRESENT) &&
>>> + (FIELD_EX64(entry, TLBENTRY, WRITE))))){
>>> + break;
>>> + }
>>> + entry = FIELD_DP64(entry, TLBENTRY, V, 1);
>>> + entry = FIELD_DP64(entry, TLBENTRY, D, 1);
>>> + } else if (tlb_error == TLBRET_DIRTY) {
>>> + if (!(FIELD_EX64(entry, TLBENTRY, WRITE))) {
>>> + break;
>>> + }
>>> + entry = FIELD_DP64(entry, TLBENTRY, D, 1);
>>> + entry = FIELD_DP64(entry, TLBENTRY, V, 1);
>>> + }
>>> + stq_phys(cs->as, tmp0, entry);
>>
>> You certainly want to use a compare and swap here, restarting if the compare fails.
>>
> Sorry , I don't understand here, could you explain it in detail?
A plain store will have an smp race condition with the guest kernel.
The update needs to be atomic.
Compare:
target/arm/ptw.c, arm_casq_ptw()
target/riscv/cpu_helper.c, get_physical_address(), s/cmpxchg/
target/i386/tcg/sysemu/excp_helper.c, ptw_setl()
r~
prev parent reply other threads:[~2024-09-05 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 1:39 [PATCH 0/5] LoongArch/tcg: Add hardware page table walker support Song Gao
2024-07-29 1:39 ` [PATCH 1/5] target/loongarch: Add a new cpu_type la664 Song Gao
2024-09-05 10:32 ` Philippe Mathieu-Daudé
2024-09-05 12:29 ` gaosong
2024-07-29 1:39 ` [PATCH 2/5] target/loongarch: Add do_lddir/ldpte() Song Gao
2024-07-29 1:39 ` [PATCH 3/5] target/loongarch: Add do_fill_tlb_entry() Song Gao
2024-07-29 1:39 ` [PATCH 4/5] target/loongarch: Add get_random_tlb_index() Song Gao
2024-07-29 1:39 ` [PATCH 5/5] target/loongarch/tcg: Add hardware page table walker support Song Gao
2024-07-29 3:57 ` Richard Henderson
2024-09-05 8:27 ` gaosong
2024-09-05 19:39 ` Richard Henderson [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=2c81231c-4c99-4d6b-96d3-47c7c1e1e576@linaro.org \
--to=richard.henderson@linaro.org \
--cc=gaosong@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).