From: Dan Williams <dan.j.williams@intel.com>
To: Ira Weiny <ira.weiny@intel.com>, Dan Williams <dan.j.williams@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.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>
Subject: Re: [PATCH 1/2] PCI: Allow drivers to request exclusive config regions
Date: Mon, 22 Aug 2022 14:18:17 -0700 [thread overview]
Message-ID: <6303f298ef92c_1b322944c@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <YwPpLWgG37ObTMAP@iweiny-desk3>
Ira Weiny wrote:
> > Similar to CONFIG_IO_STRICT_DEVMEM, just turn this warning off if you
> > are a distribution kernel vendor who does not care about DOE vendor
> > tools affecting system state, and turn on CONFIG_LOCK_DOWN_KERNEL if you
> > are on the other end of the spectrum and want protection from such
> > things. The warn is middle-road option that I expect most distros would
> > use.
>
> FWIW I did not add any Kconfig for the feature. Should I?
I think so, especially as it is a distro configuration policy about what
user-mode PCI tooling it wants to support / warn about.
next prev parent reply other threads:[~2022-08-22 21:18 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 [this message]
2022-08-23 7:19 ` Greg Kroah-Hartman
2022-08-24 9:52 ` Jonathan Cameron
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=6303f298ef92c_1b322944c@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=bhelgaas@google.com \
--cc=bwidawsk@kernel.org \
--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=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
all inboxes | Powered by JetHome®