> > > diff --git a/drivers/cxl/Kconfig b/drivers/cxl/Kconfig > > > index c4ba3aa0a05d..08eaa8e52083 100644 > > > --- a/drivers/cxl/Kconfig > > > +++ b/drivers/cxl/Kconfig > > > @@ -33,6 +33,24 @@ config CXL_MEM > > > > > > If unsure say 'm'. > > > > > > +config CXL_MEM_RAW_COMMANDS > > > + bool "RAW Command Interface for Memory Devices" > > > + depends on CXL_MEM > > > + help > > > + Enable CXL RAW command interface. > > > + > > > + The CXL driver ioctl interface may assign a kernel ioctl command > > > + number for each specification defined opcode. At any given point in > > > + time the number of opcodes that the specification defines and a device > > > + may implement may exceed the kernel's set of associated ioctl function > > > + numbers. The mismatch is either by omission, specification is too new, > > > + or by design. When prototyping new hardware, or developing / > > > debugging > > > + the driver it is useful to be able to submit any possible command to > > > + the hardware, even commands that may crash the kernel due to their > > > + potential impact to memory currently in use by the kernel. > > > + > > > + If developing CXL hardware or the driver say Y, otherwise say N. > > > > Blocking RAW commands by default will prevent vendors from developing user > > space tools that utilize vendor specific commands. Vendors of CXL.mem devices > > should take ownership of ensuring any vendor defined commands that could cause > > user data to be exposed or corrupted are disabled at the device level for > > shipping configurations. > > Thanks for brining this up Ariel. If there is a recommendation on how to codify > this, I would certainly like to know because the explanation will be long. > > --- > > The background: > > The enabling/disabling of the Kconfig option is driven by the distribution > and/or system integrator. Even if we made the default 'y', nothing stops them > from changing that. if you are using this driver in production and insist on > using RAW commands, you are free to carry around a small patch to get rid of the > WARN (it is a one-liner). > > To recap why this is in place - the driver owns the sanctity of the device and > therefore a [large] part of the whole system. What we can do as driver writers > is figure out the set of commands that are "safe" and allow those. Aside from > being able to validate them, we're able to mediate them with other parallel > operations that might conflict. We gain the ability to squint extra hard at bug > reports. We provide a reason to try to use a well defined part of the spec. > Realizing that only allowing that small set of commands in a rapidly growing > ecosystem is not a welcoming API; we decided on RAW. > > Vendor commands can be one of two types: > 1. Some functionality probably most vendors want. > 2. Functionality that is really single vendor specific. > > Hopefully we can agree that the path for case #1 is to work with the consortium > to standardize a command that does what is needed and that can eventually become > part of UAPI. The situation is unfortunate, but temporary. If you won't be able > to upgrade your kernel, patch out the WARN as above. > > The second situation is interesting and does need some more thought and > discussion. > > --- > > I see 3 realistic options for truly vendor specific commands. > 1. Tough noogies. Vendors aren't special and they shouldn't do that. > 2. modparam to disable the WARN for specific devices (let the sysadmin decide) > 3. Try to make them part of UAPI. > > The right answer to me is #1, but I also realize I live in the real world. > > #2 provides too much flexibility. Vendors will just do what they please and > distros and/or integrators will be seen as hostile if they don't accommodate. > > I like #3, but I have a feeling not everyone will agree. My proposal for vendor > specific commands is, if it's clear it's truly a unique command, allow adding it > as part of UAPI (moving it out of RAW). I expect like 5 of these, ever. If we > start getting multiple per vendor, we've failed. The infrastructure is already > in place to allow doing this pretty easily. I think we'd have to draw up some > guidelines (like adding test cases for the command) to allow these to come in. > Anything with command effects is going to need extra scrutiny. This would necessitate adding specific opcode values in the range C000h-FFFFh to UAPI, and those would then be allowed for all CXL.mem devices, correct? If so, I do not think this is the right approach, as opcodes in this range are by definition vendor defined. A given opcode value will have totally different effects depending on the vendor. I think you may be on to something with the command effects. But rather than "extra scrutiny" for opcodes that have command effects, would it make sense to allow vendor defined opcodes that have Bit[5:0] in the Command Effect field of the CEL Entry Structure (Table 173) set to 0? In conjunction, those bits represent any change to the configuration or data within the device. For commands that have no such effects, is there harm to allowing them? Of course, this approach relies on the vendor to not misrepresent the command effects. > > In my opinion, as maintainers of the driver, we do owe the community an answer > as to our direction for this. Dan, what is your thought?
