From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH] kvm tools: Repair running on non ioeventfd-capable platforms Date: Tue, 31 Jan 2012 08:44:51 -0500 Message-ID: <1328017491.6697.12.camel@lappy> References: <4F278A91.3030205@ozlabs.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: KVM list , Pekka Enberg To: Matt Evans Return-path: Received: from mail-gy0-f174.google.com ([209.85.160.174]:45772 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752261Ab2AaNot (ORCPT ); Tue, 31 Jan 2012 08:44:49 -0500 Received: by ghrr11 with SMTP id r11so9963ghr.19 for ; Tue, 31 Jan 2012 05:44:48 -0800 (PST) In-Reply-To: <4F278A91.3030205@ozlabs.org> Sender: kvm-owner@vger.kernel.org List-ID: 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 > --- > > Sasha, you screwed PPC64! And it took me a month to notice.... hahaha! I only broke it two days ago :) -- Sasha.