From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: use CPUID to locate host page table reserved bits
Date: Wed, 11 Dec 2019 16:36:40 +0000 [thread overview]
Message-ID: <20191211163641.91567206A5@mail.kernel.org> (raw)
In-Reply-To: <1575471060-55790-1-git-send-email-pbonzini@redhat.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.4.2, v5.3.15, v4.19.88, v4.14.158, v4.9.206, v4.4.206.
v5.4.2: Build OK!
v5.3.15: Failed to apply! Possible dependencies:
Unable to calculate
v4.19.88: Failed to apply! Possible dependencies:
7b6f8a06e482 ("kvm: x86: Move kvm_set_mmio_spte_mask() from x86.c to mmu.c")
f3ecb59dd49f ("kvm: x86: Fix reserved bits related calculation errors caused by MKTME")
v4.14.158: Failed to apply! Possible dependencies:
7b6f8a06e482 ("kvm: x86: Move kvm_set_mmio_spte_mask() from x86.c to mmu.c")
f3ecb59dd49f ("kvm: x86: Fix reserved bits related calculation errors caused by MKTME")
v4.9.206: Failed to apply! Possible dependencies:
114df303a7ee ("kvm: x86: reduce collisions in mmu_page_hash")
28a1f3ac1d0c ("kvm: x86: Set highest physical address bits in non-present/reserved SPTEs")
312b616b30d8 ("kvm: x86: mmu: Set SPTE_SPECIAL_MASK within mmu.c")
37f0e8fe6b10 ("kvm: x86: mmu: Do not use bit 63 for tracking special SPTEs")
66d73e12f278 ("KVM: X86: MMU: no mmu_notifier_seq++ in kvm_age_hva")
83ef6c8155c0 ("kvm: x86: mmu: Refactor accessed/dirty checks in mmu_spte_update/clear")
97dceba29a6a ("kvm: x86: mmu: Fast Page Fault path retries")
daa07cbc9ae3 ("KVM: x86: fix L1TF's MMIO GFN calculation")
dcdca5fed5f6 ("x86: kvm: mmu: make spte mmio mask more explicit")
ea4114bcd3a8 ("kvm: x86: mmu: Rename spte_is_locklessly_modifiable()")
f160c7b7bb32 ("kvm: x86: mmu: Lockless access tracking for Intel CPUs without EPT A bits.")
f3ecb59dd49f ("kvm: x86: Fix reserved bits related calculation errors caused by MKTME")
v4.4.206: Failed to apply! Possible dependencies:
018aabb56d61 ("KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct")
0e3d0648bd90 ("KVM: x86: MMU: always set accessed bit in shadow PTEs")
114df303a7ee ("kvm: x86: reduce collisions in mmu_page_hash")
14f4760562e4 ("kvm: set page dirty only if page has been writable")
28a1f3ac1d0c ("kvm: x86: Set highest physical address bits in non-present/reserved SPTEs")
37f0e8fe6b10 ("kvm: x86: mmu: Do not use bit 63 for tracking special SPTEs")
83ef6c8155c0 ("kvm: x86: mmu: Refactor accessed/dirty checks in mmu_spte_update/clear")
8d5cf1610da5 ("kvm: mmu: extend the is_present check to 32 bits")
daa07cbc9ae3 ("KVM: x86: fix L1TF's MMIO GFN calculation")
ea4114bcd3a8 ("kvm: x86: mmu: Rename spte_is_locklessly_modifiable()")
f160c7b7bb32 ("kvm: x86: mmu: Lockless access tracking for Intel CPUs without EPT A bits.")
f3ecb59dd49f ("kvm: x86: Fix reserved bits related calculation errors caused by MKTME")
ffb128c89b77 ("kvm: mmu: don't set the present bit unconditionally")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
prev parent reply other threads:[~2019-12-11 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 14:51 [PATCH] KVM: x86: use CPUID to locate host page table reserved bits Paolo Bonzini
2019-12-04 15:29 ` Sean Christopherson
2019-12-04 15:36 ` Paolo Bonzini
2019-12-11 16:36 ` Sasha Levin [this message]
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=20191211163641.91567206A5@mail.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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