All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: valentine.sinitsyn@gmail.com, qemu-devel@nongnu.org,
	crosthwaitepeter@gmail.com, jan.kiszka@web.de, marcel@redhat.com,
	David Kiarie <davidkiarie4@gmail.com>
Subject: Re: [Qemu-devel] [V3 3/4] hw/i386: ACPI table for AMD IO MMU
Date: Thu, 14 Jan 2016 11:29:48 -0500	[thread overview]
Message-ID: <20160114162948.GA1901@morn.lan> (raw)
In-Reply-To: <20160114100946.GA13170@redhat.com>

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

  parent reply	other threads:[~2016-01-14 16:29 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 [this message]
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=20160114162948.GA1901@morn.lan \
    --to=kevin@koconnor.net \
    --cc=crosthwaitepeter@gmail.com \
    --cc=davidkiarie4@gmail.com \
    --cc=jan.kiszka@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.