From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJ8wS-0007vt-A9 for qemu-devel@nongnu.org; Sun, 17 Aug 2014 18:28:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XJ8wM-0008L1-1f for qemu-devel@nongnu.org; Sun, 17 Aug 2014 18:28:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:8172) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJ8wL-0008Kx-Ph for qemu-devel@nongnu.org; Sun, 17 Aug 2014 18:28:41 -0400 Message-ID: <53F12C94.6090307@redhat.com> Date: Mon, 18 Aug 2014 00:28:36 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <5de8cf7083b0e4dabc0692451f2b319badf2b6e0.1408086974.git.peter.crosthwaite@xilinx.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH memory v1 1/1] memory: remove may_overlap property List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Peter Crosthwaite Cc: QEMU Developers Il 18/08/2014 00:23, Peter Maydell ha scritto: > Um. I think in general colliding memory regions imply a bug in the > machine model which is creating them. We have the collisions > disabled because nobody's got round to fixing this bug in the > PC model yet and it happens to be harmless there. I'm not > really convinced that yanking out the check code is better than > fixing the PC model... I'm not sure I can parse anything in the commit message for a5e1cbc80 (which disabled the warning). I guess I'll try to revert that one and see what happens. Paolo