[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v1 09/14] s390x/s390-skeys: prepare for memory devices
From: |
David Hildenbrand |
Subject: |
[PATCH v1 09/14] s390x/s390-skeys: prepare for memory devices |
Date: |
Tue, 10 Sep 2024 19:58:04 +0200 |
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.
Signed-off-by: David Hildenbrand <david@redhat.com>
---
hw/s390x/s390-skeys.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/hw/s390x/s390-skeys.c b/hw/s390x/s390-skeys.c
index bf22d6863e..8716c2e73e 100644
--- a/hw/s390x/s390-skeys.c
+++ b/hw/s390x/s390-skeys.c
@@ -251,9 +251,7 @@ 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());
-
- skeys->key_count = machine->ram_size / TARGET_PAGE_SIZE;
+ skeys->key_count = s390_get_memory_limit() / TARGET_PAGE_SIZE;
skeys->keydata = g_malloc0(skeys->key_count);
g_once_init_leave(&initialized, 1);
}
--
2.46.0
- Re: [PATCH v1 06/14] s390x: introduce s390_get_memory_limit(), (continued)
- [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, David Hildenbrand, 2024/09/10
- Re: [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, Thomas Huth, 2024/09/12
- Re: [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, Janosch Frank, 2024/09/12
- Re: [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, Halil Pasic, 2024/09/27
- Re: [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, David Hildenbrand, 2024/09/27
- Re: [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, Christian Borntraeger, 2024/09/30
- Re: [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, Halil Pasic, 2024/09/30
- Re: [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT, David Hildenbrand, 2024/09/30
[PATCH v1 08/14] s390x/s390-stattrib-kvm: prepare memory devices and sparse memory layouts, David Hildenbrand, 2024/09/10
[PATCH v1 09/14] s390x/s390-skeys: prepare for memory devices,
David Hildenbrand <=
[PATCH v1 10/14] s390x/pv: check initial, not maximum RAM size, David Hildenbrand, 2024/09/10
- Re: [PATCH v1 10/14] s390x/pv: check initial, not maximum RAM size, Nina Schoetterl-Glausch, 2024/09/24
- Re: [PATCH v1 10/14] s390x/pv: check initial, not maximum RAM size, David Hildenbrand, 2024/09/24
- Re: [PATCH v1 10/14] s390x/pv: check initial, not maximum RAM size, David Hildenbrand, 2024/09/26
- Re: [PATCH v1 10/14] s390x/pv: check initial, not maximum RAM size, Christian Borntraeger, 2024/09/30
- Re: [PATCH v1 10/14] s390x/pv: check initial, not maximum RAM size, Claudio Imbrenda, 2024/09/30
- Re: [PATCH v1 10/14] s390x/pv: check initial, not maximum RAM size, David Hildenbrand, 2024/09/30
- Re: [PATCH v1 10/14] s390x/pv: check initial, not maximum RAM size, Claudio Imbrenda, 2024/09/30
[PATCH v1 11/14] s390x/s390-virtio-ccw: prepare for memory devices, David Hildenbrand, 2024/09/10
[PATCH v1 12/14] s390x: introduce s390_get_max_pagesize(), David Hildenbrand, 2024/09/10