From: Thomas Huth <thuth@redhat.com>
To: jjherne@linux.ibm.com,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org, cohuck@redhat.com
Subject: Re: [PATCH] pc-bios/s390x: Pack ResetInfo struct
Date: Thu, 27 Aug 2020 12:07:07 +0200 [thread overview]
Message-ID: <12e6fb00-bf1c-268b-baee-ccf1eb73bece@redhat.com> (raw)
In-Reply-To: <d9891265-2254-ee64-c009-0105f7a8b02b@linux.ibm.com>
On 07/02/2020 15.02, Jason J. Herne wrote:
> On 2/7/20 6:28 AM, Christian Borntraeger wrote:
>> Jason,
>>
>> can you run objdump -Sdr on jump2ipl.o on a broken variant?
>>
>>
> To keep the volume lower, I've only pasted the output that I think
> you're interested in. If you want to see the entire thing just let me know.
>
> static void jump_to_IPL_2(void)
> {
> 1d0: eb bf f0 58 00 24 stmg %r11,%r15,88(%r15)
> 1d6: a7 fb ff 50 aghi %r15,-176
> 1da: b9 04 00 bf lgr %r11,%r15
> ResetInfo *current = 0;
> 1de: a7 19 00 00 lghi %r1,0
> 1e2: e3 10 b0 a8 00 24 stg %r1,168(%r11)
>
> void (*ipl)(void) = (void *) (uint64_t) current->ipl_continue;
> 1e8: e3 10 b0 a8 00 04 lg %r1,168(%r11)
> 1ee: 58 10 10 08 l %r1,8(%r1)
> 1f2: b9 16 00 11 llgfr %r1,%r1
> 1f6: e3 10 b0 a0 00 24 stg %r1,160(%r11)
> *current = save;
> 1fc: e3 10 b0 a8 00 04 lg %r1,168(%r11)
> 202: c0 20 00 00 00 00 larl %r2,202 <jump_to_IPL_2+0x32>
> 204: R_390_PC32DBL .bss+0x2
> 208: eb 23 20 00 00 04 lmg %r2,%r3,0(%r2)
> 20e: eb 23 10 00 00 24 stmg %r2,%r3,0(%r1)
> ipl(); /* should not return */
> 214: e3 10 b0 a0 00 04 lg %r1,160(%r11)
> 21a: 0d e1 basr %r14,%r1
> }
> 21c: 18 00 lr %r0,%r0
> 21e: eb bf b1 08 00 04 lmg %r11,%r15,264(%r11)
> 224: 07 fe br %r14
> 226: 07 07 nopr %r7
I'm currently looking through the past s390-ccw bios patches that still
might need attention ... was there ever a follow up on this discussion?
Do we need to clear the registers before jumping to the OS?
And looking at the disassembly, should we declar the ipl function
pointer with __attribute__((noreturn)) ?
Thomas
next prev parent reply other threads:[~2020-08-27 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 18:21 [PATCH] pc-bios/s390x: Pack ResetInfo struct Jason J. Herne
2020-02-06 9:55 ` Cornelia Huck
2020-02-06 10:09 ` Christian Borntraeger
2020-02-06 11:00 ` Thomas Huth
2020-02-07 11:28 ` Christian Borntraeger
2020-02-07 14:02 ` Jason J. Herne
2020-08-27 10:07 ` Thomas Huth [this message]
2020-09-01 13:02 ` Jason J. Herne
2020-02-13 18:02 ` Jason J. Herne
2020-02-13 18:24 ` Christian Borntraeger
2020-02-25 10:23 ` Jason J. Herne
2020-02-25 11:13 ` Christian Borntraeger
2020-02-25 12:58 ` Jason J. Herne
2020-02-25 15:00 ` Christian Borntraeger
2020-02-25 15:05 ` Christian Borntraeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12e6fb00-bf1c-268b-baee-ccf1eb73bece@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.