From: "최동혁/DONGHYEOK CHOE" <d7271.choe@samsung.com>
To: <will@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <hosung0.kim@samsung.com>, <changki.kim@samsung.com>,
<hajun.sung@samsung.com>, <gregkh@google.com>,
<youngmin.nam@samsung.com>
Subject: Reqeust export symbol for API in arch/arm64/*
Date: Wed, 6 May 2020 21:46:45 +0900 [thread overview]
Message-ID: <00bc01d623a4$669d1e70$33d75b50$@samsung.com> (raw)
In-Reply-To: <CGME20200506124645epcas2p25a8efbe59fa20194e19d642227dd47ae@epcas2p2.samsung.com>
Hello,
I am software engineer in charge of BSP (Samsung SOC vendor).
Recently, Google introduced GKI from Android R version.
We cannot use mainline API without 'export symbol' by the GKI policy.
But we want to make an arm64 specific vendor driver in {kernel source
root}/drivers/soc/samsung/*.
Could you support us to use the below APIs?
1. [register_kernel_break_hook]
To make runtime debug feature. We need architecture support.(break hook)
It's an architecture specific function. After cpu execute specific
instruction, A function with a parameter which is the context at that
time(the executing specific instruction) is performed. I am trying to
restore the locked context by using this fuction with the el3 trap for
debugging hardlockup core(s).
2. [dump_backtrace]
Although 'dump_stack' is already supported, we need 'dump_backtrace' also.
Because we need lighten api to debug system. In some situation like bus
hang(HW bug), dump_stack highly likely make a problem again while printing
debug information.
next parent reply other threads:[~2020-05-06 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200506124645epcas2p25a8efbe59fa20194e19d642227dd47ae@epcas2p2.samsung.com>
2020-05-06 12:46 ` 최동혁/DONGHYEOK CHOE [this message]
2020-05-06 12:53 ` Will Deacon
2020-05-06 13:05 ` 최동혁/DONGHYEOK CHOE
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='00bc01d623a4$669d1e70$33d75b50$@samsung.com' \
--to=d7271.choe@samsung.com \
--cc=changki.kim@samsung.com \
--cc=gregkh@google.com \
--cc=hajun.sung@samsung.com \
--cc=hosung0.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.org \
--cc=youngmin.nam@samsung.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
Powered by JetHome