e intel_iommu_tboot_noforce
> from tboot code to intel iommu code.
>
> Fixes: 7304e8f28bb2 ("iommu/vt-d: Correctly disable Intel IOMMU force on")
> Signed-off-by: Zhenzhong Duan
> ---
> v2: move ckeck of intel_iommu_tboot_noforce into iommu code per Baolu.
>
Tested-by: Lukasz Hawrylko
Hi Zhenzhong
On Tue, 2020-11-10 at 15:19 +0800, Zhenzhong Duan wrote:
> "intel_iommu=off" command line is used to disable iommu but iommu is force
> enabled in a tboot system for security reason.
>
> However for better performance on high speed network device, a new option
> "intel_iommu=tboot_no
Hi Thomas and Ingo
May I ask you to merge this patch? I got an acknowledgement from
previous owner, I hope that this is enough for that change.
Thanks,
Lukasz
On Mon, 2020-08-24 at 15:08 +, Sun, Ning wrote:
> Acknowledged.
>
> -Ning
>
> -Original Message-
> Fro
As an effect of changes in Intel, I took resposibility for supporting
Intel TXT in Linux from Ning Sun. This patch also replaces link to
repository, as previous one became outdated.
Signed-off-by: Lukasz Hawrylko
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Hi Daniel
On Thu, 2020-05-07 at 13:06 +0200, Daniel Kiper wrote:
> > There is a function that verifies if platform is TXT capable
> > -grub_txt_verify_platform(), it only checks SMX and GETSEC features.
> > Although BIOS should enforce both VMX and VT-d enabled when enabling
> > TXT, I think that
On Tue, 2020-05-05 at 01:21 +0200, Daniel Kiper wrote:
> Hi,
>
> This is an RFC patchset for the GRUB introducing the Intel TXT secure
> launcher.
> This is a part of larger work known as the TrenchBoot. Patchset can be split
> into two distinct parts:
> - 01-12: preparatory patches,
> - 13-1
6 matches
Mail list logo
