public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Thomas Renninger <trenn@suse.de>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Tejun Heo <tj@kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Pierre Tardy <tardyp@gmail.com>,
	Jean Pihet <jean.pihet@newoldbits.com>,
	linux-trace-users@vger.kernel.org,
	linux-pm@lists.linux-foundation.org, rjw@sisk.pl,
	linux-omap@vger.kernel.org,
	Kevin Hilman <khilman@deeprootsystems.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Frank Eigler <fche@redhat.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH [0/4] perf: clean-up of power events API
Date: Tue, 19 Oct 2010 06:27:57 -0700	[thread overview]
Message-ID: <4CBD9CDD.1010300@linux.intel.com> (raw)
In-Reply-To: <20101019115200.GC25371@elte.hu>

  On 10/19/2010 4:52 AM, Ingo Molnar wrote:
> * Peter Zijlstra<peterz@infradead.org>  wrote:
>
>> On Tue, 2010-10-19 at 13:45 +0200, Ingo Molnar wrote:
>>> * Thomas Renninger<trenn@suse.de>  wrote:
>>>
>>>>> Most definitely. It's no accident that it took such a long time for this issue
>>>>> to be raised in the first place. It's a rare occurance -
>>>> Do you agree that this occurance happened now and these events should get cleaned
>>>> up before ARM and other archs make use of the broken interface?
>>>>
>>>> If not, discussing this further, is a big waste of time... and Jean would have to
>>>> try to adapt his ARM code on the broken ABI...
>>> The discussion seems to have died down somewhat. Please re-send to lkml the latest
>>> patches you have to remind everyone of the latest state of things - the merge window
>>> is getting near.
>>>
>>> My only compatibility/ABI point is basically that it shouldnt break _existing_
>>> tracepoints (and users thereof). If your latest bits meet that then it ought to be a
>>> good first step. You are free to (and encouraged to) introduce more complete sets of
>>> events.
>> Can we deprecate and eventually remove the old ones, or will we be forever obliged
>> to carry the old ones too?
> We most definitely want to deprecate and remove the old ones - but we want to give
> instrumentation software some migration time for that.
>
> Jean, Arjan, what would be a feasible and practical deprecation period for that? One
> kernel cycle?

more like a year

for some time software needs to support both, especially if popular 
distros stick to an older kernel like *cough* RHEL6


  reply	other threads:[~2010-10-19 13:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201010062334.46971.trenn@suse.de>
     [not found] ` <4CB095FA.8060803@linux.intel.com>
     [not found]   ` <20101010121928.GA2688@elte.hu>
     [not found]     ` <201010191331.03080.trenn@suse.de>
2010-10-19 11:45       ` PATCH [0/4] perf: clean-up of power events API Ingo Molnar
2010-10-19 11:47         ` Peter Zijlstra
2010-10-19 11:52           ` Ingo Molnar
2010-10-19 13:27             ` Arjan van de Ven [this message]
2010-10-19 13:50               ` Ingo Molnar
2010-10-19 13:52                 ` Arjan van de Ven
2010-10-19 14:51                   ` Ingo Molnar

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=4CBD9CDD.1010300@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=fche@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rjw@sisk.pl \
    --cc=rostedt@goodmis.org \
    --cc=tardyp@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=trenn@suse.de \
    /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