From: Peter Zijlstra <peterz@infradead.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Don Zickus <dzickus@redhat.com>,
sedat.dilek@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] x86, perf, nmi: Disable perf if counters are not accessable
Date: Tue, 23 Nov 2010 20:07:47 +0100 [thread overview]
Message-ID: <1290539267.2072.418.camel@laptop> (raw)
In-Reply-To: <20101123190417.GC5997@lenovo>
On Tue, 2010-11-23 at 22:04 +0300, Cyrill Gorcunov wrote:
> On Tue, Nov 23, 2010 at 07:27:07PM +0100, Peter Zijlstra wrote:
> > On Tue, 2010-11-23 at 19:21 +0100, Sedat Dilek wrote:
> > > Due to BIOS l(ocal)apic is not possible:
> > >
> > > # dmesg | grep -i apic
> > > [ 0.000000] Using APIC driver default
> > > [ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
> > > [ 0.000000] APIC: disable apic facility
> > > [ 0.000000] APIC: switched to apic NOOP
> > > [ 0.008891] no APIC, boot with the "lapic" boot parameter to force-enable it.
> > > [ 0.036141] Local APIC not detected. Using dummy APIC emulation.
> >
> > Have you tried booting with "lapic" as the second last msg suggests you
> > do?
>
> Peter, Don, might not we need something like the patch below -- ie to check for
> apic earlier and do not acquire cpu for PERF cpu bit, and its cpu model, etc
> if there is no active apic? And perhaps for nmi-watchdog, we should not try
> to creat perf event for same reason and simply report that nmi-watchdog is
> disabled (though of course hpet based one should try to continue).
>
> No?
>
Ah, no.. now I get what you mean.
We can use the pmu without interrupt with we miss the lapic, that is
perf-stat will still work.
> void __init init_hw_perf_events(void)
> @@ -1346,6 +1348,10 @@ void __init init_hw_perf_events(void)
>
> pr_info("Performance Events: ");
>
> + /* apic is required */
> + if (pmu_check_apic())
> + goto no_pmu;
> +
> +no_pmu:
> + pr_cont("no PMU driver, software events only.\n");
> + return;
> }
>
> static inline void x86_pmu_read(struct perf_event *event)
next prev parent reply other threads:[~2010-11-23 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 15:15 [PATCH] x86, perf, nmi: Disable perf if counters are not accessable Sedat Dilek
2010-11-23 15:19 ` Peter Zijlstra
2010-11-23 16:56 ` Don Zickus
2010-11-23 18:21 ` Sedat Dilek
2010-11-23 18:27 ` Peter Zijlstra
2010-11-23 18:29 ` Sedat Dilek
2010-11-23 18:37 ` Sedat Dilek
2010-11-23 19:04 ` Cyrill Gorcunov
2010-11-23 19:07 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-23 19:18 Cyrill Gorcunov
2010-11-22 21:55 Don Zickus
2010-11-23 10:46 ` Peter Zijlstra
2010-11-23 14:13 ` Don Zickus
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=1290539267.2072.418.camel@laptop \
--to=peterz@infradead.org \
--cc=dzickus@redhat.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sedat.dilek@gmail.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