From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Paul Durrant <paul@xen.org>, George Dunlap <george.dunlap@citrix.com>
Subject: [PATCH v2 1/2] IOREQ: fix waiting for broadcast completion
Date: Tue, 2 Feb 2021 16:14:14 +0100 [thread overview]
Message-ID: <3365a9a1-92c0-8917-1632-b88f1c055392@suse.com> (raw)
In-Reply-To: <0e7265fe-8d89-facb-790d-9232c742c3fa@suse.com>
Checking just a single server is not enough - all of them must have
signaled that they're done processing the request.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
---
v2: New.
--- a/xen/common/ioreq.c
+++ b/xen/common/ioreq.c
@@ -213,9 +213,9 @@ bool vcpu_ioreq_handle_completion(struct
return false;
}
- sv = get_pending_vcpu(v, &s);
- if ( sv && !wait_for_io(sv, get_ioreq(s, v)) )
- return false;
+ while ( (sv = get_pending_vcpu(v, &s)) != NULL )
+ if ( !wait_for_io(sv, get_ioreq(s, v)) )
+ return false;
vio->req.state = ioreq_needs_completion(&vio->req) ?
STATE_IORESP_READY : STATE_IOREQ_NONE;
next prev parent reply other threads:[~2021-02-02 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 15:13 [PATCH v2 0/2] IOREQ: mapcache invalidation request sending corrections Jan Beulich
2021-02-02 15:14 ` Jan Beulich [this message]
2021-02-04 8:45 ` [PATCH v2 1/2] IOREQ: fix waiting for broadcast completion Paul Durrant
2021-02-02 15:14 ` [PATCH v2 2/2] IOREQ: refine when to send mapcache invalidation request Jan Beulich
2021-02-04 9:26 ` Paul Durrant
2021-02-04 11:24 ` Jan Beulich
2021-02-17 8:30 ` Ping: " Jan Beulich
2021-02-17 9:41 ` Paul Durrant
2021-02-17 10:02 ` Jan Beulich
2021-02-17 10:58 ` Julien Grall
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=3365a9a1-92c0-8917-1632-b88f1c055392@suse.com \
--to=jbeulich@suse.com \
--cc=george.dunlap@citrix.com \
--cc=paul@xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.