From: Vasant Hegde via iommu <iommu@lists.linux-foundation.org>
To: iommu@lists.linux-foundation.org, joro@8bytes.org
Subject: Re: [RESEND PATCH v1 00/37] iommu/amd: Add multiple PCI segments support
Date: Tue, 12 Apr 2022 20:27:15 +0530 [thread overview]
Message-ID: <a17ce6a4-4378-7dc1-0c97-1f9bf6900461@amd.com> (raw)
In-Reply-To: <20220404100023.324645-1-vasant.hegde@amd.com>
Hi Joerg,
On 4/4/2022 3:29 PM, Vasant Hegde via iommu wrote:
> Newer AMD systems can support multiple PCI segments, where each segment
> contains one or more IOMMU instances. However, an IOMMU instance can only
> support a single PCI segment.
>
Did you get a chance to look into this series?
Thanks
-Vasant
> Current code assumes a system contains only one PCI segment (segment 0)
> and creates global data structures such as device table, rlookup table,
> etc.
>
> This series introduces per-PCI-segment data structure, which contains
> device table, alias table, etc. For each PCI segment, all IOMMUs
> share the same data structure. The series also makes necessary code
> adjustment and logging enhancements. Finally it removes global data
> structures like device table, alias table, etc.
>
> In case of system w/ single PCI segment (e.g. PCI segment ID is zero),
> IOMMU driver allocates one PCI segment data structure, which will
> be shared by all IOMMUs.
>
> Patch 1 Updates struct iommu_dev_data defination.
>
> Patch 2 - 13 introduce new PCI segment structure and allocate per
> data structures, and introduce the amd_iommu.pci_seg pointer to point
> to the corresponded pci_segment structure. Also, we have introduced
> a helper function rlookup_amd_iommu() to reverse-lookup each iommu
> for a particular device.
>
> Patch 14 - 29 adopt to per PCI segment data structure and removes
> global data structure.
>
> Patch 30 fixes flushing logic to flush upto last_bdf.
>
> Patch 31 - 37 convert usages of 16-bit PCI device ID to include
> 16-bit segment ID.
>
>
> RFC patchset : https://lore.kernel.org/linux-iommu/20220311094854.31595-1-vasant.hegde@amd.com/T/#t
>
> Changes in RFC -> v1:
> - Rebased patches on top of iommu/next tree.
> - Update struct iommu_dev_data defination
> - Updated few log message to print segment ID
> - Fix smatch warnings
>
>
> Regards,
> Vasant
>
>
> Suravee Suthikulpanit (21):
> iommu/amd: Introduce per PCI segment device table
> iommu/amd: Introduce per PCI segment rlookup table
> iommu/amd: Introduce per PCI segment old_dev_tbl_cpy
> iommu/amd: Introduce per PCI segment alias_table
> iommu/amd: Convert to use rlookup_amd_iommu helper function
> iommu/amd: Update irq_remapping_alloc to use IOMMU lookup helper function
> iommu/amd: Introduce struct amd_ir_data.iommu
> iommu/amd: Update amd_irte_ops functions
> iommu/amd: Update alloc_irq_table and alloc_irq_index
> iommu/amd: Update set_dte_entry and clear_dte_entry
> iommu/amd: Update iommu_ignore_device
> iommu/amd: Update dump_dte_entry
> iommu/amd: Update set_dte_irq_entry
> iommu/amd: Update (un)init_device_table_dma()
> iommu/amd: Update set_dev_entry_bit() and get_dev_entry_bit()
> iommu/amd: Remove global amd_iommu_dev_table
> iommu/amd: Remove global amd_iommu_alias_table
> iommu/amd: Introduce get_device_sbdf_id() helper function
> iommu/amd: Include PCI segment ID when initialize IOMMU
> iommu/amd: Specify PCI segment ID when getting pci device
> iommu/amd: Add PCI segment support for ivrs_ioapic, ivrs_hpet, ivrs_acpihid commands
>
> Vasant Hegde (16):
> iommu/amd: Update struct iommu_dev_data defination
> iommu/amd: Introduce pci segment structure
> iommu/amd: Introduce per PCI segment irq_lookup_table
> iommu/amd: Introduce per PCI segment dev_data_list
> iommu/amd: Introduce per PCI segment unity map list
> iommu/amd: Introduce per PCI segment last_bdf
> iommu/amd: Introduce per PCI segment device table size
> iommu/amd: Introduce per PCI segment alias table size
> iommu/amd: Introduce per PCI segment rlookup table size
> iommu/amd: Convert to use per PCI segment irq_lookup_table
> iommu/amd: Convert to use per PCI segment rlookup_table
> iommu/amd: Remove global amd_iommu_last_bdf
> iommu/amd: Flush upto last_bdf only
> iommu/amd: Print PCI segment ID in error log messages
> iommu/amd: Update device_state structure to include PCI seg ID
> iommu/amd: Update amd_iommu_fault structure to include PCI seg ID
>
> .../admin-guide/kernel-parameters.txt | 34 +-
> drivers/iommu/amd/amd_iommu.h | 13 +-
> drivers/iommu/amd/amd_iommu_types.h | 127 +++-
> drivers/iommu/amd/init.c | 683 +++++++++++-------
> drivers/iommu/amd/iommu.c | 540 ++++++++------
> drivers/iommu/amd/iommu_v2.c | 67 +-
> drivers/iommu/amd/quirks.c | 4 +-
> 7 files changed, 884 insertions(+), 584 deletions(-)
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2022-04-12 14:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 9:59 [RESEND PATCH v1 00/37] iommu/amd: Add multiple PCI segments support Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 01/37] iommu/amd: Update struct iommu_dev_data defination Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 02/37] iommu/amd: Introduce pci segment structure Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 03/37] iommu/amd: Introduce per PCI segment device table Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 04/37] iommu/amd: Introduce per PCI segment rlookup table Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 05/37] iommu/amd: Introduce per PCI segment irq_lookup_table Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 06/37] iommu/amd: Introduce per PCI segment dev_data_list Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 07/37] iommu/amd: Introduce per PCI segment old_dev_tbl_cpy Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 08/37] iommu/amd: Introduce per PCI segment alias_table Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 09/37] iommu/amd: Introduce per PCI segment unity map list Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 10/37] iommu/amd: Introduce per PCI segment last_bdf Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 11/37] iommu/amd: Introduce per PCI segment device table size Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 12/37] iommu/amd: Introduce per PCI segment alias " Vasant Hegde via iommu
2022-04-04 9:59 ` [RESEND PATCH v1 13/37] iommu/amd: Introduce per PCI segment rlookup " Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 14/37] iommu/amd: Convert to use per PCI segment irq_lookup_table Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 15/37] iommu/amd: Convert to use rlookup_amd_iommu helper function Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 16/37] iommu/amd: Update irq_remapping_alloc to use IOMMU lookup " Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 17/37] iommu/amd: Introduce struct amd_ir_data.iommu Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 18/37] iommu/amd: Update amd_irte_ops functions Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 19/37] iommu/amd: Update alloc_irq_table and alloc_irq_index Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 20/37] iommu/amd: Convert to use per PCI segment rlookup_table Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 21/37] iommu/amd: Update set_dte_entry and clear_dte_entry Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 22/37] iommu/amd: Update iommu_ignore_device Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 23/37] iommu/amd: Update dump_dte_entry Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 24/37] iommu/amd: Update set_dte_irq_entry Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 25/37] iommu/amd: Update (un)init_device_table_dma() Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 26/37] iommu/amd: Update set_dev_entry_bit() and get_dev_entry_bit() Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 27/37] iommu/amd: Remove global amd_iommu_dev_table Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 28/37] iommu/amd: Remove global amd_iommu_alias_table Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 29/37] iommu/amd: Remove global amd_iommu_last_bdf Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 30/37] iommu/amd: Flush upto last_bdf only Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 31/37] iommu/amd: Introduce get_device_sbdf_id() helper function Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 32/37] iommu/amd: Include PCI segment ID when initialize IOMMU Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 33/37] iommu/amd: Specify PCI segment ID when getting pci device Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 34/37] iommu/amd: Add PCI segment support for ivrs_ioapic, ivrs_hpet, ivrs_acpihid commands Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 35/37] iommu/amd: Print PCI segment ID in error log messages Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 36/37] iommu/amd: Update device_state structure to include PCI seg ID Vasant Hegde via iommu
2022-04-04 10:00 ` [RESEND PATCH v1 37/37] iommu/amd: Update amd_iommu_fault " Vasant Hegde via iommu
2022-04-12 14:57 ` Vasant Hegde via iommu [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=a17ce6a4-4378-7dc1-0c97-1f9bf6900461@amd.com \
--to=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=vasant.hegde@amd.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