Re: [PATCH] tests/boot-sector: Fix the bad s390x assembler code

2019-12-18 Thread Cornelia Huck
On Tue, 17 Dec 2019 16:06:42 +0100 Thomas Huth wrote: > There are currently two bugs in s390x_code[]: First, the initial jump > uses the wrong offset, so it was jumping to 0x1014 instead of 0x1010. > Second, LHI only loads the lower 32-bit of the register. > > Everything worked fine as long as

Re: [PATCH] tests/boot-sector: Fix the bad s390x assembler code

2019-12-18 Thread Christian Borntraeger
On 17.12.19 16:06, Thomas Huth wrote: > There are currently two bugs in s390x_code[]: First, the initial jump > uses the wrong offset, so it was jumping to 0x1014 instead of 0x1010. 10014/10010 instead of 1014/1010 > Second, LHI only

Re: [PATCH] tests/boot-sector: Fix the bad s390x assembler code

2019-12-18 Thread Cornelia Huck
On Tue, 17 Dec 2019 16:06:42 +0100 Thomas Huth wrote: > There are currently two bugs in s390x_code[]: First, the initial jump > uses the wrong offset, so it was jumping to 0x1014 instead of 0x1010. > Second, LHI only loads the lower 32-bit of the register. > > Everything worked fine as long as

[PATCH] tests/boot-sector: Fix the bad s390x assembler code

2019-12-17 Thread Thomas Huth
There are currently two bugs in s390x_code[]: First, the initial jump uses the wrong offset, so it was jumping to 0x1014 instead of 0x1010. Second, LHI only loads the lower 32-bit of the register. Everything worked fine as long as the s390-ccw bios code was jumping here with r3 containing zeroes