From: Jiang Liu <jiang.liu@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Chen Yu <yu.c.chen@intel.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Yinghai Lu <yinghai@kernel.org>,
Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Bugfix] x86, irq: Fix regression caused by commit d32932d02e18
Date: Thu, 30 Jul 2015 16:55:34 +0800 [thread overview]
Message-ID: <55B9E686.3090209@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1507301007470.3825@nanos>
On 2015/7/30 16:33, Thomas Gleixner wrote:
> On Thu, 30 Jul 2015, Jiang Liu wrote:
>
>> Commit d32932d02e18 ("x86/irq: Convert IOAPIC to use hierarchical
>> irqdomain interfaces") introduced a regression when converting IOAPIC
>> to hierarchy irqdomain, which sets wrong irq flow handler for IOAPIC
>> pins on Surface Pro 3 and causes failure when detecting I2C controllers.
>> It's caused by using stale attribute value when setting up IOAPIC pins.
>> With this patch applied, all IOAPIC IRQ configuration are identical
>> to v4.1 on Surface Pro 3.
>>
>> Fixes: d32932d02e18 ("x86/irq: Convert IOAPIC to use hierarchical irqdomain interfaces")
>> Reported-by: Matt Fleming <matt@codeblueprint.co.uk>
>> Tested-and-reported-by: Chen Yu <yu.c.chen@intel.com>
>> Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
>> ---
>> Hi Matt,
>> Could you please help to test this patch?
>> Thanks!
>> Gerry
>> ---
>> arch/x86/kernel/apic/io_apic.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
>> index 845dc0df2002..206052e55517 100644
>> --- a/arch/x86/kernel/apic/io_apic.c
>> +++ b/arch/x86/kernel/apic/io_apic.c
>> @@ -943,7 +943,7 @@ static bool mp_check_pin_attr(int irq, struct irq_alloc_info *info)
>> */
>> if (irq < nr_legacy_irqs() && data->count == 1) {
>> if (info->ioapic_trigger != data->trigger)
>> - mp_register_handler(irq, data->trigger);
>> + mp_register_handler(irq, info->ioapic_trigger);
>> data->entry.trigger = data->trigger = info->ioapic_trigger;
>> data->entry.polarity = data->polarity = info->ioapic_polarity;
>
> Pretty obvious, but I was staring at this very piece of code for hours
> without spotting it.
You have given me the most valuable hints about the difference in
irq flow handler:)
next prev parent reply other threads:[~2015-07-30 8:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 15:21 Regression in v4.2-rc1 caused by hierarchical irqdomain changes Matt Fleming
2015-07-27 15:21 ` Matt Fleming
[not found] ` <20150727152107.GA3571-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-07-27 16:35 ` Jiang Liu
2015-07-27 16:35 ` Jiang Liu
[not found] ` <55B65DD8.9020002-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-07-27 21:15 ` Matt Fleming
2015-07-27 21:15 ` Matt Fleming
[not found] ` <20150727211502.GA2492-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-07-29 21:03 ` Thomas Gleixner
2015-07-29 21:03 ` Thomas Gleixner
2015-07-30 4:08 ` Jiang Liu
2015-07-30 4:08 ` Jiang Liu
2015-07-30 7:51 ` [Bugfix] x86, irq: Fix regression caused by commit d32932d02e18 Jiang Liu
2015-07-30 8:33 ` Thomas Gleixner
2015-07-30 8:55 ` Jiang Liu [this message]
2015-07-30 9:07 ` Matt Fleming
2015-07-30 9:12 ` Jiang Liu
2015-07-30 9:46 ` Matt Fleming
2015-07-30 19:19 ` [tip:x86/urgent] x86/irq: Use the caller provided polarity setting in mp_check_pin_attr() tip-bot for Jiang 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=55B9E686.3090209@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
--cc=yu.c.chen@intel.com \
/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.