From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] 9pfs: suppress performance warnings on qtest runs
Date: Mon, 19 Oct 2020 13:48:22 +0200 [thread overview]
Message-ID: <20201019134822.047db0fc@bahia.lan> (raw)
In-Reply-To: <a2d2ff2163f8853ea782a7a1d4e6f2afd7c29ffe.1603106145.git.qemu_oss@crudebyte.com>
On Mon, 19 Oct 2020 13:10:18 +0200
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> Don't trigger any performance warning if we're just running test cases,
> because tests intentionally run for edge cases.
>
> So far performance warnings were suppressed for the 'synth' fs driver
> backend only. This patch suppresses them for all 9p fs driver backends.
>
> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> ---
LGTM
Reviewed-by: Greg Kurz <groug@kaod.org>
> hw/9pfs/9p-synth.c | 2 --
> hw/9pfs/virtio-9p-device.c | 6 ++++++
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/hw/9pfs/9p-synth.c b/hw/9pfs/9p-synth.c
> index cec8c0eefc..7eb210ffa8 100644
> --- a/hw/9pfs/9p-synth.c
> +++ b/hw/9pfs/9p-synth.c
> @@ -541,8 +541,6 @@ static int synth_init(FsContext *ctx, Error **errp)
> QLIST_INIT(&synth_root.child);
> qemu_mutex_init(&synth_mutex);
>
> - ctx->export_flags |= V9FS_NO_PERF_WARN;
> -
> /* Add "." and ".." entries for root */
> v9fs_add_dir_node(&synth_root, synth_root.attr->mode,
> "..", synth_root.attr, synth_root.attr->inode);
> diff --git a/hw/9pfs/virtio-9p-device.c b/hw/9pfs/virtio-9p-device.c
> index 36f3aa9352..14371a78ef 100644
> --- a/hw/9pfs/virtio-9p-device.c
> +++ b/hw/9pfs/virtio-9p-device.c
> @@ -21,6 +21,7 @@
> #include "hw/virtio/virtio-access.h"
> #include "qemu/iov.h"
> #include "qemu/module.h"
> +#include "sysemu/qtest.h"
>
> static void virtio_9p_push_and_notify(V9fsPDU *pdu)
> {
> @@ -199,6 +200,11 @@ static void virtio_9p_device_realize(DeviceState *dev, Error **errp)
> VirtIODevice *vdev = VIRTIO_DEVICE(dev);
> V9fsVirtioState *v = VIRTIO_9P(dev);
> V9fsState *s = &v->state;
> + FsDriverEntry *fse = get_fsdev_fsentry(s->fsconf.fsdev_id);
> +
> + if (qtest_enabled() && fse) {
> + fse->export_flags |= V9FS_NO_PERF_WARN;
> + }
>
> if (v9fs_device_realize_common(s, &virtio_9p_transport, errp)) {
> return;
next prev parent reply other threads:[~2020-10-19 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 11:10 [PATCH 1/1] 9pfs: suppress performance warnings on qtest runs Christian Schoenebeck
2020-10-19 11:48 ` Greg Kurz [this message]
2020-10-19 12:12 ` Christian Schoenebeck
2020-10-19 12:38 ` Greg Kurz
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=20201019134822.047db0fc@bahia.lan \
--to=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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).