[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6935249b454e9_1003f1006d@dwillia2-mobl4.notmuch>
Date: Sat, 6 Dec 2025 22:54:19 -0800
From: <dan.j.williams@...el.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
<dan.j.williams@...el.com>, Alexey Kardashevskiy <aik@....com>, Joerg Roedel
<joerg.roedel@....com>, Vasant Hegde <vasant.hegde@....com>, Tom Lendacky
<thomas.lendacky@....com>
CC: <linux-coco@...ts.linux.dev>, <linux-pci@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Xu Yilun <yilun.xu@...ux.intel.com>, "Aneesh
Kumar K.V (Arm)" <aneesh.kumar@...nel.org>
Subject: Re: [GIT PULL] PCIe Link Encryption and Device Authentication
Linus Torvalds wrote:
[..]
> So if you have AMD_IOMMU enabled without KVM_AMD_SEV you end up with a
> broken build:
>
> ERROR: modpost: "amd_iommu_sev_tio_supported"
> [drivers/crypto/ccp/ccp.ko] undefined!
> make[2]: *** [scripts/Makefile.modpost:147: Module.symvers] Error 1
>
> I've pushed out a minimal fix that seems to work for me.
>
> Please check - and be more careful. This is _not_ some kind of odd config.
Ack, and ugh, sorry about that. Your:
5e5ea7f61610 iommu/amd: fix SEV-TIO support reporting
Looks good to me, and agree that SEV disabled should be a reasonable
default for folks that have not enabled it previously.
Powered by blists - more mailing lists