From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53246) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aJjzg-0006s7-Qd for qemu-devel@nongnu.org; Thu, 14 Jan 2016 10:39:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aJjzd-0007s6-Ju for qemu-devel@nongnu.org; Thu, 14 Jan 2016 10:39:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51488) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aJjzd-0007rq-Dz for qemu-devel@nongnu.org; Thu, 14 Jan 2016 10:39:21 -0500 Date: Thu, 14 Jan 2016 17:39:17 +0200 From: "Michael S. Tsirkin" Message-ID: <20160114173824-mutt-send-email-mst@redhat.com> 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: 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: David kiarie Cc: marcel@redhat.com, Valentine Sinitsyn , Peter Crosthwaite , Jan Kiszka , QEMU Developers On Thu, Jan 14, 2016 at 03:15:38PM +0300, David kiarie wrote: > On Thu, Jan 14, 2016 at 1:09 PM, 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? > > Yeah, typo. > > > > >> 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. > > Yes, that's the spec. > > We thought this could be possible via ACPI (without patching BIOS ), no ? I don't see how. We should do it the way it happens on real hardware. -- MST