From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59319) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dFxfn-0005QQ-0k for qemu-devel@nongnu.org; Wed, 31 May 2017 03:04:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dFxfh-0004Ba-Tl for qemu-devel@nongnu.org; Wed, 31 May 2017 03:04:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47056) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dFxfh-0004B1-NZ for qemu-devel@nongnu.org; Wed, 31 May 2017 03:03:57 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 5E4C780C07 for ; Wed, 31 May 2017 07:03:56 +0000 (UTC) Date: Wed, 31 May 2017 15:03:46 +0800 From: Peter Xu Message-ID: <20170531070346.GE14845@pxdev.xzpeter.org> References: <1494854073-19898-1-git-send-email-peterx@redhat.com> <20170529060813.GF22816@pxdev.xzpeter.org> <87k2506ltg.fsf@dusky.pond.sub.org> <20170529101331.GA14845@pxdev.xzpeter.org> <87d1ar504h.fsf@dusky.pond.sub.org> <13985c6d-d24a-ac50-2708-fc3b9cc64acd@redhat.com> <87h902l8qd.fsf@dusky.pond.sub.org> <6a6a91cc-7ea1-2b45-a4bd-31aa3cfef917@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <6a6a91cc-7ea1-2b45-a4bd-31aa3cfef917@redhat.com> Subject: Re: [Qemu-devel] [PATCH] msi: remove return code for msi_init() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Markus Armbruster , Marcel Apfelbaum , qemu-devel@nongnu.org, "Michael S . Tsirkin" On Tue, May 30, 2017 at 04:29:57PM +0200, Paolo Bonzini wrote: > > > On 30/05/2017 16:28, Markus Armbruster wrote: > > Paolo Bonzini writes: > > > >>> Note that a board that doesn't support MSI can take MSI-capable devices > >>> just fine. Only the broken boards can't. > >>> > >>> Obviously, broken boards should be fixed. Once they all are, we can > >>> (and should!) remove msi_nonbroken. > >> > >> That only works if we know what the broken boards are. > > > > Yes. > > > >> Right now, all boards that do not support MSI hide the capability, which > >> is wrong. > > > > Agreed. > > > >> I'd prefer to remove msi_nonbroken completely if we don't > >> know where the problem is. > > > > So you're proposing to (1) remove msi_nonbroken, (2) see which boards > > burst into flames, and (3) fix them, or perhaps add a less wrong stop > > gap msi_broken just for them? > > Yes, adding back msi_broken is one "git revert" away. Not sure whether I got the point here, but... Adding msi_broken is not a "git revert"? Since there is no msi_broken before, only msi_supported. And iirc if we want to provide one msi_broken we need to know exactly all the borads that are broken with MSI, and that blacklist is something we don't have now (as you mentioned above)? Please correct me if I misunderstood. > > Of course, this means the edu memory leak should be fixed in a separate > small patch. > > Thanks, > > Paolo Thanks, -- Peter Xu