qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org, Block layer core <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCHv2 for-2.4] block: Auto-generate node_names for each BDS entry
Date: Tue, 23 Jun 2015 11:31:49 +0200	[thread overview]
Message-ID: <55892785.5060004@redhat.com> (raw)
In-Reply-To: <87h9py4x4l.fsf@blackfin.pond.sub.org>



On 23/06/2015 11:00, Markus Armbruster wrote:
> My point is: the problem is more general than just block nodes.  Doesn't
> mean we mustn't solve the special problem unless we solve the general
> problem.  Does mean we should at least try to solve the general problem,
> and if we fail, try our best to solve the special problem in a way that
> fits into a general solution.
> 
> Have you tried to solve or at least discuss the general problem?

IIRC blockdevs are special because some of them (the backing files) are
opened without request from the user.

The same happens for board-created devices, but we can just say they
aren't unpluggable.

Paolo

  reply	other threads:[~2015-06-23  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 23:10 [Qemu-devel] [PATCHv2 for-2.4] block: Auto-generate node_names for each BDS entry Eric Blake
2015-06-23  7:14 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2015-06-23  9:00 ` [Qemu-devel] " Markus Armbruster
2015-06-23  9:31   ` Paolo Bonzini [this message]
2015-06-23 11:24     ` Markus Armbruster

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=55892785.5060004@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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).