Hi Joshua,
I have received feedback for HP-UX Systems:
Itanium Systems:
# model
ia64 hp server rx3600
# machinfo
CPU info:
Number of CPUs = 4
Number of enabled CPUs = 4
Number of enabled sockets = 2
Cores per socket = 2
Clock speed = 1595 MHz
Bus speed = 532 MT/s
CPUID registers
vendor information = "GenuineIntel"
processor serial number = 0x0000000000000000
processor version info = 0x0000000020000704
architecture revision: 0
processor family: 32 Intel(R) Itanium 2 9000 series
processor model: 0 Intel(R) Itanium 2 9000 series
Bus features
implemented = 0xbdf0000020000000
selected = 0x0000000000000000
processor revision: 7 Stepping C2
largest CPUID reg: 4
processor capabilities = 0x0000000000000005
implements long branch: 1
implements 16-byte atomic operations: 1
Cache info (per core):
L1 Instruction: size = 16 KB, associativity = 4
L1 Data: size = 16 KB, associativity = 4
L2 Instruction: size = 1024 KB, associativity = 8
L2 Data: size = 256 KB, associativity = 8
L3 Unified: size = 9216 KB, associativity = 9
Memory = 32737 MB (31.969727 GB)
Firmware info:
Firmware revision = 04.03
FP SWA driver revision: 1.18
IPMI is supported on this system.
BMC version: 5.23
Platform info:
model string = "ia64 hp server rx3600"
machine id number = ae85bea3-922e-11db-ae7d-78d4cfe3c72b
machine serial number = DEH464608N
OS info:
sysname = HP-UX
nodename = XXXXXXXXX
release = B.11.23
version = U (unlimited-user license)
machine = ia64
idnumber = 2928000675
vmunix _release_version:
@(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
PA-RISC-Systems:
===================
cstm>il
-- Converting multiple raw log files to text. --
Preparing the Information Tool Log for each selected device...
CPU Information:
Number of CPUs in the system = 4
CPU Map
cpu -----------------------------------------
slot | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 |
state|caM |ca |ca |ca | | | | |
-----------------------------------------
| 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 |
state| | | | | | | | |
-----------------------------------------
c - Configured (CPU powered on)
d - De-configured (CPU powered off)
a - Active (configured and processes running)
i - Inactive (configured and idle)
M - Monarch CPU (always Active)
C - Marked for re-configuration (Configured after next boot)
D - Marked for de-configuration (De-configured after next boot)
=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=
hth,
Martin
On Oct 22, 2013, at 8:27 AM, Martin Alfke <tux...@gmail.com> wrote:
> Hi Joshua,
>
> I will have time this weekend to check cpuinfo on Debian on my PPC64.
> I try to get someone involved with access to HP-UX.
>
> - Martin
>
> On Oct 22, 2013, at 4:17 AM, Joshua Hoblitt <jhobl...@cpan.org> wrote:
>
>> It's been a week and I haven't gotten a single response. Does anyone
>> actually use those platforms? :)
>>
>> -Josh
>>
>> --
>> On 10/13/2013 02:41 PM, Joshua Hoblitt wrote:
>>> Hi Folks,
>>>
>>> I'm looking at tidying up the way /proc/cpuinfo is parsed in facter and
>>> the in tree fixture examples for any kernel other than linux i386/amd64
>>> are pretty sparse. This is makes refactoring hairy as there are regexps
>>> and other assumptions baked into the code for these formats without any
>>> comments or test coverage. Examples for these platforms [which appear
>>> to] support cpuinfo would be immensely helpful:
>>>
>>> * aix
>>> * hpux
>>> * kfreebsd
>>> * linux
>>> - parisc
>>> - hppa
>>> - ia64
>>> - ppc64
>>> - arm
>>> - sparc
>>>
>>> My PR to migrate the existing in tree examples to
>>> facter/spec/fixtures/cpuinfo/ was recently merged and I believe
>>> everything under that path is a Linux example. I'd like to move all of
>>> those examples again to ../cpuinfo/linux and start introducing examples
>>> for other kernels under facter/spec/fixtures/cpuinfo/<kernel>/.
>>>
>>> Thanks,
>>>
>>> -Josh
>>>
>>> --
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
