From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41806) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6IgJ-0003h9-Oa for qemu-devel@nongnu.org; Mon, 05 Aug 2013 07:10:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V6IgB-0006Y8-Im for qemu-devel@nongnu.org; Mon, 05 Aug 2013 07:10:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45554) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6IgB-0006Xy-AR for qemu-devel@nongnu.org; Mon, 05 Aug 2013 07:10:23 -0400 Date: Mon, 5 Aug 2013 13:10:04 +0200 From: Paolo Bonzini Message-ID: <20130805111004.GD19162@mail.corp.redhat.com> References: <51FCBFCD.5020608@web.de> <51FF71BD.5040400@suse.de> <51FF7ED6.3050101@web.de> <51FF8211.3050509@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH 1/2] memory: Provide separate handling of unassigned io ports accesses List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Jan Kiszka , Andreas =?utf-8?Q?F=C3=A4rber?= , Aurelien Jarno , qemu-devel On Aug 05 2013, Peter Maydell wrote: > > But even if we would, the IO container now catches all accesses, so > > the system memory region will never have its default handler run for > > that window. > > Yes, that is the point -- before the IO container caught all > accesses, the default handler that would run would be the > system memory region, but now that the IO container has > default read/write ops they will take precedence. So this > would be a behaviour change if there are any boards set up > like this. (I'm not sure there are any, though.) Before 1.6 this would have happened anyway. Before 1.6, all I/O accesses would go through cpu_in/cpu_out, and would never hit the system memory region. So Jan's patch is effectively restoring old behavior. Paolo