From: David Miller <davem@davemloft.net>
To: peterz@infradead.org
Cc: mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: cpu_clock() in NMIs
Date: Mon, 14 Dec 2009 21:36:01 -0800 (PST) [thread overview]
Message-ID: <20091214.213601.77046339.davem@davemloft.net> (raw)
In-Reply-To: <1260819170.4165.346.camel@twins>
From: Peter Zijlstra <peterz@infradead.org>
Date: Mon, 14 Dec 2009 20:32:50 +0100
> OK, you convinced me plenty ;-)
>
> I guess we need some debug code to ensure we don't grow any
> local_irq_save/restore/disable code in NMI paths, and maybe document
> this some place.
>
> Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Ingo and others. I'd like to get this kernel/sched_clock.c IRQ
disabling patch into Linus's tree and then into -stable because the
fix for sparc64 perf depends upon it.
Thanks.
next prev parent reply other threads:[~2009-12-15 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 2:25 cpu_clock() in NMIs David Miller
2009-12-14 9:02 ` Peter Zijlstra
2009-12-14 19:09 ` David Miller
2009-12-14 19:32 ` Peter Zijlstra
2009-12-15 5:36 ` David Miller [this message]
2009-12-14 19:57 ` Mike Frysinger
2009-12-15 8:11 ` [tip:sched/urgent] sched: Fix cpu_clock() in NMIs, on !CONFIG_HAVE_UNSTABLE_SCHED_CLOCK tip-bot for David Miller
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=20091214.213601.77046339.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox