[Skiboot] [PATCH v8 01/24] OPAL: Add OPAL boot entry address to device tree

[Hari Bathini]

On 09/07/19 7:48 PM, Vasant Hegde wrote:
> On 07/09/2019 03:23 PM, Oliver O'Halloran wrote:
>> On Fri, 2019-06-28 at 14:34 +0530, Vasant Hegde wrote:
>>> On 06/28/2019 06:18 AM, Nicholas Piggin wrote:
>>>> Vasant Hegde's on June 17, 2019 3:10 am:
>>>>> Needed for creating OPAL core file.
>>>>>
>>>>> Sample output:
>>>>> --------------
>>>>>     sys/firmware/devicetree/base/ibm,opal # lsprop
>>>>>     ...
>>>>>     opal-boot-address
>>>>>          00000000 30002560
>>>>>     ...
>>>>
>>>> Why is this needed? We can't derive it from the symbol table?
>>>
>>
>>> Kernel needs this address to generate proper OPAL dump.
>>
>> I looked at Hari's patches to try work out what a "proper dump"
>> is. Looks like we use this to create the AT_ENTRY note for the
>> opalcore which file. Sounds important, but I can't find where
>> the same happens for the Linux vmcore, so maybe it's not?
>>
>
> vmcore is analyzed by crash.. which may not need AT_ENTRY.
> Hari can confirm.
>
Yeah. opalcore needs to rely on GDB while we have a utility called crash built
on top of GDB to handle vmcore. GDB needs this note to understand a typical core
while crash utility handles it for vmcore...

Thanks
Hari

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/skiboot/attachments/20190709/6a046aa6/attachment-0001.htm>