From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:32908) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aoT76-0005Eo-L2 for qemu-devel@nongnu.org; Fri, 08 Apr 2016 05:54:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aoT72-00086Z-Lo for qemu-devel@nongnu.org; Fri, 08 Apr 2016 05:54:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42759) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aoT72-00086P-GJ for qemu-devel@nongnu.org; Fri, 08 Apr 2016 05:54:00 -0400 Date: Fri, 8 Apr 2016 17:53:52 +0800 From: Peter Xu Message-ID: <20160408095352.GC26923@pxdev.xzpeter.org> References: <1455852618-5224-1-git-send-email-peterx@redhat.com> <1455852618-5224-6-git-send-email-peterx@redhat.com> <56C9A1B8.6070909@gmail.com> <56C9A8D1.4010604@gmail.com> <56C9BE5D.60808@web.de> <56C9DDB1.8000305@redhat.com> <56C9DF3E.4060907@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <56C9DF3E.4060907@web.de> Subject: Re: [Qemu-devel] [PATCH 05/13] acpi: add DMAR scope definition for root IOAPIC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Marcel Apfelbaum , qemu-devel@nongnu.org, ehabkost@redhat.com, mst@redhat.com, jasowang@redhat.com, imammedo@redhat.com, pbonzini@redhat.com, rth@twiddle.net, Rita Sinha On Sun, Feb 21, 2016 at 05:01:02PM +0100, Jan Kiszka wrote: > >> We have the same problem over with VT-d and IR. > >> > >> I don't think the firmware is not the right place, otherwise there would > >> be an interface in hw to adjust that parameters. I think we should > >> simply make sure that the qemu user cannot assign devices to those > >> addresses as they are reserved for the platform devices (the HPET > >> requires another ID), or even reserve the hole bus for the platform. > > > > > > I understand, but it is the firmware that assign addresses, not QEMU/user. > > Right, buses are chosen by the firmware, but device address are > (optionally) under user control. > > > We need a way to tell the firmware not to use a certain address range, > > we can do that > > with fw_config I suppose. > > The pseudo addresses of IOAPIC and HPET are part of ACPI tables, both on > AMD and Intel. Firmware can evaluate them easily. Hi, Jan, Marcel, Could you give me some hint on how to achieve this using fw_config (restriction on PCI bus numbers)? I failed to find it out myself. Thanks in advance. -- peterx