From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Cornelia Huck <cohuck@redhat.com>,
David Hildenbrand <david@redhat.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] s390/kvm: implement clearing part of IPL clear
Date: Thu, 1 Mar 2018 04:58:44 +0100 [thread overview]
Message-ID: <79f7059b-f2d3-a758-6bb9-29433b31b313@redhat.com> (raw)
In-Reply-To: <20180228195320.165230-1-borntraeger@de.ibm.com>
On 28.02.2018 20:53, Christian Borntraeger wrote:
> When a guests reboots with diagnose 308 subcode 3 it requests the memory
> to be cleared. We did not do it so far. This does not only violate the
> architecture, it also misses the chance to free up that memory on
> reboot, which would help on host memory over commitment. By using
> ram_block_discard_range we can cover both cases.
Sounds like a good idea. I wonder whether that release_all_ram()
function should maybe rather reside in exec.c, so that other machines
that want to clear all RAM at reset time can use it, too?
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> target/s390x/kvm.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/target/s390x/kvm.c b/target/s390x/kvm.c
> index 8f3a422288..2e145ad5c3 100644
> --- a/target/s390x/kvm.c
> +++ b/target/s390x/kvm.c
> @@ -34,6 +34,8 @@
> #include "qapi/error.h"
> #include "qemu/error-report.h"
> #include "qemu/timer.h"
> +#include "qemu/rcu_queue.h"
> +#include "sysemu/cpus.h"
> #include "sysemu/sysemu.h"
> #include "sysemu/hw_accel.h"
> #include "hw/boards.h"
> @@ -41,6 +43,7 @@
> #include "sysemu/device_tree.h"
> #include "exec/gdbstub.h"
> #include "exec/address-spaces.h"
> +#include "exec/ram_addr.h"
> #include "trace.h"
> #include "qapi-event.h"
> #include "hw/s390x/s390-pci-inst.h"
> @@ -1841,6 +1844,14 @@ static int kvm_arch_handle_debug_exit(S390CPU *cpu)
> return ret;
> }
>
> +static void release_all_rams(void)
s/rams/ram/ maybe?
> +{
> + struct RAMBlock *rb;
> +
> + QLIST_FOREACH_RCU(rb, &ram_list.blocks, next)
> + ram_block_discard_range(rb, 0, rb->used_length);
>From a coding style point of view, I think there should be curly braces
around ram_block_discard_range() ?
> +}
> +
> int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)
> {
> S390CPU *cpu = S390_CPU(cs);
> @@ -1853,6 +1864,14 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)
> ret = handle_intercept(cpu);
> break;
> case KVM_EXIT_S390_RESET:
> + if (run->s390_reset_flags & KVM_S390_RESET_CLEAR) {
> + /*
> + * We will stop other CPUs anyway, avoid spurious crashes and
> + * get all CPUs out. The reset will take care of the resume.
> + */
> + pause_all_vcpus();
> + release_all_rams();
> + }
> s390_reipl_request();
> break;
> case KVM_EXIT_S390_TSCH:
>
Apart from the cosmetic nits, patch looks good to me.
Thomas
next prev parent reply other threads:[~2018-03-01 3:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 19:53 [Qemu-devel] [PATCH 1/1] s390/kvm: implement clearing part of IPL clear Christian Borntraeger
2018-03-01 3:58 ` Thomas Huth [this message]
2018-03-01 7:37 ` Christian Borntraeger
2018-03-01 8:44 ` Paolo Bonzini
2018-03-01 9:24 ` Dr. David Alan Gilbert
2018-03-01 11:00 ` Christian Borntraeger
2018-03-01 11:45 ` Dr. David Alan Gilbert
2018-03-01 12:08 ` Christian Borntraeger
2018-03-01 12:28 ` Dr. David Alan Gilbert
2018-03-01 12:35 ` Christian Borntraeger
2018-03-01 12:39 ` Christian Borntraeger
2018-03-01 12:58 ` Dr. David Alan Gilbert
2018-03-01 12:49 ` Dr. David Alan Gilbert
2018-03-01 9:21 ` David Hildenbrand
2018-03-05 12:54 ` Cornelia Huck
2018-03-05 13:04 ` Christian Borntraeger
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=79f7059b-f2d3-a758-6bb9-29433b31b313@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).