[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1497524175.2897.75.camel@kernel.crashing.org>
Date: Thu, 15 Jun 2017 20:56:15 +1000
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Michael Ellerman <mpe@...erman.id.au>,
Alexey Kardashevskiy <aik@...abs.ru>,
linuxppc-dev@...ts.ozlabs.org
Cc: kvm@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org,
Gavin Shan <gwshan@...ux.vnet.ibm.com>,
Yongji Xie <elohimes@...il.com>,
Alex Williamson <alex.williamson@...hat.com>,
Paul Mackerras <paulus@...ba.org>,
Yongji Xie <xyjxie@...ux.vnet.ibm.com>,
David Gibson <david@...son.dropbear.id.au>
Subject: Re: [PATCH kernel 2/3] pci-ioda: Set PCI_BUS_FLAGS_MSI_REMAP for
IODA host bridge
On Thu, 2017-06-15 at 19:25 +1000, Michael Ellerman wrote:
> Alexey Kardashevskiy <aik@...abs.ru> writes:
>
> > From: Yongji Xie <elohimes@...il.com>
> >
> > Any IODA host bridge have the capability of IRQ remapping.
> > So we set PCI_BUS_FLAGS_MSI_REMAP when this kind of host birdge
> > is detected.
>
> Where's the code that actually enforces this property?
>
> It would be good to have a comment in pnv_pci_ioda_root_bridge_prepare()
> (probably), pointing to that code, so that we can remember the
> relationship between the two.
Actually it's not so much remapping as:
- The bridge can enforce that the interrupt is allowed for a given
partition
- Because the interrupts are handled via the hypervisor, the latter
can do the remapping.
But the effect is the same, so yes we want the flag. On P9 with XIVE
exploitation we also have HW remapping on top.
Cheers,
Ben.
Powered by blists - more mailing lists