From: David kiarie <davidkiarie4@gmail.com>
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
Subject: Re: [Qemu-devel] [V3 3/4] hw/i386: ACPI table for AMD IO MMU
Date: Fri, 15 Jan 2016 16:52:32 +0300 [thread overview]
Message-ID: <CABdVeAAyM1ShxHeSs5bEYPh9aBS22DwyTXOwPD_mtaKAya0-QA@mail.gmail.com> (raw)
In-Reply-To: <CA+1EZ4=BXCe4AxO3uzVz0B-jEu+MqegvmRQS31z51RL7udvHAA@mail.gmail.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
next prev parent reply other threads:[~2016-01-15 13:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 8:04 [Qemu-devel] [V3 0/4] AMD IOMMU David Kiarie
2016-01-14 8:04 ` [Qemu-devel] [V3 1/4] hw/i386: Introduce AMD IO MMU David Kiarie
2016-01-14 8:04 ` [Qemu-devel] [V3 2/4] hw/core: Add AMD IO MMU to machine properties David Kiarie
2016-01-17 13:45 ` Marcel Apfelbaum
2016-01-14 8:04 ` [Qemu-devel] [V3 3/4] hw/i386: ACPI table for AMD IO MMU David Kiarie
2016-01-14 9:56 ` Michael S. Tsirkin
2016-01-14 10:09 ` Michael S. Tsirkin
2016-01-14 12:15 ` David kiarie
2016-01-14 15:39 ` Michael S. Tsirkin
2016-01-14 15:42 ` Jan Kiszka
2016-01-14 16:09 ` David kiarie
2016-01-14 16:19 ` Jan Kiszka
2016-01-14 16:29 ` David kiarie
2016-01-14 16:52 ` Kevin O'Connor
2016-01-14 12:34 ` David kiarie
2016-01-14 16:29 ` Kevin O'Connor
2016-01-14 16:54 ` Valentine Sinitsyn
2016-01-15 13:52 ` David kiarie [this message]
2016-01-14 8:04 ` [Qemu-devel] [V3 4/4] hw/pci-host: Emulate " David Kiarie
2016-01-17 13:57 ` Marcel Apfelbaum
2016-01-18 16:36 ` David Kiarie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABdVeAAyM1ShxHeSs5bEYPh9aBS22DwyTXOwPD_mtaKAya0-QA@mail.gmail.com \
--to=davidkiarie4@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=jan.kiszka@web.de \
--cc=kevin@koconnor.net \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=valentine.sinitsyn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).