From: Joerg Roedel <joro@8bytes.org>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, will@kernel.org, robin.murphy@arm.com,
suravee.suthikulpanit@amd.com, jgg@ziepe.ca
Subject: Re: [PATCH v4 00/12] iommu/amd: Improve domain allocator and device attach code path
Date: Tue, 29 Oct 2024 11:15:09 +0100 [thread overview]
Message-ID: <ZyC1rZJrMqYYebRL@8bytes.org> (raw)
In-Reply-To: <ZyCni2HHjXqivNwl@8bytes.org>
On Tue, Oct 29, 2024 at 10:14:52AM +0100, Joerg Roedel wrote:
> Applied, thanks.
I have to take that back, this series heavily conflicts with the changes
in the core branch. I think I resolved everything, but it looks pretty
messy.
Can you please rebase this series on-top of the latest core branch (I just
pushed the core branch only) and re-send? Backporters of these changes
will be very grateful.
Thanks,
Joerg
next prev parent reply other threads:[~2024-10-29 10:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 11:31 [PATCH v4 00/12] iommu/amd: Improve domain allocator and device attach code path Vasant Hegde
2024-10-28 11:31 ` [PATCH v4 01/12] iommu/amd/pgtbl_v2: Take protection domain lock before invalidating TLB Vasant Hegde
2024-10-28 15:26 ` Jason Gunthorpe
2024-10-28 11:31 ` [PATCH v4 02/12] iommu/amd: Use ida interface to manage protection domain ID Vasant Hegde
2024-10-28 15:27 ` Jason Gunthorpe
2024-10-28 11:31 ` [PATCH v4 03/12] iommu/amd: Remove protection_domain.dev_cnt variable Vasant Hegde
2024-10-28 11:31 ` [PATCH v4 04/12] iommu/amd: xarray to track protection_domain->iommu list Vasant Hegde
2024-10-28 11:31 ` [PATCH v4 05/12] iommu/amd: Remove unused amd_iommus variable Vasant Hegde
2024-10-28 11:31 ` [PATCH v4 06/12] iommu/amd: Do not detach devices in domain free path Vasant Hegde
2024-10-28 11:31 ` [PATCH v4 07/12] iommu/amd: Reduce domain lock scope in attach device path Vasant Hegde
2024-10-28 15:34 ` Jason Gunthorpe
2024-10-28 11:31 ` [PATCH v4 08/12] iommu/amd: Rearrange attach device code Vasant Hegde
2024-10-28 11:31 ` [PATCH v4 09/12] iommu/amd: Convert dev_data lock from spinlock to mutex Vasant Hegde
2024-10-28 11:31 ` [PATCH v4 10/12] iommu/amd: Reorder attach device code Vasant Hegde
2024-10-28 11:31 ` [PATCH v4 11/12] iommu/amd: Add opa->release_domain Vasant Hegde
2024-10-28 15:35 ` Jason Gunthorpe
2024-10-28 11:31 ` [PATCH v4 12/12] iommu/amd: Improve amd_iommu_release_device() Vasant Hegde
2024-10-28 15:40 ` Jason Gunthorpe
2024-10-29 9:14 ` [PATCH v4 00/12] iommu/amd: Improve domain allocator and device attach code path Joerg Roedel
2024-10-29 10:15 ` Joerg Roedel [this message]
2024-10-29 16:36 ` Vasant Hegde
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=ZyC1rZJrMqYYebRL@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox