From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: mikey@neuling.org, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH V3] powerpc/irq: Enable some more exceptions in /proc/interrupts interface
Date: Tue, 21 Jul 2015 13:43:04 +0530 [thread overview]
Message-ID: <55ADFF10.7030304@linux.vnet.ibm.com> (raw)
In-Reply-To: <1436775366-21945-1-git-send-email-khandual@linux.vnet.ibm.com>
On 07/13/2015 01:46 PM, Anshuman Khandual wrote:
> This patch enables facility unavailable exceptions for generic facility,
> FPU, ALTIVEC and VSX in /proc/interrupts listing by incrementing their
> newly added IRQ statistical counters as and when these exceptions happen.
> This also adds couple of helper functions which will be called from within
> the interrupt handler context to update their statistics. Similarly this
> patch also enables alignment and program check exceptions as well.
>
> With this patch being applied, /proc/interrupts looks something
> like this after running various workloads which create these exceptions.
>
> --------------------------------------------------------------
> CPU0 CPU1
> 16: 5734 24129 XICS 2 Level IPI
> 17: 0 0 XICS 4101 Level virtio0
> 18: 0 0 XICS 4100 Level ohci_hcd:usb1
> 19: 13920 0 XICS 4099 Level virtio1
> 20: 0 0 XICS 4096 Level RAS_EPOW
> 21: 6160 3241 XICS 4102 Level ibmvscsi
> 22: 1 0 XICS 4103 Level hvc_console
> LOC: 6825 3556 Local timer interrupts for timer event device
> LOC: 22 41 Local timer interrupts for others
> SPU: 1 0 Spurious interrupts
> PMI: 0 0 Performance monitoring interrupts
> MCE: 0 0 Machine check exceptions
> DBL: 0 0 Doorbell interrupts
> ALN: 0 0 Alignment exceptions
> PRG: 0 0 Program check exceptions
> FAC: 7 14 Facility unavailable exceptions
> FPU: 2928 3162 FPU unavailable exceptions
> ALT: 12950 15536 AltiVec unavailable exceptions
> VSX: 12930 220183 VSX unavailable exceptions
> --------------------------------------------------------------
>
> Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
> ---
> Changes in V3:
> - Changed the display string from "ALTIVEC" to "AltiVec"
> - Now captured "Facility unavailable exceptions" in the example
Michael/Mikey,
I had already posted the performance comparison details with the
patch in the previous version mail thread. Does this new version
look good enough ?
next prev parent reply other threads:[~2015-07-21 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 8:16 [PATCH V3] powerpc/irq: Enable some more exceptions in /proc/interrupts interface Anshuman Khandual
2015-07-21 8:13 ` Anshuman Khandual [this message]
2015-08-04 9:57 ` [V3] " Michael Ellerman
2015-08-06 13:24 ` Anshuman Khandual
2015-08-14 2:52 ` Michael Ellerman
2015-08-19 13:54 ` Anshuman Khandual
2015-08-09 2:27 ` Benjamin Herrenschmidt
2015-08-12 8:38 ` Anshuman Khandual
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=55ADFF10.7030304@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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).