public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>,
	Jacob Shin <jacob.shin@amd.com>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>, x86 <x86@kernel.org>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND 0/3] perf, amd: Support for Family 16h L2I Performance Counters
Date: Wed, 10 Apr 2013 13:56:47 +0200	[thread overview]
Message-ID: <20130410115647.GA8083@gmail.com> (raw)
In-Reply-To: <1365594957.30071.66.camel@laptop>


* Peter Zijlstra <peterz@infradead.org> wrote:

> On Wed, 2013-04-10 at 13:49 +0200, Peter Zijlstra wrote:
> 
> > Hmm.. the 15h old interface bits got merged? I thought I kept telling
> > that should be done like the intel uncore stuff since the hardware
> > interface wasn't retarded anymore.
> 
> Ah well, that crap seems to have slipped in in Feb when I was still a
> near vegetable and not paying much attention.
> 
> /me curses a bit.
> 
> I don't suppose we can deprecate it and remove this stuff? 

I think we can - if there's a functional replacement.

Thanks,

	Ingo

  reply	other threads:[~2013-04-10 11:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 15:23 [PATCH RESEND 0/3] perf, amd: Support for Family 16h L2I Performance Counters Jacob Shin
2013-04-09 15:23 ` [PATCH RESEND 1/3] perf, amd: Further generalize NB event constraints handling logic Jacob Shin
2013-04-09 15:23 ` [PATCH RESEND 2/3] perf, x86: Allow for multiple kfree_on_online pointers Jacob Shin
2013-04-09 15:23 ` [PATCH RESEND 3/3] perf, amd: Enable L2I performance counters on AMD Family 16h Jacob Shin
2013-04-10  9:41 ` [PATCH RESEND 0/3] perf, amd: Support for Family 16h L2I Performance Counters Peter Zijlstra
2013-04-10  9:48   ` Peter Zijlstra
2013-04-10 11:38   ` Stephane Eranian
2013-04-10 11:49     ` Peter Zijlstra
2013-04-10 11:52       ` Stephane Eranian
2013-04-10 11:55       ` Peter Zijlstra
2013-04-10 11:56         ` Ingo Molnar [this message]
2013-04-10 12:12           ` Stephane Eranian
2013-04-10 12:28             ` Ingo Molnar
2013-04-10 12:29               ` Stephane Eranian
2013-04-10 15:03                 ` Jacob Shin
2013-04-10 12:29             ` Borislav Petkov

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=20130410115647.GA8083@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@ghostprotocols.net \
    --cc=eranian@google.com \
    --cc=hpa@zytor.com \
    --cc=jacob.shin@amd.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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