From: Peter Zijlstra <peterz@infradead.org>
To: Wen Yang <wenyang@linux.alibaba.com>
Cc: Stephane Eranian <eranian@google.com>,
Wen Yang <simon.wy@alibaba-inc.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
mark rutland <mark.rutland@arm.com>, jiri olsa <jolsa@redhat.com>,
namhyung kim <namhyung@kernel.org>,
borislav petkov <bp@alien8.de>,
x86@kernel.org, "h. peter anvin" <hpa@zytor.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 2/2] perf/x86: improve the event scheduling to avoid unnecessary pmu_stop/start
Date: Mon, 14 Mar 2022 11:55:12 +0100 [thread overview]
Message-ID: <Yi8fELo+k9gmkJIa@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <271bc186-7ffb-33c8-4934-cda2beb94816@linux.alibaba.com>
On Thu, Mar 10, 2022 at 11:50:33AM +0800, Wen Yang wrote:
> As you pointed out, some non-compliant rdpmc can cause problems. But you
> also know that linux is the foundation of cloud servers, and many
> third-party programs run on it (we don't have any code for it), and we can
> only observe that the monitoring data will jitter abnormally (the
> probability of this issue is not high, about dozens of tens of thousands of
> machines).
This might be a novel insight, but I *really* don't give a crap about
any of that. If they're not using it right, they get to keep the pieces.
I'd almost make it reschedule more to force them to fix their stuff.
next prev parent reply other threads:[~2022-03-14 10:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 11:03 [RESEND PATCH 1/2] perf/x86: extract code to assign perf events for both core and uncore Wen Yang
2022-03-04 11:03 ` [RESEND PATCH 2/2] perf/x86: improve the event scheduling to avoid unnecessary pmu_stop/start Wen Yang
2022-03-04 15:39 ` Peter Zijlstra
2022-03-06 14:36 ` Wen Yang
2022-03-07 17:14 ` Stephane Eranian
2022-03-08 6:42 ` Wen Yang
2022-03-08 12:53 ` Peter Zijlstra
2022-03-08 12:50 ` Peter Zijlstra
2022-03-10 3:50 ` Wen Yang
2022-03-14 10:55 ` Peter Zijlstra [this message]
2022-03-17 17:54 ` Wen Yang
2022-04-17 15:06 ` Wen Yang
2022-04-19 14:16 ` Wen Yang
2022-04-19 20:57 ` Peter Zijlstra
2022-04-19 21:18 ` Stephane Eranian
2022-04-20 14:44 ` Wen Yang
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=Yi8fELo+k9gmkJIa@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=simon.wy@alibaba-inc.com \
--cc=tglx@linutronix.de \
--cc=wenyang@linux.alibaba.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®