Re: Recompile QEMU with frame-pointers

On 2021-01-27 15:14, Salvatore Mazzarino wrote: I’m trying to profile my QEMU process but what I get is a stack full of unknown. I would then need to recompile QEMU with -fno-omit-frame-pointer. Do you know if there is a version already built for that purpose? I am not sure, but I suspect th

Re: [EXT] Re: Bugs in SSH module

On Wed, 27 Jan 2021 at 22:47, Berto Furth wrote: > I'm not sure but I think I *could* be seeing the problem. In the configure > log you're doing configure in the " ~/optee-qemu/qemu " directory > > sawyer@ubuntu:~/optee-qemu/qemu$ ./configure --disable-libssh > > But then in the make log you're d

Re: Recompile QEMU with frame-pointers

On Thu, 28 Jan 2021 at 08:42, Jakob Bohm wrote: > > On 2021-01-27 15:14, Salvatore Mazzarino wrote: > > I’m trying to profile my QEMU process but what I get is a stack full of > unknown. > > I would then need to recompile QEMU with -fno-omit-frame-pointer. > > Do you know if there is a version al

Need information about QEMU I2C

Hi all, I am currently trying to employ QEMU as testing device for ARM based machine (sabre lite). I don't have much information about QEMU's internal system that's why trying to reach someone with proper information. I want to learn how I2C device will work in QEMU in case of sabre lite machine

Re: Recompile QEMU with frame-pointers

I have compiled QEMU with the following flags ../configure \ --enable-werror \ --enable-trace-backend=simple \ --enable-debug \ --target-list="x86_64-softmmu" \ --disable-gcrypt \ --enable-nettle \ --enable-docs \ --enable-fdt=system \ --enable-slirp=system \

Re: Recompile QEMU with frame-pointers

On Thu, 28 Jan 2021 at 18:08, Salvatore Mazzarino wrote: > > I have compiled QEMU with the following flags > > ../configure \ > --enable-werror \ > --enable-trace-backend=simple \ > --enable-debug \ > --target-list="x86_64-softmmu" \ > --disable-gcrypt \ > --enable-nettle \

Re: Recompile QEMU with frame-pointers

Unfortunately it did not work. Here the flags ../configure \ --enable-werror \ --extra-cflags="-fno-omit-frame-pointer" \ --target-list="x86_64-softmmu" \ --disable-gcrypt \ --enable-nettle \ --enable-docs \ --enable-fdt=system \ --enable-slirp=system \ --enabl

[QEMU TCG] Qeustion about the PCID Feature in TCG

Hi, I am running QEMU in TCG mode (my server doesn't have kvm support), and I am getting the memory traces in a x86 guest machine of all memory accesses, including the PCID (process-context identifier, and I need that for my current research), on a linux host. I have seen the TCG PCID feature flag