From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Marcel Apfelbaum" <marcel.a@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Michael S.\ Tsirkin" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Slutz, Donald Christopher" <dslutz@verizon.com>,
"Alexander Graf" <agraf@suse.de>,
"Anthony Liguori" <aliguori@amazon.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH 1/1] xen-hvm.c: Add support for Xen access to vmport
Date: Wed, 1 Oct 2014 15:44:06 +0100 [thread overview]
Message-ID: <1412174646.4861.38.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410011011030.17038@kaball.uk.xensource.com>
On Wed, 2014-10-01 at 10:20 +0100, Stefano Stabellini wrote:
> I wonder if we could send both ioreqs at once from Xen and back from
> QEMU. Or maybe append the registers to IOREQ_TYPE_VMWARE_PORT, changing
> the size of ioreq_t only for this ioreq type.
Random idea: Why new add a IOREQ_TYPE_FULL_STATE which would be issued
for these ports and let qemu decode the fact that it is vmware
internally? That might be a more generically useful interface in the
future?
WRT to fitting all the register state in the current sized request, you
could declare that this new thing takes multiple slots.
Also, I may be wrong, but I thought most IOREQs were synchronous so only
one slot was ever used? The buffered ioreq stuff has a separate ring (or
uses a different part of the page, or something). I might be talking
nonsense here though ;-)
Ian.
next prev parent reply other threads:[~2014-10-01 14:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 18:47 [Qemu-devel] [PATCH 0/1] Add support for Xen access to vmport Don Slutz
2014-09-26 18:47 ` [Qemu-devel] [PATCH 1/1] xen-hvm.c: " Don Slutz
2014-09-29 8:12 ` Alexander Graf
2014-09-29 11:10 ` Paolo Bonzini
2014-09-29 11:53 ` Alexander Graf
2014-09-29 12:21 ` Paolo Bonzini
2014-09-29 12:57 ` Alexander Graf
2014-09-29 13:14 ` Paolo Bonzini
2014-09-30 1:05 ` Don Slutz
2014-09-30 8:14 ` Paolo Bonzini
2014-09-30 1:00 ` Don Slutz
2014-09-29 10:15 ` Stefano Stabellini
2014-09-29 10:25 ` Stefano Stabellini
2014-09-30 0:32 ` Don Slutz
2014-09-30 10:35 ` Stefano Stabellini
2014-10-01 5:21 ` Slutz, Donald Christopher
2014-10-01 9:20 ` Stefano Stabellini
2014-10-01 12:33 ` Don Slutz
2014-10-01 14:44 ` Ian Campbell [this message]
2014-10-01 16:01 ` [Qemu-devel] [Xen-devel] " Anthony Liguori
2014-10-01 15:08 ` [Qemu-devel] " Paul Durrant
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=1412174646.4861.38.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=dslutz@verizon.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).