From: Alexander Graf <agraf@suse.de>
To: Eric Auger <eric.auger@linaro.org>,
eric.auger@st.com, christoffer.dall@linaro.org,
qemu-devel@nongnu.org, kim.phillips@freescale.com,
a.rigo@virtualopensystems.com, aik@ozlabs.ru, bsd@redhat.com,
pbonzini@redhat.com, kraxel@redhat.com, stefanha@redhat.com,
peter.maydell@linaro.org
Cc: Bharat.Bhushan@freescale.com, alex.williamson@redhat.com,
patches@linaro.org, kvmarm@lists.cs.columbia.edu,
stuart.yoder@freescale.com
Subject: Re: [Qemu-devel] [RFC] vfio: migration to trace points
Date: Wed, 03 Sep 2014 11:13:36 +0200 [thread overview]
Message-ID: <5406DBC0.6070704@suse.de> (raw)
In-Reply-To: <1409733914-1272-1-git-send-email-eric.auger@linaro.org>
On 03.09.14 10:45, Eric Auger wrote:
> This patch removes all DPRINTF and replace them by trace points.
> A few DPRINTF used in error cases were transformed into error_report.
>
> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>
> ---
>
> - __func__ is removed since trace point name does the same job
> - HWADDR_PRIx were replaced by PRIx64
>
> Besides those changes format strings were kept the same. in few
> cases however I was forced to change them due to parsing errors
> (always related to parenthesis handling). This is indicated in
> trace-events. Cases than are not correctly handled are given below:
> - "(%04x:%02x:%02x.%x)" need to be replaced by " (%04x:%02x:%02x.%x)"
> - "%s read(%04x:%02x:%02x.%x:BAR%d+0x%"PRIx64", %d) = 0x%"PRIx64 ->
> "%s read(%04x:%02x:%02x.%x:BAR%d+0x%"PRIx64", %d = 0x%"PRIx64 ->
> - "%s write(%04x:%02x:%02x.%x:BAR%d+0x%"PRIx64", 0x%"PRIx64", %d)"
> "%s write(%04x:%02x:%02x.%x:BAR%d+0x%"PRIx64", 0x%"PRIx64", %d"
> This is a temporary fix.
>
> - This leads to a too large amount of trace points which may not be
> eligible as trace points - I don't know?-
> - this transformation just is tested compiled on PCI. Tested on platform
> qemu configured with --enable-trace-backends=stderr
> - in future, format strings and calls may be simplified by using a single
> name argument instead of domain, bus, slot, function.
I think it's a nice step into the right direction.
Alex
next prev parent reply other threads:[~2014-09-03 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 8:45 [Qemu-devel] [RFC] vfio: migration to trace points Eric Auger
2014-09-03 9:13 ` Alexander Graf [this message]
2014-09-18 23:30 ` Eric Auger
2014-09-19 9:03 ` Stefan Hajnoczi
2014-09-19 16:07 ` Eric Auger
2014-09-19 20:40 ` Alexander Graf
2014-09-22 16:15 ` 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=5406DBC0.6070704@suse.de \
--to=agraf@suse.de \
--cc=Bharat.Bhushan@freescale.com \
--cc=a.rigo@virtualopensystems.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=bsd@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=eric.auger@st.com \
--cc=kim.phillips@freescale.com \
--cc=kraxel@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=stuart.yoder@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.