From: Baolu Lu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] [PULL REQUEST] Intel IOMMU updates for Linux v6.2
Date: Tue, 22 Nov 2022 17:41:19 +0800 [thread overview]
Message-ID: <25981cc9-243e-bece-4e85-86f3c880d96f@linux.intel.com> (raw)
In-Reply-To: <Y3yRMXGPcYbXH9uL@8bytes.org>
Hi Joerg,
On 2022/11/22 17:06, Joerg Roedel wrote:
> Hi Baolu,
>
> On Tue, Nov 22, 2022 at 08:29:42AM +0800, Lu Baolu wrote:
>> Lu Baolu (7):
>> iommu/vt-d: Allocate pasid table in device probe path
>> iommu/vt-d: Add device_block_translation() helper
>> iommu/vt-d: Add blocking domain support
>> iommu/vt-d: Rename iommu_disable_dev_iotlb()
>> iommu/vt-d: Rename domain_add_dev_info()
>> iommu/vt-d: Remove unnecessary domain_context_mapped()
>> iommu/vt-d: Use real field for indication of first level
>
> Applied the first 6 patches. The last one has conflicts and doesn't
> apply on top of my x86/vt-d branch. Could you please have a look please?
I guess the last patch conflicts with below commit:
242b0aaeabbe ("iommu/vt-d: Preset Access bit for IOVA in FL non-leaf
paging entries")
which was merged in v6.1-rc6. Can you please bring the x86/vt-d branch
to v6.1-rc6, or do you want me to rebase that patch on the existing top
of the branch?
Best regards,
baolu
next prev parent reply other threads:[~2022-11-22 9:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 0:29 [PATCH 0/7] [PULL REQUEST] Intel IOMMU updates for Linux v6.2 Lu Baolu
2022-11-22 0:29 ` [PATCH 1/7] iommu/vt-d: Allocate pasid table in device probe path Lu Baolu
2022-11-22 0:29 ` [PATCH 2/7] iommu/vt-d: Add device_block_translation() helper Lu Baolu
2022-11-22 0:29 ` [PATCH 3/7] iommu/vt-d: Add blocking domain support Lu Baolu
2022-11-22 0:29 ` [PATCH 4/7] iommu/vt-d: Rename iommu_disable_dev_iotlb() Lu Baolu
2022-11-22 0:29 ` [PATCH 5/7] iommu/vt-d: Rename domain_add_dev_info() Lu Baolu
2022-11-22 0:29 ` [PATCH 6/7] iommu/vt-d: Remove unnecessary domain_context_mapped() Lu Baolu
2022-11-22 0:29 ` [PATCH 7/7] iommu/vt-d: Use real field for indication of first level Lu Baolu
2022-11-22 9:06 ` [PATCH 0/7] [PULL REQUEST] Intel IOMMU updates for Linux v6.2 Joerg Roedel
2022-11-22 9:41 ` Baolu Lu [this message]
2022-11-22 13:06 ` 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=25981cc9-243e-bece-4e85-86f3c880d96f@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.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