qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Kiarie <davidkiarie4@gmail.com>
To: qemu-devel@nongnu.org, jan.kiszka@web.de,
	valentine.sinitsyn@gmail.com, mst@redhat.com
Cc: David Kiarie <davidkiarie4@gmail.com>
Subject: [Qemu-devel] [PATCH 0/4] AMD IOMMU v1
Date: Fri,  9 Oct 2015 05:53:53 +0300	[thread overview]
Message-ID: <1444359237-27224-1-git-send-email-davidkiarie4@gmail.com> (raw)

David (4):
  hw/core: Add iommu to machine properties
  hw/pci-host: Add AMD IOMMU to PIIX and Q35 pcs
  hw/i386: Introduce AMD IOMMU
  hw/acpi: ACPI table for AMD IOMMU

 hw/core/machine.c           |   25 +
 hw/i386/Makefile.objs       |    1 +
 hw/i386/acpi-build.c        |   85 +++
 hw/i386/amd_iommu.c         | 1266 +++++++++++++++++++++++++++++++++++++++++++
 hw/i386/amd_iommu.h         |  363 +++++++++++++
 hw/pci-host/piix.c          |   10 +
 hw/pci-host/q35.c           |   10 +
 include/hw/acpi/acpi-defs.h |   55 ++
 include/hw/boards.h         |    2 +
 9 files changed, 1817 insertions(+)
 create mode 100644 hw/i386/amd_iommu.c
 create mode 100644 hw/i386/amd_iommu.h


AMD IOMMU v1

Changes since RFC
    -code cleanup around MMIO code
    -compacted startup code - some of the 'init' and 'reset' code is similar and can be reused
    -Implemented basic IOTLB - it's just a hashtable of already requested virtual address translations whereby if a device requests translation of the same address we don't have to do a page walk, again.
    -Implemented event logging - this version logs about all possible SW/HW errors but most of them are very unlikely to occur.
    -Changed GVA and HVA to go by the physical host bus implementations - 48 bits virtual and 40 bits physical address space.

TODO
   -Implement MMIO reserving code
   -Implement r/wc MMIO registers
   -Implement interrupts related to r/wc registers

IOMMU won't be able to implement PPR logging with the current Qemu infrastructure - Qemu doesn't implement anything that's related to PASID. Similary, guest translation won't be possible.

Note: I have not tested this code and it might have a few bugs (silly bugs) of course but the RFC version works so, if present, it's just minor bugs.
-- 
2.1.4

             reply	other threads:[~2015-10-08 11:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  2:53 David Kiarie [this message]
2015-10-09  2:53 ` [Qemu-devel] [PATCH 1/4] hw/core: Add iommu to machine properties David Kiarie
2015-10-08 18:10   ` Marcel Apfelbaum
2015-10-09 12:17     ` David kiarie
2015-10-09 17:16       ` Peter Crosthwaite
2015-10-09  2:53 ` [Qemu-devel] [PATCH 2/4] hw/pci-host: Add AMD IOMMU to PIIX and Q35 pcs David Kiarie
2015-10-08 12:11   ` Michael S. Tsirkin
2015-10-08 14:40   ` Marcel Apfelbaum
2015-10-09  2:53 ` [Qemu-devel] [PATCH 3/4] hw/i386: Introduce AMD IOMMU David Kiarie
2015-10-08 18:24   ` Marcel Apfelbaum
2015-10-09 12:20     ` David kiarie
2015-10-09  2:53 ` [Qemu-devel] [PATCH 4/4] hw/acpi: ACPI table for " David Kiarie
2015-10-09  7:17 ` [Qemu-devel] [PATCH 0/4] AMD IOMMU v1 Valentine Sinitsyn
2015-10-09 12:22   ` David kiarie
2015-10-09 12:24     ` Valentine Sinitsyn
2015-10-09 12:27       ` David kiarie
2015-10-09 12:30         ` Valentine Sinitsyn

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=1444359237-27224-1-git-send-email-davidkiarie4@gmail.com \
    --to=davidkiarie4@gmail.com \
    --cc=jan.kiszka@web.de \
    --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).