From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Pan, Zhenjie" <zhenjie.pan@intel.com>,
"paulus@samba.org" <paulus@samba.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"acme@ghostprotocols.net" <acme@ghostprotocols.net>,
"dzickus@redhat.com" <dzickus@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"Liu, Chuansheng" <chuansheng.liu@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] NMI: fix NMI period is not correct when cpu frequency changes issue.
Date: Thu, 18 Apr 2013 13:32:09 +0200 [thread overview]
Message-ID: <1366284729.19383.16.camel@laptop> (raw)
In-Reply-To: <20130415163049.08498e3a8726f0bd6f4d6ebe@linux-foundation.org>
On Mon, 2013-04-15 at 16:30 -0700, Andrew Morton wrote:
> I think this will break the build if CONFIG_PERF_EVENTS=n and
> CONFIG_LOCKUP_DETECTOR=y. I was able to create such a config for
> powerpc. If I'm reading it correctly, CONFIG_PERF_EVENTS cannot be
> disabled on x86_64? If so, what the heck?
Frederic and Ingo made that happen,.. a long while ago Frederic
promised to fix that.. I suppose its never been quite important enough
to get around to :/
(Frederic; read this as a gentle prod to move his upward on the todo
list)
next prev parent reply other threads:[~2013-04-18 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 3:47 [PATCH] NMI: fix NMI period is not correct when cpu frequency changes issue Pan, Zhenjie
2013-04-03 18:00 ` Don Zickus
2013-04-16 3:26 ` Pan, Zhenjie
2013-04-15 23:30 ` Andrew Morton
2013-04-16 3:45 ` Pan, Zhenjie
2013-04-16 4:29 ` Andrew Morton
2013-04-18 11:32 ` Peter Zijlstra [this message]
2013-07-24 17:48 ` Frederic Weisbecker
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=1366284729.19383.16.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=chuansheng.liu@intel.com \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=zhenjie.pan@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.