From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39327) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aJkmX-0004Zh-QA for qemu-devel@nongnu.org; Thu, 14 Jan 2016 11:29:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aJkmU-0005Cr-Kv for qemu-devel@nongnu.org; Thu, 14 Jan 2016 11:29:53 -0500 Received: from mail-qg0-x22d.google.com ([2607:f8b0:400d:c04::22d]:33198) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aJkmU-0005Cf-GS for qemu-devel@nongnu.org; Thu, 14 Jan 2016 11:29:50 -0500 Received: by mail-qg0-x22d.google.com with SMTP id b35so356588041qge.0 for ; Thu, 14 Jan 2016 08:29:50 -0800 (PST) Date: Thu, 14 Jan 2016 11:29:48 -0500 From: Kevin O'Connor Message-ID: <20160114162948.GA1901@morn.lan> References: <1452758668-19284-1-git-send-email-davidkiarie4@gmail.com> <1452758668-19284-4-git-send-email-davidkiarie4@gmail.com> <20160114100946.GA13170@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160114100946.GA13170@redhat.com> Subject: Re: [Qemu-devel] [V3 3/4] hw/i386: ACPI table for AMD IO MMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: valentine.sinitsyn@gmail.com, qemu-devel@nongnu.org, crosthwaitepeter@gmail.com, jan.kiszka@web.de, marcel@redhat.com, David Kiarie On Thu, Jan 14, 2016 at 12:09:46PM +0200, Michael S. Tsirkin wrote: > On Thu, Jan 14, 2016 at 11:04:27AM +0300, David Kiarie wrote: > > Add IVRS table for AMD IO MMU. Also reverve MMIO > > reserve? > > > region for IO MMU via ACPI > > > It does not look like you reserve anything. > > Pls add a link to hardware spec (in > the device implementation) so we can check > what does real hardware do. > > If this is it: > http://developer.amd.com/wordpress/media/2012/10/488821.pdf > > then the way that works seems to be by guest > programming the MMIO base. > We should do the same: patch seabios and EFI to do this. A similar question - how does a typical factory BIOS select which address to set as the MMIO base? Is it generally hard-coded or is it allocated from a range in some way? -Kevin