public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: Nadav Amit <namit@vmware.com>, Will Deacon <will@kernel.org>,
	Jiajun Cao <caojiajun@vmware.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v2 0/4] iommu/amd: Enable page-selective flushes
Date: Fri, 4 Jun 2021 17:38:22 +0200	[thread overview]
Message-ID: <YLpI7tKtsf4l5MlN@8bytes.org> (raw)
In-Reply-To: <20210524224159.32807-1-namit@vmware.com>

Hi Nadav,

[Adding Robin]

On Mon, May 24, 2021 at 03:41:55PM -0700, Nadav Amit wrote:
> Nadav Amit (4):
>   iommu/amd: Fix wrong parentheses on page-specific invalidations

This patch is already upstream in v5.13-rc4. Please rebase to that
version.

>   iommu/amd: Selective flush on unmap
>   iommu/amd: Do not sync on page size changes
>   iommu/amd: Do not use flush-queue when NpCache is on

And I think there have been objections from Robin Murphy on Patch 3,
have those been worked out?

Regards,

	Joerg

  parent reply	other threads:[~2021-06-04 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 22:41 [PATCH v2 0/4] iommu/amd: Enable page-selective flushes Nadav Amit
2021-05-24 22:41 ` [PATCH v2 1/4] iommu/amd: Fix wrong parentheses on page-specific invalidations Nadav Amit
2021-05-24 22:41 ` [PATCH v2 2/4] iommu/amd: Selective flush on unmap Nadav Amit
2021-05-24 22:41 ` [PATCH v2 3/4] iommu/amd: Do not sync on page size changes Nadav Amit
2021-05-24 22:41 ` [PATCH v2 4/4] iommu/amd: Do not use flush-queue when NpCache is on Nadav Amit
2021-06-04 15:38 ` Joerg Roedel [this message]
2021-06-04 17:10   ` [PATCH v2 0/4] iommu/amd: Enable page-selective flushes Nadav Amit
2021-06-04 18:53     ` Robin Murphy
2021-06-04 19:57       ` Nadav Amit

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=YLpI7tKtsf4l5MlN@8bytes.org \
    --to=joro@8bytes.org \
    --cc=caojiajun@vmware.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nadav.amit@gmail.com \
    --cc=namit@vmware.com \
    --cc=robin.murphy@arm.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