LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sander Eikelenboom <linux@eikelenboom.it>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
David Vrabel <david.vrabel@citrix.com>,
Tony Luck <tony.luck@intel.com>, <linux-kernel@vger.kernel.org>,
<linux-pci@vger.kernel.org>
Subject: Re: [Bugfix 0/3] Xen IRQ related hotfixes for v3.19
Date: Mon, 9 Feb 2015 17:55:50 +0100 [thread overview]
Message-ID: <1809809558.20150209175550@eikelenboom.it> (raw)
In-Reply-To: <54D8DBC8.3020502@canonical.com>
Monday, February 9, 2015, 5:09:44 PM, you wrote:
> On 09.02.2015 13:29, Stefan Bader wrote:
>> On 09.02.2015 13:12, Jiang Liu wrote:
>>> On 2015/2/9 17:47, Stefan Bader wrote:
>>>> On 05.02.2015 21:07, Sander Eikelenboom wrote:
>>>>>
>>>>> Tuesday, January 20, 2015, 3:21:04 AM, you wrote:
>>>>>
>>>>>> Hi Thomas,
>>>>>> This patch set includes three hotfixes related Xen IRQ for v3.19.
>>>>>> Sorry for the long delay to get these two regressions fixed, it really
>>>>>> cost me some time to read and understand Xen IRQ code.
>>>>>
>>>>>> Patch 1 fixes the failure to register ACPI SCI interrupt on Xen
>>>>>> domain0 by reworking acpi_gsi_to_irq(). I will backport it to v3.18
>>>>>> too once it reaches the mainstream kernel.
>>>>>
>>>>>> Patch 2 fixes the regression in Xen PCI device passthrough(pciback).
>>>>>> It's a temporary solution, I will send the formal fix for v3.20 and
>>>>>> it has passed tests too.
>>>>>
>>>>>> Patch 3 fixes an issue found when reading code. There's no real bug
>>>>>> reports related to this issue yet.
>>>>>
>>>>>> Great thanks to Konrad and Sander for testing fixes for these regressions.
>>>>>
>>>>>> Regards,
>>>>>> Gerry
>>>>>
>>>>> Hi Gerry,
>>>>>
>>>>> Since these patches now are: tested, reviewed and have landed into mainline,
>>>>> could you also provide the backports for 3.17 and 3.18 where required ?
>>>>
>>>> This would be my attempt of backporting those to 3.18 (I have not tried whether
>>>> they would apply to 3.17 as well). Those seem to work when test-booting and
>>>> Sander said he will give them a try as well. But better check yourself I did not
>>>> mess anything up while backporting. One of the three patches seemed not to be
>>>> required at all.
>>> I'm backporting them too, but now I will give up my patches:)
>>>
>>> The first one is a must, which should be applied to 3.17 and 3.18.
>>> The second one doesn't apply to 3.17 or 3.18.
>>> The third may be applied to v3.17 and v3.18, but it shouldn't be applied
>>> according to the stable-kernel doc because no user reports such a bug yet.
>>
>> Hm, ok. So maybe I should retry with only patch#1 and verify that alone gets
>> around the acpi irq and the usb problems, too. Though interestingly from the
>> history, the acpi irq I saw in 3.17 while the usb devices started to fail with
>> 3.18. I will let you know in a bit. Just want to finish another bisect first.
> So it looks like patch #1 indeed does fix both the acpi irq and my usb devices.
> Sander, do you want to verify that variant, too?
Will test 3.18 with only patch 1 after dinner.
> The only odd thing left in a 3.18 with the fix (regardless of using patch #1
> only or patches #1 and #3) is that the ahci driver shows up with its pci bus
> number in /proc/interrupts. But that does not seem to have any relevant downside
> (cannot try 3.19 on that box right now for other reasons).
> -Stefan
> ...
> # 57: 12441 0 0 0 xen-pirq-msi 0000:00:1f.2
> # (used to be ahci)
Hmm funky .. now that you mention it .. i'm seeing that as well but only on an
intel machine.
intel .. on 3.19:
52: 13529 0 0 0 xen-pirq-msi 0000:00:1f.2
on my amd machine on 3.19 it seems ok though:
114: 412535 0 0 0 0 0 xen-pirq-msi ahci0
115: 0 0 0 0 0 0 xen-pirq-msi ahci1
116: 16717 0 0 0 0 0 xen-pirq-msi ahci2
117: 0 0 0 0 0 0 xen-pirq-msi ahci3
118: 0 0 0 0 0 0 xen-pirq-msi ahci4
119: 0 0 0 0 0 0 xen-pirq-msi ahci5
--
Sander
>>
>> -Stefan
>>
>>> Regards
>>> Gerry
>>>>
>>>> -Stefan
>>>>
>>>>>
>>>>> The number of people running into these (subtle) issues with these stable
>>>>> kernels seems to be steadily increasing.
>>>>>
>>>>> --
>>>>> Sander
>>>>>
>>>>>> Jiang Liu (3):
>>>>>> xen/pci: Kill function xen_setup_acpi_sci()
>>>>>> xen/irq, ACPI: Fix regression in xen PCI passthrough caused by
>>>>>> cffe0a2b5a34
>>>>>> xen/irq: Override ACPI IRQ management callback __acpi_unregister_gsi
>>>>>
>>>>>> arch/x86/include/asm/acpi.h | 1 +
>>>>>> arch/x86/kernel/acpi/boot.c | 26 +++++++++++------------
>>>>>> arch/x86/pci/xen.c | 49 ++-----------------------------------------
>>>>>> drivers/acpi/pci_irq.c | 1 -
>>>>>> 4 files changed, 16 insertions(+), 61 deletions(-)
>>>>>
>>>>>
>>>>
>>
>>
next prev parent reply other threads:[~2015-02-09 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 2:21 Jiang Liu
2015-01-20 2:21 ` [Bugfix 1/3] xen/pci: Kill function xen_setup_acpi_sci() Jiang Liu
2015-01-20 9:54 ` David Vrabel
2015-01-20 10:49 ` [tip:x86/urgent] x86/xen: Treat SCI interrupt as normal GSI interrupt tip-bot for Jiang Liu
2015-01-20 2:21 ` [Bugfix 2/3] xen/irq, ACPI: Fix regression in xen PCI passthrough caused by cffe0a2b5a34 Jiang Liu
2015-01-20 10:49 ` [tip:x86/urgent] ACPI: pci: Do not clear pci_dev-> irq in acpi_pci_irq_disable() tip-bot for Jiang Liu
2015-01-20 2:21 ` [Bugfix 3/3] xen/irq: Override ACPI IRQ management callback __acpi_unregister_gsi Jiang Liu
2015-01-20 9:56 ` David Vrabel
2015-01-20 10:50 ` [tip:x86/urgent] x86/xen: " tip-bot for Jiang Liu
2015-02-05 20:07 ` [Bugfix 0/3] Xen IRQ related hotfixes for v3.19 Sander Eikelenboom
2015-02-09 9:47 ` Stefan Bader
2015-02-09 12:12 ` Jiang Liu
2015-02-09 12:29 ` Stefan Bader
2015-02-09 16:09 ` Stefan Bader
2015-02-09 16:55 ` Sander Eikelenboom [this message]
2015-02-09 19:15 ` Sander Eikelenboom
2015-02-10 13:31 ` Stefan Bader
2015-02-09 12:17 ` Sander Eikelenboom
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=1809809558.20150209175550@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=david.vrabel@citrix.com \
--cc=jiang.liu@linux.intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stefan.bader@canonical.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--subject='Re: [Bugfix 0/3] Xen IRQ related hotfixes for v3.19' \
/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
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).