From: Bjorn Helgaas <helgaas@kernel.org>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: linux-acpi@vger.kernel.org, rjw@rjwysocki.net,
bhelgaas@google.com, ravikanth.nalla@hpe.com,
linux@rainbow-software.org, timur@codeaurora.org,
cov@codeaurora.org, jcm@redhat.com, alex.williamson@redhat.com,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-pci@vger.kernel.org, agross@codeaurora.org,
Robert Moore <robert.moore@intel.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Lv Zheng <lv.zheng@intel.com>,
linux-arm-msm@vger.kernel.org, wim@djo.tudelft.nl,
devel@acpica.org, Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH V4 3/3] Revert "ACPI, PCI, IRQ: separate ISA penalty calculation"
Date: Sat, 22 Oct 2016 18:59:18 -0500 [thread overview]
Message-ID: <20161022235918.GJ9007@localhost> (raw)
In-Reply-To: <8dcd59ac-815b-da71-a3f2-ba533c4182c9@codeaurora.org>
On Thu, Oct 20, 2016 at 07:58:57PM -0700, Sinan Kaya wrote:
> On 10/20/2016 7:31 PM, Bjorn Helgaas wrote:
> ...
> > And I don't think it fixes a user-visible problem, so it doesn't need
> > to be applied immediately. I'm not sure this is worth doing by
> > itself; maybe it should wait until we can do more cleanup and think
> > about all these issues together?
>
> It does fix the PCI_USING penalty assignment.
>
> if (link->irq.active && link->irq.active == irq)
> penalty += PIRQ_PENALTY_PCI_USING;
>
>
> If we drop this patch, then we need
> [PATCH V3 1/3] ACPI, PCI IRQ: add PCI_USING penalty for ISA interrupts
>
> http://www.gossamer-threads.com/lists/linux/kernel/2547605
>
> as somebody needs to increment the penalty with PCI_USING when IRQ is assigned
> for a given ISA IRQ.
>
> We might as well take [PATCH V4 1/3], [PATCH V4 2/3] and [PATCH V3 1/3]
> for this regression.
It sounds like either V3 1/3 or V4 3/3 will fix the regression. The
V3 1/3 patch is much smaller and essentially makes this piece look
like it did in v4.6.
The V4 3/3 patch removes acpi_irq_penalty_init() and compensates by
using acpi_irq_pci_sharing_penalty() for ISA IRQs again. But
acpi_irq_penalty_init() added PIRQ_PENALTY_PCI_POSSIBLE for _CRS, and
only if there was no _PRS, while acpi_irq_pci_sharing_penalty() always
adds PIRQ_PENALTY_PCI_USING for _CRS, regardless of whether _PRS
exists.
Since V4 3/3 is so much bigger and makes this quite subtle change in
how _CRS is handled, I like V3 1/3 better.
Are we all set to go now? I think I've acked the patches you
mentioned.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: helgaas@kernel.org (Bjorn Helgaas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 3/3] Revert "ACPI, PCI, IRQ: separate ISA penalty calculation"
Date: Sat, 22 Oct 2016 18:59:18 -0500 [thread overview]
Message-ID: <20161022235918.GJ9007@localhost> (raw)
In-Reply-To: <8dcd59ac-815b-da71-a3f2-ba533c4182c9@codeaurora.org>
On Thu, Oct 20, 2016 at 07:58:57PM -0700, Sinan Kaya wrote:
> On 10/20/2016 7:31 PM, Bjorn Helgaas wrote:
> ...
> > And I don't think it fixes a user-visible problem, so it doesn't need
> > to be applied immediately. I'm not sure this is worth doing by
> > itself; maybe it should wait until we can do more cleanup and think
> > about all these issues together?
>
> It does fix the PCI_USING penalty assignment.
>
> if (link->irq.active && link->irq.active == irq)
> penalty += PIRQ_PENALTY_PCI_USING;
>
>
> If we drop this patch, then we need
> [PATCH V3 1/3] ACPI, PCI IRQ: add PCI_USING penalty for ISA interrupts
>
> http://www.gossamer-threads.com/lists/linux/kernel/2547605
>
> as somebody needs to increment the penalty with PCI_USING when IRQ is assigned
> for a given ISA IRQ.
>
> We might as well take [PATCH V4 1/3], [PATCH V4 2/3] and [PATCH V3 1/3]
> for this regression.
It sounds like either V3 1/3 or V4 3/3 will fix the regression. The
V3 1/3 patch is much smaller and essentially makes this piece look
like it did in v4.6.
The V4 3/3 patch removes acpi_irq_penalty_init() and compensates by
using acpi_irq_pci_sharing_penalty() for ISA IRQs again. But
acpi_irq_penalty_init() added PIRQ_PENALTY_PCI_POSSIBLE for _CRS, and
only if there was no _PRS, while acpi_irq_pci_sharing_penalty() always
adds PIRQ_PENALTY_PCI_USING for _CRS, regardless of whether _PRS
exists.
Since V4 3/3 is so much bigger and makes this quite subtle change in
how _CRS is handled, I like V3 1/3 better.
Are we all set to go now? I think I've acked the patches you
mentioned.
Bjorn
next prev parent reply other threads:[~2016-10-22 23:59 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 22:21 [PATCH V4 0/3] ACPI,PCI,IRQ: revert penalty calculation for ISA and SCI interrupts Sinan Kaya
2016-10-19 22:21 ` [PATCH V4 0/3] ACPI, PCI, IRQ: " Sinan Kaya
2016-10-19 22:21 ` Sinan Kaya
2016-10-19 22:21 ` [PATCH V4 1/3] ACPI, PCI, IRQ: assign ISA IRQ directly during early boot stages Sinan Kaya
2016-10-19 22:21 ` Sinan Kaya
2016-10-19 22:21 ` Sinan Kaya
2016-10-20 21:39 ` Rafael J. Wysocki
2016-10-20 21:39 ` Rafael J. Wysocki
2016-10-24 3:48 ` Sinan Kaya
2016-10-24 3:48 ` Sinan Kaya
2016-10-21 1:39 ` Bjorn Helgaas
2016-10-21 1:39 ` Bjorn Helgaas
2016-10-21 14:07 ` Bjorn Helgaas
2016-10-21 14:07 ` Bjorn Helgaas
2016-10-24 3:22 ` Sinan Kaya
2016-10-24 3:22 ` Sinan Kaya
2016-10-23 3:48 ` [V4, " Jonathan Liu
2016-10-23 3:48 ` Jonathan Liu
2016-10-24 4:17 ` Sinan Kaya
2016-10-24 4:17 ` Sinan Kaya
2016-10-24 4:21 ` Jonathan Liu
2016-10-24 4:21 ` Jonathan Liu
2016-10-19 22:21 ` [PATCH V4 2/3] Revert "ACPI,PCI,IRQ: remove SCI penalize function" Sinan Kaya
2016-10-19 22:21 ` Sinan Kaya
2016-10-19 22:21 ` Sinan Kaya
2016-10-21 1:58 ` Bjorn Helgaas
2016-10-21 1:58 ` Bjorn Helgaas
2016-10-21 14:45 ` Bjorn Helgaas
2016-10-21 14:45 ` Bjorn Helgaas
2016-10-21 16:13 ` Sinan Kaya
2016-10-21 16:13 ` Sinan Kaya
2016-10-22 14:57 ` Bjorn Helgaas
2016-10-22 14:57 ` Bjorn Helgaas
2016-10-24 3:48 ` Sinan Kaya
2016-10-24 3:48 ` Sinan Kaya
2016-10-22 23:28 ` Bjorn Helgaas
2016-10-22 23:28 ` Bjorn Helgaas
2016-10-24 3:48 ` Sinan Kaya
2016-10-24 3:48 ` Sinan Kaya
2016-10-23 3:49 ` [V4,2/3] " Jonathan Liu
2016-10-23 3:49 ` Jonathan Liu
2016-10-19 22:21 ` [PATCH V4 3/3] Revert "ACPI,PCI,IRQ: separate ISA penalty calculation" Sinan Kaya
2016-10-19 22:21 ` [PATCH V4 3/3] Revert "ACPI, PCI, IRQ: " Sinan Kaya
2016-10-19 22:21 ` Sinan Kaya
2016-10-21 2:31 ` Bjorn Helgaas
2016-10-21 2:31 ` Bjorn Helgaas
2016-10-21 2:58 ` Sinan Kaya
2016-10-21 2:58 ` Sinan Kaya
2016-10-22 23:59 ` Bjorn Helgaas [this message]
2016-10-22 23:59 ` Bjorn Helgaas
2016-10-24 4:16 ` Sinan Kaya
2016-10-24 4:16 ` Sinan Kaya
2016-10-23 3:49 ` [V4,3/3] Revert "ACPI,PCI,IRQ: " Jonathan Liu
2016-10-23 3:49 ` Jonathan Liu
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=20161022235918.GJ9007@localhost \
--to=helgaas@kernel.org \
--cc=agross@codeaurora.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=cov@codeaurora.org \
--cc=devel@acpica.org \
--cc=hpa@zytor.com \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=lv.zheng@intel.com \
--cc=mingo@redhat.com \
--cc=okaya@codeaurora.org \
--cc=ravikanth.nalla@hpe.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=tglx@linutronix.de \
--cc=timur@codeaurora.org \
--cc=wim@djo.tudelft.nl \
--cc=x86@kernel.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 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.