From: Dan Williams <dan.j.williams@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Harold Johnson <harold.johnson@broadcom.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>,
<linux-cxl@vger.kernel.org>,
Sreenivas Bagalkote <sreenivas.bagalkote@broadcom.com>,
Brett Henning <brett.henning@broadcom.com>,
Sumanesh Samanta <sumanesh.samanta@broadcom.com>,
<linux-kernel@vger.kernel.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
Dave Jiang <dave.jiang@intel.com>,
"Alison Schofield" <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>, <linuxarm@huawei.com>,
<linux-api@vger.kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
"Natu, Mahesh" <mahesh.natu@intel.com>
Subject: Re: RFC: Restricting userspace interfaces for CXL fabric management
Date: Sat, 27 Apr 2024 09:22:21 -0700 [thread overview]
Message-ID: <662d263dd17c7_b6e0294ab@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <2024042708-outscore-dreadful-2c21@gregkh>
Greg KH wrote:
[..]
> So while innovating at the hardware level is fine, follow the ways that
> everyone has done this for other specification types (USB, PCI, etc.)
> and just allow vendor drivers to provide the information. Don't do this
> in crazy userspace drivers which will circumvent the whole reason we
> have standard kernel/user apis in the first place for these types of
> things.
Right, standard kernel/user apis is the requirement.
The suggestion of opaque vendor passthrough tunnels, and every vendor
ships their custom tool to do what should be common flows, is where this
discussion went off the rails.
next prev parent reply other threads:[~2024-04-27 16:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 17:44 RFC: Restricting userspace interfaces for CXL fabric management Jonathan Cameron
2024-03-21 21:41 ` Sreenivas Bagalkote
2024-03-22 9:32 ` Jonathan Cameron
2024-03-22 13:24 ` Sreenivas Bagalkote
2024-04-01 16:51 ` Sreenivas Bagalkote
2024-04-06 0:04 ` Dan Williams
2024-04-10 11:45 ` Jonathan Cameron
2024-04-15 20:09 ` Sreenivas Bagalkote
2024-04-23 22:44 ` Sreenivas Bagalkote
2024-04-23 23:24 ` Greg KH
2024-04-24 0:07 ` Dan Williams
2024-04-25 11:33 ` Jonathan Cameron
2024-04-25 16:18 ` Dan Williams
2024-04-25 17:26 ` Jonathan Cameron
2024-04-25 19:25 ` Dan Williams
2024-04-26 8:45 ` Jonathan Cameron
2024-04-26 16:16 ` Dan Williams
2024-04-26 16:53 ` Jonathan Cameron
2024-04-26 19:25 ` Harold Johnson
2024-04-27 11:12 ` Greg KH
2024-04-27 16:22 ` Dan Williams [this message]
2024-04-28 4:25 ` Sirius
2024-04-29 12:18 ` Jonathan Cameron
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=662d263dd17c7_b6e0294ab@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=brett.henning@broadcom.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gregkh@linuxfoundation.org \
--cc=harold.johnson@broadcom.com \
--cc=ira.weiny@intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lpieralisi@kernel.org \
--cc=mahesh.natu@intel.com \
--cc=sreenivas.bagalkote@broadcom.com \
--cc=sumanesh.samanta@broadcom.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).