From: Paolo Bonzini <pbonzini@redhat.com>
To: Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [RFC for-2.7] block: keep AioContext pointer in BlockBackend
Date: Tue, 17 May 2016 13:37:29 +0200 [thread overview]
Message-ID: <573B0279.9030205@redhat.com> (raw)
In-Reply-To: <214ef2a3-8d51-9570-1be5-fff12a58231a@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
On 17/05/2016 13:14, Max Reitz wrote:
>> That could be another BdrvChild member, couldn't it?
>
> I think it would rather require a new function pointer in
> BdrvChildRole (after Kevin's series, that is).
Yes, that's what I meant. :)
Paolo
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-05-17 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 14:14 [Qemu-devel] [RFC for-2.7] block: keep AioContext pointer in BlockBackend Stefan Hajnoczi
2016-05-09 16:48 ` Paolo Bonzini
2016-05-10 9:33 ` Stefan Hajnoczi
2016-05-10 10:38 ` Paolo Bonzini
2016-05-11 13:24 ` Stefan Hajnoczi
2016-05-17 10:52 ` Max Reitz
2016-05-17 11:07 ` Paolo Bonzini
2016-05-17 11:14 ` Max Reitz
2016-05-17 11:37 ` Paolo Bonzini [this message]
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=573B0279.9030205@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).