<html><body><p><font size="2">> </font><tt><font size="2">Is there a 'quiesce' opcode one can use, like the nap one?</font></tt><br><font size="2">The only thing I can think of is the ATTN instruction. See src/kernel/forceattn_p9.S for what we do. Some of that makes the attention visible which you don't care about, not sure how much you need to get exactly what you want. The issue is that 'quiesced' is a maintenance state and you aren't really allowed to put yourself into a maintenance mode. There are scoms to stop instructions though if that would help.</font><br><font size="2"><br>--<br>Dan Crowell<br>Senior Software Engineer - Power Systems Enablement Firmware<br>IBM Rochester: t/l 553-2987<br>dcrowell@us.ibm.com</font><br><br><img width="16" height="16" src="cid:1__=09BB0E11DFE35C4D8f9e8a93df938690918c09B@" border="0" alt="Inactive hide details for "Marty E. Plummer" ---09/25/2019 10:26:05 PM---Holy crap. Think I finally got it at least loading the"><font size="2" color="#424282">"Marty E. Plummer" ---09/25/2019 10:26:05 PM---Holy crap. Think I finally got it at least loading the faked hbb. I managed to (probably) dump the 6</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Marty E. Plummer" <hanetzer@startmail.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">Alistair Popple <apopple@linux.ibm.com></font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">Amit J Tendolkar <amit.tendolkar@in.ibm.com>, Raja Das1 <rajadas2@in.ibm.com>, openpower-firmware@lists.ozlabs.org, Dean Sanner <dsanner@us.ibm.com>, Sachin Gupta24 <sgupta2m@in.ibm.com></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">09/25/2019 10:26 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[EXTERNAL] Re: [OpenPower-Firmware] A few questions about early hostboot</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">"OpenPower-Firmware" <openpower-firmware-bounces+dcrowell=us.ibm.com@lists.ozlabs.org></font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><font size="2">Holy crap. Think I finally got it at least loading the faked hbb.<br>I managed to (probably) dump the 64b you mentioned, assuming that<br>0x8208000 is the correct address. I was getting consistently:<br><br>00000000 10 30 24 31 41 42 43 e0 e1 e2 e4 f4 34 24 31 41 |.0$1ABC.....4$1A| <br>00000010 42 43 e0 e1 e2 e4 f4 00 00 00 00 00 00 00 00 00 |BC..............| <br>00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|<br><br>which is a series of ffs toc errors. So, I moved the backup toc<br>from 0x3ff8000 to 0x3ff7000 (which is consistent with the 'stock'<br>firmware and src/include/usr/pnor/pnor_const.H:171; I only used<br>0x3ff8000 because it made for easy maths) and I get an entirely<br>different result:<br><br>00000000 10 30 24 31 41 42 43 44 45 32 35 11 24 12 16 00 |.0$1ABCDE25.$...| <br>00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|<br><br>which is as far as 'ok, we copied it'. It may have stopped<br>here because _start is 'b .', more testing is required, but<br>sbe and hbbl are unmodified<br><br>I still can't consistently get all the threads to stop or read<br>spr 313, but this is at least some form of progress (I think).<br>_______________________________________________<br>OpenPower-Firmware mailing list<br>OpenPower-Firmware@lists.ozlabs.org<br><a href="https://lists.ozlabs.org/listinfo/openpower-firmware">https://lists.ozlabs.org/listinfo/openpower-firmware</a> <br><br></font></tt><br><br><BR>
</body></html>