From: Paolo Bonzini <pbonzini@redhat.com>
To: Tom Knych <thomaswk@google.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
David Turner <digit@google.com>,
qemu-devel@nongnu.org, gleb@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/1] KVM: Retry KVM_CREATE_VM on EINTR or EAGAIN
Date: Wed, 15 Jan 2014 08:47:37 +0100 [thread overview]
Message-ID: <52D63D19.6040501@redhat.com> (raw)
In-Reply-To: <CAB=aRPN7P6VhT5mHdP+8MHDRcqfx9QYE_94Xq2Stqrb25B3SpA@mail.gmail.com>
Il 15/01/2014 03:09, Tom Knych ha scritto:
> Doing it with sigprocmask seems good I will send an updated patch
No need, I'll apply this patch.
Paolo
prev parent reply other threads:[~2014-01-15 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 21:14 [Qemu-devel] [PATCH 0/1] KVM: Retry KVM_CREATE_VM on EINTR or EAGAIN thomas knych
2014-01-09 21:14 ` [Qemu-devel] [PATCH 1/1] " thomas knych
2014-01-10 13:01 ` Paolo Bonzini
2014-01-10 22:15 ` Tom Knych
2014-01-13 11:16 ` Paolo Bonzini
2014-01-14 18:56 ` Andrea Arcangeli
2014-01-15 2:09 ` Tom Knych
2014-01-15 7:47 ` Paolo Bonzini [this message]
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=52D63D19.6040501@redhat.com \
--to=pbonzini@redhat.com \
--cc=aarcange@redhat.com \
--cc=digit@google.com \
--cc=gleb@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomaswk@google.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 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).