From: Eric Blake <eblake@redhat.com>
To: quintela@redhat.com
Cc: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday, July 3rd
Date: Mon, 02 Jul 2012 11:33:49 -0600 [thread overview]
Message-ID: <4FF1DB7D.1000006@redhat.com> (raw)
In-Reply-To: <874npqwjqe.fsf@elfo.mitica>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On 07/02/2012 04:16 AM, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.
Can we discuss the future of 'getfd', the possibility of 'pass-fd', or
even the enhancement of all existing monitor commands to take an
optional 'nfds' JSON argument for atomic management of fd passing?
Which commands need to reopen a file with different access, and do we
bite the bullet to special case all of those commands to allow fd
passing or can we make qemu_open() coupled with high-level fd passing
generic enough to satisfy all of our reopen needs?
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <eblake@redhat.com>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday, July 3rd
Date: Mon, 02 Jul 2012 11:33:49 -0600 [thread overview]
Message-ID: <4FF1DB7D.1000006@redhat.com> (raw)
In-Reply-To: <874npqwjqe.fsf@elfo.mitica>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On 07/02/2012 04:16 AM, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.
Can we discuss the future of 'getfd', the possibility of 'pass-fd', or
even the enhancement of all existing monitor commands to take an
optional 'nfds' JSON argument for atomic management of fd passing?
Which commands need to reopen a file with different access, and do we
bite the bullet to special case all of those commands to allow fd
passing or can we make qemu_open() coupled with high-level fd passing
generic enough to satisfy all of our reopen needs?
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2012-07-02 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 10:16 KVM call agenda for Tuesday, July 3rd Juan Quintela
2012-07-02 10:16 ` [Qemu-devel] " Juan Quintela
2012-07-02 17:33 ` Eric Blake [this message]
2012-07-02 17:33 ` Eric Blake
2012-07-03 12:33 ` Kevin Wolf
2012-07-03 12:33 ` Kevin Wolf
2012-07-03 13:14 ` Corey Bryant
2012-07-03 13:14 ` [Qemu-devel] " Corey Bryant
2012-07-03 3:59 ` 王永博
2012-07-03 3:59 ` [Qemu-devel] " 王永博
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=4FF1DB7D.1000006@redhat.com \
--to=eblake@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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.