On 01.03.2018 14:53, Thomas Huth wrote:
> On 01.03.2018 13:08, David Hildenbrand wrote:
>> Let's also put the 31-bit hack in front of the REAL MMU, otherwise right
>> now we get errors when loading a PSW where the highest bit is set (e.g.
>> via s390-netboot.img). The highest bit is not masked away
On 01.03.2018 13:08, David Hildenbrand wrote:
> Let's also put the 31-bit hack in front of the REAL MMU, otherwise right
> now we get errors when loading a PSW where the highest bit is set (e.g.
> via s390-netboot.img). The highest bit is not masked away, therefore we
> inject addressing exceptions
On Thu, 1 Mar 2018 13:08:26 +0100
David Hildenbrand wrote:
> Let's also put the 31-bit hack in front of the REAL MMU, otherwise right
> now we get errors when loading a PSW where the highest bit is set (e.g.
> via s390-netboot.img). The highest bit is not masked away, therefore we
> inject addre
Let's also put the 31-bit hack in front of the REAL MMU, otherwise right
now we get errors when loading a PSW where the highest bit is set (e.g.
via s390-netboot.img). The highest bit is not masked away, therefore we
inject addressing exceptions into the guest.
The proper fix will later be to do a
