All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com>
To: lcapitulino@redhat.com
Cc: qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v5 0/3] qemu-ga: add hook to quiesce the guest on fsfreeze-freeze/thaw
Date: Fri, 30 Nov 2012 21:40:04 +0900	[thread overview]
Message-ID: <50B8A924.6090801@hitachi.com> (raw)
In-Reply-To: <20121130094219.70a862cd@doriath.home>

On 2012/11/30 20:42, Luiz Capitulino wrote:
> On Fri, 30 Nov 2012 15:25:57 +0900
> Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com> wrote:
> 
>> Hi,
>>
>> This is version 5 of the qemu-ga fsfreeze hook patchset.
> 
> This series split is not good. You should squash patches 3/3 and 1/3 and
> rebase this series on top of:
> 
>  http://lists.gnu.org/archive/html/qemu-devel/2012-11/msg03016.html

I see, I will resend a patchset squashed and rebased on this.
BTW, is there a git branch for 1.4 anywhere?

> Also, please look at qmp_shutdown() and bios_supports_mode() for examples
> of command execution with improved error reporting.
> 
>> *Changes from v4: ( http://patchwork.ozlabs.org/patch/200924/ )
>>  1/3: Improve error messages when fsfreeze hook is not executable.
>>       Make fsfreeze-hook disabled by default, and enabled only if
>>       --fsfreeze-hook option is specified.
> 
> Let me clarify that there are two ways of doing this. One is the way above,
> the other way is to enable it by default but allow something like
> "--fsfreeze-hook no" to disable the hook execution.

I chose the way to disable it by default because it's more precise.
If we enable the hook by default, we need to guess whether the hook is
executed by its presence, and then the hook placed on wrong path will
not cause an error.

> Both ways are fine with me.
> 

Thanks,
-- 
Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com>
Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory

  reply	other threads:[~2012-11-30 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30  6:25 [Qemu-devel] [PATCH v5 0/3] qemu-ga: add hook to quiesce the guest on fsfreeze-freeze/thaw Tomoki Sekiyama
2012-11-30  6:26 ` [Qemu-devel] [PATCH v5 1/3] qemu-ga: execute " Tomoki Sekiyama
2012-11-30  6:26 ` [Qemu-devel] [PATCH v5 2/3] qemu-ga: sample fsfreeze hooks Tomoki Sekiyama
2012-11-30  6:26 ` [Qemu-devel] [PATCH v5 3/3] [for 1.4] qemu-ga: Improve error reporting in execute_fsfreeze_hook() Tomoki Sekiyama
2012-11-30 11:42 ` [Qemu-devel] [PATCH v5 0/3] qemu-ga: add hook to quiesce the guest on fsfreeze-freeze/thaw Luiz Capitulino
2012-11-30 12:40   ` Tomoki Sekiyama [this message]
2012-11-30 12:51     ` Luiz Capitulino

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=50B8A924.6090801@hitachi.com \
    --to=tomoki.sekiyama.qu@hitachi.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --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.