mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jinlong Mao <quic_jinlmao@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "Catalin Marinas" <catalin.marinas@arm.com>,
	"Will Deacon" <will@kernel.org>,
	"Bjorn Andersson" <quic_bjorande@quicinc.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: defconfig: Enable Ftrace and STM configs
Date: Tue, 24 Sep 2024 17:19:14 +0800	[thread overview]
Message-ID: <023f532b-62d6-4a38-b288-e08b5f7788ac@quicinc.com> (raw)
In-Reply-To: <CAA8EJppY4QXDWK1QsrorQM8NTOmi4cK_Fjhkzf10muRE85BQ-w@mail.gmail.com>



On 2024/9/20 16:10, Dmitry Baryshkov wrote:
> On Fri, 20 Sept 2024 at 09:59, Mao Jinlong <quic_jinlmao@quicinc.com> wrote:
>>
>> Ftrace logs can be captured by STM over TMC sink path. We can enable
>> ftrace logs along with HW trace of coresight component. The timestamp
>> of ftrace logs and hw traces will be in sync which helps to debug.
> 
> You are describing what can be done. Please describe why this is
> necessary and what is actually being done. See
> Documentation/process/submitting-patches.rst. The "why" part is the
> most important.
> 
Thanks for the review. I will update in next version.
>>
>> Signed-off-by: Mao Jinlong <quic_jinlmao@quicinc.com>
>> ---
>>   arch/arm64/configs/defconfig | 8 +++++++-
>>   1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>> index 4a3999eefa67..c0a56e58e554 100644
>> --- a/arch/arm64/configs/defconfig
>> +++ b/arch/arm64/configs/defconfig
>> @@ -1554,6 +1554,12 @@ CONFIG_NVMEM_SNVS_LPGPR=y
>>   CONFIG_NVMEM_SPMI_SDAM=m
>>   CONFIG_NVMEM_SUNXI_SID=y
>>   CONFIG_NVMEM_UNIPHIER_EFUSE=y
>> +CONFIG_STM_PROTO_BASIC=m
>> +CONFIG_STM_PROTO_SYS_T=m
>> +CONFIG_STM_DUMMY=m
>> +CONFIG_STM_SOURCE_CONSOLE=m
>> +CONFIG_STM_SOURCE_HEARTBEAT=m
>> +CONFIG_STM_SOURCE_FTRACE=m
>>   CONFIG_FPGA=y
>>   CONFIG_FPGA_MGR_ALTERA_CVP=m
>>   CONFIG_FPGA_MGR_STRATIX10_SOC=m
>> @@ -1663,7 +1669,7 @@ CONFIG_DEBUG_INFO_REDUCED=y
>>   CONFIG_MAGIC_SYSRQ=y
>>   CONFIG_DEBUG_FS=y
>>   # CONFIG_SCHED_DEBUG is not set
>> -# CONFIG_FTRACE is not set
>> +CONFIG_FTRACE=y
>>   CONFIG_CORESIGHT=m
>>   CONFIG_CORESIGHT_LINK_AND_SINK_TMC=m
>>   CONFIG_CORESIGHT_CATU=m
>> --
>> 2.46.0
>>
> 
> 


  reply	other threads:[~2024-09-24  9:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20  7:59 Mao Jinlong
2024-09-20  8:10 ` Dmitry Baryshkov
2024-09-24  9:19   ` Jinlong Mao [this message]
2024-09-20 12:48 ` Krzysztof Kozlowski
2024-09-24  9:19   ` Jinlong Mao

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=023f532b-62d6-4a38-b288-e08b5f7788ac@quicinc.com \
    --to=quic_jinlmao@quicinc.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=nfraprado@collabora.com \
    --cc=quic_bjorande@quicinc.com \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®