All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yijing Wang <wangyijing0307@gmail.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
	Yijing Wang <wangyijing@huawei.com>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jiang Liu <jiang.liu@linux.intel.com>,
	Will Deacon <Will.Deacon@arm.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>
Subject: Re: Removal of bus->msi assignment breaks MSI with stacked domains
Date: Fri, 21 Nov 2014 19:57:01 +0800	[thread overview]
Message-ID: <546F288D.2040705@gmail.com> (raw)
In-Reply-To: <546F0FB6.3050404@arm.com>


在 2014/11/21 18:11, Marc Zyngier 写道:
> On 21/11/14 01:22, Yijing Wang wrote:
>> On 2014/11/21 0:31, Marc Zyngier wrote:
>>> Bjorn, Yijing,
>>>
>>> I've just realized that patch c167caf8d174 (PCI/MSI: Remove useless
>>> bus->msi assignment) completely breaks MSI on arm64 when using the new
>>> MSI stacked domain:
>> Sorry, this is my first part to refactor MSI related code, now
>> how to get pci msi_controller depends arch functions(pcibios_msi_controller() or
>> arch_setup_msi_irq()), we are working on generic pci_host_bridge, after that,
>> we could eventually eliminate MSI arch functions and find pci dev 's msi controller
>> by pci_host_bridge->get_msi_controller().
>>
>> Marc, could you tell me what pci host driver in your test platform ?
> I'm using pci-host-generic (with a couple of patches to help it fit the
> new "generic pci" infrastructure).
>
> This lives at:
> git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
> irq/arm64-pci

Thanks, I would have a look at it.

>
> Thanks,
>
> 	M.


WARNING: multiple messages have this Message-ID (diff)
From: wangyijing0307@gmail.com (Yijing Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: Removal of bus->msi assignment breaks MSI with stacked domains
Date: Fri, 21 Nov 2014 19:57:01 +0800	[thread overview]
Message-ID: <546F288D.2040705@gmail.com> (raw)
In-Reply-To: <546F0FB6.3050404@arm.com>


? 2014/11/21 18:11, Marc Zyngier ??:
> On 21/11/14 01:22, Yijing Wang wrote:
>> On 2014/11/21 0:31, Marc Zyngier wrote:
>>> Bjorn, Yijing,
>>>
>>> I've just realized that patch c167caf8d174 (PCI/MSI: Remove useless
>>> bus->msi assignment) completely breaks MSI on arm64 when using the new
>>> MSI stacked domain:
>> Sorry, this is my first part to refactor MSI related code, now
>> how to get pci msi_controller depends arch functions(pcibios_msi_controller() or
>> arch_setup_msi_irq()), we are working on generic pci_host_bridge, after that,
>> we could eventually eliminate MSI arch functions and find pci dev 's msi controller
>> by pci_host_bridge->get_msi_controller().
>>
>> Marc, could you tell me what pci host driver in your test platform ?
> I'm using pci-host-generic (with a couple of patches to help it fit the
> new "generic pci" infrastructure).
>
> This lives at:
> git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
> irq/arm64-pci

Thanks, I would have a look at it.

>
> Thanks,
>
> 	M.

  reply	other threads:[~2014-11-21 11:57 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 16:31 Removal of bus->msi assignment breaks MSI with stacked domains Marc Zyngier
2014-11-20 16:31 ` Marc Zyngier
2014-11-20 21:53 ` Bjorn Helgaas
2014-11-20 21:53   ` Bjorn Helgaas
2014-11-20 23:10   ` Thomas Gleixner
2014-11-20 23:10     ` Thomas Gleixner
2014-11-20 23:30     ` Bjorn Helgaas
2014-11-20 23:30       ` Bjorn Helgaas
2014-11-21  9:33       ` Marc Zyngier
2014-11-21  9:33         ` Marc Zyngier
2014-11-21  1:54     ` Yijing Wang
2014-11-21  1:54       ` Yijing Wang
2014-11-21  2:25       ` Jiang Liu
2014-11-21  2:25         ` Jiang Liu
2014-11-21  3:46         ` Yijing Wang
2014-11-21  3:46           ` Yijing Wang
2014-11-21 10:00       ` Marc Zyngier
2014-11-21 10:00         ` Marc Zyngier
2014-11-21 17:31       ` Bjorn Helgaas
2014-11-21 17:31         ` Bjorn Helgaas
2014-11-22  4:13         ` Yijing Wang
2014-11-22  4:13           ` Yijing Wang
2014-11-21  1:22 ` Yijing Wang
2014-11-21  1:22   ` Yijing Wang
2014-11-21  1:46   ` Thomas Gleixner
2014-11-21  1:46     ` Thomas Gleixner
2014-11-21  2:03     ` Jiang Liu
2014-11-21  2:03       ` Jiang Liu
2014-11-21  2:12       ` Yijing Wang
2014-11-21  2:12         ` Yijing Wang
2014-11-21  2:05     ` Yijing Wang
2014-11-21  2:05       ` Yijing Wang
2014-11-21  8:46       ` Lucas Stach
2014-11-21  8:46         ` Lucas Stach
2014-11-21 10:29     ` Marc Zyngier
2014-11-21 10:29       ` Marc Zyngier
2014-11-21 10:49       ` Thomas Gleixner
2014-11-21 10:49         ` Thomas Gleixner
2014-11-21 11:30         ` Marc Zyngier
2014-11-21 11:30           ` Marc Zyngier
2014-11-21 12:04       ` Yijing Wang
2014-11-21 12:04         ` Yijing Wang
2014-11-21 10:11   ` Marc Zyngier
2014-11-21 10:11     ` Marc Zyngier
2014-11-21 11:57     ` Yijing Wang [this message]
2014-11-21 11:57       ` 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=546F288D.2040705@gmail.com \
    --to=wangyijing0307@gmail.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=bhelgaas@google.com \
    --cc=jiang.liu@linux.intel.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=tglx@linutronix.de \
    --cc=wangyijing@huawei.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.