<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 09/07/19 7:48 PM, Vasant Hegde
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8399f101-576b-bafc-530a-ec484df8c553@linux.vnet.ibm.com">On
07/09/2019 03:23 PM, Oliver O'Halloran wrote:
<br>
<blockquote type="cite">On Fri, 2019-06-28 at 14:34 +0530, Vasant
Hegde wrote:
<br>
<blockquote type="cite">On 06/28/2019 06:18 AM, Nicholas Piggin
wrote:
<br>
<blockquote type="cite">Vasant Hegde's on June 17, 2019 3:10
am:
<br>
<blockquote type="cite">Needed for creating OPAL core file.
<br>
<br>
Sample output:
<br>
--------------
<br>
sys/firmware/devicetree/base/ibm,opal # lsprop
<br>
...
<br>
opal-boot-address
<br>
00000000 30002560
<br>
...
<br>
</blockquote>
<br>
Why is this needed? We can't derive it from the symbol
table?
<br>
</blockquote>
<br>
</blockquote>
<br>
<blockquote type="cite">Kernel needs this address to generate
proper OPAL dump.
<br>
</blockquote>
<br>
I looked at Hari's patches to try work out what a "proper dump"
<br>
is. Looks like we use this to create the AT_ENTRY note for the
<br>
opalcore which file. Sounds important, but I can't find where
<br>
the same happens for the Linux vmcore, so maybe it's not?
<br>
<br>
</blockquote>
<br>
vmcore is analyzed by crash.. which may not need AT_ENTRY.
<br>
Hari can confirm.
<br>
<br>
</blockquote>
<pre>
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
</pre>
</body>
</html>