[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFCv3 1/9] s390x: move setting of maximum ram size to machine
|
From: |
Cornelia Huck |
|
Subject: |
Re: [PATCH RFCv3 1/9] s390x: move setting of maximum ram size to machine init |
|
Date: |
Mon, 27 Jul 2020 11:13:09 +0200 |
On Fri, 24 Jul 2020 16:37:42 +0200
David Hildenbrand <david@redhat.com> wrote:
> As we no longer fixup the maximum ram size in sclp code, let's move
> setting the maximum ram size to ccw_init()->s390_memory_init(), which
> now looks like a better fit.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> hw/s390x/s390-virtio-ccw.c | 19 ++++++++++++++++---
> hw/s390x/sclp.c | 15 +--------------
> 2 files changed, 17 insertions(+), 17 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
- [PATCH RFCv3 0/9] s390x: initial support for virtio-mem, David Hildenbrand, 2020/07/24
- [PATCH RFCv3 2/9] s390x/diag: no need to check for PGM_PRIVILEGED in diag308, David Hildenbrand, 2020/07/24
- [PATCH RFCv3 1/9] s390x: move setting of maximum ram size to machine init, David Hildenbrand, 2020/07/24
- Re: [PATCH RFCv3 1/9] s390x: move setting of maximum ram size to machine init,
Cornelia Huck <=
- [PATCH RFCv3 4/9] s390x: prepare for more diag500 hypercalls, David Hildenbrand, 2020/07/24
- [PATCH RFCv3 5/9] s390x: rename s390-virtio-hcall* to s390-hypercall*, David Hildenbrand, 2020/07/24
- [PATCH RFCv3 7/9] s390x: prepare device memory address space, David Hildenbrand, 2020/07/24
- [PATCH RFCv3 6/9] s390x/diag: subcode to query device memory region, David Hildenbrand, 2020/07/24