All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	stefanha@redhat.com, kchamart@redhat.com,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 2/2] qemu-img: Document --force-share / -U
Date: Tue, 30 Jan 2018 17:38:20 +0100	[thread overview]
Message-ID: <20180130163820.GC4503@localhost.localdomain> (raw)
In-Reply-To: <b552c5fb-f79a-98f1-bac7-26cf6e106f06@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

Am 30.01.2018 um 15:23 hat Eric Blake geschrieben:
> On 01/30/2018 12:34 AM, Fam Zheng wrote:
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> >  qemu-img.texi | 7 +++++++
> >  1 file changed, 7 insertions(+)
> > 
> > diff --git a/qemu-img.texi b/qemu-img.texi
> > index 60a0e080c6..ec7e2f5d1e 100644
> > --- a/qemu-img.texi
> > +++ b/qemu-img.texi
> > @@ -86,6 +86,13 @@ exclusive with the @var{-O} parameters. It is currently required to also use
> >  the @var{-n} parameter to skip image creation. This restriction may be relaxed
> >  in a future release.
> >  
> > +@item --force-share (-U)
> > +If specified, @code{qemu-img} will open the image in shared mode, allowing
> > +concurrent writers. For example, this can be used to get the image information
> 
> Actually, we only permit one writer at a time.  Would it be better to
> say "allowing a concurrent writer"?

As far as qemu-img is concerned, multiple writers to the image are
allowed. There may be further restrictions imposed by a writer so that a
second writer isn't allowed, but with raw images and share-rw=on nothing
prevents two qemu instances writing to the same image while qemu-img is
accessing it read-only.

Kevin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2018-01-30 16:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  6:34 [Qemu-devel] [PATCH v6 0/2] qemu-img: Document --force-share / -U Fam Zheng
2018-01-30  6:34 ` [Qemu-devel] [PATCH v6 1/2] qemu-img.texi: Clean up parameter list Fam Zheng
2018-01-30 13:50   ` Eric Blake
2018-01-30  6:34 ` [Qemu-devel] [PATCH v6 2/2] qemu-img: Document --force-share / -U Fam Zheng
2018-01-30 12:14   ` Stefan Hajnoczi
2018-01-30 13:52   ` Eric Blake
2018-01-30 14:23   ` Eric Blake
2018-01-30 14:34     ` Kashyap Chamarthy
2018-01-30 16:38     ` Kevin Wolf [this message]
2018-01-31 14:12       ` Stefan Hajnoczi
2018-01-31 14:22         ` Kevin Wolf
2018-02-01 11:44           ` Stefan Hajnoczi
2018-02-09  3:29             ` Fam Zheng
2018-02-09  3:31             ` Fam Zheng

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=20180130163820.GC4503@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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.