linux-kernel - Re: [PATCH 0/6] [PULL REQUEST] Intel IOMMU updates for Linux v6.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <64405aee-0701-5b1f-084a-f0750372a563@linux.intel.com>
Date:   Mon, 26 Sep 2022 20:38:09 +0800
From:   Baolu Lu <baolu.lu@...ux.intel.com>
To:     Joerg Roedel <joro@...tes.org>
Cc:     baolu.lu@...ux.intel.com, iommu@...ts.linux.dev,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] [PULL REQUEST] Intel IOMMU updates for Linux v6.1

Hi Joerg,

On 2022/9/26 20:15, Joerg Roedel wrote:
> Hi Baolu,
> 
> On Fri, Sep 23, 2022 at 08:42:00AM +0800, Lu Baolu wrote:
>> Lu Baolu (5):
>>    iommu/vt-d: Remove unnecessary SVA data accesses in page fault path
>>    iommu/vt-d: Decouple PASID & PRI enabling from SVA
>>    iommu/vt-d: Remove pasid_set_eafe()
>>    iommu/vt-d: Avoid unnecessary global IRTE cache invalidation
>>    iommu/vt-d: Avoid unnecessary global DMA cache invalidation
>>
>> Yi Liu (1):
>>    iommu/vt-d: Rename cap_5lp_support to cap_fl5lp_support
> 
> These don't apply cleanly on v6.0-rc4 or -rc7. Please rebase these
> patches to my x86/vt-d branch and re-send.

This pull request is based on the next branch. There's a conflict
between

de9f8a91eb32 iommu/dma: Clean up Kconfig (core branch)

and

iommu/vt-d: Decouple PASID & PRI enabling from SVA (this series).

Do you prefer applying de9f8a91eb32 to vt-d branch, or let me send a new
v6.0-rc7 based pull request?

Best regards,
baolu