From: Anthony PERARD <anthony.perard@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Qemu-devel] [PATCH 1/3] xen-bus: use a separate fd for each event channel
Date: Wed, 10 Apr 2019 12:37:42 +0100 [thread overview]
Message-ID: <20190410113742.GD1435@perard.uk.xensource.com> (raw)
In-Reply-To: <20190408151617.13025-2-paul.durrant@citrix.com>
On Mon, Apr 08, 2019 at 04:16:15PM +0100, Paul Durrant wrote:
> To better support use of IOThread-s it will be necessary to be able to set
> the AioContext for each XenEventChannel and hence it is necessary to open a
> separate handle to libxenevtchan for each channel.
>
> This patch stops using NotifierList for event channel callbacks, replacing
> that construct by a list of complete XenEventChannel structures. Each of
> these now has a xenevtchn_handle pointer in place of the single pointer
> previously held in the XenDevice structure. The individual handles are
> opened/closed in xen_device_bind/unbind_event_channel(), replacing the
> single open/close in xen_device_realize/unrealize().
>
> NOTE: This patch does not add an AioContext parameter to
> xen_device_bind_event_channel(). That will be done in a subsequent
> patch.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
There are a few places were I would have like to add an assert, but they
can't be compiled-out in QEMU :-(.
Thanks,
--
Anthony PERARD
WARNING: multiple messages have this Message-ID (diff)
From: Anthony PERARD <anthony.perard@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] xen-bus: use a separate fd for each event channel
Date: Wed, 10 Apr 2019 12:37:42 +0100 [thread overview]
Message-ID: <20190410113742.GD1435@perard.uk.xensource.com> (raw)
Message-ID: <20190410113742.4_QfOJv9ExZZvnX62o1nwD1L8U06cUKKKRhCSvkMR8I@z> (raw)
In-Reply-To: <20190408151617.13025-2-paul.durrant@citrix.com>
On Mon, Apr 08, 2019 at 04:16:15PM +0100, Paul Durrant wrote:
> To better support use of IOThread-s it will be necessary to be able to set
> the AioContext for each XenEventChannel and hence it is necessary to open a
> separate handle to libxenevtchan for each channel.
>
> This patch stops using NotifierList for event channel callbacks, replacing
> that construct by a list of complete XenEventChannel structures. Each of
> these now has a xenevtchn_handle pointer in place of the single pointer
> previously held in the XenDevice structure. The individual handles are
> opened/closed in xen_device_bind/unbind_event_channel(), replacing the
> single open/close in xen_device_realize/unrealize().
>
> NOTE: This patch does not add an AioContext parameter to
> xen_device_bind_event_channel(). That will be done in a subsequent
> patch.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
There are a few places were I would have like to add an assert, but they
can't be compiled-out in QEMU :-(.
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2019-04-10 11:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 15:16 [Qemu-devel] [PATCH 0/3] Support IOThread polling for PV shared rings Paul Durrant
2019-04-08 15:16 ` Paul Durrant
2019-04-08 15:16 ` [Qemu-devel] [PATCH 1/3] xen-bus: use a separate fd for each event channel Paul Durrant
2019-04-08 15:16 ` Paul Durrant
2019-04-10 11:37 ` Anthony PERARD [this message]
2019-04-10 11:37 ` Anthony PERARD
2019-04-08 15:16 ` [Qemu-devel] [PATCH 2/3] xen-bus: allow AioContext to be specified " Paul Durrant
2019-04-08 15:16 ` Paul Durrant
2019-04-10 12:57 ` Anthony PERARD
2019-04-10 12:57 ` Anthony PERARD
2019-04-10 15:20 ` Paul Durrant
2019-04-10 15:20 ` Paul Durrant
2019-04-10 15:22 ` Anthony PERARD
2019-04-10 15:22 ` Anthony PERARD
2019-04-10 15:56 ` Paul Durrant
2019-04-10 15:56 ` Paul Durrant
2019-04-15 8:42 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2019-04-15 8:42 ` Stefan Hajnoczi
2019-04-16 9:36 ` Paul Durrant
2019-04-16 9:36 ` Paul Durrant
2019-04-08 15:16 ` [Qemu-devel] [PATCH 3/3] xen-bus / xen-block: add support for event channel polling Paul Durrant
2019-04-08 15:16 ` Paul Durrant
2019-04-10 15:09 ` Anthony PERARD
2019-04-10 15:09 ` Anthony PERARD
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=20190410113742.GD1435@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=paul.durrant@citrix.com \
--cc=qemu-block@nongnu.org \
--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).