[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2] MAINTAINERS: Add myself as an AMD SVM & IOMMU reviewer


  • To: Jan Beulich <jbeulich@xxxxxxxx>, Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx>
  • From: Jason Andryuk <jason.andryuk@xxxxxxx>
  • Date: Thu, 9 Oct 2025 04:19:19 -0400
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=suse.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Y4xIl5OdSlkig+e6ZpoL8aGvzZkMHBQ0pJ1JXmPemjQ=; b=EeEkQXUyz7gsEhR+0vmwz19mc1IHdF3a0eNP7oggTZjsueSFoRYKUNINvOGNC03RdA/2xXP+hFSO+q5OHt8UOi3sMXj+NEJ5OMU/LDKtpgzyIN0vZiyNf6bG4MrW6pz+Z/Urgy/UihY4XpA1MYpx/fTXWqinj7XGotq8vScfdeBXFgZRXl8BMsssddmYLM1Iql0rc4HLgcLmpd5bf9jMseVmmnmtozZa/uJRwcY8exwrl6IPVKAW10yEiBR4A42CZIbFCmm64lb14qJxONrIRPOlZIUGD6GzByMu4gjBJdWcvrsJq9j4si4SZ1MGQoU+kyVg8xwqHVsYiOgrfkMBEA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=CE8r3R8NoOUNlU/ozII1zIhMyrh0h1ChG96nCRRIUKhZqRaOPkCptb4lhFkWXoVz+ETdpF1yvlnojNi2xTLTCEwEvExbvtILOhXO1KlU2stOclksLPMBKZCZehrs5MoLayt55R/jPa6mJ+wcIbgG82kNOXxQg+gkl7JMKE02ce0reS85JGJpIsTfO0YhagkELBNHCfafR2beCAloVf569n13KZ9awnE/hVasyCt2PI0Jgf/rVukvWpA1yrpF5O6k56aaE70dgpSe7qYNlcwym7uGE/4o1jPnCr1fNrlLPBpu5WrFX6s1yyeR3thoTZKQR/u3EH9QIzrJUgibN0LGZA==
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>, "Julien Grall" <julien@xxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 09 Oct 2025 12:53:43 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 2025-10-09 08:36, Jan Beulich wrote:
On 08.10.2025 22:11, Jason Andryuk wrote:
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -220,6 +220,23 @@ F: xen/drivers/acpi/
  F:    xen/include/acpi/
  F:    tools/libacpi/
+AMD IOMMU
+M:     Jan Beulich <jbeulich@xxxxxxxx>
+M:     Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
+M:     Roger Pau Monné <roger.pau@xxxxxxxxxx>
+R:     Jason Andryuk <jason.andryuk@xxxxxxx>
+S:     Supported
+F:     xen/drivers/passthrough/amd/
+
+AMD SVM
+M:     Jan Beulich <jbeulich@xxxxxxxx>
+M:     Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
+M:     Roger Pau Monné <roger.pau@xxxxxxxxxx>
+R:     Jason Andryuk <jason.andryuk@xxxxxxx>
+S:     Supported
+F:     xen/arch/x86/hvm/svm/
+F:     xen/arch/x86/cpu/vpmu_amd.c

What about xen/arch/x86/include/asm/hvm/svm/ ? It didn't need specific
mentioning on the X86 entry, but it would now. Also F: entries generally
want sorting alphabetically as well.

Yes, that all sounds good. I based this on a revert of 8395f275ebd11b4cacb12da09911e7918ccc7518 and alphabetization was incorrect there. Sorry about that.

@@ -601,7 +618,8 @@ M:  Roger Pau Monné <roger.pau@xxxxxxxxxx>
  S:    Supported
  L:    xen-devel@xxxxxxxxxxxxxxxxxxxx
  F:    xen/arch/x86/
-F:     xen/drivers/passthrough/amd/
+X:     xen/arch/x86/hvm/svm/
+X:     xen/arch/x86/cpu/vpmu_amd.c

Didn't the v1 discussion result in there being no need for these X:
entries?

I thought Anthony said they should be split out for proper nesting:

>The exclusion is likely unnecessary, and ./get_maintainer.pl will just
>get the information (email, ...) from every sections that a file match.
>But the duplication is necessary due to the "The meaning of nesting"
>described in the MAINTAINERS file.

I took the second sentence to mean they should remain.

As long as there's agreement, I'd be happy to make adjustments while
committing. Oleksii - I take it that ./MAINTAINERS changes can still go
in pretty freely?

Thanks,
Jason



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.