From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<ira.weiny@intel.com>, Bjorn Helgaas <bhelgaas@google.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Ben Widawsky" <bwidawsk@kernel.org>, <linux-cxl@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH 1/2] PCI: Allow drivers to request exclusive config regions
Date: Wed, 24 Aug 2022 10:52:29 +0100 [thread overview]
Message-ID: <20220824105229.00006c79@huawei.com> (raw)
In-Reply-To: <6303dcb63e3e1_1b32294d9@dwillia2-xfh.jf.intel.com.notmuch>
>
> > What are you trying to protect yourself from, bogus bug reports by
> > people doing bad things and then blaming you? That's easy to handle,
> > just ignore them :)
>
> I asked Ira to push on this to protect the kernel from people like me,
> :). So, there is this massively complicated specification for device
> attestation and link integrity / encryption protection (SPDM and IDE)
> that has applications to both PCIe and CXL. I do not see a path in the
> near term to land that support in the kernel.
>
> DOE being user accessible though, lends itself to pure userspace
> implementations of SPDM and IDE infrastructure. I want to develop that
> infrastructure, but also have the kernel reserve the space / right to
> obviate that implementation with kernel control of the DOE mailbox, SPDM
> sessions, and IDE keys in the future.
Can't resist...
If anyone is at Plumbers (in person or virtually) the will be a BoF on
SPDM etc. Not scheduled yet...
https://lpc.events/event/16/contributions/1304/
Come join the Kernel vs Partly Kernel vs fully Userspace discussions.
Thanks,
Jonathan
next prev parent reply other threads:[~2022-08-24 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 0:52 [PATCH 0/2] CXL: Taint user access to DOE mailbox config space ira.weiny
2022-08-22 0:52 ` [PATCH 1/2] PCI: Allow drivers to request exclusive config regions ira.weiny
2022-08-22 6:39 ` Greg Kroah-Hartman
2022-08-22 19:44 ` Dan Williams
2022-08-22 20:38 ` Ira Weiny
2022-08-22 21:18 ` Dan Williams
2022-08-23 7:19 ` Greg Kroah-Hartman
2022-08-24 9:52 ` Jonathan Cameron [this message]
2022-08-22 0:52 ` [PATCH 2/2] cxl/doe: Request exclusive DOE access ira.weiny
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=20220824105229.00006c79@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=bhelgaas@google.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=vishal.l.verma@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).