qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] QEMU option -d in_asm on i386
@ 2013-07-15 12:21 Anderson Sartor
  2013-07-15 12:32 ` Peter Maydell
  0 siblings, 1 reply; 3+ messages in thread
From: Anderson Sartor @ 2013-07-15 12:21 UTC (permalink / raw)
  To: qemu-devel

[-- Attachment #1: Type: text/plain, Size: 337 bytes --]

Regarding the QEMU code present in the Android source (I tested on QEMU
1.1.2 as well and got the same results), I am able to get in_asm, out_asm,
etc data with ARM and MIPS architectures. However on i386 nothing is saved
to the log using any of the "-d" options. Why is i386 different? How can I
get this data for x86 as well?

Thanks,

[-- Attachment #2: Type: text/html, Size: 848 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] QEMU option -d in_asm on i386
  2013-07-15 12:21 [Qemu-devel] QEMU option -d in_asm on i386 Anderson Sartor
@ 2013-07-15 12:32 ` Peter Maydell
  2013-07-15 13:04   ` Anderson Sartor
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Maydell @ 2013-07-15 12:32 UTC (permalink / raw)
  To: Anderson Sartor; +Cc: qemu-devel

On 15 July 2013 13:21, Anderson Sartor <andersonsartor@gmail.com> wrote:
> Regarding the QEMU code present in the Android source (I tested on QEMU
> 1.1.2 as well and got the same results), I am able to get in_asm, out_asm,
> etc data with ARM and MIPS architectures. However on i386 nothing is saved
> to the log using any of the "-d" options. Why is i386 different? How can I
> get this data for x86 as well?

1.1.2 is a pretty old release of QEMU -- do you still get the
same results on something recent (eg 1.5) ?

My guess is that on x86 you are (either accidentally or deliberately)
using KVM acceleration -- the debug tracing only works for TCG
(emulated) mode, not when using KVM.

-- PMM

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] QEMU option -d in_asm on i386
  2013-07-15 12:32 ` Peter Maydell
@ 2013-07-15 13:04   ` Anderson Sartor
  0 siblings, 0 replies; 3+ messages in thread
From: Anderson Sartor @ 2013-07-15 13:04 UTC (permalink / raw)
  To: Peter Maydell; +Cc: qemu-devel

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

Thank you for your answer. It was, as you guessed, the KVM acceleration,
explicity calling "-disable-kvm" did the trick and everything is working
now.

Thanks again


2013/7/15 Peter Maydell <peter.maydell@linaro.org>

> On 15 July 2013 13:21, Anderson Sartor <andersonsartor@gmail.com> wrote:
> > Regarding the QEMU code present in the Android source (I tested on QEMU
> > 1.1.2 as well and got the same results), I am able to get in_asm,
> out_asm,
> > etc data with ARM and MIPS architectures. However on i386 nothing is
> saved
> > to the log using any of the "-d" options. Why is i386 different? How can
> I
> > get this data for x86 as well?
>
> 1.1.2 is a pretty old release of QEMU -- do you still get the
> same results on something recent (eg 1.5) ?
>
> My guess is that on x86 you are (either accidentally or deliberately)
> using KVM acceleration -- the debug tracing only works for TCG
> (emulated) mode, not when using KVM.
>
> -- PMM
>

[-- Attachment #2: Type: text/html, Size: 1408 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-07-15 13:17 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-15 12:21 [Qemu-devel] QEMU option -d in_asm on i386 Anderson Sartor
2013-07-15 12:32 ` Peter Maydell
2013-07-15 13:04   ` Anderson Sartor

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).