linux-kernel - Re: [PATCH] iommu/amd: Override wrong IVRS IOAPIC on Raven Ridge systems

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: <9CDD544D-DE4C-4AC6-B0DC-CD30C99EA71C@canonical.com>
Date:   Tue, 13 Aug 2019 11:58:48 +0800
From:   Kai-Heng Feng <kai.heng.feng@...onical.com>
To:     Joerg Roedel <joro@...tes.org>
Cc:     iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iommu/amd: Override wrong IVRS IOAPIC on Raven Ridge
 systems

at 23:39, Joerg Roedel <joro@...tes.org> wrote:

> On Thu, Aug 08, 2019 at 06:17:07PM +0800, Kai-Heng Feng wrote:
>> Raven Ridge systems may have malfunction touchpad or hang at boot if
>> incorrect IVRS IOAPIC is provided by BIOS.
>>
>> Users already found correct "ivrs_ioapic=" values, let's put them inside
>> kernel to workaround buggy BIOS.
>
> Will that still work when a fixed BIOS for these laptops is released?

Do you mean that we should stop applying these quirks once a BIOS fix is  
confirmed?

We can modify the quirk to compare BIOS version, if there’s an unlikely  
BIOS update really fixes the issue.
Before that happens, I think it’s OK to let the quirks stay this way.

Kai-Heng

>
>
> 	Joerg