qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, crosthwaite.peter@gmail.com,
	stefanha@redhat.com, rth@twiddle.net
Subject: [Qemu-devel] [PATCH] exec: Rename and fix trace events for tracing I/O port access.
Date: Tue, 29 Mar 2016 16:02:24 +0100	[thread overview]
Message-ID: <1459263745-1035-1-git-send-email-rjones@redhat.com> (raw)

Back in the day you used to be able to set DEBUG_IOPORT in ioport.c
and get qemu to dump what (x86) I/O ports were being accessed by the
guest.  This was rather useful for finding out what closed source
device drivers were up to.

Now you're supposed to use cpu_in/cpu_out tracepoints instead.
However for the majority of guests these tracepoints will never be
called.

So this patch tries to rationalize all of that.  It:

 - replaces cpu_in/cpu_out with ioport_in/ioport_out tracepoints

 - moves them down in the stack, so they actually get called

 - fixes various details like address size

It turns out this is still not particularly useful for debugging
because (a) it creates massive amounts of log messages and (b) there's
no way to select a range of addresses or a device of interest.  For
example, if you have a serial port, everything else gets swamped by
I/O access to the serial port.  Maybe using a different tracing
backend (eg. stap) would help?

Anyway, it still seems to me to be an improvement over the current
situation.

Rich.

             reply	other threads:[~2016-03-29 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 15:02 Richard W.M. Jones [this message]
2016-03-29 15:02 ` [Qemu-devel] [PATCH] exec: Rename and fix trace events for tracing I/O port access Richard W.M. Jones
2016-03-29 15:09 ` Daniel P. Berrange
2016-03-30 13:30 ` Paolo Bonzini
2016-03-31 10:08 ` Stefan Hajnoczi

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=1459263745-1035-1-git-send-email-rjones@redhat.com \
    --to=rjones@redhat.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@redhat.com \
    /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).