On Mon, 14 Apr 2025 21:50:31 -0700 Dan Williams <dan.j.willi...@intel.com> wrote:
> Jonathan Cameron wrote: > [..] > > To me we don't need to answer the question of whether we fully understand > > requirements, or whether this support covers them, but rather to ask > > if anyone has requirements that are not sensible to satisfy with additional > > work building on this? > > Wearing only my upstream kernel development hat, the question for > merging is "what is the end user visible impact of merging this?". As > long as DCD remains in proof-of-concept mode then leave the code out of > tree until it is ready to graduate past that point. Hi Dan, Seems like we'll have to disagree on this. The only thing I can therefore do is help to keep this patch set in a 'ready to go' state. I would ask that people review it with that in mind so that we can merge it the day someone is willing to announce a product which is a lot more about marketing decisions than anything technical. Note that will be far too late for distro cycles so distro folk may have to pick up the fork (which they will hate). Hopefully that 'fork' will provide a base on which we can build the next set of key features. > > Same held for HDM-D support which was an out-of-tree POC until > Alejandro arrived with the SFC consumer. Obviously I can't comment on status of that hardware! > > DCD is joined by HDM-DB (awaiting an endpoint) and CXL Error Isolation > (awaiting a production consumer) as solutions that have time to validate > that the ecosystem is indeed graduating to consume them. Those I'm fine with waiting on, though obviously others may not be! > There was no > "chicken-egg" paradox for the ecosystem to deliver base > static-memory-expander CXL support. That is (at least partly) because the ecosystem for those was initially BIOS only. That's not true for DCD. So people built devices on basis they didn't need any kernel support. Lots of disadvantages to that but it's what happened. As a side note, I'd much rather that path had never been there as it is continuing to make a mess for Gregory and others. > > The ongoing failure to get productive engagement on just how ruthlessly > simple the implementation could be and still meet planned usages > continues to give the impression that Linux is way out in front of > hardware here. Uncomfortably so. I'll keep pushing for others to engage with this. I also have on my list writing a document on the future of DCD and proposing at least one way to add all features on that roadmap. A major intent of that being to show that there is no blocker to what we have here. I.e. we can extend it in a logical fashion to exactly what is needed. Reality is I cannot say anything about unannounced products. Whilst some companies will talk about stuff well ahead of hardware being ready for customers we do not do that (normally we announce long after customers have it.) Hence it seems I have no way to get this upstream other than hope someone else has a more flexible policy. Jonathan
