From: Peter Zijlstra <peterz@infradead.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
mingo@kernel.org, tglx@linutronix.de, hpa@zytor.com
Subject: Re: [BUG] perf tests: Test converting perf time to TSC
Date: Thu, 3 Oct 2013 15:57:48 +0200 [thread overview]
Message-ID: <20131003135748.GK28601@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <524D59B5.4040004@intel.com>
On Thu, Oct 03, 2013 at 02:49:09PM +0300, Adrian Hunter wrote:
> You can boot with notsc and perf still seems to work
> e.g.
>
> $ dmesg | grep -i tsc
> [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0+ root=UUID=f1b4c71a-15aa-41a6-8898-cdde49966bce ro ignore_loglevel earlyprintk=ttyS0 console=ttyS0,115200n8 no_console_suspend notsc=1
> [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0+ root=UUID=f1b4c71a-15aa-41a6-8898-cdde49966bce ro ignore_loglevel earlyprintk=ttyS0 console=ttyS0,115200n8 no_console_suspend notsc=1
> [ 0.000000] tsc: Kernel compiled with CONFIG_X86_TSC, cannot disable TSC completely
> [ 0.000000] tsc: Fast TSC calibration using PIT
> [ 0.004000] tsc: Detected 2593.932 MHz processor
> [ 0.224000] TSC deadline timer enabled
Yeah, and we still use the TSC deadline timer too.. I think we should
seriously consider removing the notsc option. I really don't know what
its good for.
Thomas, Ingo, hpa?
prev parent reply other threads:[~2013-10-03 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 13:23 [BUG] perf tests: Test converting perf time to TSC Jiri Olsa
2013-10-02 13:46 ` Adrian Hunter
2013-10-02 16:14 ` Arnaldo Carvalho de Melo
2013-10-03 8:17 ` Jiri Olsa
2013-10-03 8:42 ` Adrian Hunter
2013-10-03 8:56 ` Peter Zijlstra
2013-10-03 8:58 ` Peter Zijlstra
2013-10-03 9:54 ` Adrian Hunter
2013-10-03 9:59 ` Peter Zijlstra
2013-10-03 10:13 ` Adrian Hunter
2013-10-03 11:02 ` Peter Zijlstra
2013-10-03 11:49 ` Adrian Hunter
2013-10-03 13:57 ` Peter Zijlstra [this message]
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=20131003135748.GK28601@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.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