From: Richard Henderson <richard.henderson@linaro.org>
To: Mark Burton <mburton@qti.qualcomm.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Matheus Bernardino" <mathbern@qti.qualcomm.com>,
"Sid Manning" <sidneym@quicinc.com>,
"Brian Cain" <bcain@quicinc.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: Record AS in full tlb
Date: Thu, 11 Dec 2025 13:24:42 -0600 [thread overview]
Message-ID: <081b44f3-48aa-4af3-a0d1-c8e5915d95e3@linaro.org> (raw)
In-Reply-To: <2A86D9C4-7EA7-4275-943F-D75801B5539C@qti.qualcomm.com>
On 12/11/25 12:49, Mark Burton wrote:
>> Adding the as to CPUTLBEntryFull is unnecessary because
>>
>> (1) Each CPUTLB, and thus each CPUTLBEntryFull, is private to the cpu.
>> (2) Each CPUTLBEntryFull contains the MemTxAttrs for the access.
>>
>> Thus the AddressSpace is purely a function of (cpu, attrs).
>
> The issue is, it would seem, it is also a function of the lookup provided by an IOMMU access - that kindly provides an address space independent of any CPU.
No, it really isn't.
Because you think that, it seems like you're doing something wrong with IOMMU accesses.
Since I don't know the wider context of the query means I don't know how to help you further.
My shot in the dark: there is a flush that's supposed to happen for changes to a cpu's
address space. There are plenty of ways in which this happens, e.g. x86 a20 translation
line and pci bar changes. I forget the exact details when it comes to IOMMU, but there
must be something related when translations change. The actual tcg flush will happen via
the MemoryListener interface.
r~
next prev parent reply other threads:[~2025-12-11 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 10:47 Record AS in full tlb Mark Burton via
2025-12-09 12:14 ` Alex Bennée
2025-12-09 12:20 ` Alex Bennée
2025-12-09 12:22 ` Mark Burton
2025-12-09 12:43 ` Matheus Bernardino
2025-12-11 15:04 ` Richard Henderson
2025-12-11 18:49 ` Mark Burton
2025-12-11 19:24 ` Richard Henderson [this message]
2025-12-11 19:49 ` Mark Burton
2025-12-11 20:14 ` Richard Henderson
2025-12-11 20:35 ` Mark Burton
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=081b44f3-48aa-4af3-a0d1-c8e5915d95e3@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bcain@quicinc.com \
--cc=mathbern@qti.qualcomm.com \
--cc=mburton@qti.qualcomm.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sidneym@quicinc.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).