From: Sasha Levin <levinsasha928@gmail.com>
To: Matt Evans <matt@ozlabs.org>
Cc: KVM list <kvm@vger.kernel.org>, Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH] kvm tools: Repair running on non ioeventfd-capable platforms
Date: Tue, 31 Jan 2012 08:44:51 -0500 [thread overview]
Message-ID: <1328017491.6697.12.camel@lappy> (raw)
In-Reply-To: <4F278A91.3030205@ozlabs.org>
On Tue, 2012-01-31 at 17:30 +1100, Matt Evans wrote:
>
> Commit d3923126a24212f1e746a84a575dadbd9f259418 added a bunch of
> nice error checking around ioevent__init() but the init may gracefully
> fail if ioevents simply aren't supported (PPC64 KVM).
>
> This commit adds a new return code for the init -- positive, but
> identifiable as 'not success 0'.
>
> Signed-off-by: Matt Evans <matt@ozlabs.org>
> ---
>
> Sasha, you screwed PPC64! And it took me a month to notice.... hahaha!
I only broke it two days ago :)
--
Sasha.
prev parent reply other threads:[~2012-01-31 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 6:30 [PATCH] kvm tools: Repair running on non ioeventfd-capable platforms Matt Evans
2012-01-31 8:13 ` Pekka Enberg
2012-01-31 13:44 ` Sasha Levin [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=1328017491.6697.12.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=matt@ozlabs.org \
--cc=penberg@kernel.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).