From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] ARM: mvebu: Enable perf support in mvebu_v7_defconfig
Date: Wed, 22 Oct 2014 12:33:41 -0300 [thread overview]
Message-ID: <5447CE55.6020808@free-electrons.com> (raw)
In-Reply-To: <20141022141127.GN22642@leverpostej>
On 10/22/2014 11:11 AM, Mark Rutland wrote:
> On Wed, Oct 22, 2014 at 02:43:47PM +0100, Ezequiel Garcia wrote:
>> Now that Armada 375/38x have support for the PMU, this commit enables perf
>> events in the defconfig.
>>
>> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
>> ---
>> arch/arm/configs/mvebu_v7_defconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm/configs/mvebu_v7_defconfig b/arch/arm/configs/mvebu_v7_defconfig
>> index ed0a0d1..d1a4669 100644
>> --- a/arch/arm/configs/mvebu_v7_defconfig
>> +++ b/arch/arm/configs/mvebu_v7_defconfig
>> @@ -5,6 +5,7 @@ CONFIG_HIGH_RES_TIMERS=y
>> CONFIG_LOG_BUF_SHIFT=14
>> CONFIG_BLK_DEV_INITRD=y
>> CONFIG_EXPERT=y
>> +CONFIG_PERF_EVENTS=y
>
> Isn't this provided by CONFIG_ARM already?
>
No, you need to select it explicitly, as the other platforms do.
> Surely you want CONFIG_HW_PERF_EVENTS?
>
Yes, but it defaults to 'yes' if PERF_EVENTS is enabled, so you don't
need it in the defconfig.
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-22 15:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 13:43 [PATCH 0/7] Armada 375/38x perf support, and a bonus irqchip driver simplification Ezequiel Garcia
2014-10-22 13:43 ` [PATCH 1/7] irqchip: armada-370-xp: Simplify interrupt map, mask and unmask Ezequiel Garcia
2014-10-31 16:36 ` Gregory CLEMENT
2014-11-04 15:11 ` Ezequiel Garcia
2014-11-10 17:09 ` Gregory CLEMENT
2014-10-22 13:43 ` [PATCH 2/7] irqchip: armada-370-xp: Initialize per cpu registers when CONFIG_SMP=N Ezequiel Garcia
2014-11-12 10:30 ` Gregory CLEMENT
2014-10-22 13:43 ` [PATCH 3/7] irqchip: armada-370-xp: Introduce a is_percpu_irq() helper for readability Ezequiel Garcia
2014-10-22 13:58 ` Mark Rutland
2014-10-22 15:14 ` Ezequiel Garcia
2014-10-22 13:43 ` [PATCH 4/7] irqchip: armada-370-xp: Enable Performance Counter interrupts Ezequiel Garcia
2014-10-22 13:43 ` [PATCH 5/7] ARM: mvebu: Enable Performance Monitor Unit on Armada 375 SoC Ezequiel Garcia
2014-10-22 14:04 ` Mark Rutland
2014-10-22 22:16 ` Ezequiel Garcia
2014-10-23 9:14 ` Thomas Petazzoni
2014-10-23 11:51 ` Ezequiel Garcia
2014-10-23 12:07 ` Thomas Petazzoni
2014-10-23 12:19 ` Ezequiel Garcia
2014-10-23 13:18 ` Mark Rutland
2014-10-31 16:23 ` Ezequiel Garcia
2014-10-23 9:41 ` Mark Rutland
2014-10-22 13:43 ` [PATCH 6/7] ARM: mvebu: Enable Performance Monitor Unit on Armada 380/385 SoC Ezequiel Garcia
2014-10-22 14:06 ` Mark Rutland
2014-10-22 22:18 ` Ezequiel Garcia
2014-10-22 13:43 ` [PATCH 7/7] ARM: mvebu: Enable perf support in mvebu_v7_defconfig Ezequiel Garcia
2014-10-22 14:11 ` Mark Rutland
2014-10-22 15:33 ` Ezequiel Garcia [this message]
2014-10-22 15:38 ` Mark Rutland
2014-11-09 5:23 ` [PATCH 0/7] Armada 375/38x perf support, and a bonus irqchip driver simplification Jason Cooper
2014-11-09 9:41 ` Thomas Petazzoni
2014-11-09 12:18 ` Ezequiel Garcia
2014-11-09 22:50 ` Jason Cooper
2014-11-23 0:45 ` Ezequiel Garcia
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=5447CE55.6020808@free-electrons.com \
--to=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).