linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akemi Yagi <toracat@elrepo.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Alan Bartlett <ajb@elrepo.org>,
	Leo Yan <leo.yan@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-perf-users@vger.kernel.org, ElRepo <contact@elrepo.org>,
	Jiri Olsa <jolsa@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf scripts python: Let script to be python2 compliant
Date: Tue, 26 Jul 2022 13:35:40 -0700	[thread overview]
Message-ID: <CABA31DoEJEyVeUgzROzzj_OA2exmj69WamaavQWi=7nWq52dxw@mail.gmail.com> (raw)
In-Reply-To: <YuBDw/+7McESS05X@kernel.org>

On Tue, Jul 26, 2022 at 12:43 PM Arnaldo Carvalho de Melo
<acme@kernel.org> wrote:
>
> Em Tue, Jul 26, 2022 at 10:52:31AM -0700, Ian Rogers escreveu:

> > So I'm somewhat concerned about perf supporting unsupported
> > distributions and this holding the code base back. RHEL7 was launched
> > 8 years ago (June 10, 2014) and full support ended 3 years ago (August
> > 6, 2019) [1]. Currently RHEL7 is in "Maintenance Support or
> > Maintenance Support 2" phase which is defined to mean [2]:
[...]

> In this specific supporting things that people report using, like was
> done in this case, isn't such a big problem.
>
> Someone reported a problem in a system they used, the author of the code
> in question posted a patch allowing perf to be used in such old systems,
> doesn't get in the way of newer systems, small patch, merged, life goes
> on.
>
> Sometimes some organizations are stuck with some distro till they can go
> thru re-certifications, bidding for new hardware, whatever, and then
> they want to continue using the latest perf on those systems because
> they want to benefit from new features we're working on that work on
> such systems. If the cost is small, like in this case, I see no problems
> to have perf working on such older systems.
>
> - Arnaldo

Just wanted to make a note about the "old" systems.

While RHEL 7 might be regarded as "old" in general, it may not be so
in the world of Enterprise Linux. A graph of EPEL mirror stats [1],
while it is from about a year ago, shows EL 7 (RHEL 7 and its
rebuilds) has a huge user base and was still growing quite fast.

By the way, my main workstation runs RHEL 7. ;-)

Akemi

[1] https://twitter.com/mattdm/status/1447224008831811588

  reply	other threads:[~2022-07-26 20:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 10:42 [PATCH] perf scripts python: Let script to be python2 compliant Leo Yan
2022-07-25 15:51 ` Arnaldo Carvalho de Melo
2022-07-26 16:56   ` Alan Bartlett
2022-07-26 17:52     ` Ian Rogers
2022-07-26 19:42       ` Arnaldo Carvalho de Melo
2022-07-26 20:35         ` Akemi Yagi [this message]
2022-07-26 20:54           ` Ian Rogers
2022-07-27 16:17           ` Peter Zijlstra
2022-07-26 20:43         ` Ian Rogers
2022-07-26 21:17           ` Arnaldo Carvalho de Melo
2022-08-17 19:52           ` Chuck Zmudzinski
2022-08-17 22:13             ` Chuck Zmudzinski
2022-08-17 22:36               ` Ian Rogers
2022-08-18  1:12                 ` Chuck Zmudzinski
2022-08-18  3:03                   ` Leo Yan
2022-08-18 14:52                     ` Ian Rogers
2022-08-19  6:48                       ` Leo Yan
2022-08-19 13:56                         ` Chuck Zmudzinski

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='CABA31DoEJEyVeUgzROzzj_OA2exmj69WamaavQWi=7nWq52dxw@mail.gmail.com' \
    --to=toracat@elrepo.org \
    --cc=acme@kernel.org \
    --cc=ajb@elrepo.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=contact@elrepo.org \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linaro.org \
    --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=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).