linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	peterz@infradead.org, 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: Sun, 2 Aug 2020 13:51:24 +0200	[thread overview]
Message-ID: <20200802115124.GA1044@bug> (raw)
In-Reply-To: <20200729175704.gsbh4gkbqxas5j2t@altlinux.org>

Hi!

> > >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!

Someone should tell debian, AFAICT they believe perf version == kernel version is a 
requirement...and so says their manpage.

										Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2020-08-02 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 15:56 Should perf version match kernel version? Vitaly Chikunov
2020-07-29 16:02 ` peterz
2020-07-29 16:27   ` Arnaldo Carvalho de Melo
2020-07-29 17:57     ` Vitaly Chikunov
2020-07-29 18:28       ` Arnaldo Carvalho de Melo
2020-08-02 11:51       ` Pavel Machek [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=20200802115124.GA1044@bug \
    --to=pavel@ucw.cz \
    --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 \
    --cc=vt@altlinux.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).