From: Michael Ellerman <michael@ellerman.id.au>
To: Ian Munsie <imunsie@au1.ibm.com>
Cc: Michael Neuling <mikey@neuling.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc: Add accounting for Doorbell interrupts
Date: Fri, 22 Mar 2013 15:18:03 +1100 [thread overview]
Message-ID: <20130322041803.GB26908@concordia> (raw)
In-Reply-To: <1363765332-28461-1-git-send-email-imunsie@au1.ibm.com>
On Wed, Mar 20, 2013 at 06:42:12PM +1100, Ian Munsie wrote:
> From: Ian Munsie <imunsie@au1.ibm.com>
>
> This patch adds a new line to /proc/interrupts to account for the
> doorbell interrupts that each hardware thread has received. The total
> interrupt count in /proc/stat will now also include doorbells.
Should it be inside CONFIG_PPC_DOORBELL ?
cheers
next prev parent reply other threads:[~2013-03-22 4:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 7:42 [PATCH] powerpc: Add accounting for Doorbell interrupts Ian Munsie
2013-03-21 0:28 ` Michael Neuling
2013-03-22 4:18 ` Michael Ellerman [this message]
2013-03-22 5:13 ` Ian Munsie
2013-03-22 5:22 ` [PATCH v2] " Ian Munsie
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=20130322041803.GB26908@concordia \
--to=michael@ellerman.id.au \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
/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).