From: <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
<dan.j.williams@intel.com>, Alexey Kardashevskiy <aik@amd.com>,
Joerg Roedel <joerg.roedel@amd.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Cc: <linux-coco@lists.linux.dev>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Xu Yilun <yilun.xu@linux.intel.com>,
"Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>
Subject: Re: [GIT PULL] PCIe Link Encryption and Device Authentication
Date: Sat, 6 Dec 2025 22:54:19 -0800 [thread overview]
Message-ID: <6935249b454e9_1003f1006d@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <CAHk-=wh9dTX5eg0+NruSDbOCT_tafsO=a8m3cbhxFBvt-21bxQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2025-12-07 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 3:08 [GIT PULL] PCIe Link Encryption and Device Authentication dan.j.williams
2025-12-06 19:04 ` pr-tracker-bot
2025-12-06 19:21 ` Linus Torvalds
2025-12-07 6:54 ` dan.j.williams [this message]
2025-12-07 15:58 ` Joerg Roedel
2025-12-08 0:56 ` Alexey Kardashevskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6935249b454e9_1003f1006d@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=aik@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=joerg.roedel@amd.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=vasant.hegde@amd.com \
--cc=yilun.xu@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox