All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Woods, Brian" <Brian.Woods@amd.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"Woods, Brian" <Brian.Woods@amd.com>,
	"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [Xen-devel] [PATCH v5 00/10] AMD IOMMU: further improvements
Date: Thu, 15 Aug 2019 22:30:28 +0000	[thread overview]
Message-ID: <20190815223025.GA29402@amd.com> (raw)
In-Reply-To: <5a4d4a61-a543-c657-8458-cbc6b5a8a633@suse.com>

On Tue, Aug 06, 2019 at 03:05:36PM +0200, Jan Beulich wrote:
> Only the first patch here is left from v4, everything else is new,
> yet still related. The main goal is to reduce the huge memory
> overhead that we've noticed. On the way there a number of other
> things were once again noticed. Unfortunately before I was able to
> also test the last two patches there, my Rome box broke again.
> Hence these two patches have been tested on a (less affected)
> Fam15 system only.
> 
> 01: miscellaneous DTE handling adjustments
> 02: drop stray "else"
> 03: don't free shared IRT multiple times
> 04: introduce a "valid" flag for IVRS mappings
> 05: let callers of amd_iommu_alloc_intremap_table() handle errors
> 06: don't blindly allocate interrupt remapping tables
> 07: make phantom functions share interrupt remapping tables
> 08: x86/PCI: read MSI-X table entry count early
> 09: replace INTREMAP_ENTRIES
> 10: restrict interrupt remapping table sizes
> 
> Full set of patches once again attached here due to still unresolved
> email issues over here.
> 
> Jan
> 

I don't think I have enough time here left to review these, but I've
tested them via PCI device passthrough on an AMD Rome system.

-- 
Brian Woods

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2019-08-15 22:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 13:05 [Xen-devel] [PATCH v5 00/10] AMD IOMMU: further improvements Jan Beulich
2019-08-06 13:07 ` [Xen-devel] [PATCH v5 01/10] AMD/IOMMU: miscellaneous DTE handling adjustments Jan Beulich
2019-08-06 20:11   ` Woods, Brian
2019-08-06 13:08 ` [Xen-devel] [PATCH v5 02/10] AMD/IOMMU: drop stray "else" Jan Beulich
2019-08-07  9:48   ` Andrew Cooper
2019-08-07  9:58     ` Jan Beulich
2019-08-08 16:30   ` Woods, Brian
2019-08-06 13:08 ` [Xen-devel] [PATCH v5 03/10] AMD/IOMMU: don't free shared IRT multiple times Jan Beulich
2019-09-17 12:42   ` Andrew Cooper
2019-08-06 13:08 ` [Xen-devel] [PATCH v5 04/10] AMD/IOMMU: introduce a "valid" flag for IVRS mappings Jan Beulich
2019-09-17 12:45   ` Andrew Cooper
2019-08-06 13:09 ` [Xen-devel] [PATCH v5 05/10] AMD/IOMMU: let callers of amd_iommu_alloc_intremap_table() handle errors Jan Beulich
2019-09-17 12:47   ` Andrew Cooper
2019-08-06 13:09 ` [Xen-devel] [PATCH v5 06/10] AMD/IOMMU: don't blindly allocate interrupt remapping tables Jan Beulich
2019-09-17 13:10   ` Andrew Cooper
2019-09-18  8:55     ` Jan Beulich
2019-09-18 11:36       ` Andrew Cooper
2019-09-18 13:01         ` Jan Beulich
2019-08-06 13:09 ` [Xen-devel] [PATCH v5 07/10] AMD/IOMMU: make phantom functions share " Jan Beulich
2019-09-17 13:20   ` Andrew Cooper
2019-08-06 13:10 ` [Xen-devel] [PATCH v5 08/10] x86/PCI: read MSI-X table entry count early Jan Beulich
2019-08-06 14:25   ` Roger Pau Monné
2019-08-06 14:47     ` Jan Beulich
2019-08-06 15:16       ` Roger Pau Monné
2019-08-06 15:24         ` Jan Beulich
2019-09-17 13:29   ` Andrew Cooper
2019-08-06 13:11 ` [Xen-devel] [PATCH v5 09/10] AMD/IOMMU: replace INTREMAP_ENTRIES Jan Beulich
2019-09-17 15:08   ` Andrew Cooper
2019-08-06 13:11 ` [Xen-devel] [PATCH v5 10/10] AMD/IOMMU: restrict interrupt remapping table sizes Jan Beulich
2019-09-17 15:30   ` Andrew Cooper
2019-09-18  8:11     ` Jan Beulich
2019-09-18 10:45       ` Andrew Cooper
2019-09-18 12:31         ` Jan Beulich
2019-08-15 22:30 ` Woods, Brian [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=20190815223025.GA29402@amd.com \
    --to=brian.woods@amd.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.