All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] Making QMP 'block-job-cancel' transactionable
Date: Mon, 3 Apr 2017 15:38:47 +0100	[thread overview]
Message-ID: <20170403143847.GB3539@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170328152934.rebdzsjfsfc6ajrh@eukaryote>

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

On Tue, Mar 28, 2017 at 05:29:34PM +0200, Kashyap Chamarthy wrote:
> On Tue, Mar 28, 2017 at 09:49:40AM -0500, Eric Blake wrote:
> > On 03/24/2017 07:34 AM, Kashyap Chamarthy wrote:
> > > While debugging some other issue, I happened to stumble across an old
> > > libvirt commit[*] that adds support for pivot (whether QEMU should
> > > switch to a target copy or not) operation as a result of issuing QMP
> > > 'block-job-cancel' to a 'drive-mirror' (in libvirt parlance, "block
> > > copy").
> > > 
> > > In the libvirt commit message[*] Eric Blake writes:
> > > 
> > >     "[...] There may be potential improvements to the snapshot code to
> > >     exploit block copy over multiple disks all at one point in time.
> > >     And, if 'block-job-cancel' were made part of 'transaction', you
> > >     could copy multiple disks at the same point in time without pausing
> > >     the domain. [...]"
> > > 
> > > I realize that 'block-job-cancel' is currently not part of the
> > > @TransactionAction.  Is it worthwhile to do so?
> > 
> > Yes, it is still worthwhile to make that improvement, although it is
> > now 2.10 material.
> 
> Thanks for looking, didn't imply that it's for 2.9 (which is in Release
> Candidate phase) -- I realize most people are busy with it.  Further
> discussion could be had when 2.10 tree opens up.

Thanks for the discussion.  I have added this task to the block layer
todo list:

http://wiki.qemu-project.org/ToDo/Block#Atomic_block-job-cancel

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

  reply	other threads:[~2017-04-03 14:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 12:34 [Qemu-devel] Making QMP 'block-job-cancel' transactionable Kashyap Chamarthy
2017-03-28 14:49 ` Eric Blake
2017-03-28 15:29   ` Kashyap Chamarthy
2017-04-03 14:38     ` Stefan Hajnoczi [this message]
2017-04-03 20:29 ` [Qemu-devel] [Qemu-block] " John Snow
2017-04-03 20:38   ` Eric Blake
2017-04-04 13:28     ` Kashyap Chamarthy
2017-04-04 13:54       ` Eric Blake
2017-04-11  9:42         ` Markus Armbruster
2017-04-11 10:30           ` Kashyap Chamarthy
2017-04-11 12:05   ` Kevin Wolf
2017-04-11 13:14     ` Eric Blake
2017-04-11 13:30       ` Kevin Wolf
2017-04-12  8:42         ` Fam Zheng
2017-04-12  8:59           ` Kevin Wolf
2017-04-12  9:12             ` 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=20170403143847.GB3539@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=eblake@redhat.com \
    --cc=kchamart@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 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.