From: Peter Maydell <peter.maydell@linaro.org>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Jayanto Minocha" <jayanto@gmail.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Tracing guest virtual addresses
Date: Mon, 26 Jun 2017 13:14:52 +0100 [thread overview]
Message-ID: <CAFEAcA8m8cKnVeqvoGnP7uNetMyPTPkc3GRELNa3OLoGS5FgEw@mail.gmail.com> (raw)
In-Reply-To: <87mv8vc5va.fsf@frigg.lan>
On 26 June 2017 at 13:04, Lluís Vilanova <vilanova@ac.upc.edu> wrote:
> Peter Maydell writes:
>
>> On 26 June 2017 at 10:26, Lluís Vilanova <vilanova@ac.upc.edu> wrote:
>>> There's two places where memory access tracing is triggered:
>>>
>>> * tcg_gen_qemu_ld/st_...
>>> * ld/st templates (both softmmu and user)
>>>
>>> AFAIK, helpers use the ld/st templates to access guest memory.
>
>> Mostly, but there are one or two special cases, for instance
>> the ARM HELPER(dc_zva) in target/arm/helper.c, which has a
>> fastpath that uses tlb_vaddr_to_host to look up the host memory
>> address and then memset to do the clear-to-zeroes operation.
>
> Should that be replaced with a cpu_memset or similar?
Possibly -- PPC and S390 also have a fast-memset like this
(and S390 also has a fast-memmove). However I would be wary
of there being architecture-specific corner cases (eg
needing to get the right vaddr for a fault if the accesses
fault).
thanks
-- PMM
next prev parent reply other threads:[~2017-06-26 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 21:15 [Qemu-devel] Tracing guest virtual addresses Jayanto Minocha
2017-06-20 11:02 ` Lluís Vilanova
2017-06-20 11:13 ` Peter Maydell
2017-06-21 14:44 ` Alex Bennée
2017-06-25 12:20 ` Lluís Vilanova
2017-06-25 17:35 ` Alex Bennée
2017-06-26 9:26 ` Lluís Vilanova
2017-06-26 9:32 ` Peter Maydell
2017-06-26 12:04 ` Lluís Vilanova
2017-06-26 12:14 ` Peter Maydell [this message]
2017-06-20 17:20 ` Emilio G. Cota
2017-06-20 22:30 ` Jayanto Minocha
2017-06-22 5:36 ` Lluís Vilanova
2017-06-25 12:16 ` Lluís Vilanova
2017-06-26 17:42 ` Emilio G. Cota
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=CAFEAcA8m8cKnVeqvoGnP7uNetMyPTPkc3GRELNa3OLoGS5FgEw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=jayanto@gmail.com \
--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).