Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, suravee.suthikulpanit@amd.com,
	wei.huang2@amd.com, jsnitsel@redhat.com, jgg@ziepe.ca
Subject: Re: [PATCH v7 00/17] iommu/amd: SVA Support (part 3) - refactor support for GCR3 table
Date: Fri, 9 Feb 2024 11:44:41 +0100	[thread overview]
Message-ID: <ZcYCGdZQo82ZcMDD@8bytes.org> (raw)
In-Reply-To: <20240205115615.6053-1-vasant.hegde@amd.com>

On Mon, Feb 05, 2024 at 11:55:58AM +0000, Vasant Hegde wrote:
> Suravee Suthikulpanit (8):
>   iommu/amd: Introduce get_amd_iommu_from_dev()
>   iommu/amd: Introduce struct protection_domain.pd_mode
>   iommu/amd: Introduce per-device GCR3 table
>   iommu/amd: Refactor helper function for setting / clearing GCR3
>   iommu/amd: Refactor attaching / detaching device functions
>   iommu/amd: Refactor protection_domain helper functions
>   iommu/amd: Refactor GCR3 table helper functions
>   iommu/amd: Remove unused GCR3 table parameters from struct protection_domain
> 
> Vasant Hegde (9):
>   iommu/amd: Pass struct iommu_dev_data to set_dte_entry()
>   iommu/amd: Enable Guest Translation before registering devices
>   iommu/amd: Use protection_domain.flags to check page table mode
>   iommu/amd: Add support for device based TLB invalidation
>   iommu/amd: Rearrange GCR3 table setup code
>   iommu: Introduce iommu_group_mutex_assert()
>   iommu/amd: Remove unused flush pasid functions
>   iommu/amd: Rearrange device flush code
>   iommu/amd: Introduce per-device domain ID to fix potential TLB
>     aliasing issue
> 
>  drivers/iommu/amd/amd_iommu.h       |  29 +-
>  drivers/iommu/amd/amd_iommu_types.h |  26 +-
>  drivers/iommu/amd/init.c            |   6 +-
>  drivers/iommu/amd/io_pgtable_v2.c   |  21 +-
>  drivers/iommu/amd/iommu.c           | 627 +++++++++++++---------------
>  drivers/iommu/iommu.c               |  19 +
>  include/linux/iommu.h               |  24 ++
>  7 files changed, 376 insertions(+), 376 deletions(-)

Applied, thanks.

      parent reply	other threads:[~2024-02-09 10:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 11:55 [PATCH v7 00/17] iommu/amd: SVA Support (part 3) - refactor support for GCR3 table Vasant Hegde
2024-02-05 11:55 ` [PATCH v7 01/17] iommu/amd: Pass struct iommu_dev_data to set_dte_entry() Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 02/17] iommu/amd: Enable Guest Translation before registering devices Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 03/17] iommu/amd: Introduce get_amd_iommu_from_dev() Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 04/17] iommu/amd: Introduce struct protection_domain.pd_mode Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 05/17] iommu/amd: Introduce per-device GCR3 table Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 06/17] iommu/amd: Use protection_domain.flags to check page table mode Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 07/17] iommu/amd: Add support for device based TLB invalidation Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 08/17] iommu/amd: Rearrange GCR3 table setup code Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 09/17] iommu: Introduce iommu_group_mutex_assert() Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 10/17] iommu/amd: Refactor helper function for setting / clearing GCR3 Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 11/17] iommu/amd: Refactor attaching / detaching device functions Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 12/17] iommu/amd: Refactor protection_domain helper functions Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 13/17] iommu/amd: Refactor GCR3 table " Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 14/17] iommu/amd: Remove unused flush pasid functions Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 15/17] iommu/amd: Rearrange device flush code Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 16/17] iommu/amd: Remove unused GCR3 table parameters from struct protection_domain Vasant Hegde
2024-02-05 11:56 ` [PATCH v7 17/17] iommu/amd: Introduce per-device domain ID to fix potential TLB aliasing issue Vasant Hegde
2024-02-09 10:44 ` Joerg Roedel [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=ZcYCGdZQo82ZcMDD@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=jsnitsel@redhat.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=wei.huang2@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