From: Jiang Liu <jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Matt Fleming
<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Regression in v4.2-rc1 caused by hierarchical irqdomain changes
Date: Thu, 30 Jul 2015 12:08:49 +0800 [thread overview]
Message-ID: <55B9A351.1060702@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1507292245000.3825@nanos>
On 2015/7/30 5:03, Thomas Gleixner wrote:
> On Mon, 27 Jul 2015, Matt Fleming wrote:
>> [BAD]
>> 3: 1 0 0 0 IR-IO-APIC 3-edge
>> 6: 0 0 0 0 IR-IO-APIC 6-edge dw_dmac
>> 7: 15 1 0 0 IR-IO-APIC 7-edge INT3432:00, INT3433:00
>
> [GOOD]
>> 3: 16 17 49 20 IR-IO-APIC-fasteoi AudioDSP, dw_dmac
>> 6: 0 0 0 0 IR-IO-APIC-fasteoi dw_dmac
>> 7: 2662 3072 12307 5419 IR-IO-APIC-fasteoi INT3432:00, INT3433:00
>
> So the old code uses fasteoi while the new one uses edge.
>
> Jiang????
Sorry for the slow response.
We have reproduced this regression on Surface Pro 3, but are still
trying to figure out the root cause.
Thanks!
Gerry
prev parent reply other threads:[~2015-07-30 4:08 UTC|newest]
Thread overview: 5+ 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
[not found] ` <20150727152107.GA3571-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-07-27 16:35 ` Jiang Liu
[not found] ` <55B65DD8.9020002-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
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-30 4:08 ` Jiang Liu [this message]
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=55B9A351.1060702@linux.intel.com \
--to=jiang.liu-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).