From: Joerg Roedel <joro@8bytes.org>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux-foundation.org
Subject: Re: [PATCH v3 00/35] iommu/amd: Add multiple PCI segments support
Date: Fri, 20 May 2022 12:03:02 +0200 [thread overview]
Message-ID: <YodnVsHH8B6ypep0@8bytes.org> (raw)
In-Reply-To: <3b3b668f-64e1-1713-9126-59c7313bd894@amd.com>
Hi Vasant,
On Fri, May 20, 2022 at 03:25:38PM +0530, Vasant Hegde wrote:
> Ping. Did you get a chance to look into this series?
Sorry, too late for this round. The changes are pretty invasive and
merging them at -rc7 stage would not give them enough testing before
being merged. Please send me a reminder after the next merge window.
Regards,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-05-20 10:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 7:21 [PATCH v3 00/35] iommu/amd: Add multiple PCI segments support Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 01/35] iommu/amd: Update struct iommu_dev_data definition Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 02/35] iommu/amd: Introduce pci segment structure Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 03/35] iommu/amd: Introduce per PCI segment device table Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 04/35] iommu/amd: Introduce per PCI segment rlookup table Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 05/35] iommu/amd: Introduce per PCI segment irq_lookup_table Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 06/35] iommu/amd: Introduce per PCI segment dev_data_list Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 07/35] iommu/amd: Introduce per PCI segment old_dev_tbl_cpy Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 08/35] iommu/amd: Introduce per PCI segment alias_table Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 09/35] iommu/amd: Introduce per PCI segment unity map list Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 10/35] iommu/amd: Introduce per PCI segment last_bdf Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 11/35] iommu/amd: Introduce per PCI segment device table size Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 12/35] iommu/amd: Introduce per PCI segment alias " Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 13/35] iommu/amd: Introduce per PCI segment rlookup " Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 14/35] iommu/amd: Convert to use per PCI segment irq_lookup_table Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 15/35] iommu/amd: Convert to use rlookup_amd_iommu helper function Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 16/35] iommu/amd: Update irq_remapping_alloc to use IOMMU lookup " Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 17/35] iommu/amd: Introduce struct amd_ir_data.iommu Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 18/35] iommu/amd: Update amd_irte_ops functions Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 19/35] iommu/amd: Update alloc_irq_table and alloc_irq_index Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 20/35] iommu/amd: Convert to use per PCI segment rlookup_table Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 21/35] iommu/amd: Update set_dte_entry and clear_dte_entry Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 22/35] iommu/amd: Update iommu_ignore_device Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 23/35] iommu/amd: Update dump_dte_entry Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 24/35] iommu/amd: Update set_dte_irq_entry Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 25/35] iommu/amd: Update (un)init_device_table_dma() Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 26/35] iommu/amd: Update set_dev_entry_bit() and get_dev_entry_bit() Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 27/35] iommu/amd: Remove global amd_iommu_[dev_table/alias_table/last_bdf] Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 28/35] iommu/amd: Flush upto last_bdf only Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 29/35] iommu/amd: Introduce get_device_sbdf_id() helper function Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 30/35] iommu/amd: Include PCI segment ID when initialize IOMMU Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 31/35] iommu/amd: Specify PCI segment ID when getting pci device Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 32/35] iommu/amd: Add PCI segment support for ivrs_[ioapic/hpet/acpihid] commands Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 33/35] iommu/amd: Print PCI segment ID in error log messages Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 34/35] iommu/amd: Update device_state structure to include PCI seg ID Vasant Hegde via iommu
2022-05-11 7:21 ` [PATCH v3 35/35] iommu/amd: Update amd_iommu_fault " Vasant Hegde via iommu
2022-05-20 9:55 ` [PATCH v3 00/35] iommu/amd: Add multiple PCI segments support Vasant Hegde via iommu
2022-05-20 10:03 ` Joerg Roedel [this message]
2022-05-20 12:12 ` Vasant Hegde via iommu
2022-06-07 10:47 ` Vasant Hegde via iommu
2022-06-22 9:59 ` Vasant Hegde via iommu
2022-06-23 7:54 ` Joerg Roedel
2022-06-28 7:49 ` Vasant Hegde via iommu
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=YodnVsHH8B6ypep0@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).