qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, eric.auger@redhat.com,
	prem.mallappa@broadcom.com, peter.maydell@linaro.org,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org,
	shannon.zhao@linaro.org
Cc: christoffer.dall@linaro.org, drjones@redhat.com, tn@semihalf.com
Subject: [Qemu-devel] [PATCH v2 0/2] ACPI IORT generation for ITS support
Date: Fri, 14 Oct 2016 10:54:53 +0200	[thread overview]
Message-ID: <1476435295-21885-1-git-send-email-eric.auger@redhat.com> (raw)

This series completes the support of MSIs for ACPI guest featuring an ITS.

It generates an ACPI IORT table which describes the IO relationship between
the root complex and the ITS. This typically enables vhost-net support on
such guest.

The series applies on top of Drew's series:
[PATCH 0/2] couple ITS support fixups, which is now on target-arm.next.

Original contribution was sent by Prem Mallapa in
[PATCH v2 9/9] [optional] arm: smmu-v3: ACPI IORT initial support,
part of [PATCH v2 0/9] SMMUv3 Emulation support.
https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg04350.html

Prem's 1st integration targetted Root Complex - vSMMU relationship
description whereas this series targets RC - ITS description.

This was tested with a v4.8 guest + rebased Tomasz' series:
- [PATCH V11 0/8] Introduce ACPI world to ITS,
  https://lkml.org/lkml/2016/9/12/926

History:
v1 -> v2:
- addressed Drew's comments, see individual patches

Prem's version -> v1:
- split into 2 separate patches
- iort struct field names match include/acpi/actbl2.h 's ones
- added ITS node
- added ID mapping in RC node
- removed smmu mode


Prem Mallappa (2):
  ACPI: Add IORT Structure definition
  ARM: Virt: ACPI: Build an IORT table with RC and ITS nodes

 hw/arm/virt-acpi-build.c    | 73 ++++++++++++++++++++++++++++++++++++++-------
 include/hw/acpi/acpi-defs.h | 68 +++++++++++++++++++++++++++++++++++++++++
 2 files changed, 130 insertions(+), 11 deletions(-)

-- 
2.5.5

             reply	other threads:[~2016-10-14  8:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14  8:54 Eric Auger [this message]
2016-10-14  8:54 ` [Qemu-devel] [PATCH v2 1/2] ACPI: Add IORT Structure definition Eric Auger
2016-10-14 11:30   ` Andrew Jones
2016-10-14 11:59     ` Auger Eric
2016-10-14 12:42   ` Igor Mammedov
2016-10-14 13:32     ` Andrew Jones
2016-10-14 14:03       ` Auger Eric
2016-10-14  8:54 ` [Qemu-devel] [PATCH v2 2/2] ARM: Virt: ACPI: Build an IORT table with RC and ITS nodes Eric Auger
2016-10-14 11:57   ` Andrew Jones
2016-10-14 12:03     ` Auger Eric
2016-10-14 12:41   ` Igor Mammedov
2016-10-14 13:51     ` Auger Eric
2016-10-14  9:02 ` [Qemu-devel] [PATCH v2 0/2] ACPI IORT generation for ITS support no-reply

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=1476435295-21885-1-git-send-email-eric.auger@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=christoffer.dall@linaro.org \
    --cc=drjones@redhat.com \
    --cc=eric.auger.pro@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=prem.mallappa@broadcom.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.org \
    --cc=tn@semihalf.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).