From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Emilio G. Cota" <cota@braap.org>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/5] trace-mem fixes
Date: Thu, 7 Jun 2018 09:44:25 +0100 [thread overview]
Message-ID: <20180607084425.GA19032@stefanha-x1.localdomain> (raw)
In-Reply-To: <1527028012-21888-1-git-send-email-cota@braap.org>
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
On Tue, May 22, 2018 at 06:26:47PM -0400, Emilio G. Cota wrote:
> This series fixes a few issues that I found while testing
> the tracing of guest memory accesses in TCG. Please review!
>
> You can fetch these patches from:
> https://github.com/cota/qemu/commits/trace-mem
Doesn't look like anyone else is going to review this.
Thanks, applied to my tracing tree:
https://github.com/stefanha/qemu/commits/tracing
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2018-06-07 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 22:26 [Qemu-devel] [PATCH 0/5] trace-mem fixes Emilio G. Cota
2018-05-22 22:26 ` [Qemu-devel] [PATCH 1/5] trace: fix misreporting of TCG access sizes for user-space Emilio G. Cota
2018-05-22 22:26 ` [Qemu-devel] [PATCH 2/5] trace: simplify trace_mem functions Emilio G. Cota
2018-05-22 22:26 ` [Qemu-devel] [PATCH 3/5] trace: expand mem_info:size_shift to 3 bits Emilio G. Cota
2018-05-22 22:26 ` [Qemu-devel] [PATCH 4/5] trace: add trace_mem_build_info_no_se_be/le Emilio G. Cota
2018-05-22 22:26 ` [Qemu-devel] [PATCH 5/5] trace: enable tracing of TCG atomics Emilio G. Cota
2018-05-25 15:20 ` [Qemu-devel] [PATCH 0/5] trace-mem fixes Stefan Hajnoczi
2018-06-07 8:44 ` 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=20180607084425.GA19032@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=cota@braap.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).