From: Thomas Huth <thuth@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, qemu-devel@nongnu.org
Cc: cohuck@redhat.com, borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
mihajlov@linux.ibm.com, david@redhat.com
Subject: Re: [PATCH v2 2/3] s390x: Add missing vcpu reset functions
Date: Mon, 2 Dec 2019 15:28:30 +0100 [thread overview]
Message-ID: <da71ec1a-7c3f-4032-0627-11252bd17e27@redhat.com> (raw)
In-Reply-To: <20191202140146.3910-3-frankja@linux.ibm.com>
On 02/12/2019 15.01, Janosch Frank wrote:
> Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach
> for the initial reset, which was also called for the clear reset. To
> be architecture compliant, we also need to clear local interrupts on a
> normal reset.
>
> Because of this and the upcoming protvirt support we need to add
> ioctls for the missing clear and normal resets.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
[...]
> @@ -403,20 +405,44 @@ int kvm_arch_destroy_vcpu(CPUState *cs)
> return 0;
> }
>
> -void kvm_s390_reset_vcpu(S390CPU *cpu)
> +static void kvm_s390_reset_vcpu(S390CPU *cpu, unsigned long type)
> {
> CPUState *cs = CPU(cpu);
>
> - /* The initial reset call is needed here to reset in-kernel
> - * vcpu data that we can't access directly from QEMU
> - * (i.e. with older kernels which don't support sync_regs/ONE_REG).
> - * Before this ioctl cpu_synchronize_state() is called in common kvm
> - * code (kvm-all) */
> - if (kvm_vcpu_ioctl(cs, KVM_S390_INITIAL_RESET, NULL)) {
> - error_report("Initial CPU reset failed on CPU %i", cs->cpu_index);
> + /*
> + * The reset call is needed here to reset in-kernel vcpu data that
> + * we can't access directly from QEMU (i.e. with older kernels
> + * which don't support sync_regs/ONE_REG). Before this ioctl
> + * cpu_synchronize_state() is called in common kvm code
> + * (kvm-all).
> + */
> + if (kvm_vcpu_ioctl(cs, type)) {
> + error_report("CPU reset failed on CPU %i", cs->cpu_index);
In case you respin, maybe also print the "type" variable here?
> }
> }
>
> +void kvm_s390_reset_vcpu_initial(S390CPU *cpu)
> +{
> + kvm_s390_reset_vcpu(cpu, KVM_S390_INITIAL_RESET);
> +}
> +
> +void kvm_s390_reset_vcpu_clear(S390CPU *cpu)
> +{
> + if (!cap_vcpu_resets) {
> + kvm_s390_reset_vcpu(cpu, KVM_S390_INITIAL_RESET);
> + } else {
> + kvm_s390_reset_vcpu(cpu, KVM_S390_CLEAR_RESET);
> + }
Cosmetic nit: It's a tiny bit nicer the other way round:
if (cap_vcpu_resets) {
kvm_s390_reset_vcpu(cpu, KVM_S390_CLEAR_RESET);
} else {
kvm_s390_reset_vcpu(cpu, KVM_S390_INITIAL_RESET);
}
Anyway,
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2019-12-02 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 14:01 [PATCH v2 0/3] s390x: Increase architectural compliance Janosch Frank
2019-12-02 14:01 ` [PATCH v2 1/3] Header sync Janosch Frank
2019-12-02 14:01 ` [PATCH v2 2/3] s390x: Add missing vcpu reset functions Janosch Frank
2019-12-02 14:22 ` David Hildenbrand
2019-12-02 14:28 ` Thomas Huth [this message]
2019-12-02 14:48 ` [PATCH v3] " Janosch Frank
2019-12-02 15:46 ` [PATCH v2 2/3] " Cornelia Huck
2019-12-03 13:03 ` Janosch Frank
2019-12-02 14:01 ` [PATCH v2 3/3] s390x: Fix cpu normal reset ri clearing Janosch Frank
2019-12-03 10:07 ` Christian Borntraeger
2019-12-03 10:21 ` David Hildenbrand
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=da71ec1a-7c3f-4032-0627-11252bd17e27@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=mihajlov@linux.ibm.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).