[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFCv2 3/6] s390x/diag: implement diag260
|
From: |
Heiko Carstens |
|
Subject: |
Re: [PATCH RFCv2 3/6] s390x/diag: implement diag260 |
|
Date: |
Wed, 15 Jul 2020 12:53:34 +0200 |
On Wed, Jul 15, 2020 at 11:19:03AM +0200, David Hildenbrand wrote:
> On 14.07.20 12:17, Claudio Imbrenda wrote:
> > shouldn't it return all the hotplugged areas once hotplugging is
> > enabled?
>
> No, that would be dangerous and wrong. Memory ranges part of memory
> devices never must be indicated as part of hw/firmware interfaces to
> indicate valid boot memory. Memory provided via memory devices
> (virtio-mem, virtio-pmem, ...) has different semantics than ordinary
> hotplugged memory, and unmodified OSs (esp., older Linux versions)
> should not silently try to make use of any such memory. It's not just
> some hotplugged memory a guest OS should detect+use during boot as
> system ram. Thanks!
How is kdump supposed to work, if there is no mechanism to figure out
which memory ranges have been added dynamically to the system?
[PATCH RFCv2 5/6] s390x: implement virtio-mem-ccw, David Hildenbrand, 2020/07/10
[PATCH RFCv2 6/6] s390x: initial support for virtio-mem, David Hildenbrand, 2020/07/10