[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251008061403.GA13979@lst.de>
Date: Wed, 8 Oct 2025 08:14:04 +0200
From: hch <hch@....de>
To: Johannes Thumshirn <Johannes.Thumshirn@....com>
Cc: hch <hch@....de>, Jens Axboe <axboe@...nel.dk>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-trace-kernel@...r.kernel.org" <linux-trace-kernel@...r.kernel.org>,
"linux-btrace@...r.kernel.org" <linux-btrace@...r.kernel.org>,
John Garry <john.g.garry@...cle.com>,
Hannes Reinecke <hare@...e.de>, Damien Le Moal <dlemoal@...nel.org>,
Naohiro Aota <Naohiro.Aota@....com>,
Shinichiro Kawasaki <shinichiro.kawasaki@....com>,
Chaitanya Kulkarni <chaitanyak@...dia.com>,
"Martin K . Petersen" <martin.petersen@...cle.com>
Subject: Re: [PATCH v2 11/15] blktrace: add block trace commands for zone
operations
On Tue, Oct 07, 2025 at 01:08:00PM +0000, Johannes Thumshirn wrote:
> Sure for the old commands everything is still in the lower 32bits, this
> has the nice property that we don't need to duplicate all the code for
> v1 and v2.
I don't think you need to duplicate anything, just have a little
function that maps from the free-form v2 commands and flags to the
v1 field. Preferably including a mapping of all unsupported ones to
a catchall unsupported command and flag each to indicate that the
trace includes something only visible with v2.
Powered by blists - more mailing lists