From: "Jan Beulich" <JBeulich@suse.com> To: qemu-devel@nongnu.org Cc: anthony.perard@citrix.com, Paul Durrant <paul.durrant@citrix.com>, Stefano Stabellini <sstabellini@kernel.org>, xen-devel <xen-devel@lists.xenproject.org> Subject: [Qemu-devel] [PATCH v2 3/3] xen: ignore direction in bufioreq handling Date: Fri, 25 Nov 2016 03:06:58 -0700 [thread overview] Message-ID: <58381B520200007800122271@prv-mh.provo.novell.com> (raw) In-Reply-To: <583819ED020000780012225B@prv-mh.provo.novell.com> There's no way to communicate back read data, so only writes can ever be usefully specified. Ignore the field, paving the road for eventually re-using the bit for something else in a few (many?) years time. Signed-off-by: Jan Beulich <jbeulich@suse.com> Reviewed-by: Paul Durrant <paul.durrant@citrix.com> Acked-by: Stefano Stabellini <sstabellini@kernel.org> --- a/xen-hvm.c +++ b/xen-hvm.c @@ -997,6 +997,7 @@ static int handle_buffered_iopage(XenIOS memset(&req, 0x00, sizeof(req)); req.state = STATE_IOREQ_READY; req.count = 1; + req.dir = IOREQ_WRITE; for (;;) { uint32_t rdptr = buf_page->read_pointer, wrptr; @@ -1014,7 +1015,6 @@ static int handle_buffered_iopage(XenIOS req.size = 1U << buf_req->size; req.addr = buf_req->addr; req.data = buf_req->data; - req.dir = buf_req->dir; req.type = buf_req->type; xen_rmb(); qw = (req.size == 8); @@ -1031,10 +1031,12 @@ static int handle_buffered_iopage(XenIOS handle_ioreq(state, &req); /* Only req.data may get updated by handle_ioreq(), albeit even that - * should not happen as such data would never make it to the guest. + * should not happen as such data would never make it to the guest (we + * can only usefully see writes here after all). */ assert(req.state == STATE_IOREQ_READY); assert(req.count == 1); + assert(req.dir == IOREQ_WRITE); assert(!req.data_is_ptr); atomic_add(&buf_page->read_pointer, qw + 1);
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com> To: qemu-devel@nongnu.org Cc: anthony.perard@citrix.com, xen-devel <xen-devel@lists.xenproject.org>, Paul Durrant <paul.durrant@citrix.com>, Stefano Stabellini <sstabellini@kernel.org> Subject: [PATCH v2 3/3] xen: ignore direction in bufioreq handling Date: Fri, 25 Nov 2016 03:06:58 -0700 [thread overview] Message-ID: <58381B520200007800122271@prv-mh.provo.novell.com> (raw) In-Reply-To: <583819ED020000780012225B@prv-mh.provo.novell.com> There's no way to communicate back read data, so only writes can ever be usefully specified. Ignore the field, paving the road for eventually re-using the bit for something else in a few (many?) years time. Signed-off-by: Jan Beulich <jbeulich@suse.com> Reviewed-by: Paul Durrant <paul.durrant@citrix.com> Acked-by: Stefano Stabellini <sstabellini@kernel.org> --- a/xen-hvm.c +++ b/xen-hvm.c @@ -997,6 +997,7 @@ static int handle_buffered_iopage(XenIOS memset(&req, 0x00, sizeof(req)); req.state = STATE_IOREQ_READY; req.count = 1; + req.dir = IOREQ_WRITE; for (;;) { uint32_t rdptr = buf_page->read_pointer, wrptr; @@ -1014,7 +1015,6 @@ static int handle_buffered_iopage(XenIOS req.size = 1U << buf_req->size; req.addr = buf_req->addr; req.data = buf_req->data; - req.dir = buf_req->dir; req.type = buf_req->type; xen_rmb(); qw = (req.size == 8); @@ -1031,10 +1031,12 @@ static int handle_buffered_iopage(XenIOS handle_ioreq(state, &req); /* Only req.data may get updated by handle_ioreq(), albeit even that - * should not happen as such data would never make it to the guest. + * should not happen as such data would never make it to the guest (we + * can only usefully see writes here after all). */ assert(req.state == STATE_IOREQ_READY); assert(req.count == 1); + assert(req.dir == IOREQ_WRITE); assert(!req.data_is_ptr); atomic_add(&buf_page->read_pointer, qw + 1); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-25 10:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-11-25 10:01 [Qemu-devel] [PATCH v2 0/3] xen: XSA-197 follow-ups Jan Beulich 2016-11-25 10:05 ` [Qemu-devel] [PATCH v2 1/3] xen: fix quad word bufioreq handling Jan Beulich 2016-11-25 10:08 ` Paul Durrant 2016-11-25 10:08 ` Paul Durrant 2016-11-28 19:21 ` Stefano Stabellini 2016-11-28 19:21 ` [Qemu-devel] " Stefano Stabellini 2016-11-25 10:05 ` Jan Beulich 2016-11-25 10:06 ` [Qemu-devel] [PATCH v2 2/3] xen: slightly simplify " Jan Beulich 2016-11-25 10:06 ` Jan Beulich 2016-11-28 19:24 ` Stefano Stabellini 2016-11-28 19:24 ` [Qemu-devel] " Stefano Stabellini 2016-11-25 10:06 ` Jan Beulich [this message] 2016-11-25 10:06 ` [PATCH v2 3/3] xen: ignore direction in " Jan Beulich 2016-11-25 11:06 ` [PATCH v2 0/3] xen: XSA-197 follow-ups Jan Beulich
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=58381B520200007800122271@prv-mh.provo.novell.com \ --to=jbeulich@suse.com \ --cc=anthony.perard@citrix.com \ --cc=paul.durrant@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: linkBe 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.