From: Joerg Roedel <joro@8bytes.org>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, dwmw2@infradead.org,
robin.murphy@arm.com, alex.williamson@redhat.com,
shameerali.kolothum.thodi@huawei.com,
jean-philippe.brucker@arm.com
Subject: Re: [PATCH v6 0/7] RMRR related fixes and enhancements
Date: Wed, 12 Jun 2019 10:33:28 +0200 [thread overview]
Message-ID: <20190612083328.GD17505@8bytes.org> (raw)
In-Reply-To: <20190603065336.10524-1-eric.auger@redhat.com>
On Mon, Jun 03, 2019 at 08:53:29AM +0200, Eric Auger wrote:
> Eric Auger (7):
> iommu: Fix a leak in iommu_insert_resv_region
> iommu/vt-d: Duplicate iommu_resv_region objects per device list
> iommu/vt-d: Introduce is_downstream_to_pci_bridge helper
> iommu/vt-d: Handle RMRR with PCI bridge device scopes
> iommu/vt-d: Handle PCI bridge RMRR device scopes in
> intel_iommu_get_resv_regions
> iommu: Introduce IOMMU_RESV_DIRECT_RELAXABLE reserved memory regions
> iommu/vt-d: Differentiate relaxable and non relaxable RMRRs
Applied, thanks.
prev parent reply other threads:[~2019-06-12 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 6:53 [PATCH v6 0/7] RMRR related fixes and enhancements Eric Auger
2019-06-03 6:53 ` [PATCH v6 1/7] iommu: Fix a leak in iommu_insert_resv_region Eric Auger
2019-06-03 6:53 ` [PATCH v6 2/7] iommu/vt-d: Duplicate iommu_resv_region objects per device list Eric Auger
2019-06-03 6:53 ` [PATCH v6 3/7] iommu/vt-d: Introduce is_downstream_to_pci_bridge helper Eric Auger
2019-06-03 6:53 ` [PATCH v6 4/7] iommu/vt-d: Handle RMRR with PCI bridge device scopes Eric Auger
2019-06-03 6:53 ` [PATCH v6 5/7] iommu/vt-d: Handle PCI bridge RMRR device scopes in intel_iommu_get_resv_regions Eric Auger
2019-06-03 6:53 ` [PATCH v6 6/7] iommu: Introduce IOMMU_RESV_DIRECT_RELAXABLE reserved memory regions Eric Auger
2019-06-03 6:53 ` [PATCH v6 7/7] iommu/vt-d: Differentiate relaxable and non relaxable RMRRs Eric Auger
2019-06-12 8:33 ` Joerg Roedel [this message]
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=20190612083328.GD17505@8bytes.org \
--to=joro@8bytes.org \
--cc=alex.williamson@redhat.com \
--cc=dwmw2@infradead.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe.brucker@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.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