From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Jason J. Herne" <jjherne@us.ibm.com>,
afaerber@suse.de, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] s390: Storage key global access
Date: Thu, 06 Feb 2014 16:19:29 +0100 [thread overview]
Message-ID: <52F3A801.2030405@de.ibm.com> (raw)
In-Reply-To: <1390405693-15696-1-git-send-email-jjherne@us.ibm.com>
On 22/01/14 16:48, Jason J. Herne wrote:
> From: "Jason J. Herne" <jjherne@us.ibm.com>
>
> Introduces global access to storage key data so we can set it for each cpu in
> the S390 cpu initialization routine.
>
> Signed-off-by: Jason J. Herne <jjherne@us.ibm.com>
> ---
> hw/s390x/s390-virtio-ccw.c | 3 +--
> hw/s390x/s390-virtio.c | 6 +++---
> hw/s390x/s390-virtio.h | 2 +-
> target-s390x/cpu.h | 3 +++
> 4 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
> index 733d988..62319b9 100644
> --- a/hw/s390x/s390-virtio-ccw.c
> +++ b/hw/s390x/s390-virtio-ccw.c
> @@ -80,7 +80,6 @@ static void ccw_init(QEMUMachineInitArgs *args)
> MemoryRegion *sysmem = get_system_memory();
> MemoryRegion *ram = g_new(MemoryRegion, 1);
> int shift = 0;
> - uint8_t *storage_keys;
> int ret;
> VirtualCssBus *css_bus;
>
> @@ -112,7 +111,7 @@ static void ccw_init(QEMUMachineInitArgs *args)
> storage_keys = g_malloc0(my_ram_size / TARGET_PAGE_SIZE);
>
> /* init CPUs */
> - s390_init_cpus(args->cpu_model, storage_keys);
> + s390_init_cpus(args->cpu_model);
>
> if (kvm_enabled()) {
> kvm_s390_enable_css_support(s390_cpu_addr2state(0));
> diff --git a/hw/s390x/s390-virtio.c b/hw/s390x/s390-virtio.c
> index 7adf92a..804483f 100644
> --- a/hw/s390x/s390-virtio.c
> +++ b/hw/s390x/s390-virtio.c
> @@ -53,6 +53,7 @@
>
> static VirtIOS390Bus *s390_bus;
> static S390CPU **ipi_states;
> +uint8_t *storage_keys;
This would add another global variable. I am find with this right now
but somewhen in the future we might want to take care of storage keys
in regard to migration as well.
Could we add a container-device/memory? We could make it
a child of the machine then? Dont know if that will work out with
migration, though.
Christian
next prev parent reply other threads:[~2014-02-06 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 15:48 [Qemu-devel] [PATCH] s390: Storage key global access Jason J. Herne
2014-02-03 20:09 ` Jason J. Herne
2014-02-06 15:19 ` Christian Borntraeger [this message]
2014-02-25 14:34 ` Jason J. Herne
2014-02-25 19:15 ` Christian Borntraeger
2014-02-25 19:34 ` Andreas Färber
2014-02-25 21:17 ` Christian Borntraeger
2014-02-26 14:57 ` Jason J. Herne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F3A801.2030405@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=jjherne@us.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.