From: Borislav Petkov <bp@alien8.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, hpa@zytor.com,
tglx@linutronix.de, ak@linux.intel.com,
torvalds@linux-foundation.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf/x86: Export some PMU attributes in caps/ directory
Date: Mon, 28 Aug 2017 13:01:32 +0200 [thread overview]
Message-ID: <20170828110132.phq54h637hmq3fzt@pd.tnic> (raw)
In-Reply-To: <20170828104650.2u3rsim4jafyjzv2@hirez.programming.kicks-ass.net>
On Mon, Aug 28, 2017 at 12:46:50PM +0200, Peter Zijlstra wrote:
> Boris, could you give this a spin?
>
> ---
> Subject: perf/x86: Fix caps/ for !Intel
>
> Move the 'max_precise' capability into generic x86 code where it
> belongs. This fixes a sysfs splat on !Intel systems where we fail to set
> x86_pmu_caps_group.atts.
>
> Fixes: 22688d1c20f5 ("x86/perf: Export some PMU attributes in caps/ directory")
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reported-and-tested-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-08-28 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 18:51 x86/perf: Improve sysfs enumeration for cpu pmu Andi Kleen
2017-08-22 18:52 ` [PATCH v1 1/2] x86/perf: Only show format attributes when supported Andi Kleen
2017-08-25 11:54 ` [tip:perf/core] perf/x86: " tip-bot for Andi Kleen
2017-08-22 18:52 ` [PATCH v1 2/2] x86/perf: Export some PMU attributes in caps Andi Kleen
2017-08-25 11:55 ` [tip:perf/core] perf/x86: Export some PMU attributes in caps/ directory tip-bot for Andi Kleen
2017-08-28 10:46 ` Peter Zijlstra
2017-08-28 11:01 ` Borislav Petkov [this message]
2017-08-28 19:29 ` Andi Kleen
2017-08-29 14:22 ` [tip:perf/core] perf/x86: Fix caps/ for !Intel tip-bot for Peter Zijlstra
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=20170828110132.phq54h637hmq3fzt@pd.tnic \
--to=bp@alien8.de \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).