From: Joerg Roedel <joro@8bytes.org>
To: Nadav Amit <namit@vmware.com>
Cc: "iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>, Will Deacon <will@kernel.org>,
Jiajun Cao <caojiajun@vmware.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iommu/amd: page-specific invalidations for more than one page
Date: Thu, 8 Apr 2021 09:18:48 +0200 [thread overview]
Message-ID: <YG6uWFAS6GCWJPGO@8bytes.org> (raw)
In-Reply-To: <71C74038-943D-4041-B6FF-09A8C40CA204@vmware.com>
Hi Nadav,
On Wed, Apr 07, 2021 at 05:57:31PM +0000, Nadav Amit wrote:
> I tested it on real bare-metal hardware. I ran some basic I/O workloads
> with the IOMMU enabled, checkers enabled/disabled, and so on.
>
> However, I only tested the IOMMU-flushes and I did not test that the
> device-IOTLB flush work, since I did not have the hardware for that.
>
> If you can refer me to the old patches, I will have a look and see
> whether I can see a difference in the logic or test them. If you want
> me to run different tests - let me know. If you want me to remove
> the device-IOTLB invalidations logic - that is also fine with me.
Here is the patch-set, it is from 2010 and against a very old version of
the AMD IOMMU driver:
https://lore.kernel.org/lkml/1265898797-32183-1-git-send-email-joerg.roedel@amd.com/
Regards,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-04-08 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 21:06 [PATCH] iommu/amd: page-specific invalidations for more than one page Nadav Amit
2021-04-07 10:01 ` Joerg Roedel
2021-04-07 17:57 ` Nadav Amit
2021-04-08 7:18 ` Joerg Roedel [this message]
2021-04-08 10:29 ` Nadav Amit
2021-04-08 13:23 ` Joerg Roedel
2021-04-08 15:16 ` Joerg Roedel
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=YG6uWFAS6GCWJPGO@8bytes.org \
--to=joro@8bytes.org \
--cc=caojiajun@vmware.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@vmware.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;
as well as URLs for NNTP newsgroup(s).