mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shijith Thotton <sthotton@marvell.com>
To: Julien Thierry <julien.thierry@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	"Jayachandran Chandrasekharan Nair" <jnair@marvell.com>,
	Ganapatrao Kulkarni <gkulkarni@marvell.com>,
	Jan Glauber <jglauber@marvell.com>,
	Robert Richter <rrichter@marvell.com>
Subject: Re: [PATCH] genirq: update irq stats from NMI handlers
Date: Thu, 4 Jul 2019 10:36:57 +0000	[thread overview]
Message-ID: <a4ce3800-22f4-72dc-6ff8-75dfed1c377b@marvell.com> (raw)
In-Reply-To: <6adfb296-50f1-9efb-0840-cc8732b8ebf9@arm.com>


Hi Julien,

On 7/4/19 12:13 AM, Julien Thierry wrote:
> On 04/07/2019 05:22, Shijith Thotton wrote:
>> The NMI handlers handle_percpu_devid_fasteoi_nmi() and
>> handle_fasteoi_nmi() added by commit 2dcf1fbcad35 ("genirq: Provide NMI
>> handlers") do not update the interrupt counts. Due to that the NMI
>> interrupt count does not show up correctly in /proc/interrupts.
>>
>> Update the functions to fix this. With this change, we can see stats of
>> the perf NMI interrupts on arm64.
>>
>> Fixes: 2dcf1fbcad35 ("genirq: Provide NMI handlers")
>>
>> Signed-off-by: Shijith Thotton <sthotton@marvell.com>
>> ---
>>   kernel/irq/chip.c | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
>> index 29d6c7d070b4..88d1e054c6ea 100644
>> --- a/kernel/irq/chip.c
>> +++ b/kernel/irq/chip.c
>> @@ -748,6 +748,8 @@ void handle_fasteoi_nmi(struct irq_desc *desc)
>>   	unsigned int irq = irq_desc_get_irq(desc);
>>   	irqreturn_t res;
>>   
>> +	kstat_incr_irqs_this_cpu(desc);
>> +
> 
> This needs to be called with the desc lock taken, otherwise we're likely
> to corrupt desc->tot_count.
> But taking the desc lock is something we can't do in NMI context (
> *spin_lock_irq*() won't prevent an NMI from happening).
> 
>>   	trace_irq_handler_entry(irq, action);
>>   	/*
>>   	 * NMIs cannot be shared, there is only one action.
>> @@ -962,6 +964,8 @@ void handle_percpu_devid_fasteoi_nmi(struct irq_desc *desc)
>>   	unsigned int irq = irq_desc_get_irq(desc);
>>   	irqreturn_t res;
>>   
>> +	__kstat_incr_irqs_this_cpu(desc);
>> +
> 
> Looking at handle_percpu_irq(), I think this might be acceptable. But
> does it make sense to only have kstats for percpu NMIs?
> 

It would be better to have stats for both.

handle_fasteoi_nmi() can use __kstat_incr_irqs_this_cpu() if below 
change can be added to kstat_irqs_cpu().

diff --git a/kernel/irq/irqdesc.c b/kernel/irq/irqdesc.c
index a92b33593b8d..9484e88dabc2 100644
--- a/kernel/irq/irqdesc.c
+++ b/kernel/irq/irqdesc.c
@@ -950,6 +950,11 @@ unsigned int kstat_irqs_cpu(unsigned int irq, int cpu)
                         *per_cpu_ptr(desc->kstat_irqs, cpu) : 0;
  }

+static bool irq_is_nmi(struct irq_desc *desc)
+{
+       return desc->istate & IRQS_NMI;
+}
+
  /**
   * kstat_irqs - Get the statistics for an interrupt
   * @irq:       The interrupt number
@@ -967,7 +972,8 @@ unsigned int kstat_irqs(unsigned int irq)
         if (!desc || !desc->kstat_irqs)
                 return 0;
         if (!irq_settings_is_per_cpu_devid(desc) &&
-           !irq_settings_is_per_cpu(desc))
+           !irq_settings_is_per_cpu(desc) &&
+           !irq_is_nmi(desc))
             return desc->tot_count;

         for_each_possible_cpu(cpu)


Thomas,
Please suggest a better way if any.

Thanks,
Shijith

  reply	other threads:[~2019-07-04 10:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  4:22 Shijith Thotton
2019-07-04  7:13 ` Julien Thierry
2019-07-04 10:36   ` Shijith Thotton [this message]
2019-07-04 16:19     ` Thomas Gleixner
2019-07-04 16:31       ` Shijith Thotton
2019-07-05  7:56 ` [PATCH v2] " Shijith Thotton
2019-07-06  8:43   ` [tip:irq/core] genirq: Update " tip-bot for Shijith Thotton

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=a4ce3800-22f4-72dc-6ff8-75dfed1c377b@marvell.com \
    --to=sthotton@marvell.com \
    --cc=catalin.marinas@arm.com \
    --cc=gkulkarni@marvell.com \
    --cc=jglauber@marvell.com \
    --cc=jnair@marvell.com \
    --cc=julien.thierry@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rrichter@marvell.com \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.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®