LKML Archive on lore.kernel.org
 help / color / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: 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: Wed, 29 Jul 2020 13:27:32 -0300
Message-ID: <7CEC30D2-0C1E-4E88-A1D2-35C121EB1013@gmail.com> (raw)
In-Reply-To: <20200729160220.GB2655@hirez.programming.kicks-ass.net>



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.

- Arnaldo

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply index

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 [this message]
2020-07-29 17:57     ` Vitaly Chikunov
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=7CEC30D2-0C1E-4E88-A1D2-35C121EB1013@gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@kernel.org \
    --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

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
	git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
	git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git
	git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
		linux-kernel@vger.kernel.org
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git