[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Tracing guest virtual addresses
From: |
Peter Maydell |
Subject: |
Re: [Qemu-devel] Tracing guest virtual addresses |
Date: |
Tue, 20 Jun 2017 12:13:00 +0100 |
On 20 June 2017 at 12:02, Lluís Vilanova <address@hidden> wrote:
> Jayanto Minocha writes:
>> But that is only used to instrument the cpu_ld/cpu_st macros, which is only
>> called in the case of a tlb miss.
>
>> I've been going over the archives, and it looks like I need to instrument
>> tcg_out_tlb_load. Am I on the right path ?
>
> That event should trace all guest memory accesses performed by the CPU. If you
> found any case where this does not hold, it is likely a bug and I'd appreciate
> it if you can point me to the smallest possible failing example.
Does it catch memory accesses that are performed via helper functions,
or only ones done by inline TCG code?
thanks
-- PMM
- [Qemu-devel] Tracing guest virtual addresses, Jayanto Minocha, 2017/06/19
- Re: [Qemu-devel] Tracing guest virtual addresses, Lluís Vilanova, 2017/06/20
- Re: [Qemu-devel] Tracing guest virtual addresses,
Peter Maydell <=
- Re: [Qemu-devel] Tracing guest virtual addresses, Alex Bennée, 2017/06/21
- Re: [Qemu-devel] Tracing guest virtual addresses, Lluís Vilanova, 2017/06/25
- Re: [Qemu-devel] Tracing guest virtual addresses, Alex Bennée, 2017/06/25
- Re: [Qemu-devel] Tracing guest virtual addresses, Lluís Vilanova, 2017/06/26
- Re: [Qemu-devel] Tracing guest virtual addresses, Peter Maydell, 2017/06/26
- Re: [Qemu-devel] Tracing guest virtual addresses, Lluís Vilanova, 2017/06/26
- Re: [Qemu-devel] Tracing guest virtual addresses, Peter Maydell, 2017/06/26
Re: [Qemu-devel] Tracing guest virtual addresses, Emilio G. Cota, 2017/06/20