Hey Tony, nice to hear back from you.
I'm taking the liberty of moving our conversation to the coresight
mailing list. The team is getting a little bigger now and it allows
people to know what is going on and chime in with ideas of their own.
What you are referring to is called the kernel crash dump utility.
Ubuntu has a good introduction page on the mechanism [1] and we even
have a card for it [2] (I hope you can see it) after a conversation
with Will Deacon in San Francisco back in Septemeber. Intel has a
patchset out that tries to do that as well [3] but don't know where
the venture is at.
We are currently not working on this feature for lack of resources.
Regards,
Mathieu
[1]. https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html
[2]. https://projects.linaro.org/browse/KWG-157
[3]. http://thread.gmane.org/gmane.linux.kernel/2007199
On 11 December 2015 at 09:11, Tony Armitstead <Tony.Armitstead(a)arm.com> wrote:
> Hi Mathieu,
>
>
>
> Hope you are well – we have not spoken in a while.
>
>
>
> I am being asked about integration of CoreSight Access Library with Linux
> kernel panic situations. Now I know this is not a sensible question, but the
> idea that the kernel can write out the data set (register, memory, ETB
> content etc) somewhere on a kernel panic and then get this picked up somehow
> and converted into a data file set for DS-5’s crash dump files, does make
> sense. The ‘problem’ is that how does the kernel write the data somewhere
> when it has just panicked?
>
>
>
> So the question that occurs to me is whether this is already a solved
> problem in ‘Linux land’ and there is some frame work our users could use to
> provide this feature. Are you aware of anything?
>
>
>
> Regards Tony
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
Hi,
While I'm doing some meddlation with the makefiles to build .so libs, it occurs to me that this might be a good time to consider the library names.
Rctdl_c_api and ref_trace_decoder reflect the origins of the code as an ARM project to produce an open source reference trace decode library - prior to this effort being contributed and folded in to OpenCSD.
My thoughts were either
libarm_opencsd.so / libarm_opencsd_c_api.so
or
libarm_cstraced.so / libarm_cstraced_c_api.so
Both of which specify the architecture and function a little better than the old names.
Opinions??
Regards
Mike
(RCTDL appears across much of the source code too, but changing that is a massive job, so I'm not considering that at present).
----------------------------------------------------------------
Mike Leach +44 (0)1254 893911 (Direct)
Principal Engineer +44 (0)1254 893900 (Main)
Arm Blackburn Design Centre +44 (0)1254 893901 (Fax)
Belthorn House
Walker Rd mailto:mike.leach@arm.com
Guide
Blackburn
BB1 2QE
----------------------------------------------------------------
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Mike, Mathieu
I've been reading STM driver and its device tree configurations along
with the specifications recently.
Yesterday, Mathieu asked me a question about the true definition of
STM masters. This morning, I read code and spec again. There's still a
few details need to ask Mike.
Mike, please correct me if anything what I'm writing here is wrong.
>From what I have understood, I think STM masters/channels are a
continuous physical space in STM, a bit like registers on this point.
On my Spreadtrum's board, for example, we are configuring 0x180000
byte space for stimulus ports (i.e. channels). The TRM documents that
CS-STM has 129 masters, 128 for software, each supporting 65536
channels. And my question is :
1) How much physical space each channel should take?
2) Do the channels dump the trace packets in real time?
3) Is it correct that set total 0x180000 byte space for 128 masters
and 128*65536 channels?
Thank you,
Chunyan
