From: Mike Qiu <qiudayu@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, Mike Qiu <qiudayu@linux.vnet.ibm.com>
Subject: [PATCH 0/3] Enable multiple MSI feature in pSeries
Date: Tue, 15 Jan 2013 15:38:53 +0800 [thread overview]
Message-ID: <1358235536-32741-1-git-send-email-qiudayu@linux.vnet.ibm.com> (raw)
Currently, multiple MSI feature hasn't been enabled in pSeries,
These patches try to enbale this feature.
These patches have been tested by using ipr driver, and the driver patch
has been made by Wen Xiong <wenxiong@linux.vnet.ibm.com>:
[PATCH 0/7] Add support for new IBM SAS controllers
Test platform: One partition of pSeries with one cpu core(4 SMTs) and
RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) in POWER7
OS version: SUSE Linux Enterprise Server 11 SP2 (ppc64) with 3.8-rc3 kernel
IRQ 21 and 22 are assigned to the ipr device which support 2 mutiple MSI.
The test results is shown by 'cat /proc/interrups':
CPU0 CPU1 CPU2 CPU3
16: 240458 261601 226310 200425 XICS Level IPI
17: 0 0 0 0 XICS Level RAS_EPOW
18: 10 0 3 2 XICS Level hvc_console
19: 122182 28481 28527 28864 XICS Level ibmvscsi
20: 506 7388226 108 118 XICS Level eth0
21: 6 5 5 5 XICS Level host1-0
22: 817 814 816 813 XICS Level host1-1
LOC: 398077 316725 231882 203049 Local timer interrupts
SPU: 1659 919 961 903 Spurious interrupts
CNT: 0 0 0 0 Performance
monitoring interrupts
MCE: 0 0 0 0 Machine check exceptions
Mike Qiu (3):
irq: Set multiple MSI descriptor data for multiple IRQs
irq: Add hw continuous IRQs map to virtual continuous IRQs support
powerpc/pci: Enable pSeries multiple MSI feature
arch/powerpc/kernel/msi.c | 4 --
arch/powerpc/platforms/pseries/msi.c | 62 ++++++++++++++++++++++++++++++++-
include/linux/irq.h | 4 ++
include/linux/irqdomain.h | 3 ++
kernel/irq/chip.c | 40 ++++++++++++++++-----
kernel/irq/irqdomain.c | 61 +++++++++++++++++++++++++++++++++
6 files changed, 158 insertions(+), 16 deletions(-)
--
1.7.7.6
next reply other threads:[~2013-01-15 7:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 7:38 Mike Qiu [this message]
2013-01-15 7:38 ` [PATCH 1/3] irq: Set multiple MSI descriptor data for multiple IRQs Mike Qiu
2013-06-05 23:03 ` Grant Likely
2013-01-15 7:38 ` [PATCH 2/3] irq: Add hw continuous IRQs map to virtual continuous IRQs support Mike Qiu
2013-03-05 2:23 ` Michael Ellerman
2013-03-05 7:19 ` Mike Qiu
2013-03-06 3:54 ` Michael Ellerman
2013-03-06 5:34 ` Mike Qiu
2013-03-06 5:42 ` Michael Ellerman
2013-03-06 7:02 ` Mike Qiu
2013-03-05 2:41 ` Paul Mundt
2013-03-05 7:44 ` Mike Qiu
2013-01-15 7:38 ` [PATCH 3/3] powerpc/pci: Enable pSeries multiple MSI feature Mike Qiu
2013-01-31 2:10 ` [PATCH 0/3] Enable multiple MSI feature in pSeries Mike
2013-02-04 3:23 ` Michael Ellerman
2013-02-04 3:49 ` Mike Qiu
2013-02-04 5:56 ` Michael Ellerman
2013-02-04 6:43 ` Mike Qiu
2013-03-01 3:07 ` Mike
2013-03-01 3:08 ` Mike
2013-03-01 3:54 ` Michael Ellerman
2013-03-04 3:14 ` Mike Qiu
2013-03-05 0:28 ` Michael Ellerman
2013-05-21 14:45 ` Alexander Gordeev
2013-05-22 0:15 ` Benjamin Herrenschmidt
2013-05-22 6:16 ` Mike Qiu
2013-05-22 5:57 ` Mike Qiu
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=1358235536-32741-1-git-send-email-qiudayu@linux.vnet.ibm.com \
--to=qiudayu@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).