Bug 2066824

Summary: Aarch64: Drop unsupported CPU types
Product: Red Hat Enterprise Linux 9 Reporter: Andrew Jones <drjones>
Component: qemu-kvmAssignee: Guowen Shan <gshan>
qemu-kvm sub component: CPU Models QA Contact: Zhenyu Zhang <zhenyzha>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: chayang, coli, jinzhao, juzhang, lijin, mrezanin, nilal, qizhu, virt-maint, yfu, zhenyzha
Version: 9.1Keywords: RFE, TestOnly, Triaged
Target Milestone: rc   
Target Release: 9.1   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-7.0.0-8.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2064757 Environment:
Last Closed: 2022-11-15 09:54:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2060839    
Bug Blocks: 1924294    

Description Andrew Jones 2022-03-22 14:32:24 UTC
+++ This bug was initially created as a clone of Bug #2064757 +++

We rebase qemu-kvm regularly to lower backporting costs and to support new features. As QEMU 7.0.0 is release we are going to rebase to this version for RHEL 9.

Comment 1 Andrew Jones 2022-03-22 14:54:58 UTC
*** Bug 2066823 has been marked as a duplicate of this bug. ***

Comment 3 Andrew Jones 2022-05-30 13:26:52 UTC
Unfortunately, even though we can drop five CPU types, keeping only three total, because we still keep at least one TCG CPU type, we don't save anything with respect to code size. I tried to remove files that appeared to provide TCG support for 32-bit CPU types, but the TCG code is too intertwined. I was able to remove target/arm/cpu_tcg.c from the build, but it was mostly commented out for RHEL already and its functions are only initializers with almost no logic anyway.

So, the question is, do we still want to remove unsupported CPU types just to make sure nobody uses them?

Comment 6 Andrew Jones 2022-06-01 09:09:27 UTC
(In reply to Andrew Jones from comment #3)
> So, the question is, do we still want to remove unsupported CPU types just
> to make sure nobody uses them?

We discussed this in our weekly call. We've decided, yes, we want to enforce our decision to not support certain CPU types by removing them.

Comment 7 Nitesh Narayan Lal 2022-06-01 13:26:37 UTC
(In reply to Andrew Jones from comment #6)
> (In reply to Andrew Jones from comment #3)
> > So, the question is, do we still want to remove unsupported CPU types just
> > to make sure nobody uses them?
> 
> We discussed this in our weekly call. We've decided, yes, we want to enforce
> our decision to not support certain CPU types by removing them.

Luiz, Drew, is it possible to set the DTM for this so that QE can plan the testing accordingly?
Thanks

Comment 22 Guowen Shan 2022-07-05 00:05:38 UTC
The fix will be merged through bug 2060839 and MR-94. What we need to
do is test it after MR-94 gets merged.

https://bugzilla.redhat.com/show_bug.cgi?id=2060839
https://gitlab.com/redhat/centos-stream/src/qemu-kvm/-/merge_requests/94

Comment 23 Guowen Shan 2022-07-08 00:29:22 UTC
MR-94 for bug 2060839 is merged to qemu-kvm-7.0.0-8.el9. Move this to ON_QA.

Comment 28 errata-xmlrpc 2022-11-15 09:54:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: qemu-kvm security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7967