From: "Michael S. Tsirkin" <mst@redhat.com>
To: David kiarie <davidkiarie4@gmail.com>
Cc: marcel@redhat.com,
Valentine Sinitsyn <valentine.sinitsyn@gmail.com>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
Jan Kiszka <jan.kiszka@web.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [V3 3/4] hw/i386: ACPI table for AMD IO MMU
Date: Thu, 14 Jan 2016 17:39:17 +0200 [thread overview]
Message-ID: <20160114173824-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <CABdVeADg91Tfpf8nysiNniF9xY2oxyrfA-YDSe1qUHLmqm2g0Q@mail.gmail.com>
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 <mst@redhat.com> 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
next prev parent reply other threads:[~2016-01-14 15:39 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 [this message]
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
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=20160114173824-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=crosthwaitepeter@gmail.com \
--cc=davidkiarie4@gmail.com \
--cc=jan.kiszka@web.de \
--cc=marcel@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).