[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <00bc01d623a4$669d1e70$33d75b50$@samsung.com>
Date: Wed, 6 May 2020 21:46:45 +0900
From: ÃÖµ¿Çõ/DONGHYEOK CHOE
<d7271.choe@...sung.com>
To: <will@...nel.org>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Cc: <hosung0.kim@...sung.com>, <changki.kim@...sung.com>,
<hajun.sung@...sung.com>, <gregkh@...gle.com>,
<youngmin.nam@...sung.com>
Subject: Reqeust export symbol for API in arch/arm64/*
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.
Powered by blists - more mailing lists