From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-kernel 0/2] cherry-picks and config-options for downfall
Date: Fri, 11 Aug 2023 18:04:30 +0200 [thread overview]
Message-ID: <20230811180430.62a7a43b@rosa.proxmox.com> (raw)
In-Reply-To: <20230811160105.379662-1-s.ivanov@proxmox.com>
On Fri, 11 Aug 2023 18:01:02 +0200
Stoiko Ivanov <s.ivanov@proxmox.com> wrote:
please ignore this - I accidentally sent a patch too many (which got
removed in the moderation queue)
the actual series is the next thread on the list
> Changes taken from ubuntu's repository (at launchpad)
> sending as individual cherry-picks, as we're currently based on our
> own tag.
>
> Split into 2 patches as applying the patches happens after we copy the
> source (and remove debian/ubuntu specific folders)
>
> The resulting build should in all cases be tested on an affected machine too!
>
> Stoiko Ivanov (2):
> add fixes for downfall
> d/rules: enable mitigation config-options
>
> debian/rules | 4 +-
> ...-init-Provide-arch_cpu_finalize_init.patch | 85 +++
> ...cpu-Switch-to-arch_cpu_finalize_init.patch | 235 +++++++
> ...cpu-Switch-to-arch_cpu_finalize_init.patch | 82 +++
> ...cpu-Switch-to-arch_cpu_finalize_init.patch | 80 +++
> ...cpu-Switch-to-arch_cpu_finalize_init.patch | 89 +++
> ...cpu-Switch-to-arch_cpu_finalize_init.patch | 108 ++++
> ...cpu-Switch-to-arch_cpu_finalize_init.patch | 217 +++++++
> ...cpu-Switch-to-arch_cpu_finalize_init.patch | 80 +++
> ...cpu-Switch-to-arch_cpu_finalize_init.patch | 75 +++
> ...022-init-Remove-check_bugs-leftovers.patch | 172 +++++
> ...nvoke-arch_cpu_finalize_init-earlier.patch | 64 ++
> ...m_encrypt_init-into-arch_cpu_finaliz.patch | 121 ++++
> ...it-Initialize-signal-frame-size-late.patch | 81 +++
> ...cpuinfo-argument-from-init-functions.patch | 76 +++
> ...7-x86-fpu-Mark-init-functions-__init.patch | 44 ++
> ...-initialization-into-arch_cpu_finali.patch | 80 +++
> ...-Unbreak-the-AMD_MEM_ENCRYPT-n-build.patch | 69 ++
> ...ondary-processors-FPU-initialization.patch | 42 ++
> ...-Add-Gather-Data-Sampling-mitigation.patch | 595 ++++++++++++++++++
> ...n-Add-force-option-to-GDS-mitigation.patch | 172 +++++
> ...eculation-Add-Kconfig-option-for-GDS.patch | 75 +++
> .../0034-KVM-Add-GDS_NO-support-to-KVM.patch | 85 +++
> ...6-Fix-backwards-on-off-logic-about-Y.patch | 38 ++
> 24 files changed, 2768 insertions(+), 1 deletion(-)
> create mode 100644 patches/kernel/0013-init-Provide-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0014-x86-cpu-Switch-to-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0015-ARM-cpu-Switch-to-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0016-ia64-cpu-Switch-to-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0017-m68k-cpu-Switch-to-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0018-mips-cpu-Switch-to-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0019-sh-cpu-Switch-to-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0020-sparc-cpu-Switch-to-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0021-um-cpu-Switch-to-arch_cpu_finalize_init.patch
> create mode 100644 patches/kernel/0022-init-Remove-check_bugs-leftovers.patch
> create mode 100644 patches/kernel/0023-init-Invoke-arch_cpu_finalize_init-earlier.patch
> create mode 100644 patches/kernel/0024-init-x86-Move-mem_encrypt_init-into-arch_cpu_finaliz.patch
> create mode 100644 patches/kernel/0025-x86-init-Initialize-signal-frame-size-late.patch
> create mode 100644 patches/kernel/0026-x86-fpu-Remove-cpuinfo-argument-from-init-functions.patch
> create mode 100644 patches/kernel/0027-x86-fpu-Mark-init-functions-__init.patch
> create mode 100644 patches/kernel/0028-x86-fpu-Move-FPU-initialization-into-arch_cpu_finali.patch
> create mode 100644 patches/kernel/0029-x86-mem_encrypt-Unbreak-the-AMD_MEM_ENCRYPT-n-build.patch
> create mode 100644 patches/kernel/0030-x86-xen-Fix-secondary-processors-FPU-initialization.patch
> create mode 100644 patches/kernel/0031-x86-speculation-Add-Gather-Data-Sampling-mitigation.patch
> create mode 100644 patches/kernel/0032-x86-speculation-Add-force-option-to-GDS-mitigation.patch
> create mode 100644 patches/kernel/0033-x86-speculation-Add-Kconfig-option-for-GDS.patch
> create mode 100644 patches/kernel/0034-KVM-Add-GDS_NO-support-to-KVM.patch
> create mode 100644 patches/kernel/0035-Documentation-x86-Fix-backwards-on-off-logic-about-Y.patch
>
next prev parent reply other threads:[~2023-08-11 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 16:01 Stoiko Ivanov
2023-08-11 16:01 ` [pve-devel] [PATCH pve-kernel 2/2] d/rules: enable mitigation config-options Stoiko Ivanov
2023-08-11 16:04 ` Stoiko Ivanov [this message]
2023-08-11 16:02 [pve-devel] [PATCH pve-kernel 0/2] cherry-picks and config-options for downfall Stoiko Ivanov
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=20230811180430.62a7a43b@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-devel@lists.proxmox.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