From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Frederic Barrat <fbarrat@linux.ibm.com>,
clg@kaod.org, mst@redhat.com, marcel.apfelbaum@gmail.com,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] pcie: Don't try triggering a LSI when not defined
Date: Thu, 24 Mar 2022 11:02:48 -0300 [thread overview]
Message-ID: <f3efd672-3d8e-8533-4aff-720c32d5800c@gmail.com> (raw)
In-Reply-To: <5a482e34-cadc-571a-360a-fb5ede7d8a2d@linux.ibm.com>
On 3/24/22 10:47, Frederic Barrat wrote:
>
>
> On 24/03/2022 14:07, Daniel Henrique Barboza wrote:
>>
>>
>> On 3/21/22 12:33, Frederic Barrat wrote:
>>> This patch skips [de]asserting a LSI interrupt if the device doesn't
>>> have any LSI defined. Doing so would trigger an assert in
>>> pci_irq_handler().
>>>
>>> The PCIE root port implementation in qemu requests a LSI (INTA), but a
>>> subclass may want to change that behavior since it's a valid
>>> configuration. For example on the POWER8/POWER9/POWER10 systems, the
>>> root bridge doesn't request any LSI.
>>>
>>> Signed-off-by: Frederic Barrat <fbarrat@linux.ibm.com>
>>> ---
>>
>> I assume that it's easier to handle just the codepaths that powernv PHBs uses
>> rather than handling all instances where pci_irq_handler() would be asserting
>> without LSIs.
>
>
> The real reason is that the LSI is added when we realize the TYPE_PCIE_ROOT_PORT object. See rp_realize(). So I'm only trying to fix the code paths that can be called from a subclass of TYPE_PCIE_ROOT_PORT which would choose to override the "interrupt pin" setting in the config space. I believe they are all covered by this patch.
> The assert() in pci_irq_handler() is there for a reason and I don't want to mess with that.
Yes, handling this situation inside pci_irq_handler() would require changing the
"assert(0 <= irq_num && irq_num < PCI_NUM_PINS)" assert or doing some sanity before
it to avoid the trigger.
Since this is a common code used everywhere we're better of doing minimalist changes
as you're doing. We can reevaluate this design if more machines/devices start to get
in the same situation we have now with powernv PHBs.
Daniel
>
> Fred
>
>
>>
>>
>> Patch LGTM. Small nits below:
>>
>>> hw/pci/pcie.c | 8 ++++++--
>>> hw/pci/pcie_aer.c | 4 +++-
>>> 2 files changed, 9 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
>>> index 67a5d67372..71c5194b80 100644
>>> --- a/hw/pci/pcie.c
>>> +++ b/hw/pci/pcie.c
>>> @@ -354,7 +354,9 @@ static void hotplug_event_notify(PCIDevice *dev)
>>> } else if (msi_enabled(dev)) {
>>> msi_notify(dev, pcie_cap_flags_get_vector(dev));
>>> } else {
>>> - pci_set_irq(dev, dev->exp.hpev_notified);
>>> + if (pci_intx(dev) != -1) {
>>> + pci_set_irq(dev, dev->exp.hpev_notified);
>>> + }
>>
>>
>> Since you're not doing anything unless the condition is met, you can use 'else if'
>> like it's done in the other conditionals:
>>
>>
>> if (msix_enabled(dev)) {
>> msix_notify(dev, pcie_cap_flags_get_vector(dev));
>> } else if (msi_enabled(dev)) {
>> msi_notify(dev, pcie_cap_flags_get_vector(dev));
>> } else if (pci_intx(dev) != -1) {
>> pci_set_irq(dev, dev->exp.hpev_notified);
>> }
>>
>>
>>
>>> }
>>> }
>>> @@ -362,7 +364,9 @@ static void hotplug_event_clear(PCIDevice *dev)
>>> {
>>> hotplug_event_update_event_status(dev);
>>> if (!msix_enabled(dev) && !msi_enabled(dev) && !dev->exp.hpev_notified) {
>>> - pci_irq_deassert(dev);
>>> + if (pci_intx(dev) != -1) {
>>> + pci_irq_deassert(dev);
>>> + }
>>> }
>>
>> Similar comment here:
>>
>> if (!msix_enabled(dev) && !msi_enabled(dev) && !dev->exp.hpev_notified &&
>> pci_intx(dev) != -1) {
>> pci_irq_deassert(dev);
>> }
>>
>>
>>
>>> }
>>> diff --git a/hw/pci/pcie_aer.c b/hw/pci/pcie_aer.c
>>> index e1a8a88c8c..d936bfca20 100644
>>> --- a/hw/pci/pcie_aer.c
>>> +++ b/hw/pci/pcie_aer.c
>>> @@ -291,7 +291,9 @@ static void pcie_aer_root_notify(PCIDevice *dev)
>>> } else if (msi_enabled(dev)) {
>>> msi_notify(dev, pcie_aer_root_get_vector(dev));
>>> } else {
>>> - pci_irq_assert(dev);
>>> + if (pci_intx(dev) != -1) {
>>> + pci_irq_assert(dev);
>>> + }
>>
>>
>> And here:
>>
>> if (msix_enabled(dev)) {
>> msix_notify(dev, pcie_aer_root_get_vector(dev));
>> } else if (msi_enabled(dev)) {
>> msi_notify(dev, pcie_aer_root_get_vector(dev));
>> } else if (pci_intx(dev) != -1) {
>> pci_irq_assert(dev);
>> }
>>
>>
>>
>> Thanks,
>>
>>
>> Daniel
>>
>>> }
>>> }
next prev parent reply other threads:[~2022-03-24 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 15:33 [PATCH 0/2] Remove PCIE root bridge LSI on powernv Frederic Barrat
2022-03-21 15:33 ` [PATCH 1/2] pcie: Don't try triggering a LSI when not defined Frederic Barrat
2022-03-24 13:07 ` Daniel Henrique Barboza
2022-03-24 13:47 ` Frederic Barrat
2022-03-24 14:02 ` Daniel Henrique Barboza [this message]
2022-03-21 15:33 ` [PATCH 2/2] ppc/pnv: Remove LSI on the PCIE host bridge Frederic Barrat
2022-03-24 13:10 ` Daniel Henrique Barboza
2022-04-06 7:52 ` [PATCH 0/2] Remove PCIE root bridge LSI on powernv Michael S. Tsirkin
2022-04-06 8:57 ` Frederic Barrat
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=f3efd672-3d8e-8533-4aff-720c32d5800c@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).