Bug 1790667

Summary:	[RFE][RHEL7] Add cpu family, cpu model, cpu stepping, and NUMA information to lshw
Product:	Red Hat Enterprise Linux 7	Reporter:	Matthew Whitehead <mwhitehe>
Component:	lshw	Assignee:	lijiang
Status:	CLOSED ERRATA	QA Contact:	Jeff Bastian <jbastian>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.8	CC:	fhirtz, lijiang, ruyang, rvr
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	7.9
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1794049 (view as bug list)		Environment:
Last Closed:	2020-09-29 20:37:15 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:	1788766, 1794049

Description Matthew Whitehead 2020-01-13 21:08:46 UTC

Description of problem: lshw does not provide cpu information easily obtainable from /proc/cpuinfo. It should provide:

- cpu family
- cpu model
- cpu stepping
- cpu NUMA information (in the style of 'lscpu' NUMA data)


Version-Release number of selected component (if applicable): 7.8


How reproducible: 100%


Steps to Reproduce:
1. Run 'lshw' and it lacks the requested data.


Actual results:
Missing cpu data.

Expected results:
Provide additional cpu data.


Additional info:

Comment 5 Matthew Whitehead 2020-01-22 16:17:12 UTC

Here is the justification offered by the customer:

"Since lshw has decided to pull in things like all the cpu flags, which are also present in /proc/cpuinfo, then they should also pull in stepping, family, etc. Why should we need to pull from multiple sources when one will do?"

Comment 6 lijiang 2020-03-30 09:43:53 UTC

Merged in upstream: f914f225975b ("report CPU family/model/stepping"). Please refer to the comment#3 in the bz1794049. Thanks.

Comment 27 errata-xmlrpc 2020-09-29 20:37:15 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 (lshw 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/RHBA-2020:4018