From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54652) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2HQ7-0005Vy-IB for qemu-devel@nongnu.org; Thu, 25 Jul 2013 05:01:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V2HQ5-0000Vq-CV for qemu-devel@nongnu.org; Thu, 25 Jul 2013 05:01:11 -0400 Received: from gate.crashing.org ([63.228.1.57]:46284) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2HQ5-0000Vd-3S for qemu-devel@nongnu.org; Thu, 25 Jul 2013 05:01:09 -0400 Message-ID: <1374742849.6142.72.camel@pasglop> From: Benjamin Herrenschmidt Date: Thu, 25 Jul 2013 19:00:49 +1000 In-Reply-To: <51F0E47D.1060807@redhat.com> References: <1374501278-31549-1-git-send-email-pbonzini@redhat.com> <87ip02wqvn.fsf@codemonkey.ws> <1374729976.6142.61.camel@pasglop> <1374731256.6142.63.camel@pasglop> <51F0E47D.1060807@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/28] Memory API for 1.6: fix I/O port endianness mess List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Anthony Liguori , aik@ozlabs.ru, jan.kiszka@siemens.com, qemu-devel@nongnu.org, agraf@suse.de, hpoussin@reactos.org, aurelien@aurel32.net On Thu, 2013-07-25 at 10:40 +0200, Paolo Bonzini wrote: > In any case, let me reinforce point 6 above. The patches were not > reverted because nobody posted the patches to do so. Until someone > does > so, it is basically Anthony's call. If he trusts people to fix the > whole thing, he has no reason to revert anything. My track record of > fixing mess is probably better than my track record of not causing it, > so he didn't revert it. That's fine, I know you can fix stuff :-) I'm just really annoyed that upstream qemu remained broken for so long (and still is) while the whole thing derailed into a mostly pointless discussion on endianness and nobody (including Alexey) hollered loud enough that the breakage was fairly extensive (BTW. The EHCI problem doesn't seem limited to SLOF, from what I remember of what Alexey showed me today, the Linux EHCI driver also segfaults qemu). Cheers, Ben.