[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PULL 10/15] s390x/s390-skeys: prepare for memory devices
From: |
David Hildenbrand |
Subject: |
[PULL 10/15] s390x/s390-skeys: prepare for memory devices |
Date: |
Wed, 18 Dec 2024 11:52:58 +0100 |
With memory devices, we will have storage keys for memory that
exceeds the initial ram size.
The TODO already states that current handling is subopimal,
but we won't worry about improving that (TCG-only) thing for now.
Message-ID: <20241008105455.2302628-10-david@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
---
hw/s390x/s390-skeys.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/s390x/s390-skeys.c b/hw/s390x/s390-skeys.c
index 6d0a47ed73..6ea4d8c20e 100644
--- a/hw/s390x/s390-skeys.c
+++ b/hw/s390x/s390-skeys.c
@@ -11,7 +11,7 @@
#include "qemu/osdep.h"
#include "qemu/units.h"
-#include "hw/boards.h"
+#include "hw/s390x/s390-virtio-ccw.h"
#include "hw/qdev-properties.h"
#include "hw/s390x/storage-keys.h"
#include "qapi/error.h"
@@ -251,9 +251,9 @@ static bool qemu_s390_enable_skeys(S390SKeysState *ss)
* g_once_init_enter() is good enough.
*/
if (g_once_init_enter(&initialized)) {
- MachineState *machine = MACHINE(qdev_get_machine());
+ S390CcwMachineState *s390ms = S390_CCW_MACHINE(qdev_get_machine());
- skeys->key_count = machine->ram_size / TARGET_PAGE_SIZE;
+ skeys->key_count = s390_get_memory_limit(s390ms) / TARGET_PAGE_SIZE;
skeys->keydata = g_malloc0(skeys->key_count);
g_once_init_leave(&initialized, 1);
}
--
2.47.1
- [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, David Hildenbrand, 2024/12/18
- [PULL 02/15] s390x/s390-virtio-ccw: don't crash on weird RAM sizes, David Hildenbrand, 2024/12/18
- [PULL 05/15] s390x: rename s390-virtio-hcall* to s390-hypercall*, David Hildenbrand, 2024/12/18
- [PULL 08/15] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, David Hildenbrand, 2024/12/18
- [PULL 11/15] s390x/s390-virtio-ccw: prepare for memory devices, David Hildenbrand, 2024/12/18
- [PULL 13/15] s390x: remember the maximum page size, David Hildenbrand, 2024/12/18
- [PULL 12/15] s390x/pv: prepare for memory devices, David Hildenbrand, 2024/12/18
- [PULL 01/15] virtio-mem: unplug memory only during system resets, not device resets, David Hildenbrand, 2024/12/18
- [PULL 10/15] s390x/s390-skeys: prepare for memory devices,
David Hildenbrand <=
- [PULL 14/15] s390x/virtio-ccw: add support for virtio based memory devices, David Hildenbrand, 2024/12/18
- [PULL 03/15] s390x/s390-virtio-hcall: remove hypercall registration mechanism, David Hildenbrand, 2024/12/18
- [PULL 15/15] s390x: virtio-mem support, David Hildenbrand, 2024/12/18
- [PULL 04/15] s390x/s390-virtio-hcall: prepare for more diag500 hypercalls, David Hildenbrand, 2024/12/18
- [PULL 06/15] s390x/s390-virtio-ccw: move setting the maximum guest size from sclp to machine code, David Hildenbrand, 2024/12/18
- [PULL 09/15] s390x/s390-stattrib-kvm: prepare for memory devices and sparse memory layouts, David Hildenbrand, 2024/12/18
- [PULL 07/15] s390x: introduce s390_get_memory_limit(), David Hildenbrand, 2024/12/18
- Re: [PULL 00/15] Host Memory Backends and Memory devices queue 2024-12-18, Stefan Hajnoczi, 2024/12/18