Bug 1443020

Summary:	Allow armv7m_systick device for aarch64
Product:	Red Hat Enterprise Linux 7	Reporter:	Miroslav Rezanina <mrezanin>
Component:	qemu-kvm-rhev	Assignee:	Miroslav Rezanina <mrezanin>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.4	CC:	chayang, drjones, juzhang, mtessun, philmd, virt-maint
Target Milestone:	rc	Keywords:	FutureFeature, OtherQA
Target Release:	7.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	qemu-kvm-rhev-2.9.0-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 07:34:11 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:
Bug Blocks:	1173755

Description Miroslav Rezanina 2017-04-18 10:09:50 UTC

In QEMU 2.9, functionality of armv7m_systick timer was moved to separate device. Keep this device supported.

Comment 2 Wei Huang (AMD) 2017-04-18 14:14:00 UTC

I support the proposal of keeping armv7m_systick in qemu-rhev-2.9 with the following reasons:

1) Right now armv7m_nvic is an integrated part of QEMU ARM code. In fact target/arm/helper.c calls armv7m_nvic functions directly. QEMU compilation will fail without armv7m_nvic.
2) armv7m_nvic.c initializes TYPE_SYSTICK object. If we didn't keep armv7m_systick, object dependency will fail.

Combining (1) and (2), I think we should keep armv7m_systick.

Comment 5 RHEL Program Management 2021-01-15 07:34:11 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.