linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Michael Walle <michael@walle.cc>,
	linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH] irqdomain: remove debugfs_file from struct irq_domain
Date: Thu, 18 Feb 2021 10:39:39 +0000	[thread overview]
Message-ID: <aada952a251b192acbdc163fc35dbd05@kernel.org> (raw)
In-Reply-To: <YC41eWXKjE77zIBo@kroah.com>

On 2021-02-18 09:38, Greg KH wrote:
> On Thu, Feb 18, 2021 at 09:04:42AM +0000, Marc Zyngier wrote:
>> On Thu, 18 Feb 2021 08:54:00 +0000,
>> Greg KH <gregkh@linuxfoundation.org> wrote:
>> 
>> [...]
>> 
>> > > > Wow, wait, you are removing a debugfs file _before_ debugfs is even
>> > > > initialized?  Didn't expect that, ok, let me go try this again...
>> > >
>> > > Yeah, that's a poor man's rename (file being deleted and re-created).
>> >
>> > True, but that's not happening here, right?  Some driver is being
>> > initialized and creates a debugfs file, and then decides to unload so it
>> > removes the debugfs file?
>> 
>> No, that's not what is happening.
>> 
>> The irqchip driver starts, creates an irqdomain. File gets created, at
>> least in theory (it fails because debugfs isn't ready, but that's not
>> the issue).
>> 
>> It then changes an attribute to the domain (the so-called bus_token),
>> which gets reflected in the domain name to avoid aliasing.
>> Delete/create follows.
>> 
>> > Why was it trying to create the file in the first place if it didn't
>> > properly bind to the hardware?
>> 
>> See above. We encode properties of the domain in the filename, and
>> reflect the change of these properties as they happen.
> 
> Ah, ok, you really are doing delete/re-create.  Crazy.  And amazing it
> was working previously without the checks I just added...
> 
> Funny that you all never were even noticing that the debugfs files are
> not present in the system because they are tryign to be created before
> debugfs is present?  Is that an issue or has no one complained?

See how irq_debugfs_init() is called in the middle of the boot sequence,
and retroactively populates all the debugfs files what we missed during
the early boot.

So we're not missing anything in the end, it's just delayed.

> Anyway, I'll go turn this into a real patch and get it into 5.12-rc1 so
> that the irqdomain patch I sent you will not blow anything up.  Feel
> free to also queue it up in your tree if you want to as well.

Thanks for that.

         M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2021-02-18 12:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 14:36 [PATCH] irqdomain: remove debugfs_file from struct irq_domain Greg Kroah-Hartman
2021-02-16 15:36 ` [irqchip: irq/irqchip-next] irqdomain: Remove " irqchip-bot for Greg Kroah-Hartman
2021-02-17 19:57 ` [PATCH] irqdomain: remove " Michael Walle
2021-02-17 20:02   ` Marc Zyngier
2021-02-17 20:10     ` Michael Walle
2021-02-17 21:50       ` Marc Zyngier
2021-02-17 22:21         ` Michael Walle
2021-02-18  7:16           ` Greg KH
2021-02-18  7:31         ` Greg KH
2021-02-18  8:27           ` Michael Walle
2021-02-18  8:38             ` Greg KH
2021-02-18  8:47               ` Marc Zyngier
2021-02-18  8:54                 ` Greg KH
2021-02-18  9:04                   ` Marc Zyngier
2021-02-18  9:38                     ` Greg KH
2021-02-18 10:39                       ` Marc Zyngier [this message]
2021-02-18  8:52             ` Greg KH
2021-02-18  9:04               ` Michael Walle
2021-02-18  9:08               ` Marc Zyngier
2021-02-18  8:40   ` Greg KH
2021-02-18  8:46     ` Michael Walle
2021-02-18 11:43 ` [irqchip: irq/irqchip-next] irqdomain: Remove " irqchip-bot for Greg Kroah-Hartman
2021-03-08 20:25 ` irqchip-bot for Greg Kroah-Hartman

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=aada952a251b192acbdc163fc35dbd05@kernel.org \
    --to=maz@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=tglx@linutronix.de \
    /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).