From: Vitaly Chikunov <vt@altlinux.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>, peterz@infradead.org
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org,
"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: Should perf version match kernel version?
Date: Wed, 29 Jul 2020 20:57:04 +0300 [thread overview]
Message-ID: <20200729175704.gsbh4gkbqxas5j2t@altlinux.org> (raw)
In-Reply-To: <7CEC30D2-0C1E-4E88-A1D2-35C121EB1013@gmail.com>
Peter, Arnaldo,
On Wed, Jul 29, 2020 at 01:27:32PM -0300, Arnaldo Carvalho de Melo wrote:
>
>
> On July 29, 2020 1:02:20 PM GMT-03:00, peterz@infradead.org wrote:
> >On Wed, Jul 29, 2020 at 06:56:47PM +0300, Vitaly Chikunov wrote:
> >> Hi,
> >>
> >> It seems that most distros try to have perf version to match with
> >> running kernel version. Is is requirement? Would it be better to have
> >> single perf from kernel mainline to work with any (older) kernel
> >> version?
> >>
> >> We have different kernel versions in ALT Linux (stable for 4.19, 5.4,
> >> and 5.7) and I want to understand if we should have three perfs or
> >> single package will be enough.
> >
> >We strive to have it all compatible, older perf should work on newer
> >kernel and newer perf should work on older kernel.
> >
> >How well it's all tested is another.
> >
> >Personally I often use a very old perf.
>
> Yeah, never was a requirement, if you find some problem using a new perf on an old kernel or the other way around, please report.
That's great to know. Thanks for the answers!
next prev parent reply other threads:[~2020-07-29 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 15:56 Vitaly Chikunov
2020-07-29 16:02 ` peterz
2020-07-29 16:27 ` Arnaldo Carvalho de Melo
2020-07-29 17:57 ` Vitaly Chikunov [this message]
2020-07-29 18:28 ` Arnaldo Carvalho de Melo
2020-08-02 11:51 ` Pavel Machek
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=20200729175704.gsbh4gkbqxas5j2t@altlinux.org \
--to=vt@altlinux.org \
--cc=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®