On Thu, Jun 13, 2024 at 04:32:44PM -0700, Dave Jiang wrote: > Are you open to pass in potential user input for the info query? I'm > working on plumbing fwctl for CXL. Neat! > The current CXL query command [1] takes a number of commands as > input for its ioctl. For fwctl_cmd_info(), the current > implementation is when ->info() is called no information about the > user buffer length or an input buffer is provided. Right, the purpose of info is to report information about the fwctl driver. It is to allow the userspace to connect to the correct userspace driver. It shouldn't be doing much with the device. If you want to execute a info command *to the fw* then I'd expect you'd execute the command through the normal RPC channel? Does something prevent this? This is how the mlx5 driver is working where there are many info (called CAP) commands that return data, and they all run over the rpc channel. Thanks, Jason
