From: Patrick Williams <patrick@stwcx.xyz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Zev Weiss <zev@bewilderbeest.net>,
kvm@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
Kirti Wankhede <kwankhede@nvidia.com>,
Jeremy Kerr <jk@codeconstruct.com.au>,
Rajat Jain <rajatja@google.com>, Jianxiong Gao <jxgao@google.com>,
Dave Jiang <dave.jiang@intel.com>,
Saravana Kannan <saravanak@google.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
openbmc@lists.ozlabs.org, devicetree@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Alex Williamson <alex.williamson@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Bhaskar Chowdhury <unixbhaskar@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Jeffery <andrew@aj.id.au>,
Cornelia Huck <cohuck@redhat.com>,
linux-kernel@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH 4/5] driver core: inhibit automatic driver binding on reserved devices
Date: Mon, 25 Oct 2021 06:44:26 -0500 [thread overview]
Message-ID: <YXaYmie/CUHnixtX@heinlein> (raw)
In-Reply-To: <YXZLjTvGevAXcidW@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
On Mon, Oct 25, 2021 at 08:15:41AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Oct 25, 2021 at 12:38:08AM -0500, Frank Rowand wrote:
> > On 10/23/21 3:56 AM, Greg Kroah-Hartman wrote:
> We have the bind/unbind ability today, from userspace, that can control
> this. Why not just have Linux grab the device when it boots, and then
> when userspace wants to "give the device up", it writes to "unbind" in
> sysfs, and then when all is done, it writes to the "bind" file and then
> Linux takes back over.
>
> Unless for some reason Linux should _not_ grab the device when booting,
> then things get messier, as we have seen in this thread.
This is probably more typical on a BMC than atypical. The systems often require
the BMC (running Linux) to be able to reboot independently from the managed host
(running anything). In the example Zev gave, the BMC rebooting would rip away
the BIOS chip from the running host.
The BMC almost always needs to come up in a "I don't know what could possibly be
going on in the system" state and re-discover where the system was left off.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-25 11:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 2:00 [PATCH 0/5] driver core, of: support for reserved devices Zev Weiss
2021-10-22 2:00 ` [PATCH 1/5] of: base: add function to check for status = "reserved" Zev Weiss
2021-10-22 6:43 ` Greg Kroah-Hartman
2021-10-22 7:38 ` Zev Weiss
2021-10-22 7:45 ` Greg Kroah-Hartman
2021-10-22 2:00 ` [PATCH 2/5] device property: add fwnode_device_is_reserved() Zev Weiss
2021-10-22 2:00 ` [PATCH 3/5] of: property: add support for fwnode_device_is_reserved() Zev Weiss
2021-10-22 2:00 ` [PATCH 4/5] driver core: inhibit automatic driver binding on reserved devices Zev Weiss
2021-10-22 6:46 ` Greg Kroah-Hartman
2021-10-22 8:32 ` Zev Weiss
2021-10-22 8:57 ` Greg Kroah-Hartman
2021-10-22 15:18 ` Patrick Williams
2021-10-23 8:56 ` Greg Kroah-Hartman
2021-10-25 5:38 ` Frank Rowand
2021-10-25 6:15 ` Greg Kroah-Hartman
2021-10-25 11:44 ` Patrick Williams [this message]
2021-10-25 12:58 ` Andy Shevchenko
2021-10-25 13:20 ` Patrick Williams
2021-10-25 13:34 ` Greg Kroah-Hartman
2021-10-25 14:02 ` Patrick Williams
2021-10-25 14:09 ` Greg Kroah-Hartman
2021-10-25 15:54 ` Patrick Williams
2021-10-25 18:36 ` Greg Kroah-Hartman
2021-10-22 16:27 ` Zev Weiss
2021-10-23 8:55 ` Greg Kroah-Hartman
2021-10-22 2:00 ` [PATCH 5/5] of: platform: instantiate " Zev Weiss
2021-10-22 2:58 ` [PATCH 0/5] driver core, of: support for " Rob Herring
2021-10-22 3:13 ` Zev Weiss
2021-10-22 6:50 ` Greg Kroah-Hartman
2021-10-22 6:50 ` Greg Kroah-Hartman
2021-10-22 9:00 ` Zev Weiss
2021-10-22 9:22 ` Greg Kroah-Hartman
2021-10-25 5:53 ` Frank Rowand
2021-10-25 13:57 ` Frank Rowand
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=YXaYmie/CUHnixtX@heinlein \
--to=patrick@stwcx.xyz \
--cc=alex.williamson@redhat.com \
--cc=andrew@aj.id.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=cohuck@redhat.com \
--cc=dave.jiang@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jk@codeconstruct.com.au \
--cc=jxgao@google.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=rafael@kernel.org \
--cc=rajatja@google.com \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=tglx@linutronix.de \
--cc=unixbhaskar@gmail.com \
--cc=vkoul@kernel.org \
--cc=zev@bewilderbeest.net \
/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).