From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] tracing: Rename cpu_in/out to pio_in/out
Date: Tue, 19 Oct 2010 16:19:25 +0100 [thread overview]
Message-ID: <20101019151925.GB20899@stefan-thinkpad.transitives.com> (raw)
In-Reply-To: <4CBDB54B.8090806@siemens.com>
On Tue, Oct 19, 2010 at 05:12:11PM +0200, Jan Kiszka wrote:
> This is a more commonly used term, including the KVM in-kernel
> tracepoints. Only QEMU developers probably know the relation between
> cpu_in/out services and I/O port access.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> ioport.c | 12 ++++++------
> trace-events | 4 ++--
> 2 files changed, 8 insertions(+), 8 deletions(-)
Makes sense to me.
Acked-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
prev parent reply other threads:[~2010-10-19 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 15:12 [Qemu-devel] [PATCH] tracing: Rename cpu_in/out to pio_in/out Jan Kiszka
2010-10-19 15:19 ` Stefan Hajnoczi [this message]
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=20101019151925.GB20899@stefan-thinkpad.transitives.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/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).