When debugging s390 linux kernel with qemu kvm gdbstub, dumping memory
contents at addresses in range 0x8000-0x1 results in an
error or all zeroes being returned.
The problem appears to be that linux puts 2G page at that location,
which qemu currently does not know about.
Check FC
On 16.07.19 15:11, Christian Borntraeger wrote:
>
> On 16.07.19 15:04, Cornelia Huck wrote:
>> On Tue, 16 Jul 2019 14:52:03 +0200
>> Ilya Leoshkevich wrote:
>>
Am 16.07.2019 um 14:41 schrieb David Hildenbrand :
How urgent is this? If this can wait, I can polish and send my series
On 16.07.19 15:04, Cornelia Huck wrote:
> On Tue, 16 Jul 2019 14:52:03 +0200
> Ilya Leoshkevich wrote:
>
>>> Am 16.07.2019 um 14:41 schrieb David Hildenbrand :
>>>
>>> How urgent is this? If this can wait, I can polish and send my series I
>>> have here
>>> instead, which also implents
>>> -
> Am 16.07.2019 um 15:04 schrieb Cornelia Huck :
>
> On Tue, 16 Jul 2019 14:52:03 +0200
> Ilya Leoshkevich wrote:
>
>>> Am 16.07.2019 um 14:41 schrieb David Hildenbrand :
>>>
>>> How urgent is this? If this can wait, I can polish and send my series I
>>> have here
>>> instead, which also
On Tue, 16 Jul 2019 14:52:03 +0200
Ilya Leoshkevich wrote:
> > Am 16.07.2019 um 14:41 schrieb David Hildenbrand :
> >
> > How urgent is this? If this can wait, I can polish and send my series I
> > have here
> > instead, which also implents
> > - IEP support
> > -
> Am 16.07.2019 um 14:41 schrieb David Hildenbrand :
>
> How urgent is this? If this can wait, I can polish and send my series I have
> here
> instead, which also implents
> - IEP support
> - access-exception-fetch/store-indication facility
> - ESOP-1, ESOP-2
This is not urgent, I can live with
On 16.07.19 14:34, Ilya Leoshkevich wrote:
> When debugging s390 linux kernel with qemu kvm gdbstub, dumping memory
> contents at addresses in range 0x8000-0x1 results in an
> error or all zeroes being returned.
>
> The problem appears to be that linux puts 2G page at that location,
>
