From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: pbonzini@redhat.com, thomas.lendacky@amd.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] KVM: x86: use CPUID to locate host page table reserved bits" failed to apply to 5.4-stable tree
Date: Sun, 9 Feb 2020 14:58:05 -0500 [thread overview]
Message-ID: <20200209195805.GW3584@sasha-vm> (raw)
In-Reply-To: <158125147044100@kroah.com>
On Sun, Feb 09, 2020 at 01:31:10PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.4-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 7adacf5eb2d2048045d9fd8fdab861fd9e7e2e96 Mon Sep 17 00:00:00 2001
>From: Paolo Bonzini <pbonzini@redhat.com>
>Date: Wed, 4 Dec 2019 15:50:27 +0100
>Subject: [PATCH] KVM: x86: use CPUID to locate host page table reserved bits
>
>The comment in kvm_get_shadow_phys_bits refers to MKTME, but the same is actually
>true of SME and SEV. Just use CPUID[0x8000_0008].EAX[7:0] unconditionally if
>available, it is simplest and works even if memory is not encrypted.
>
>Cc: stable@vger.kernel.org
>Reported-by: Tom Lendacky <thomas.lendacky@amd.com>
>Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
For 5.4 it was just due to a file rename, I've fixed it and queued it
up. 4.19 still needs a backport.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-02-09 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 12:31 FAILED: patch "[PATCH] KVM: x86: use CPUID to locate host page table reserved bits" failed to apply to 5.4-stable tree gregkh
2020-02-09 19:58 ` Sasha Levin [this message]
2020-02-09 20:05 ` Sasha Levin
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=20200209195805.GW3584@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.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