From: Peter Zijlstra <peterz@infradead.org>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: zhenwei pi <pizhenwei@bytedance.com>,
Thomas Gleixner <tglx@linutronix.de>,
pbonzini@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: Re: [PATCH v2 2/2] KVM: x86: use x86_get_freq to get freq for kvmclock
Date: Sat, 4 Dec 2021 11:44:25 +0100 [thread overview]
Message-ID: <20211204104425.GS16608@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <ce49cc3e3ae5885d992261589cd0f4adad118776.camel@redhat.com>
On Fri, Dec 03, 2021 at 09:53:53AM +0200, Maxim Levitsky wrote:
> > Perf exposes it, it's not really convenient if you're not using perf,
> > but it can be found there.
> That is good to know! I will check out the source but if you remember,
> is there cli option in perf to show it, or it only uses it for internal
> purposes?
perf tool doesn't expose it I think, it's stuffed in
perf_event_mmap_page::time_* fields, see
include/uapi/linux/perf_event.h, it has comments on.
prev parent reply other threads:[~2021-12-04 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 2:46 [PATCH v2 0/2] Introduce x86_get_cpufreq_khz() zhenwei pi
2021-12-01 2:46 ` [PATCH v2 1/2] x86/cpu: " zhenwei pi
2021-12-02 22:25 ` Peter Zijlstra
2021-12-03 7:34 ` zhenwei pi
2021-12-04 10:46 ` Peter Zijlstra
2021-12-01 2:46 ` [PATCH v2 2/2] KVM: x86: use x86_get_freq to get freq for kvmclock zhenwei pi
2021-12-02 2:48 ` Thomas Gleixner
2021-12-02 5:26 ` zhenwei pi
2021-12-02 7:19 ` Maxim Levitsky
2021-12-02 22:45 ` Peter Zijlstra
2021-12-03 7:53 ` Maxim Levitsky
2021-12-04 10:44 ` 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=20211204104425.GS16608@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.