On 4/27/23 10:18 AM, Sean Christopherson wrote: > On Thu, Apr 27, 2023, Carlos Bilbao wrote: >> On 4/27/23 7:29 AM, Reshetova, Elena wrote: >>> I agree with Dave that I think the goal of this document is not to come up with a >>> fancy name (I am fine with call it anything), but to introduce kernel developers to the >>> new Linux threat model angle for this-particular-use-case-of-confidential-computing. >>> So that when we submit the hardening mechanisms in the future people are >>> already familiar with why we need to do this and we don’t have to repeat this story >>> again and again. >> >> Yes! To reiterate, there's two things we definitely wish to do: >> >> 1. Narrow down the problem: This new document can be specific to CoCo in >> virtual environments. v2 should be clear about that. > > Then rename the document as I already suggested. If you want to claim > confidential-computing.rst, then IMO such a doc needs to be written something > like the surprisingly good Wikipedia article[*]. Until one of those two things > happens, my NAK stands. > > [*] https://en.wikipedia.org/wiki/Confidential_computing That's "mea culpa". I should have made it clearer in my previous emails that changing the name is a non-issue. Also that we are very interested in feedback from other CoCo flavors. In this regard, we've reached out to ARM and RISC-V folks. Hopefully, they help us improve the doc and we can add them as maintainers. Whenever we have a v2, I'd like to CC people from CSP sector (Oracle, etc.) as well. Thanks, Carlos
