lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 23 Jun 2022 10:30:16 -0700
From:   Saravana Kannan <>
To:     Andy Shevchenko <>
Cc:     sascha hauer <>,
        Greg Kroah-Hartman <>,
        "Rafael J. Wysocki" <>,
        Rob Herring <>,
        Frank Rowand <>,
        Daniel Scally <>,
        Heikki Krogerus <>,
        Sakari Ailus <>,
        Len Brown <>, peng fan <>,
        kevin hilman <>,
        ulf hansson <>,
        len brown <>, pavel machek <>,
        joerg roedel <>, will deacon <>,
        andrew lunn <>,
        heiner kallweit <>,
        russell king <>,
        "david s. miller" <>,
        eric dumazet <>,
        jakub kicinski <>,
        paolo abeni <>,
        linus walleij <>,
        hideaki yoshifuji <>,
        david ahern <>,,,,,,,,,
Subject: Re: [PATCH v2 2/2] of: base: Avoid console probe delay when fw_devlink.strict=1

On Thu, Jun 23, 2022 at 9:39 AM Andy Shevchenko
<> wrote:
> On Thu, Jun 23, 2022 at 12:04:21PM +0200, sascha hauer wrote:
> > On Thu, Jun 23, 2022 at 01:03:43AM -0700, Saravana Kannan wrote:
> ...
> > I wonder if it wouldn't be a better approach to just probe all devices
> > and record the device(node) they are waiting on. Then you know that you
> > don't need to probe them again until the device they are waiting for
> > is available.
> There may be no device, but resource. And we become again to the something like
> deferred probe ugly hack.
> The real solution is to rework device driver model in the kernel that it will
> create a graph of dependencies and then simply follow it. But actually it should
> be more than 1 graph, because there are resources and there are power, clock and
> resets that may be orthogonal to the higher dependencies (like driver X provides
> a resource to driver Y).

We already do this with fw_devlink for DT based systems and we do
effectively just probe the devices in graph order (by deferring any
attempts that happen too early and before it even gets to the driver).
The problem is the knowledge of what's considered an optional vs
mandatory dependency and that's affected by the global state of driver
support in the kernel.


Powered by blists - more mailing lists