From: yalin wang <yalin.wang2010@gmail.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: add HAVE_LATENCYTOP_SUPPORT config
Date: Sat, 7 Nov 2015 00:11:16 +0800 [thread overview]
Message-ID: <247F438B-3EEA-4550-970E-A649D0E604ED@gmail.com> (raw)
In-Reply-To: <20151106160501.GR6087@arm.com>
i just enable it on ARM64,
and it can work,
i don’t see some special requirement to enable this config .
> On Nov 7, 2015, at 00:05, Will Deacon <will.deacon@arm.com> wrote:
>
> On Fri, Nov 06, 2015 at 11:57:58PM +0800, yalin wang wrote:
>> Add HAVE_LATENCYTOP_SUPPORT in Kconfig, so that
>> we can enable this feature on ARM64
>
> Do you know what the prerequisites for HAVE_LATENCYTOP_SUPPORT actually
> are (beyond those explicitly listed as dependencies for CONFIG_LATENCYTOP)?
>
> Will
WARNING: multiple messages have this Message-ID (diff)
From: yalin.wang2010@gmail.com (yalin wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: add HAVE_LATENCYTOP_SUPPORT config
Date: Sat, 7 Nov 2015 00:11:16 +0800 [thread overview]
Message-ID: <247F438B-3EEA-4550-970E-A649D0E604ED@gmail.com> (raw)
In-Reply-To: <20151106160501.GR6087@arm.com>
i just enable it on ARM64,
and it can work,
i don?t see some special requirement to enable this config .
> On Nov 7, 2015, at 00:05, Will Deacon <will.deacon@arm.com> wrote:
>
> On Fri, Nov 06, 2015 at 11:57:58PM +0800, yalin wang wrote:
>> Add HAVE_LATENCYTOP_SUPPORT in Kconfig, so that
>> we can enable this feature on ARM64
>
> Do you know what the prerequisites for HAVE_LATENCYTOP_SUPPORT actually
> are (beyond those explicitly listed as dependencies for CONFIG_LATENCYTOP)?
>
> Will
next prev parent reply other threads:[~2015-11-06 16:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 15:57 [PATCH] arm64: add HAVE_LATENCYTOP_SUPPORT config yalin wang
2015-11-06 15:57 ` yalin wang
2015-11-06 16:05 ` Will Deacon
2015-11-06 16:05 ` Will Deacon
2015-11-06 16:11 ` yalin wang [this message]
2015-11-06 16:11 ` yalin wang
2015-11-06 16:21 ` Will Deacon
2015-11-06 16:21 ` Will Deacon
2015-11-10 7:41 ` Heiko Carstens
2015-11-10 7:41 ` Heiko Carstens
2015-11-10 10:05 ` Will Deacon
2015-11-10 10:05 ` Will Deacon
2015-11-10 11:01 ` Heiko Carstens
2015-11-10 11:01 ` Heiko Carstens
2015-11-10 11:18 ` Will Deacon
2015-11-10 11:18 ` Will Deacon
2015-11-10 11:24 ` yalin wang
2015-11-10 11:24 ` yalin wang
2015-11-10 11:34 ` Heiko Carstens
2015-11-10 11:34 ` Heiko Carstens
2015-12-14 22:02 ` Shi, Yang
2015-12-14 22:02 ` Shi, Yang
2015-12-15 9:48 ` Will Deacon
2015-12-15 9:48 ` Will Deacon
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=247F438B-3EEA-4550-970E-A649D0E604ED@gmail.com \
--to=yalin.wang2010@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will.deacon@arm.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 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.