From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [-next] !irqd_can_balance() WARNINGs at irq_move_masked_irq()
Date: Sat, 20 Jun 2015 01:23:52 +0900 [thread overview]
Message-ID: <20150619162352.GA1412@swordfish> (raw)
In-Reply-To: <alpine.DEB.2.11.1506191815110.4107@nanos>
On (06/19/15 18:15), Thomas Gleixner wrote:
[..]
> > > Hi Thomas,
> > > Maybe it's caused by the hpet driver itself?
> > > irq_set_affinity() may set the IRQD_SETAFFINITY_PENDING flag,
> > > thus triggering the warning.
> > And the usage pattern seems reasonable, the IRQF_NOBALANCING flag
> > means nobody may change the affinity except myself:)
>
> Right, that's why I removed the restriction.
>
> I just wonder why we have not seen that before ...
just a note,
I compile/run every linux-next on at least two different
x86-64 boxen, w/o changing the .config a lot.
-ss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-06-19 16:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 7:11 [-next] !irqd_can_balance() WARNINGs at irq_move_masked_irq() Sergey Senozhatsky
2015-06-19 9:25 ` Thomas Gleixner
2015-06-19 12:21 ` Thomas Gleixner
2015-06-19 13:11 ` Sergey Senozhatsky
2015-06-19 16:09 ` Jiang Liu
2015-06-19 16:12 ` Jiang Liu
2015-06-19 16:15 ` Thomas Gleixner
2015-06-19 16:21 ` Jiang Liu
2015-06-19 16:30 ` Thomas Gleixner
2015-06-19 16:47 ` Jiang Liu
2015-06-19 17:14 ` Sergey Senozhatsky
2015-06-20 4:32 ` Sergey Senozhatsky
2015-06-20 10:07 ` [tip:x86/apic] x86/hpet: Check for irq== 0 when allocating hpet MSI interrupts tip-bot for Jiang Liu
2015-06-19 16:23 ` Sergey Senozhatsky [this message]
2015-06-20 4:31 ` [-next] !irqd_can_balance() WARNINGs at irq_move_masked_irq() Sergey Senozhatsky
2015-06-20 7:52 ` Thomas Gleixner
2015-06-20 7:57 ` Sergey Senozhatsky
2015-06-20 8:13 ` Thomas Gleixner
2015-06-20 8:27 ` Sergey Senozhatsky
2015-06-20 9:12 ` Thomas Gleixner
2015-06-20 17:53 ` Sergey Senozhatsky
2015-06-21 4:15 ` Sergey Senozhatsky
2015-06-21 14:37 ` Thomas Gleixner
2015-06-21 14:43 ` [tip:x86/apic] x86/hpet: Use proper hpet device number for MSI allocation tip-bot for Thomas Gleixner
2015-06-20 17:20 ` [tip:irq/core] genirq: Remove bogus restriction in irq_move_mask_irq() tip-bot for Thomas Gleixner
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=20150619162352.GA1412@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=bp@alien8.de \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=tglx@linutronix.de \
/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.