From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Aaron Lindsay" <aaron@os.amperecomputing.com>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
cota@braap.org, richard.henderson@linaro.org,
Peter Xu <peterx@redhat.com>
Subject: Re: Plugin virtual-to-physical translation incorrect for some IO accesses
Date: Tue, 6 Jul 2021 23:10:08 +0200 [thread overview]
Message-ID: <c3c2440e-bd91-1671-f9dd-e297f90d01ab@redhat.com> (raw)
In-Reply-To: <YOTBZiyOcNYcqjOO@strawberry.localdomain>
+Peter/Paolo
On 7/6/21 10:47 PM, Aaron Lindsay wrote:
> Hello,
>
> I previously supplied a patch which modified the plugin interface such
> that it will return physical addresses for IO regions [0]. However, I
> have now found a case where the interface does not appear to correctly
> return the full physical addresses.
>
> In particular, when in qemu_plugin_hwaddr_phys_addr() for a particular
> store to IO memory (haddr->is_io==true), I find that haddr->v.io.offset
> is 0x0 and mrs->mr->addr is 0x3000, meaning 0x3000 is the returned
> "physical address". However, I also find that
> mrs->offset_within_address_space is 0x8000007000 (and also that
> 0x8000007000 matches up with what an actual translation would be from
> inspecting the page tables).
>
> Would it be 'safe' to *always* begin using
> mrs->offset_within_address_space as the returned physical address here
> instead of `haddr->v.io.offset + mrs->mr->addr`, or is there a reason we
> should not do that?
'safety' is not my area, but using mrs->offset_within_address_space
sounds correct to me.
> Thanks!
>
> -Aaron
>
> [0] https://lists.nongnu.org/archive/html/qemu-devel/2021-03/msg03137.html
>
next prev parent reply other threads:[~2021-07-06 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 20:47 Plugin virtual-to-physical translation incorrect for some IO accesses Aaron Lindsay
2021-07-06 21:10 ` Philippe Mathieu-Daudé [this message]
2021-07-06 21:56 ` Aaron Lindsay via
2021-07-07 7:53 ` Philippe Mathieu-Daudé
2021-07-07 11:35 ` Aaron Lindsay via
2021-07-07 14:05 ` Aaron Lindsay via
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=c3c2440e-bd91-1671-f9dd-e297f90d01ab@redhat.com \
--to=philmd@redhat.com \
--cc=aaron@os.amperecomputing.com \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@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).