Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1505426
| From | Sinan Kaya <okaya@codeaurora.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V4 3/3] Revert "ACPI, PCI, IRQ: separate ISA penalty calculation" |
| Date | 2016-10-21 05:10 +0200 |
| Message-ID | <suynw-8hS-7@gated-at.bofh.it> (permalink) |
| References | <su7wZ-7rI-5@gated-at.bofh.it> <su7x0-7rI-41@gated-at.bofh.it> <suxUt-7SK-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 10/20/2016 7:31 PM, Bjorn Helgaas wrote:
>> Let's try to simplify the code one more time to share code.
> I'm sort of OK with this, but it's not exactly a revert of the above
> (the commits you mention don't check "link->irq.initialized == 1".
I can split the initialized bit. If I remove it from this commit, it can
break the git bisect. That's why, I folded it into this review. I
briefly mentioned about it in the cover letter. It might not be quiet
clear.
>
> Previously acpi_irq_penalty_init() looked at _PRS info ("possible"
> IRQs), but now we won't. Maybe that's good; I dunno. But it should
> be mentioned.
I'm directing all IRQs to acpi_irq_pci_sharing_penalty function.
acpi_irq_pci_sharing_penalty checks for the possible values here from
_PRS.
/*
* penalize the IRQs PCI might use, but not as severely.
*/
for (i = 0; i < link->irq.possible_count; i++)
if (link->irq.possible[i] == irq)
penalty += PIRQ_PENALTY_PCI_POSSIBLE /
link->irq.possible_count;
>
> 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.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH V4 3/3] Revert "ACPI,PCI,IRQ: separate ISA penalty calculation" Sinan Kaya <okaya@codeaurora.org> - 2016-10-20 00:30 +0200
Re: [PATCH V4 3/3] Revert "ACPI, PCI, IRQ: separate ISA penalty calculation" Bjorn Helgaas <helgaas@kernel.org> - 2016-10-21 04:40 +0200
Re: [PATCH V4 3/3] Revert "ACPI, PCI, IRQ: separate ISA penalty calculation" Sinan Kaya <okaya@codeaurora.org> - 2016-10-21 05:10 +0200
Re: [PATCH V4 3/3] Revert "ACPI, PCI, IRQ: separate ISA penalty calculation" Bjorn Helgaas <helgaas@kernel.org> - 2016-10-23 02:00 +0200
Re: [PATCH V4 3/3] Revert "ACPI, PCI, IRQ: separate ISA penalty calculation" Sinan Kaya <okaya@codeaurora.org> - 2016-10-24 06:20 +0200
Re: [V4,3/3] Revert "ACPI,PCI,IRQ: separate ISA penalty calculation" Jonathan Liu <net147@gmail.com> - 2016-10-23 05:50 +0200
csiph-web