mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Thomas Gleixner <tglx@linutronix.de>,
	Nicholas Piggin <npiggin@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] genirq: reduce irqdebug bouncing cachelines
Date: Tue, 13 Apr 2021 14:16:36 +0200	[thread overview]
Message-ID: <b299bb0c-2997-6f6f-8646-4a7ecb2c79c0@kaod.org> (raw)
In-Reply-To: <87wnt71xmm.ffs@nanos.tec.linutronix.de>

Thomas,

>> We could test irq_settings_no_debug() directly under handle_nested_irq() 
>> and handle_irq_event_percpu() to avoid calling note_interrupt(), just 
>> like we do for noirqdebug.
> 
> We can do that, but then we should not just make it:
> 
>    if (!irqnodebug && !irq_settings_no_debug(desc))
>    	note_interrupt(...);
> 
> Instead have only one condition:
> 
>    if (!irq_settings_no_debug(desc))
>    	note_interrupt(...);
> 
> See the uncompiled delta patch below.

I merged this second part with the first and gave IRQF_NO_DEBUG a try 
on P8 and P9 systems and all looked fine. I should send both patches 
after IRQF_NO_AUTOEN is merged in mainline.     

Thanks,

C.

  reply	other threads:[~2021-04-13 12:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 13:20 Nicholas Piggin
2021-04-10 11:38 ` [tip: irq/core] genirq: Reduce irqdebug cacheline bouncing tip-bot2 for Nicholas Piggin
2021-04-10 11:58 ` [PATCH] genirq: reduce irqdebug bouncing cachelines Thomas Gleixner
2021-04-12  9:06   ` Cédric Le Goater
2021-04-12 12:43     ` Thomas Gleixner
2021-04-13 12:16       ` Cédric Le Goater [this message]
2021-04-13 20:24         ` Thomas Gleixner
2021-04-14 13:13           ` Cédric Le Goater
2021-05-15 17:01           ` Cédric Le Goater
2021-05-17 18:04             ` [tip: irq/core] genirq: Add a IRQF_NO_DEBUG flag tip-bot2 for Thomas Gleixner

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=b299bb0c-2997-6f6f-8646-4a7ecb2c79c0@kaod.org \
    --to=clg@kaod.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --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
all inboxes | Powered by JetHome®