[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240214101126.0c3681ee@kernel.org>
Date: Wed, 14 Feb 2024 10:11:26 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Andy Gospodarek <andrew.gospodarek@...adcom.com>, Christoph Hellwig
<hch@...radead.org>, Saeed Mahameed <saeed@...nel.org>, Arnd Bergmann
<arnd@...db.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Leon
Romanovsky <leonro@...dia.com>, Jiri Pirko <jiri@...dia.com>, Leonid Bloch
<lbloch@...dia.com>, Itay Avraham <itayavr@...dia.com>, Saeed Mahameed
<saeedm@...dia.com>, David Ahern <dsahern@...nel.org>, Aron Silverton
<aron.silverton@...cle.com>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH V4 0/5] mlx5 ConnectX control misc driver
On Wed, 14 Feb 2024 13:57:35 -0400 Jason Gunthorpe wrote:
> There is a clear split in my mind between:
> - inspection debugging
> - invasive mutating debugging
> - configuration
Yes there's a clear split, and how are you going to enforce it on
an opaque interface? Put an "evil" bit in the common header?
> And maybe "invasive mutating debugging" taints the kernel or something
> like that.
Powered by blists - more mailing lists