From: Wei Liu <wei.liu2@citrix.com>
To: minios-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: [PATCH MINI-OS] xenbus: notify the other end when necessary
Date: Mon, 26 Oct 2015 09:47:48 +0000 [thread overview]
Message-ID: <1445852868-16532-1-git-send-email-wei.liu2@citrix.com> (raw)
The xenbus thread didn't send notification to other end when it expected
more data or consumed responses, which led to stalling the ring from
time to time.
This is the culprit that guest was less responsive when using stubdom
because the device model was stalled.
Fix this by sending notification to the other end at the right places.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
Cc: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
With this path I can migrate a guest with stubdom a few thousand times
without any issue, while before I could easily trigger time out
within a few iterations. This should make OSSTest stubdom test case more
reliable.
Ian J, this is a patch suitable for backporting to 4.6. It's good time
to branch mini-os now.
---
xenbus/xenbus.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/xenbus/xenbus.c b/xenbus/xenbus.c
index 4613ed6..7451161 100644
--- a/xenbus/xenbus.c
+++ b/xenbus/xenbus.c
@@ -205,8 +205,10 @@ static void xenbus_thread_func(void *ign)
prod = xenstore_buf->rsp_prod;
DEBUG("Rsp_cons %d, rsp_prod %d.\n", xenstore_buf->rsp_cons,
xenstore_buf->rsp_prod);
- if (xenstore_buf->rsp_prod - xenstore_buf->rsp_cons < sizeof(msg))
+ if (xenstore_buf->rsp_prod - xenstore_buf->rsp_cons < sizeof(msg)) {
+ notify_remote_via_evtchn(start_info.store_evtchn);
break;
+ }
rmb();
memcpy_from_ring(xenstore_buf->rsp,
&msg,
@@ -217,8 +219,10 @@ static void xenbus_thread_func(void *ign)
xenstore_buf->rsp_prod - xenstore_buf->rsp_cons,
msg.req_id);
if (xenstore_buf->rsp_prod - xenstore_buf->rsp_cons <
- sizeof(msg) + msg.len)
+ sizeof(msg) + msg.len) {
+ notify_remote_via_evtchn(start_info.store_evtchn);
break;
+ }
DEBUG("Message is good.\n");
@@ -265,6 +269,9 @@ static void xenbus_thread_func(void *ign)
xenstore_buf->rsp_cons += msg.len + sizeof(msg);
wake_up(&req_info[msg.req_id].waitq);
}
+
+ wmb();
+ notify_remote_via_evtchn(start_info.store_evtchn);
}
}
}
--
2.1.4
next reply other threads:[~2015-10-26 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 9:47 Wei Liu [this message]
2015-10-26 12:02 ` [PATCH MINI-OS] xenbus: notify the other end when necessary Samuel Thibault
2015-10-26 12:14 ` Wei Liu
2015-10-26 12:21 ` Samuel Thibault
2015-10-26 12:30 ` Wei Liu
2015-10-26 12:33 ` Samuel Thibault
2015-10-26 12:36 ` [Minios-devel] " Wei Liu
2015-11-02 12:14 ` Ian Campbell
2015-11-02 15:00 ` Wei Liu
2015-11-02 15:08 ` Ian Campbell
2015-11-02 15:53 ` Wei Liu
2015-11-02 16:07 ` Ian Campbell
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=1445852868-16532-1-git-send-email-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=minios-devel@lists.xenproject.org \
--cc=samuel.thibault@ens-lyon.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).