The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: vcaputo@pengaru.com
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: thinkpad x60: sound problems in 4.15-rc1 was Re: thinkpad x60: sound problems in 4.14.0-next-20171114
Date: Sat, 23 Dec 2017 21:33:37 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1712232132500.1853@nanos> (raw)
In-Reply-To: <20171223203741.q4hwq6i33cjf3dyg@shells.gnugeneration.com>

On Sat, 23 Dec 2017, vcaputo@pengaru.com wrote:
> On Fri, Dec 22, 2017 at 09:37:01PM -0800, vcaputo@pengaru.com wrote:
> Added the following instrumentation:
> 
> diff --git a/arch/x86/kernel/apic/vector.c b/arch/x86/kernel/apic/vector.c
> index 93edc2236282..7034eda4d494 100644
> --- a/arch/x86/kernel/apic/vector.c
> +++ b/arch/x86/kernel/apic/vector.c
> @@ -228,6 +228,9 @@ static int __assign_irq_vector(int irq, struct apic_chip_data *d,
>         cpumask_and(vector_searchmask, vector_searchmask, mask);
>         BUG_ON(apic->cpu_mask_to_apicid(vector_searchmask, irqdata,
>                                         &d->cfg.dest_apicid));
> +
> +       printk("allocated vector=%i maskfirst=%i\n", d->cfg.vector, cpumask_first(vector_searchmask));
> +
>         return 0;
>  }
>  
> This is what I see:
> 
> Upon playing song in cmus (on AC power since boot):
>  Dec 22 22:26:52 iridesce kernel: allocated vector=35 maskfirst=1
> 
> Yank AC:
>  Dec 22 22:27:14 iridesce kernel: allocated vector=51 maskfirst=1
>  Dec 22 22:27:15 iridesce kernel: do_IRQ: 0.35 No irq handler for vector
> 
> So CPU 0 vector 35 got an interrupt when maskfirst=1 for 35 as seen in
> the added printk.
> 
> It seems like the affinity changes are assuming a strict adherence to
> the CPU mask when the underlying hardware is treating it more as a hint.
> Perhaps handlers still need to be maintained on all CPUs in a given apic
> domain, regardless of what the masks are configured as, to cover these
> situations.

That's odd. I'll have a look after the holidays.

Merry Christmas!

Thanks,

	tglx

  reply	other threads:[~2017-12-23 20:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 10:05 thinkpad x60: sound problems in 4.14.0-next-20171114 Pavel Machek
2017-11-15 10:43 ` Takashi Iwai
2017-11-15 11:11   ` Pavel Machek
2017-11-15 11:14     ` Takashi Iwai
2017-11-20 23:25       ` Pavel Machek
2017-11-27 16:30     ` thinkpad x60: sound problems in 4.15-rc1 was " Pavel Machek
2017-11-27 16:33       ` Takashi Iwai
2017-11-27 18:31         ` Pavel Machek
2017-11-27 18:35           ` Takashi Iwai
2017-11-27 18:44             ` Pavel Machek
2017-11-28  7:00               ` Takashi Iwai
2017-12-14  9:57                 ` Pavel Machek
2017-12-19  2:06                   ` vcaputo
2017-12-19  4:54                     ` vcaputo
2017-12-19 23:12                       ` vcaputo
2017-12-19 23:22                         ` Pavel Machek
2017-12-20  0:36                           ` vcaputo
2017-12-20  0:33                             ` Thomas Gleixner
2017-12-20  0:59                               ` vcaputo
2017-12-23  5:37                               ` vcaputo
2017-12-23 20:37                                 ` vcaputo
2017-12-23 20:33                                   ` Thomas Gleixner [this message]
2017-12-24 16:16                                     ` vcaputo
2017-12-28 10:41                                       ` Thomas Gleixner
2017-12-28 18:30                                         ` vcaputo
2017-12-28 23:24                                         ` [tip:x86/urgent] x86/apic: Switch all APICs to Fixed delivery mode tip-bot for Thomas Gleixner
2017-12-29 13:31                                         ` tip-bot for Thomas Gleixner
2017-12-29 13:35                                           ` Thomas Gleixner
2017-12-25 10:12                                 ` thinkpad x60: sound problems in 4.15-rc1 was Re: thinkpad x60: sound problems in 4.14.0-next-20171114 Pavel Machek
2017-12-25 10:09                       ` Pavel Machek
2018-01-02 20:54                 ` Pavel Machek

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=alpine.DEB.2.20.1712232132500.1853@nanos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=vcaputo@pengaru.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox