All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@redhat.com>,
	Vineet Gupta <vgupta@synopsys.com>,
	Steven Miao <realmz6@gmail.com>,
	James Hogan <james.hogan@imgtec.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Cody P Schafer <cody@linux.vnet.ibm.com>,
	linux-sh@vger.kernel.org,
	Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH 0/6] perf: Use common PMU interrupt disabled code on all architectures
Date: Sun, 15 Jun 2014 06:54:23 +0000	[thread overview]
Message-ID: <20140615065423.GA20028@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1406150156510.16738@vincent-weaver-1.umelst.maine.edu>


* Vince Weaver <vincent.weaver@maine.edu> wrote:

> 
> Now that "perf/x86: Use common PMU interrupt disabled code"
> (c184c980de30dc) was merged, I went and audited all of the
> architectures.  The following patchset attempts to move
> all of the ones that have code disabling sampled events
> due to lack of overflow interrupt to the new common code.
> 
> ARM and x86 were already updated with the original changeset.
> 
> Note that this is an ABI change in some cases, as many
> architectures returned EINVAL previously rather than
> EOPNOTSUPP.
> 
> Unfortunately these patches are not tested at all, as I don't have
> access to the hardware.

Looks good to me, for v3.17. Peter, what do you think?

Reviewed-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@redhat.com>,
	Vineet Gupta <vgupta@synopsys.com>,
	Steven Miao <realmz6@gmail.com>,
	James Hogan <james.hogan@imgtec.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Cody P Schafer <cody@linux.vnet.ibm.com>,
	linux-sh@vger.kernel.org,
	Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH 0/6] perf: Use common PMU interrupt disabled code on all architectures
Date: Sun, 15 Jun 2014 08:54:23 +0200	[thread overview]
Message-ID: <20140615065423.GA20028@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1406150156510.16738@vincent-weaver-1.umelst.maine.edu>


* Vince Weaver <vincent.weaver@maine.edu> wrote:

> 
> Now that "perf/x86: Use common PMU interrupt disabled code"
> (c184c980de30dc) was merged, I went and audited all of the
> architectures.  The following patchset attempts to move
> all of the ones that have code disabling sampled events
> due to lack of overflow interrupt to the new common code.
> 
> ARM and x86 were already updated with the original changeset.
> 
> Note that this is an ABI change in some cases, as many
> architectures returned EINVAL previously rather than
> EOPNOTSUPP.
> 
> Unfortunately these patches are not tested at all, as I don't have
> access to the hardware.

Looks good to me, for v3.17. Peter, what do you think?

Reviewed-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

  reply	other threads:[~2014-06-15  6:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-15  5:59 [PATCH 0/6] perf: Use common PMU interrupt disabled code on all architectures Vince Weaver
2014-06-15  5:59 ` Vince Weaver
2014-06-15  6:54 ` Ingo Molnar [this message]
2014-06-15  6:54   ` 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=20140615065423.GA20028@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=benh@kernel.crashing.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=cody@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=realmz6@gmail.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=vgupta@synopsys.com \
    --cc=vincent.weaver@maine.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.