From: Sean Christopherson <seanjc@google.com>
To: Carlos Bilbao <carlos.bilbao@amd.com>
Cc: Elena Reshetova <elena.reshetova@intel.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ardb@kernel.org" <ardb@kernel.org>,
"kraxel@redhat.com" <kraxel@redhat.com>,
"dovmurik@linux.ibm.com" <dovmurik@linux.ibm.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"Dhaval.Giani@amd.com" <Dhaval.Giani@amd.com>,
"michael.day@amd.com" <michael.day@amd.com>,
"pavankumar.paluri@amd.com" <pavankumar.paluri@amd.com>,
"David.Kaplan@amd.com" <David.Kaplan@amd.com>,
"Reshma.Lal@amd.com" <Reshma.Lal@amd.com>,
"Jeremy.Powell@amd.com" <Jeremy.Powell@amd.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"dinechin@redhat.com" <dinechin@redhat.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"berrange@redhat.com" <berrange@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"tytso@mit.edu" <tytso@mit.edu>,
"jikos@kernel.org" <jikos@kernel.org>,
"joro@8bytes.org" <joro@8bytes.org>,
"leon@kernel.org" <leon@kernel.org>,
"richard.weinberger@gmail.com" <richard.weinberger@gmail.com>,
"lukas@wunner.de" <lukas@wunner.de>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"cdupontd@redhat.com" <cdupontd@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"sameo@rivosinc.com" <sameo@rivosinc.com>,
"bp@alien8.de" <bp@alien8.de>,
"security@kernel.org" <security@kernel.org>,
Andrew Bresticker <abrestic@rivosinc.com>,
Rajnesh Kanwal <rkanwal@rivosinc.com>,
Dylan Reid <dylan@rivosinc.com>, Ravi Sahita <ravi@rivosinc.com>
Subject: Re: [PATCH] docs: security: Confidential computing intro and threat model
Date: Thu, 27 Apr 2023 08:18:58 -0700 [thread overview]
Message-ID: <ZEqSRTirPCxjy6M4@google.com> (raw)
In-Reply-To: <c99d6a6b-cb8b-c62d-7305-6b739a8c0671@amd.com>
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
next prev parent reply other threads:[~2023-04-27 15:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:18 [PATCH] docs: security: Confidential computing intro and threat model Carlos Bilbao
2023-03-29 10:40 ` Greg KH
2023-03-30 17:32 ` Carlos Bilbao
2023-04-22 3:17 ` Bagas Sanjaya
2023-04-21 21:09 ` Kaplan, David
2023-04-25 13:43 ` Carlos Bilbao
2023-04-25 15:02 ` Sean Christopherson
2023-04-26 13:32 ` Reshetova, Elena
2023-04-26 15:08 ` Carlos Bilbao
2023-04-26 15:51 ` Sean Christopherson
2023-04-26 19:21 ` Carlos Bilbao
2023-04-26 19:53 ` Sean Christopherson
2023-04-26 20:15 ` Carlos Bilbao
2023-04-26 21:33 ` Sean Christopherson
2023-04-26 22:27 ` Carlos Bilbao
2023-04-27 12:29 ` Reshetova, Elena
2023-04-27 14:16 ` Carlos Bilbao
2023-04-27 15:18 ` Sean Christopherson [this message]
2023-04-27 17:59 ` Carlos Bilbao
2023-04-26 20:12 ` Dave Hansen
2023-04-26 15:18 ` James Bottomley
2023-04-26 16:17 ` Sean Christopherson
2023-04-27 12:43 ` Reshetova, Elena
2023-04-27 13:18 ` James Bottomley
2023-04-27 15:47 ` Reshetova, Elena
2023-04-27 16:16 ` James Bottomley
2023-04-27 16:46 ` Randy Dunlap
2023-04-27 17:19 ` Michael S. Tsirkin
2023-04-27 18:27 ` James Bottomley
2023-04-27 12:56 ` Reshetova, Elena
2023-04-26 15:46 ` Dave Hansen
2023-04-26 16:03 ` Sean Christopherson
2023-04-27 19:06 ` Peter Gonda
2023-04-27 18:47 ` Peter Gonda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZEqSRTirPCxjy6M4@google.com \
--to=seanjc@google.com \
--cc=David.Kaplan@amd.com \
--cc=Dhaval.Giani@amd.com \
--cc=Jeremy.Powell@amd.com \
--cc=Reshma.Lal@amd.com \
--cc=abrestic@rivosinc.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ardb@kernel.org \
--cc=berrange@redhat.com \
--cc=bp@alien8.de \
--cc=carlos.bilbao@amd.com \
--cc=cdupontd@redhat.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=dgilbert@redhat.com \
--cc=dinechin@redhat.com \
--cc=dovmurik@linux.ibm.com \
--cc=dylan@rivosinc.com \
--cc=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=jikos@kernel.org \
--cc=joro@8bytes.org \
--cc=kraxel@redhat.com \
--cc=leon@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.day@amd.com \
--cc=mst@redhat.com \
--cc=pavankumar.paluri@amd.com \
--cc=ravi@rivosinc.com \
--cc=richard.weinberger@gmail.com \
--cc=rkanwal@rivosinc.com \
--cc=sameo@rivosinc.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=security@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.