From: Paul Durrant <Paul.Durrant@citrix.com>
To: Anthony Perard <anthony.perard@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Xen-devel] [PATCH v2 2/2] xen-bus: Avoid rewriting identical values to xenstore
Date: Tue, 27 Aug 2019 09:46:15 +0000 [thread overview]
Message-ID: <322ae907c2594237bdc7b63a24f63bab@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20190823101534.465-3-anthony.perard@citrix.com>
> -----Original Message-----
> From: Anthony PERARD <anthony.perard@citrix.com>
> Sent: 23 August 2019 11:16
> To: qemu-devel@nongnu.org
> Cc: Anthony Perard <anthony.perard@citrix.com>; Stefano Stabellini <sstabellini@kernel.org>; Paul
> Durrant <Paul.Durrant@citrix.com>; xen-devel@lists.xenproject.org
> Subject: [PATCH v2 2/2] xen-bus: Avoid rewriting identical values to xenstore
>
> When QEMU receives a xenstore watch event suggesting that the "state"
> of the frontend changed, it records this in its own state but it also
> re-write the value back into xenstore even so there were no change.
> This triggers an unnecessary xenstore watch event which QEMU will
> process again (and maybe the frontend as well). Also QEMU could
> potentially write an already old value.
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Reviewed-by: Paul Durrant <paul.durrant@citrix.com>
> ---
>
> Notes:
> v2:
> - fix coding style
> - only change frontend_set_state() and use 'publish' instead of 'export'.
>
> hw/xen/xen-bus.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/hw/xen/xen-bus.c b/hw/xen/xen-bus.c
> index 62c127b926..a04478ad4f 100644
> --- a/hw/xen/xen-bus.c
> +++ b/hw/xen/xen-bus.c
> @@ -698,7 +698,8 @@ int xen_device_frontend_scanf(XenDevice *xendev, const char *key,
> }
>
> static void xen_device_frontend_set_state(XenDevice *xendev,
> - enum xenbus_state state)
> + enum xenbus_state state,
> + bool publish)
> {
> const char *type = object_get_typename(OBJECT(xendev));
>
> @@ -710,7 +711,9 @@ static void xen_device_frontend_set_state(XenDevice *xendev,
> xs_strstate(state));
>
> xendev->frontend_state = state;
> - xen_device_frontend_printf(xendev, "state", "%u", state);
> + if (publish) {
> + xen_device_frontend_printf(xendev, "state", "%u", state);
> + }
> }
>
> static void xen_device_frontend_changed(void *opaque)
> @@ -726,7 +729,7 @@ static void xen_device_frontend_changed(void *opaque)
> state = XenbusStateUnknown;
> }
>
> - xen_device_frontend_set_state(xendev, state);
> + xen_device_frontend_set_state(xendev, state, false);
>
> if (state == XenbusStateInitialising &&
> xendev->backend_state == XenbusStateClosed &&
> @@ -1169,7 +1172,7 @@ static void xen_device_realize(DeviceState *dev, Error **errp)
> xen_device_frontend_printf(xendev, "backend-id", "%u",
> xenbus->backend_id);
>
> - xen_device_frontend_set_state(xendev, XenbusStateInitialising);
> + xen_device_frontend_set_state(xendev, XenbusStateInitialising, true);
>
> xendev->exit.notify = xen_device_exit;
> qemu_add_exit_notifier(&xendev->exit);
> --
> Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-08-27 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190823101534.465-1-anthony.perard@citrix.com>
2019-08-23 10:15 ` [Xen-devel] [PATCH v2 1/2] xen-bus: Fix backend state transition on device reset Anthony PERARD
2019-08-27 9:44 ` Paul Durrant
2019-08-23 10:15 ` [Xen-devel] [PATCH v2 2/2] xen-bus: Avoid rewriting identical values to xenstore Anthony PERARD
2019-08-27 9:46 ` Paul Durrant [this message]
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=322ae907c2594237bdc7b63a24f63bab@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).