From: Jens Axboe <axboe@kernel.dk>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: linux-block@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
linux-btrace@vger.kernel.org
Subject: Re: [PATCH v2 00/11] blktrace: parse blk_io_trace2 in btt and iowatcher
Date: Fri, 02 Oct 2026 08:25:39 -0600 [thread overview]
Message-ID: <179095113917.28522.1401186462565976436.b4-ty@b4> (raw)
In-Reply-To: <20260720111417.1658507-1-johannes.thumshirn@wdc.com>
On Mon, 20 Jul 2026 13:14:06 +0200, Johannes Thumshirn wrote:
> We had an internal report that the new blktrace format does not work
> with the btt tool.
>
> This is because I simply forgot to update these tools. Do so now and
> sorry for all the inconvenience it might have brought.
>
> Johannes Thumshirn (11):
> btt: use blk_io_trace2 internally
> btt: natively parse blk_io_trace2
> blktrace: add option to request a specific trace protocol version
> blkrawverify: use blk_io_trace2 internally
> blkrawverify: natively parse blk_io_trace2
> blkiomon: use blk_io_trace2 internally
> blkiomon: natively parse blk_io_trace2
> iowatcher: use blk_io_trace2 internally
> iowatcher: natively parse blk_io_trace2
> btreplay: support blk_io_trace2 in btrecord
> blkparse: add option to emit a specific trace protocol version
>
> [...]
Applied, thanks!
[01/11] btt: use blk_io_trace2 internally
commit: 99d239becf12afe328a262ed9473a255a9d517f9
[02/11] btt: natively parse blk_io_trace2
commit: 30ee0821473d64959a134cfb857248f8e4b8a131
[03/11] blktrace: add option to request a specific trace protocol version
commit: 950f297e790fac0b85737ed5fba03fcc55df5a91
[04/11] blkrawverify: use blk_io_trace2 internally
commit: 5d12335aece2c8a207438b1d27071854fd1f5c88
[05/11] blkrawverify: natively parse blk_io_trace2
commit: 05d921fab95b43c2f3e2f9c4a020d3a72d2c9ca5
[06/11] blkiomon: use blk_io_trace2 internally
commit: c5d11505bba6f000176485d1d694f7d668618e7e
[07/11] blkiomon: natively parse blk_io_trace2
commit: 838bc02d9cff5f85ca8453980a7f610799a3c22d
[08/11] iowatcher: use blk_io_trace2 internally
commit: 65378ab2fe0f3e0130562fad72789c94288c961b
[09/11] iowatcher: natively parse blk_io_trace2
commit: 4cd8158ed9a8495fc8b5151f3288ed690d36acf5
[10/11] btreplay: support blk_io_trace2 in btrecord
commit: f7c1738a9a2463d01ec2072a70f0d444228f9144
[11/11] blkparse: add option to emit a specific trace protocol version
commit: bf32369c515f09aae6cdcc5d9a40fdc3597693d1
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-10-02 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 11:14 [PATCH v2 00/11] blktrace: parse blk_io_trace2 in btt and iowatcher Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 01/11] btt: use blk_io_trace2 internally Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 02/11] btt: natively parse blk_io_trace2 Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 03/11] blktrace: add option to request a specific trace protocol version Johannes Thumshirn
2026-07-20 11:52 ` Damien Le Moal
2026-07-20 11:14 ` [PATCH v2 04/11] blkrawverify: use blk_io_trace2 internally Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 05/11] blkrawverify: natively parse blk_io_trace2 Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 06/11] blkiomon: use blk_io_trace2 internally Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 07/11] blkiomon: natively parse blk_io_trace2 Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 08/11] iowatcher: use blk_io_trace2 internally Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 09/11] iowatcher: natively parse blk_io_trace2 Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 10/11] btreplay: support blk_io_trace2 in btrecord Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 11/11] blkparse: add option to emit a specific trace protocol version Johannes Thumshirn
2026-09-23 12:38 ` [PATCH v2 00/11] blktrace: parse blk_io_trace2 in btt and iowatcher Johannes Thumshirn
2026-10-02 7:53 ` Johannes Thumshirn
2026-10-02 14:25 ` Jens Axboe [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=179095113917.28522.1401186462565976436.b4-ty@b4 \
--to=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrace@vger.kernel.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