From: Paolo Bonzini <pbonzini@redhat.com>
To: Emanuele Giuseppe Esposito <eesposit@redhat.com>, qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Yanan Wang" <wangyanan55@huawei.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH v2 1/3] accel: introduce accelerator blocker API
Date: Fri, 11 Nov 2022 11:48:27 +0100 [thread overview]
Message-ID: <9e6288e1-0c51-bd3f-5cee-c71049ffa684@redhat.com> (raw)
In-Reply-To: <20221110164807.1306076-2-eesposit@redhat.com>
On 11/10/22 17:48, Emanuele Giuseppe Esposito wrote:
> +/*
> + * QEMU accel blocker class
"Lock to inhibit accelerator ioctls"
> + *
> + * Copyright (c) 2014 Red Hat Inc.
2022, you can also add an Author line.
> +static int accel_in_ioctls(void)
Return bool (and return early if ret becomes true).
> +void accel_ioctl_inhibit_begin(void)
> +{
> + CPUState *cpu;
> +
> + /*
> + * We allow to inhibit only when holding the BQL, so we can identify
> + * when an inhibitor wants to issue an ioctl easily.
> + */
> + g_assert(qemu_mutex_iothread_locked());
> +
> + /* Block further invocations of the ioctls outside the BQL. */
> + CPU_FOREACH(cpu) {
> + qemu_lockcnt_lock(&cpu->in_ioctl_lock);
> + }
> + qemu_lockcnt_lock(&accel_in_ioctl_lock);
> +
> + /* Keep waiting until there are running ioctls */
> + while (accel_in_ioctls()) {
> + /* Reset event to FREE. */
> + qemu_event_reset(&accel_in_ioctl_event);
> +
> + if (accel_in_ioctls()) {
> +
> + CPU_FOREACH(cpu) {
> + /* exit the ioctl */
> + qemu_cpu_kick(cpu);
Only kick if the lockcnt count is > 0? (this is not racy; if it is == 0,
it cannot ever become > 0 again while the lock is taken)
> diff --git a/include/sysemu/accel-blocker.h b/include/sysemu/accel-blocker.h
> new file mode 100644
> index 0000000000..135ebea566
> --- /dev/null
> +++ b/include/sysemu/accel-blocker.h
> @@ -0,0 +1,45 @@
> +/*
> + * Accelerator blocking API, to prevent new ioctls from starting and wait the
> + * running ones finish.
> + * This mechanism differs from pause/resume_all_vcpus() in that it does not
> + * release the BQL.
> + *
> + * Copyright (c) 2014 Red Hat Inc.
2022, you can also add an Author line here too.
> + * This work is licensed under the terms of the GNU GPL, version 2 or later.
> + * See the COPYING file in the top-level directory.
> + */
> +#ifndef ACCEL_BLOCKER_H
> +#define ACCEL_BLOCKER_H
> +
> +#include "qemu/osdep.h"
> +#include "qemu/accel.h"
qemu/accel.h not needed?
> +#include "sysemu/cpus.h"
> +
> +extern void accel_blocker_init(void);
> +
> +/*
> + * accel_set_in_ioctl/accel_cpu_set_in_ioctl:
> + * Mark when ioctl is about to run or just finished.
> + * If @in_ioctl is true, then mark it is beginning. Otherwise marks that it is
> + * ending.
> + *
> + * These functions will block after accel_ioctl_inhibit_begin() is called,
> + * preventing new ioctls to run. They will continue only after
> + * accel_ioctl_inibith_end().
> + */
> +extern void accel_set_in_ioctl(bool in_ioctl);
> +extern void accel_cpu_set_in_ioctl(CPUState *cpu, bool in_ioctl);
Why not just
extern void accel_ioctl_begin(void);
extern void accel_ioctl_end(void);
extern void accel_cpu_ioctl_begin(CPUState *cpu);
extern void accel_cpu_ioctl_end(CPUState *cpu);
?
Otherwise it's very nice.
Paolo
next prev parent reply other threads:[~2022-11-11 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 16:48 [PATCH v2 0/3] KVM: allow listener to stop all vcpus before Emanuele Giuseppe Esposito
2022-11-10 16:48 ` [PATCH v2 1/3] accel: introduce accelerator blocker API Emanuele Giuseppe Esposito
2022-11-11 10:48 ` Paolo Bonzini [this message]
2022-11-11 14:52 ` Emanuele Giuseppe Esposito
2022-11-10 16:48 ` [PATCH v2 2/3] KVM: keep track of running ioctls Emanuele Giuseppe Esposito
2022-11-11 10:49 ` Paolo Bonzini
2022-11-10 16:48 ` [PATCH v2 3/3] kvm: Atomic memslot updates Emanuele Giuseppe Esposito
2022-11-11 11:01 ` Paolo Bonzini
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=9e6288e1-0c51-bd3f-5cee-c71049ffa684@redhat.com \
--to=pbonzini@redhat.com \
--cc=eduardo@habkost.net \
--cc=eesposit@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wangyanan55@huawei.com \
/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).