Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1326928 +++
RHELSA 7.3 will be based on Linux 4.5. We are asked to backport KVM patches from Linux 4.6 and 4.7 (whichever versions applicable). So far we have divided the target patches based on sub-components (e.g. PMU, VHE, VGIC optimization, etc) and we have created BZs for each sub-component. There are still smaller patches that are required for RHELSA 7.3. This BZ is created to capture all of them.
Related:
BZ1260100, BZ1290593, BZ1326893, BZ1326920
--- Additional comment from RHEL Product and Program Management on 2016-04-13 21:16:16 CEST ---
Since this bug report was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
--- Additional comment from Andrew Jones on 2016-04-18 19:32:54 CEST ---
More fixes to take
57c841f131ef2 arm/arm64: KVM: Handle out-of-RAM cache maintenance as a NOP
1c5631c73fc22 KVM: arm/arm64: Handle forward time correction gracefully
b2740d3533a3f KVM: ensure __gfn_to_pfn_memslot initializes *writable
Patches I think we should take for context
13720a56edbd8 arm64: KVM: Move kvm/hyp/hyp.h to include/asm/kvm_hyp.h
6d50d54cd80cb arm64: KVM: Move vgic-v2 and timer save/restore to virt/kvm/arm/hyp
21a4179ce0a12 arm64: KVM: Move __cpu_init_stage2 after kvm_call_hyp
22b39ca3f22ac arm64: KVM: Move kvm_call_hyp back to its original localtion
A patch that isn't a fix, but looks like a good idea
6b6de68c63eda KVM: halt_polling: improve grow/shrink setting
This bug is cloned from bug 1326928, which addressed several backports. The commits I listed (which are also listed in comment 0 of this bug) still need to be backported though.
(In reply to Andrew Jones from comment #2)
> Closing, as we will now address each bug/feature separately for 7.3, rather
> than with "mini-rebase" bugs.
Actually, to be more specific for the plans for the commits listed in this bug
57c841f131ef2 arm/arm64: KVM: Handle out-of-RAM cache maintenance as a NOP
1c5631c73fc22 KVM: arm/arm64: Handle forward time correction gracefully
were posted under bug 1326928
We can live without
b2740d3533a3f KVM: ensure __gfn_to_pfn_memslot initializes *writable
as it just silences a static checker. The context we can bring as needed.
6b6de68c63eda KVM: halt_polling: improve grow/shrink setting
is currently unnecessary.
I'll live this BZ closed as not-a-bug, but could as well close it as current-release, as we got what we wanted already.