qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: eblake@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2]: qemu-ga: make shutdown & suspend synchronous
Date: Mon, 14 May 2012 14:26:04 -0300	[thread overview]
Message-ID: <20120514142604.5a51cc93@doriath.home> (raw)
In-Reply-To: <20120514171904.GD28865@illuin>

On Mon, 14 May 2012 12:19:04 -0500
Michael Roth <mdroth@linux.vnet.ibm.com> wrote:

> On Mon, May 14, 2012 at 01:39:50PM -0300, Luiz Capitulino wrote:
> > On Mon, 14 May 2012 09:56:30 -0500
> > Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
> > 
> > > Hi Luiz,
> > > 
> > > I have these patches applied to qga branch with Eric's suggested fix-ups included. I've attached them for your review. If all looks good I'll send a PULL some time today with what's hopefully all the pending fixes for qemu-ga 1.1
> > 
> > Yes, looks good. I was finishing to work on a similar version that moves
> > the loop to a function called ga_waitpid(), it's only missing some testing. But
> > you can merge this version if you're hurrying.
> > 
> > Btw, I have another fix that fixes guest-shutdown to use async-safe-signal
> > functions.
> > 
> > What's the best way to go? Do you want me to send just the guest-shutdown
> > fix or should I post my v2 of this series too (that uses ga_waitpid())?
> > 
> 
> Hmm, since Eric has already reviewed the quick fix let's just save ga_waitpid()
> for another day.

OK.

> Will keep an eye out for guest-shutdown fixes. I have a patch that
> switches it to using reopen_to_null() btw, but if that's already part of
> your patch I'll drop it in favor of yours:
> 
> https://github.com/mdroth/qemu/commits/qga

Yes, it's. Besides using reopen_to_null() we also have to switch to
execle() and _exit(). I'll give it a quick test and post it shortly.

  reply	other threads:[~2012-05-14 17:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 19:19 [Qemu-devel] [PATCH 0/2]: qemu-ga: make shutdown & suspend synchronous Luiz Capitulino
2012-05-11 19:19 ` [Qemu-devel] [PATCH 1/2] qemu-ga: guest-suspend: make the API synchronous Luiz Capitulino
2012-05-11 22:10   ` Eric Blake
2012-05-11 19:19 ` [Qemu-devel] [PATCH 2/2] qemu-ga: guest-shutdown: become synchronous Luiz Capitulino
2012-05-11 22:11   ` Eric Blake
2012-05-14 14:56 ` [Qemu-devel] [PATCH 0/2]: qemu-ga: make shutdown & suspend synchronous Michael Roth
2012-05-14 14:56   ` [Qemu-devel] [PATCH 1/2] qemu-ga: guest-suspend: make the API synchronous Michael Roth
2012-05-14 15:30     ` Eric Blake
2012-05-14 14:56   ` [Qemu-devel] [PATCH 2/2] qemu-ga: guest-shutdown: become synchronous Michael Roth
2012-05-14 15:31     ` Eric Blake
2012-05-14 16:39   ` [Qemu-devel] [PATCH 0/2]: qemu-ga: make shutdown & suspend synchronous Luiz Capitulino
2012-05-14 17:19     ` Michael Roth
2012-05-14 17:26       ` Luiz Capitulino [this message]
2012-05-14 17:06 ` Michal Privoznik
2012-05-14 17:14   ` Luiz Capitulino
2012-05-14 17:17   ` Eric Blake
2012-05-14 18:12     ` Michael Roth
2012-05-14 18:18       ` 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=20120514142604.5a51cc93@doriath.home \
    --to=lcapitulino@redhat.com \
    --cc=eblake@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 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).