From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: quintela@redhat.com, chegu_vinod@hp.com, qemu-devel@nongnu.org,
"Michael R. Hines" <mrhines@linux.vnet.ibm.com>,
owasserm@redhat.com, onom@us.ibm.com, abali@us.ibm.com,
mrhines@us.ibm.com, gokul@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 for-1.7] rdma: rename 'x-rdma' => 'rdma'
Date: Fri, 22 Nov 2013 17:50:53 +0100 [thread overview]
Message-ID: <528F8B6D.3060008@redhat.com> (raw)
In-Reply-To: <20131116103245.GC9975@redhat.com>
Il 16/11/2013 11:32, Daniel P. Berrange ha scritto:
> There's also an SELinux question to deal with there. If multiple QEMUs
> need concurrent access we can't do a selective grant of the device just
> when migration is running - we would have to give all QEMU's access
> all the time. This would be a case where doing FD passing of the
> pre-opened devices might be a better option. It depends on what the
> downsides are to giving QEMU access to the devices unconditionally.
I think unconditional SELinux access + conditional cgroups access would
work best here.
How did Gluster deal with the same problem (for the gluster+rdma:// URI
scheme)? I guess no one bothered to mention it when the Gluster patches
were committed, but it should be the same. It would also be the same
for userspace iSCSI if libiscsi were to grow support for iSER (iSCSI
extensions for RDMA).
Paolo
prev parent reply other threads:[~2013-11-22 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 18:59 [Qemu-devel] [PATCH v3 for-1.7] rdma: rename 'x-rdma' => 'rdma' mrhines
2013-11-06 19:04 ` Eric Blake
2013-11-15 17:06 ` Daniel P. Berrange
2013-11-15 17:40 ` Michael R. Hines
2013-11-15 19:25 ` Eric Blake
2013-11-15 19:44 ` Michael R. Hines
2013-11-15 19:49 ` Eric Blake
2013-11-16 10:32 ` Daniel P. Berrange
2013-11-22 16:50 ` 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=528F8B6D.3060008@redhat.com \
--to=pbonzini@redhat.com \
--cc=abali@us.ibm.com \
--cc=berrange@redhat.com \
--cc=chegu_vinod@hp.com \
--cc=gokul@us.ibm.com \
--cc=mrhines@linux.vnet.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=onom@us.ibm.com \
--cc=owasserm@redhat.com \
--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 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).