From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55220)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <davidkiarie4@gmail.com>) id 1aK4nr-0001Ng-T4
	for qemu-devel@nongnu.org; Fri, 15 Jan 2016 08:52:37 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <davidkiarie4@gmail.com>) id 1aK4nq-0001DO-Ex
	for qemu-devel@nongnu.org; Fri, 15 Jan 2016 08:52:35 -0500
Received: from mail-yk0-x244.google.com ([2607:f8b0:4002:c07::244]:36047)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <davidkiarie4@gmail.com>) id 1aK4nq-0001DD-AS
	for qemu-devel@nongnu.org; Fri, 15 Jan 2016 08:52:34 -0500
Received: by mail-yk0-x244.google.com with SMTP id k129so40115436yke.3
	for <qemu-devel@nongnu.org>; Fri, 15 Jan 2016 05:52:33 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <CA+1EZ4=BXCe4AxO3uzVz0B-jEu+MqegvmRQS31z51RL7udvHAA@mail.gmail.com>
References: <1452758668-19284-1-git-send-email-davidkiarie4@gmail.com>
	<1452758668-19284-4-git-send-email-davidkiarie4@gmail.com>
	<20160114100946.GA13170@redhat.com>
	<20160114162948.GA1901@morn.lan>
	<CA+1EZ4=BXCe4AxO3uzVz0B-jEu+MqegvmRQS31z51RL7udvHAA@mail.gmail.com>
Date: Fri, 15 Jan 2016 16:52:32 +0300
Message-ID: <CABdVeAAyM1ShxHeSs5bEYPh9aBS22DwyTXOwPD_mtaKAya0-QA@mail.gmail.com>
From: David kiarie <davidkiarie4@gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] [V3 3/4] hw/i386: ACPI table for AMD IO MMU
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Valentine Sinitsyn <valentine.sinitsyn@gmail.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>, Peter Crosthwaite <crosthwaitepeter@gmail.com>, Kevin O'Connor <kevin@koconnor.net>, Jan Kiszka <jan.kiszka@web.de>, marcel@redhat.com

Hi all,

I think, from coreboot code, the MMIO reservation is done through an
MCFG table. I can't see one in Qemu but I don't have a clue how to
extend it. There's literally nothing about MCFG online neither do I
have an org that's a member of pcisig.

Could someone have the docs describing MCFG ?

On Thu, Jan 14, 2016 at 7:54 PM, Valentine Sinitsyn
<valentine.sinitsyn@gmail.com> wrote:
> Hi all,
>
> I recall I saw IVRS filling code in the coreboot for one of the boards
> supported. David, you may want to have a look there.
>
> Valentine
> (from the phone)
>
> On Jan 14, 2016 9:29 PM, "Kevin O'Connor" <kevin@koconnor.net> wrote:
>>
>> 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