linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
	Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@redhat.com>, Kees Cook <keescook@chromium.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Erik Bosman <ebn310@few.vu.nl>,
	mpe@ellerman.id.au, anton@samba.org,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [RFC 5/5] x86,perf: Only allow rdpmc if a perf_event is mapped
Date: Tue, 21 Oct 2014 08:52:59 -0700	[thread overview]
Message-ID: <CALCETrX8Y-PGBxU+tcCy7s-8KmYY3SVGHUWmvhBimgmwri+4uw@mail.gmail.com> (raw)
In-Reply-To: <20141021091434.GN23531@worktop.programming.kicks-ass.net>

On Tue, Oct 21, 2014 at 2:14 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Oct 20, 2014 at 12:51:10PM +0200, Hendrik Brueckner wrote:
>> I think it would makes sense to return 0 as default in the
>> perf_event_idx_default() and let each PMU/arch that actually supports
>> reading PMCs from user space return the proper index.  And according
>> to tools/perf/design.txt, index must be non-zero to trigger a user space
>> read.
>
> OK, I've got something like the below. Michael/Anton, would you please
> clarify the ppc book3s capabilities?
>
> ---
> Subject: perf: Clean up pmu::event_idx
> From: Peter Zijlstra <peterz@infradead.org>
> Date: Tue Oct 21 11:10:21 CEST 2014
>
> Andy reported that the current state of event_idx is rather confused.
> So remove all but the x86_pmu implementation and change the default to
> return 0 (the safe option).

I wrote essentially the same patch yesterday, so looks good to me :)

>
> Reported-by: Andy Lutomirski <luto@amacapital.net>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
>  arch/powerpc/perf/hv-24x7.c     |    6 ------
>  arch/powerpc/perf/hv-gpci.c     |    6 ------
>  arch/s390/kernel/perf_cpum_sf.c |    6 ------
>  kernel/events/core.c            |   15 +--------------
>  kernel/events/hw_breakpoint.c   |    7 -------
>  5 files changed, 1 insertion(+), 39 deletions(-)
>
> --- a/arch/powerpc/perf/hv-24x7.c
> +++ b/arch/powerpc/perf/hv-24x7.c
> @@ -417,11 +417,6 @@ static int h_24x7_event_add(struct perf_
>         return 0;
>  }
>
> -static int h_24x7_event_idx(struct perf_event *event)
> -{
> -       return 0;
> -}
> -
>  static struct pmu h_24x7_pmu = {
>         .task_ctx_nr = perf_invalid_context,
>
> @@ -433,7 +428,6 @@ static struct pmu h_24x7_pmu = {
>         .start       = h_24x7_event_start,
>         .stop        = h_24x7_event_stop,
>         .read        = h_24x7_event_update,
> -       .event_idx   = h_24x7_event_idx,
>  };
>
>  static int hv_24x7_init(void)
> --- a/arch/powerpc/perf/hv-gpci.c
> +++ b/arch/powerpc/perf/hv-gpci.c
> @@ -246,11 +246,6 @@ static int h_gpci_event_init(struct perf
>         return 0;
>  }
>
> -static int h_gpci_event_idx(struct perf_event *event)
> -{
> -       return 0;
> -}
> -
>  static struct pmu h_gpci_pmu = {
>         .task_ctx_nr = perf_invalid_context,
>
> @@ -262,7 +257,6 @@ static struct pmu h_gpci_pmu = {
>         .start       = h_gpci_event_start,
>         .stop        = h_gpci_event_stop,
>         .read        = h_gpci_event_update,
> -       .event_idx   = h_gpci_event_idx,
>  };
>
>  static int hv_gpci_init(void)
> --- a/arch/s390/kernel/perf_cpum_sf.c
> +++ b/arch/s390/kernel/perf_cpum_sf.c
> @@ -1411,11 +1411,6 @@ static void cpumsf_pmu_del(struct perf_e
>         perf_pmu_enable(event->pmu);
>  }
>
> -static int cpumsf_pmu_event_idx(struct perf_event *event)
> -{
> -       return event->hw.idx;
> -}
> -
>  CPUMF_EVENT_ATTR(SF, SF_CYCLES_BASIC, PERF_EVENT_CPUM_SF);
>  CPUMF_EVENT_ATTR(SF, SF_CYCLES_BASIC_DIAG, PERF_EVENT_CPUM_SF_DIAG);
>
> @@ -1458,7 +1453,6 @@ static struct pmu cpumf_sampling = {
>         .stop         = cpumsf_pmu_stop,
>         .read         = cpumsf_pmu_read,
>
> -       .event_idx    = cpumsf_pmu_event_idx,
>         .attr_groups  = cpumsf_pmu_attr_groups,
>  };
>
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -6071,11 +6071,6 @@ static int perf_swevent_init(struct perf
>         return 0;
>  }
>
> -static int perf_swevent_event_idx(struct perf_event *event)
> -{
> -       return 0;
> -}
> -
>  static struct pmu perf_swevent = {
>         .task_ctx_nr    = perf_sw_context,
>
> @@ -6085,8 +6080,6 @@ static struct pmu perf_swevent = {
>         .start          = perf_swevent_start,
>         .stop           = perf_swevent_stop,
>         .read           = perf_swevent_read,
> -
> -       .event_idx      = perf_swevent_event_idx,
>  };
>
>  #ifdef CONFIG_EVENT_TRACING
> @@ -6204,8 +6197,6 @@ static struct pmu perf_tracepoint = {
>         .start          = perf_swevent_start,
>         .stop           = perf_swevent_stop,
>         .read           = perf_swevent_read,
> -
> -       .event_idx      = perf_swevent_event_idx,
>  };
>
>  static inline void perf_tp_register(void)
> @@ -6431,8 +6422,6 @@ static struct pmu perf_cpu_clock = {
>         .start          = cpu_clock_event_start,
>         .stop           = cpu_clock_event_stop,
>         .read           = cpu_clock_event_read,
> -
> -       .event_idx      = perf_swevent_event_idx,
>  };
>
>  /*
> @@ -6511,8 +6500,6 @@ static struct pmu perf_task_clock = {
>         .start          = task_clock_event_start,
>         .stop           = task_clock_event_stop,
>         .read           = task_clock_event_read,
> -
> -       .event_idx      = perf_swevent_event_idx,
>  };
>
>  static void perf_pmu_nop_void(struct pmu *pmu)
> @@ -6542,7 +6529,7 @@ static void perf_pmu_cancel_txn(struct p
>
>  static int perf_event_idx_default(struct perf_event *event)
>  {
> -       return event->hw.idx + 1;
> +       return 0;
>  }
>
>  /*
> --- a/kernel/events/hw_breakpoint.c
> +++ b/kernel/events/hw_breakpoint.c
> @@ -605,11 +605,6 @@ static void hw_breakpoint_stop(struct pe
>         bp->hw.state = PERF_HES_STOPPED;
>  }
>
> -static int hw_breakpoint_event_idx(struct perf_event *bp)
> -{
> -       return 0;
> -}
> -
>  static struct pmu perf_breakpoint = {
>         .task_ctx_nr    = perf_sw_context, /* could eventually get its own */
>
> @@ -619,8 +614,6 @@ static struct pmu perf_breakpoint = {
>         .start          = hw_breakpoint_start,
>         .stop           = hw_breakpoint_stop,
>         .read           = hw_breakpoint_pmu_read,
> -
> -       .event_idx      = hw_breakpoint_event_idx,
>  };
>
>  int __init init_hw_breakpoint(void)



-- 
Andy Lutomirski
AMA Capital Management, LLC

  reply	other threads:[~2014-10-21 15:53 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 22:57 [RFC 0/5] CR4 handling improvements Andy Lutomirski
2014-10-14 22:57 ` [RFC 1/5] x86: Clean up cr4 manipulation Andy Lutomirski
2014-10-16  8:16   ` Peter Zijlstra
2014-10-16 11:18     ` Borislav Petkov
2014-10-16 11:29       ` Borislav Petkov
2014-10-16 15:32         ` Andy Lutomirski
2014-10-16 15:47           ` Borislav Petkov
2014-10-14 22:57 ` [RFC 2/5] x86: Store a per-cpu shadow copy of CR4 Andy Lutomirski
2014-10-16  8:26   ` Peter Zijlstra
2014-10-16 11:49   ` Borislav Petkov
2014-10-16 15:30     ` Andy Lutomirski
2014-10-14 22:57 ` [RFC 3/5] x86: Add a comment clarifying LDT context switching Andy Lutomirski
2014-10-16 15:49   ` Borislav Petkov
2014-10-16 16:21     ` Andy Lutomirski
2014-10-21  5:41       ` Borislav Petkov
2014-10-21  5:44         ` Andy Lutomirski
2014-10-21  6:05           ` Borislav Petkov
2014-10-14 22:57 ` [RFC 4/5] perf: Add pmu callbacks to track event mapping and unmapping Andy Lutomirski
2014-10-14 22:57 ` [RFC 5/5] x86,perf: Only allow rdpmc if a perf_event is mapped Andy Lutomirski
2014-10-16  8:42   ` Peter Zijlstra
2014-10-16 15:37     ` Andy Lutomirski
2014-10-16 15:57     ` Borislav Petkov
2014-10-17  0:00   ` Andy Lutomirski
2014-10-19 20:23     ` Andy Lutomirski
2014-10-19 21:33       ` Peter Zijlstra
2014-10-19 22:05         ` Andy Lutomirski
2014-10-19 22:20           ` Peter Zijlstra
2014-10-19 22:57             ` Andy Lutomirski
2014-10-20  8:33               ` Peter Zijlstra
2014-10-20 16:49                 ` Andy Lutomirski
2014-10-20 17:39                   ` Andy Lutomirski
2014-10-21  8:59                     ` Peter Zijlstra
2014-10-19 21:35     ` Peter Zijlstra
2014-10-20  0:08       ` Andy Lutomirski
2014-10-20  8:48         ` Peter Zijlstra
2014-10-20  9:24           ` Martin Schwidefsky
2014-10-20 10:51           ` Hendrik Brueckner
2014-10-21  9:14             ` Peter Zijlstra
2014-10-21 15:52               ` Andy Lutomirski [this message]
2014-10-21  4:06 ` [RFC 0/5] CR4 handling improvements Vince Weaver
2014-10-21  4:28   ` Andy Lutomirski
2014-10-21 15:00     ` Vince Weaver
2014-10-21 16:04       ` Peter Zijlstra
2014-10-21 17:05         ` Vince Weaver
2014-10-23 11:42           ` Peter Zijlstra
2014-10-24 12:41             ` Vince Weaver
2014-10-24 22:14               ` Andy Lutomirski

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=CALCETrX8Y-PGBxU+tcCy7s-8KmYY3SVGHUWmvhBimgmwri+4uw@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=aarcange@redhat.com \
    --cc=acme@kernel.org \
    --cc=anton@samba.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=ebn310@few.vu.nl \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=schwidefsky@de.ibm.com \
    /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).