<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>c5529418 - x86/sev: Carve out and export SNP guest messaging init routines</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/virt/coco/sev-guest/Kconfig#c5529418</link>
        <description>x86/sev: Carve out and export SNP guest messaging init routinesCurrently, the sev-guest driver is the only user of SNP guest messaging. Allroutines for initializing SNP guest messaging are implemented within thesev-guest driver and are not available during early boot.In preparation for adding Secure TSC guest support, carve out APIs to allocateand initialize the guest messaging descriptor context and make it part ofcoco/sev/core.c. As there is no user of sev_guest_platform_data anymore,remove the structure.Signed-off-by: Nikunj A Dadhania &lt;nikunj@amd.com&gt;Signed-off-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;Reviewed-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;Link: https://lore.kernel.org/r/20250106124633.1418972-4-nikunj@amd.com

            List of files:
            /linux-6.15/drivers/virt/coco/sev-guest/Kconfig</description>
        <pubDate>Mon, 06 Jan 2025 12:46:23 +0000</pubDate>
        <dc:creator>Nikunj A Dadhania &lt;nikunj@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>f3476bc7 - virt: sev-guest: Use AES GCM crypto library</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/virt/coco/sev-guest/Kconfig#f3476bc7</link>
        <description>virt: sev-guest: Use AES GCM crypto libraryThe sev-guest driver encryption code uses the crypto API for SNP guestmessaging with the AMD Security processor. In order to enable secure TSC,SEV-SNP guests need to send such a TSC_INFO message before the APs arebooted. Details from the TSC_INFO response will then be used to program theVMSA before the APs are brought up.However, the crypto API is not available this early in the boot process.In preparation for moving the encryption code out of sev-guest to supportsecure TSC and to ease review, switch to using the AES GCM libraryimplementation instead.Drop __enc_payload() and dec_payload() helpers as both are small and can bemoved to the respective callers.Signed-off-by: Nikunj A Dadhania &lt;nikunj@amd.com&gt;Signed-off-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;Reviewed-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;Acked-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;Tested-by: Peter Gonda &lt;pgonda@google.com&gt;Link: https://lore.kernel.org/r/20241009092850.197575-2-nikunj@amd.com

            List of files:
            /linux-6.15/drivers/virt/coco/sev-guest/Kconfig</description>
        <pubDate>Wed, 09 Oct 2024 09:28:32 +0000</pubDate>
        <dc:creator>Nikunj A Dadhania &lt;nikunj@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>f4790678 - virt: sevguest: Add TSM_REPORTS support for SNP_GET_EXT_REPORT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/virt/coco/sev-guest/Kconfig#f4790678</link>
        <description>virt: sevguest: Add TSM_REPORTS support for SNP_GET_EXT_REPORTThe sevguest driver was a first mover in the confidential computingspace. As a first mover that afforded some leeway to build the driverwithout concern for common infrastructure.Now that sevguest is no longer a singleton [1] the common operation ofbuilding and transmitting attestation report blobs can / should be madecommon. In this model the so called &quot;TSM-provider&quot; implementations canshare a common envelope ABI even if the contents of that envelope remainvendor-specific. When / if the industry agrees on an attestation recordformat, that definition can also fit in the same ABI. In the meantimethe kernel&apos;s maintenance burden is reduced and collaboration on thecommons is increased.Convert sevguest to use CONFIG_TSM_REPORTS to retrieve the data thatthe SNP_GET_EXT_REPORT ioctl produces. An example flow follows forretrieving the report blob via the TSM interface utility,assuming no nonce and VMPL==2:    report=/sys/kernel/config/tsm/report/report0    mkdir $report    echo 2 &gt; $report/privlevel    dd if=/dev/urandom bs=64 count=1 &gt; $report/inblob    hexdump -C $report/outblob # SNP report    hexdump -C $report/auxblob # cert_table    rmdir $reportGiven that the platform implementation is free to return emptycertificate data if none is available it lets configfs-tsm be simplifiedas it only needs to worry about wrapping SNP_GET_EXT_REPORT, and leaveSNP_GET_REPORT alone.The old ioctls can be lazily deprecated, the main motivation of thiseffort is to stop the proliferation of new ioctls, and to increasecross-vendor collaboration.Link: http://lore.kernel.org/r/64961c3baf8ce_142af829436@dwillia2-xfh.jf.intel.com.notmuch [1]Cc: Borislav Petkov &lt;bp@alien8.de&gt;Cc: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;Cc: Dionna Glaze &lt;dionnaglaze@google.com&gt;Cc: Jeremi Piotrowski &lt;jpiotrowski@linux.microsoft.com&gt;Tested-by: Kuppuswamy Sathyanarayanan &lt;sathyanarayanan.kuppuswamy@linux.intel.com&gt;Tested-by: Alexey Kardashevskiy &lt;aik@amd.com&gt;Reviewed-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/virt/coco/sev-guest/Kconfig</description>
        <pubDate>Wed, 11 Oct 2023 03:03:19 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>84b9b44b - virt: sevguest: Add CONFIG_CRYPTO dependency</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/virt/coco/sev-guest/Kconfig#84b9b44b</link>
        <description>virt: sevguest: Add CONFIG_CRYPTO dependencyThis driver fails to link when CRYPTO is disabled, or in a loadablemodule:  WARNING: unmet direct dependencies detected for CRYPTO_GCM  WARNING: unmet direct dependencies detected for CRYPTO_AEAD2    Depends on [m]: CRYPTO [=m]    Selected by [y]:    - SEV_GUEST [=y] &amp;&amp; VIRT_DRIVERS [=y] &amp;&amp; AMD_MEM_ENCRYPT [=y]x86_64-linux-ld: crypto/aead.o: in function `crypto_register_aeads&apos;:Fixes: fce96cf04430 (&quot;virt: Add SEV-SNP guest driver&quot;)Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;Link: https://lore.kernel.org/r/20230117171416.2715125-1-arnd@kernel.org

            List of files:
            /linux-6.15/drivers/virt/coco/sev-guest/Kconfig</description>
        <pubDate>Tue, 17 Jan 2023 17:13:56 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>d63670d2 - virt: sevguest: Rename the sevguest dir and files to sev-guest</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/virt/coco/sev-guest/Kconfig#d63670d2</link>
        <description>virt: sevguest: Rename the sevguest dir and files to sev-guestRename the drivers/virt/coco/sevguest directory and files to sev-guestso as to match the driver name.  [ bp: Rename Documentation/virt/coco/sevguest.rst too, as reported by sfr:    https://lore.kernel.org/r/20220427101059.3bf55262@canb.auug.org.au ]Signed-off-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;Link: https://lore.kernel.org/r/2f5c9cb16e3a67599c8e3170f6c72c8712c47d53.1650464054.git.thomas.lendacky@amd.com

            List of files:
            /linux-6.15/drivers/virt/coco/sev-guest/Kconfig</description>
        <pubDate>Wed, 20 Apr 2022 14:14:14 +0000</pubDate>
        <dc:creator>Tom Lendacky &lt;thomas.lendacky@amd.com&gt;</dc:creator>
    </item>
</channel>
</rss>
