linux-kernel - Re: [PATCH RESEND 2] intel_iommu: disable all VT-d PMRs when TXT launched

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] [day] [month] [year] [list]

Message-ID: <20110421224415.GG9569@sequoia.sous-sol.org>
Date:	Thu, 21 Apr 2011 15:44:15 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Joseph Cihula <joseph.cihula@...el.com>
Cc:	"dwmw2@...radead.org" <dwmw2@...radead.org>,
	"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	akpm@...ux-foundation.org, "Wei, Gang" <gang.wei@...el.com>
Subject: Re: [PATCH RESEND 2] intel_iommu: disable all VT-d PMRs when TXT
 launched

* Joseph Cihula (joseph.cihula@...el.com) wrote:
> This patch detects when the kernel has been launched with TXT and then
> disables the PMRs on all VT-d engines.  In some cases where the reason
> that remapping is not being enabled is due to possible ACPI DMAR table
> errors, the VT-d engine addresses may not be correct and thus not able
> to be safely programmed even to disable PMRs.  Because part of the TXT
> launch process is the verification of these addresses, it will always be
> safe to disable PMRs if the TXT launch has succeeded and hence only
> doing this in such cases.

What about on resume?  The ->ignored units won't get PMR disabled.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/