All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Yijing Wang <wangyijing0307@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Yijing Wang <wangyijing@huawei.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Ingo Molnar <mingo@redhat.com>,
	"grant.likely@linaro.org" <grant.likely@linaro.org>,
	Yingjoe Chen <yingjoe.chen@mediatek.com>,
	Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Tony Luck <tony.luck@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Patch V1 0/6] Refine generic/PCI MSI irqodmian interfaces
Date: Fri, 14 Nov 2014 23:25:13 +0800	[thread overview]
Message-ID: <54661ED9.8090901@linux.intel.com> (raw)
In-Reply-To: <54661CB8.2070704@arm.com>

On 2014/11/14 23:16, Marc Zyngier wrote:
> On 14/11/14 14:26, Jiang Liu wrote:
>> On 2014/11/14 22:11, Yijing Wang wrote:
>>>
>> We have achieved 1 and 2. And seems we could also achieve 3 by
>> converting all arch specific PCI MSI code to use hierarchy
>> irqdomain. But not sure whether we could achieve 4, not familiar
>> with ARM world:)
> 
> Killing all the weak functions shouldn't be a problem for ARM, we're
> trying very hard not to rely on them.
> 
> Killing msi_chip is a different story, as this is what we use to match a
> PCI host controller with its MSI controller (that's what the of_node
> field in msi_chip is for). See drivers/of/of_pci.c for details.
> 
> Also, we use msi_chip directly in the MSI drivers as a way to go from a
> pci_dev to the MSI controller specific structure:
> 
> http://git.kernel.org/cgit/linux/kernel/git/maz/arm-platforms.git/tree/drivers/irqchip/irq-gic-v3-its.c?h=irq/stacked-its-v2#n1143
> 
> If we're going to kill msi_chip, we must make sure we have mechanisms
> that allow the conversion of the existing code.
Hi Marc,
	Seem it doesn't worth the effort to remove irq_chip,
so I will focus on killing all weak functions first:)
After that, we may kill setup_irq and teardown_irq in irq_chip,
but seems irq_chip still has other usages, so I won't try to
kill irq_chip.
Regards!
Gerry
> 
> Thanks,
> 
> 	M.
> 

WARNING: multiple messages have this Message-ID (diff)
From: jiang.liu@linux.intel.com (Jiang Liu)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch V1 0/6] Refine generic/PCI MSI irqodmian interfaces
Date: Fri, 14 Nov 2014 23:25:13 +0800	[thread overview]
Message-ID: <54661ED9.8090901@linux.intel.com> (raw)
In-Reply-To: <54661CB8.2070704@arm.com>

On 2014/11/14 23:16, Marc Zyngier wrote:
> On 14/11/14 14:26, Jiang Liu wrote:
>> On 2014/11/14 22:11, Yijing Wang wrote:
>>>
>> We have achieved 1 and 2. And seems we could also achieve 3 by
>> converting all arch specific PCI MSI code to use hierarchy
>> irqdomain. But not sure whether we could achieve 4, not familiar
>> with ARM world:)
> 
> Killing all the weak functions shouldn't be a problem for ARM, we're
> trying very hard not to rely on them.
> 
> Killing msi_chip is a different story, as this is what we use to match a
> PCI host controller with its MSI controller (that's what the of_node
> field in msi_chip is for). See drivers/of/of_pci.c for details.
> 
> Also, we use msi_chip directly in the MSI drivers as a way to go from a
> pci_dev to the MSI controller specific structure:
> 
> http://git.kernel.org/cgit/linux/kernel/git/maz/arm-platforms.git/tree/drivers/irqchip/irq-gic-v3-its.c?h=irq/stacked-its-v2#n1143
> 
> If we're going to kill msi_chip, we must make sure we have mechanisms
> that allow the conversion of the existing code.
Hi Marc,
	Seem it doesn't worth the effort to remove irq_chip,
so I will focus on killing all weak functions first:)
After that, we may kill setup_irq and teardown_irq in irq_chip,
but seems irq_chip still has other usages, so I won't try to
kill irq_chip.
Regards!
Gerry
> 
> Thanks,
> 
> 	M.
> 

  reply	other threads:[~2014-11-14 15:25 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 11:43 [Patch V1 0/6] Refine generic/PCI MSI irqodmian interfaces Jiang Liu
2014-11-13 11:43 ` Jiang Liu
2014-11-13 11:43 ` [Patch V1 1/6] PCI, MSI: Fix errors caused by commit e5f1a59c4e12 Jiang Liu
2014-11-13 11:43   ` Jiang Liu
2014-11-13 11:43 ` [Patch V1 2/6] PCI, MSI: Introduce helpers to hide struct msi_desc implemenation details Jiang Liu
2014-11-13 11:43   ` Jiang Liu
2014-11-13 11:43 ` [Patch V1 3/6] genirq: Introduce msi_domain_{alloc|free}_irqs() Jiang Liu
2014-11-13 11:43   ` Jiang Liu
2014-11-13 20:23   ` Marc Zyngier
2014-11-13 20:23     ` Marc Zyngier
2014-11-14  0:18     ` Jiang Liu
2014-11-14  0:18       ` Jiang Liu
2014-11-13 11:43 ` [Patch V1 3/6] genirq: Introduce msi_irq_domain_{alloc|free}_irqs() Jiang Liu
2014-11-13 11:43   ` Jiang Liu
2014-11-13 12:34   ` Yijing Wang
2014-11-13 12:34     ` Yijing Wang
2014-11-13 12:41     ` Jiang Liu
2014-11-13 12:41       ` Jiang Liu
2014-11-13 12:57       ` Yijing Wang
2014-11-13 12:57         ` Yijing Wang
2014-11-13 11:43 ` [Patch V1 4/6] genirq: Provide default callbacks for msi_domain_ops Jiang Liu
2014-11-13 11:43   ` Jiang Liu
2014-11-13 11:43 ` [Patch V1 5/6] PCI, MSI: Refine irqdomain interfaces to simplify its usage Jiang Liu
2014-11-13 11:43   ` Jiang Liu
2014-11-13 11:43 ` [Patch V1 6/6] PCI, MSI: Provide mechanism to alloc/free MSI/MSIX interrupt from irqdomain Jiang Liu
2014-11-13 11:43   ` Jiang Liu
2014-11-13 19:46   ` Marc Zyngier
2014-11-13 19:46     ` Marc Zyngier
2014-11-13 12:28 ` [Patch V1 0/6] Refine generic/PCI MSI irqodmian interfaces Yijing Wang
2014-11-13 12:28   ` Yijing Wang
2014-11-13 12:39   ` Jiang Liu
2014-11-13 12:39     ` Jiang Liu
2014-11-13 12:55     ` Yijing Wang
2014-11-13 12:55       ` Yijing Wang
2014-11-13 13:03       ` Jiang Liu
2014-11-13 13:03         ` Jiang Liu
2014-11-13 13:05       ` Jiang Liu
2014-11-13 13:05         ` Jiang Liu
2014-11-13 21:00 ` Marc Zyngier
2014-11-13 21:00   ` Marc Zyngier
2014-11-13 21:11   ` Thomas Gleixner
2014-11-13 21:11     ` Thomas Gleixner
2014-11-13 21:28     ` Marc Zyngier
2014-11-13 21:28       ` Marc Zyngier
2014-11-14 15:54       ` Jiang Liu
2014-11-14 15:54         ` Jiang Liu
2014-11-14 16:13         ` Marc Zyngier
2014-11-14 16:13           ` Marc Zyngier
2014-11-14  0:25   ` Jiang Liu
2014-11-14  0:25     ` Jiang Liu
2014-11-14  1:09     ` Yijing Wang
2014-11-14  1:09       ` Yijing Wang
2014-11-14  1:22       ` Jiang Liu
2014-11-14  1:22         ` Jiang Liu
2014-11-14  1:31       ` Thomas Gleixner
2014-11-14  1:31         ` Thomas Gleixner
2014-11-14  1:39         ` Jiang Liu
2014-11-14  1:39           ` Jiang Liu
2014-11-14 12:13           ` Thomas Gleixner
2014-11-14 12:13             ` Thomas Gleixner
2014-11-14 14:11           ` Yijing Wang
2014-11-14 14:11             ` Yijing Wang
2014-11-14 14:26             ` Jiang Liu
2014-11-14 14:26               ` Jiang Liu
2014-11-14 15:16               ` Marc Zyngier
2014-11-14 15:16                 ` Marc Zyngier
2014-11-14 15:25                 ` Jiang Liu [this message]
2014-11-14 15:25                   ` Jiang Liu
2014-11-14 16:03                   ` Marc Zyngier
2014-11-14 16:03                     ` Marc Zyngier
2014-11-14 17:11                     ` Lucas Stach
2014-11-14 17:11                       ` Lucas Stach
2014-11-14  2:16         ` Yijing Wang
2014-11-14  2:16           ` Yijing Wang

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=54661ED9.8090901@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=grant.likely@linaro.org \
    --cc=hpa@zytor.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=wangyijing0307@gmail.com \
    --cc=wangyijing@huawei.com \
    --cc=yingjoe.chen@mediatek.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 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.