From: Scott Wood <scottwood@freescale.com>
To: Jiang Liu <jiang.liu@linux.intel.com>
Cc: Tudor Laurentiu <b10716@freescale.com>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Ask help about killing irqchip.irq_print_chip on PPC platforms
Date: Tue, 23 Dec 2014 01:58:49 -0600 [thread overview]
Message-ID: <1419321529.5581.181.camel@freescale.com> (raw)
In-Reply-To: <5499204B.4040808@linux.intel.com>
On Tue, 2014-12-23 at 15:56 +0800, Jiang Liu wrote:
> Hi Scott and Tudor,
> Sorry, resend and Ccing the list.
Resending reply...
> We are trying to clean up some irqchip interfaces, and
> irqchip.irq_print_chip is a candidate for removal. After some
> changes on x86 side, arch/powerpc/sysdev/fsl_msi.c may be the
> last user of irqchip.irq_print_chip. So could you please help
> to advice on whether we could kill irqchip.irq_print_chip
> by using "fsl-msi" instead of "fsl-msi-%d" for irqchip name?
> Will it break any userspace interfaces?
> Thanks!
> Gerry
fsl-msi-%d was introduced to allow userspace to identify the cascade
interrupt belonging to a particular MSI, for the purpose of setting
affinity, as this cannot be done on the MSI itself due to hardware
limitations.
Removing it would not exactly eliminate a lot of code or complexity...
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Jiang Liu <jiang.liu@linux.intel.com>
Cc: Tudor Laurentiu <b10716@freescale.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: Ask help about killing irqchip.irq_print_chip on PPC platforms
Date: Tue, 23 Dec 2014 01:58:49 -0600 [thread overview]
Message-ID: <1419321529.5581.181.camel@freescale.com> (raw)
In-Reply-To: <5499204B.4040808@linux.intel.com>
On Tue, 2014-12-23 at 15:56 +0800, Jiang Liu wrote:
> Hi Scott and Tudor,
> Sorry, resend and Ccing the list.
Resending reply...
> We are trying to clean up some irqchip interfaces, and
> irqchip.irq_print_chip is a candidate for removal. After some
> changes on x86 side, arch/powerpc/sysdev/fsl_msi.c may be the
> last user of irqchip.irq_print_chip. So could you please help
> to advice on whether we could kill irqchip.irq_print_chip
> by using "fsl-msi" instead of "fsl-msi-%d" for irqchip name?
> Will it break any userspace interfaces?
> Thanks!
> Gerry
fsl-msi-%d was introduced to allow userspace to identify the cascade
interrupt belonging to a particular MSI, for the purpose of setting
affinity, as this cannot be done on the MSI itself due to hardware
limitations.
Removing it would not exactly eliminate a lot of code or complexity...
-Scott
next prev parent reply other threads:[~2014-12-23 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54991DE5.5090805@linux.intel.com>
2014-12-23 7:56 ` Ask help about killing irqchip.irq_print_chip on PPC platforms Jiang Liu
2014-12-23 7:56 ` Jiang Liu
2014-12-23 7:58 ` Scott Wood [this message]
2014-12-23 7:58 ` Scott Wood
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=1419321529.5581.181.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=b10716@freescale.com \
--cc=jiang.liu@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.