From: Like Xu <like.xu.linux@gmail.com>
To: Song Liu <songliubraving@fb.com>
Cc: Peter Zijlstra <peterz@infradead.org>, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
"like.xu@linux.intel.com" <like.xu@linux.intel.com>,
Andi Kleen <andi@firstfloor.org>,
"Liang, Kan" <kan.liang@intel.com>
Subject: Re: bpf_get_branch_snapshot on qemu-kvm
Date: Fri, 8 Oct 2021 11:34:05 +0800 [thread overview]
Message-ID: <ee2a1209-8572-a147-fdac-1a3d83862022@gmail.com> (raw)
In-Reply-To: <0676194C-3ADF-4FF9-8655-2B15D54E72BE@fb.com>
On 30/9/2021 4:05 am, Song Liu wrote:
> Hi Kan,
>
>> On Sep 29, 2021, at 9:35 AM, Liang, Kan <kan.liang@intel.com> wrote:
>>
>>>>> - get confirmation that clearing GLOBAL_CTRL is suffient to supress
>>>>> PEBS, in which case we can simply remove the PEBS_ENABLE clear.
>>>>
>>>> How should we confirm this? Can we run some tests for this? Or do we
>>>> need hardware experts' input for this?
>>>
>>> I'll put it on the list to ask the hardware people when I talk to them next. But
>>> maybe Kan or Andi know without asking.
>>
>> If the GLOBAL_CTRL is explicitly disabled, the counters do not count anymore.
>> It doesn't matter if PEBS is enabled or not.
>>
>> See 6c1c07b33eb0 ("perf/x86/intel: Avoid unnecessary PEBS_ENABLE MSR
>> access in PMI "). We optimized the PMU handler base on it.
>
> Thanks for these information!
>
> IIUC, all we need is the following on top of bpf-next/master:
>
> diff --git i/arch/x86/events/intel/core.c w/arch/x86/events/intel/core.c
> index 1248fc1937f82..d0d357e7d6f21 100644
> --- i/arch/x86/events/intel/core.c
> +++ w/arch/x86/events/intel/core.c
> @@ -2209,7 +2209,6 @@ intel_pmu_snapshot_branch_stack(struct perf_branch_entry *entries, unsigned int
> /* must not have branches... */
> local_irq_save(flags);
> __intel_pmu_disable_all(false); /* we don't care about BTS */
If the value passed in is true, does it affect your use case?
> - __intel_pmu_pebs_disable_all();
In that case, we can reuse "static __always_inline void intel_pmu_disable_all(void)"
regardless of whether PEBS is supported or enabled inside the guest and the host ?
> __intel_pmu_lbr_disable();
How about using intel_pmu_lbr_disable_all() to cover Arch LBR?
> /* ... until here */
> return __intel_pmu_snapshot_branch_stack(entries, cnt, flags);
> @@ -2223,7 +2222,6 @@ intel_pmu_snapshot_arch_branch_stack(struct perf_branch_entry *entries, unsigned
> /* must not have branches... */
> local_irq_save(flags);
> __intel_pmu_disable_all(false); /* we don't care about BTS */
> - __intel_pmu_pebs_disable_all();
> __intel_pmu_arch_lbr_disable();
> /* ... until here */
> return __intel_pmu_snapshot_branch_stack(entries, cnt, flags);
>
>
> In the test, this does eliminate the warning.
>
> Thanks,
> Song
>
next prev parent reply other threads:[~2021-10-08 3:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 0:04 bpf_get_branch_snapshot on qemu-kvm Song Liu
2021-09-29 7:35 ` Peter Zijlstra
2021-09-29 12:05 ` Like Xu
2021-09-29 12:26 ` Peter Zijlstra
2021-09-29 14:42 ` Song Liu
2021-09-29 15:59 ` Peter Zijlstra
2021-09-29 16:35 ` Liang, Kan
2021-09-29 20:05 ` Song Liu
2021-10-08 3:34 ` Like Xu [this message]
2021-10-08 5:46 ` Song Liu
2021-10-08 6:36 ` Like Xu
2021-10-08 17:08 ` Song Liu
2021-10-09 9:03 ` Like Xu
2021-10-26 7:09 ` Song Liu
2021-10-28 3:09 ` Like Xu
2021-10-29 18:09 ` Song Liu
2021-09-29 23:20 ` Andi Kleen
2021-09-29 14:39 ` Song Liu
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=ee2a1209-8572-a147-fdac-1a3d83862022@gmail.com \
--to=like.xu.linux@gmail.com \
--cc=Kernel-team@fb.com \
--cc=andi@firstfloor.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kan.liang@intel.com \
--cc=like.xu@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).