Bug 1343016

Summary:	RFE: Record 'address sizes' field
Product:	[Retired] Beaker	Reporter:	Dr. David Alan Gilbert <dgilbert>
Component:	inventory	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	develop	CC:	jtluka, mjia
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-21 14:13:43 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:

Description Dr. David Alan Gilbert 2016-06-06 10:43:37 UTC

Description of problem:
CPUs typically have a pair of limits on their 'address space size', on x86 this is shown in /proc/cpuinfo as:
   address sizes	: 46 bits physical, 48 bits virtual

other architectures typically have similar limits (typically also physical and virtual although they may have other names for it).

Please record these values as two separate key/value pairs so that a user could search beaker for machines with a particular range of values for specific tests.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dan Callaghan 2016-06-07 06:04:33 UTC

Is this kernel-specific, or hardware-specific, or both?

Comment 2 Dr. David Alan Gilbert 2016-06-07 08:02:40 UTC

(In reply to Dan Callaghan from comment #1)
> Is this kernel-specific, or hardware-specific, or both?

Hardware only I think.

Dave