From owner-freebsd-ppc@freebsd.org Tue Jun 7 16:04:59 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D070BB6E062 for ; Tue, 7 Jun 2016 16:04:59 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 980E21C4B for ; Tue, 7 Jun 2016 16:04:59 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3rPGPK2lMKz1cXL0 for ; Tue, 7 Jun 2016 17:55:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id 5KoNAVUOsbhZ for ; Tue, 7 Jun 2016 17:55:33 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3rPGPK21Fyz1cXKx for ; Tue, 7 Jun 2016 17:55:33 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id D36361B7483 for ; Tue, 7 Jun 2016 17:55:26 +0200 (CEST) Date: Tue, 7 Jun 2016 17:55:25 +0200 From: Luciano Mannucci To: freebsd-ppc@freebsd.org Subject: Re: IBM KVM on P8 saga: FreeBSD-11.0-ALPHA1-powerpc-powerpc64-20160528-r300895 won't boot In-Reply-To: <3fc108e2-d56a-baa2-dae1-54e0704fe789@freebsd.org> References: <3r9Zbp6spTz1cXL0@baobab.bilink.it> <3rJNSk16Hjz1cXKx@baobab.bilink.it> <254582a5-efe3-4ec9-785f-b158b350ec95@freebsd.org> <3rJpbK0kp5z1cXL0@baobab.bilink.it> <3fc108e2-d56a-baa2-dae1-54e0704fe789@freebsd.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3rPGPK21Fyz1cXKx@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2016 16:04:59 -0000 On Thu, 2 Jun 2016 13:45:07 -0700 Nathan Whitehorn wrote: > Interesting. Can you tell me what happens if you add -threads 8 to the > QEMU command line to expose all the threads? Yes. It says: Error starting domain: internal error: process exited while connecting to monitor: qemu-system-ppc64: -threads: invalid option Details: Error starting domain: internal error: process exited while connecting to monitor: qemu-system-ppc64: -threads: invalid option Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1437, in startup self._backend.create() File "/usr/local/lib/python2.7/site-packages/libvirt.py", line 1035, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: process exited while connecting to monitor: qemu-system-ppc64: -threads: invalid option I've added: to the xml domain. Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Tue Jun 7 16:11:02 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9511B6E0EA for ; Tue, 7 Jun 2016 16:11:02 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9FB871E16 for ; Tue, 7 Jun 2016 16:11:02 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net (184-23-18-234.dsl.dynamic.fusionbroadband.com [184.23.18.234]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id u57GB0x1006082 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Tue, 7 Jun 2016 09:11:00 -0700 Subject: Re: IBM KVM on P8 saga: FreeBSD-11.0-ALPHA1-powerpc-powerpc64-20160528-r300895 won't boot To: freebsd-ppc@freebsd.org References: <3r9Zbp6spTz1cXL0@baobab.bilink.it> <3rJNSk16Hjz1cXKx@baobab.bilink.it> <254582a5-efe3-4ec9-785f-b158b350ec95@freebsd.org> <3rJpbK0kp5z1cXL0@baobab.bilink.it> <3fc108e2-d56a-baa2-dae1-54e0704fe789@freebsd.org> <3rPGPK21Fyz1cXKx@baobab.bilink.it> From: Nathan Whitehorn Message-ID: <8826c4e2-0115-fee0-7aef-776b9548b0e4@freebsd.org> Date: Tue, 7 Jun 2016 09:11:00 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <3rPGPK21Fyz1cXKx@baobab.bilink.it> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVboYcycUJz3xKGh24ZF+0DoPltETw94Dek0c1qgo2yxzHFiawLDjwB1JX6VUyrN8gC1dsrBtHMyotphrr+zrGiT2U5L+eevmm8= X-Sonic-ID: C;SJL3bMos5hGacrsdzAjavA== M;nE04bcos5hGacrsdzAjavA== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2016 16:11:03 -0000 You may need to run ppc64_cpu --smt=off on the KVM host first. I can reproduce hangs in late boot without the threads option and am working on it. It would be great if you could file a PR. -Nathan On 06/07/16 08:55, Luciano Mannucci wrote: > On Thu, 2 Jun 2016 13:45:07 -0700 > Nathan Whitehorn wrote: > >> Interesting. Can you tell me what happens if you add -threads 8 to the >> QEMU command line to expose all the threads? > Yes. > It says: > > Error starting domain: internal error: process exited while connecting to monitor: qemu-system-ppc64: -threads: invalid option > > Details: > > Error starting domain: internal error: process exited while connecting to > monitor: qemu-system-ppc64: -threads: invalid option > > > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper > callback(asyncjob, *args, **kwargs) > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb > callback(*args, **kwargs) > File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn > ret = fn(self, *args, **kwargs) > File "/usr/share/virt-manager/virtManager/domain.py", line 1437, in startup > self._backend.create() > File "/usr/local/lib/python2.7/site-packages/libvirt.py", line 1035, in create > if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) > libvirtError: internal error: process exited while connecting to monitor: qemu-system-ppc64: -threads: invalid option > > I've added: > > > > > > to the xml domain. > > Luciano. From owner-freebsd-ppc@freebsd.org Tue Jun 7 16:32:08 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B316B6E836 for ; Tue, 7 Jun 2016 16:32:08 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id C13351F54 for ; Tue, 7 Jun 2016 16:32:07 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3rPHCc6GWSzRRqX for ; Tue, 7 Jun 2016 18:32:12 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id 7e-tp8FnA5Gp for ; Tue, 7 Jun 2016 18:32:12 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3rPHCc5MbQzRRqT for ; Tue, 7 Jun 2016 18:32:12 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 33F2A1B7483 for ; Tue, 7 Jun 2016 18:32:06 +0200 (CEST) Date: Tue, 7 Jun 2016 18:32:05 +0200 From: Luciano Mannucci To: freebsd-ppc@freebsd.org Subject: Re: IBM KVM on P8 saga: FreeBSD-11.0-ALPHA1-powerpc-powerpc64-20160528-r300895 won't boot In-Reply-To: <8826c4e2-0115-fee0-7aef-776b9548b0e4@freebsd.org> References: <3r9Zbp6spTz1cXL0@baobab.bilink.it> <3rJNSk16Hjz1cXKx@baobab.bilink.it> <254582a5-efe3-4ec9-785f-b158b350ec95@freebsd.org> <3rJpbK0kp5z1cXL0@baobab.bilink.it> <3fc108e2-d56a-baa2-dae1-54e0704fe789@freebsd.org> <3rPGPK21Fyz1cXKx@baobab.bilink.it> <8826c4e2-0115-fee0-7aef-776b9548b0e4@freebsd.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3rPHCc5MbQzRRqT@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2016 16:32:08 -0000 On Tue, 7 Jun 2016 09:11:00 -0700 Nathan Whitehorn wrote: > You may need to run ppc64_cpu --smt=off on the KVM host first. I can > reproduce hangs in late boot without the threads option and am working > on it. It would be great if you could file a PR. Here is the result... [root@archimede images]# ppc64_cpu --smt=off [root@archimede images]# virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # edit EPP-IT Domain EPP-IT XML configuration edited. virsh # console EPP-IT Connected to domain EPP-IT Escape character is ^] 00 0800 (D) : 10ec 8139 network [ ethernet ] No NVRAM common partition, re-initializing... Scanning USB OHCI: initializing USB Keyboard USB mouse Using default console: /vdevice/vty@30000000 Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /vdevice/v-scsi@2000/disk@8001000000000000 ... Successfully loaded Consoles: Open Firmware console FreeBSD/powerpc64 Open Firmware loader, Revision 0.1 (root@releng2.nyi.freebsd.org, Fri Jun 3 07:43:43 UTC 2016) Memory: 2097152KB Booted from: /vdevice/v-scsi@2000/disk@8001000000000000 Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0xe9d298+0x423d28 syms=[0x8+0x14b368+0x8+0x147d51] \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 7 seconds... Type '?' for a list of commands, 'help' for more detailed help. OK boot -v Booting... Kernel entry at 0x1024f0 ... KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-ALPHA2 #0 r301230: Fri Jun 3 07:51:47 UTC 2016 root@releng2.nyi.freebsd.org:/usr/obj/powerpc.powerpc64/usr/src/sys/GENERIC64 powerpc gcc version 4.2.1 20070831 patched [FreeBSD] WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. Preloaded elf kernel "/boot/kernel/kernel" at 0x1656000. cpu0: IBM POWER8E revision 2.1, 3425.00 MHz cpu0: Features dc005180 cpu0: Features2 c2000000 real memory = 2110451712 (2012 MB) available KVA = 7650267135 (7295 MB) Physical memory chunk(s): 0x0000000000025000 - 0x00000000000fffff, 897024 bytes (219 pages) 0x0000000001c40000 - 0x0000000001c3ffff, 0 bytes (0 pages) 0x0000000003a49000 - 0x000000007ae67fff, 2000809984 bytes (488479 pages) 0x000000007ffa0000 - 0x000000007ffaffff, 65536 bytes (16 pages) 0x000000007ffb5000 - 0x000000007ffeffff, 241664 bytes (59 pages) 0x000000007fff1000 - 0x000000007fffffff, 61440 bytes (15 pages) 0x0000000001658000 - 0x0000000001bfffff, 5931008 bytes (1448 pages) avail memory = 1989722112 (1897 MB) FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs cpu0: dev=7e5e00b8 (BSP) ULE: setup cpu 0 random: entropy device external interface snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 firmware: 'isp_1040' version 1: 22944 bytes loaded at 0xc54204 firmware: 'isp_1080' version 1: 31350 bytes loaded at 0xc59ba4 firmware: 'isp_12160' version 1: 28050 bytes loaded at 0xc6161a firmware: 'isp_2100' version 1: 76770 bytes loaded at 0xc683ac firmware: 'isp_2200' version 1: 84566 bytes loaded at 0xc7af8e firmware: 'isp_2300' version 1: 125252 bytes loaded at 0xc8f9e4 firmware: 'isp_2322' version 1: 120814 bytes loaded at 0xcae328 firmware: 'isp_2400' version 1: 204384 bytes loaded at 0xccf690 firmware: 'isp_2500' version 1: 223908 bytes loaded at 0xd0f0c0 kbd0 at kbdmux0 mem: nfslock: pseudo-device null: openfirm: random: harvesting attach, 8 bytes (4 bits) from nexus0 ofwbus0: on nexus0 random: harvesting attach, 8 bytes (4 bits) from ofwbus0 xicp0: on ofwbus0 random: harvesting attach, 8 bytes (4 bits) from xicp0 cpulist0: on ofwbus0 cpu0: on cpulist0 random: harvesting attach, 8 bytes (4 bits) from cpu0 cpu1: on cpulist0 random: harvesting attach, 8 bytes (4 bits) from cpu1 cpu2: on cpulist0 random: harvesting attach, 8 bytes (4 bits) from cpu2 cpu3: on cpulist0 random: harvesting attach, 8 bytes (4 bits) from cpu3 cpu4: on cpulist0 random: harvesting attach, 8 bytes (4 bits) from cpu4 cpu5: on cpulist0 random: harvesting attach, 8 bytes (4 bits) from cpu5 random: harvesting attach, 8 bytes (4 bits) from cpulist0 pcib0: on ofwbus0 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x1af4, dev=0x1002, revid=0x00 domain=0, bus=0, slot=3, func=0 class=00-ff-00, hdrtype=0x00, mfdev=0 cmdreg=0x0100, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=0 map[10]: type I/O Port, range 32, base 0x20, size 5, port disabled found-> vendor=0x106b, dev=0x003f, revid=0x00 domain=0, bus=0, slot=2, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=0 map[10]: type Memory, range 32, base 0xc0000000, size 8, enabled found-> vendor=0x10ec, dev=0x8139, revid=0x20 domain=0, bus=0, slot=1, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0100, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=0 map[10]: type I/O Port, range 32, base 0x100, size 8, port disabled map[14]: type Memory, range 32, base 0xc0000100, size 8, memory disabled pci0: at device 3.0 (no driver attached) ohci0: mem 0xc0000000-0xc00000ff irq 4100 at device 2.0 on pci0 ohci0: Mapping IOMMU domain 0x80000000 ofw_pci mapdev: start 100e0000000, len 256 usbus0 on ohci0 ohci0: usbpf: Attached random: harvesting attach, 8 bytes (4 bits) from usbus0 random: harvesting attach, 8 bytes (4 bits) from ohci0 re0: port 0x100-0x1ff mem 0xc0000100-0xc00001ff irq 4099 at device 1.0 on pci0 ofw_pci mapdev: start 100e0000100, len 256 re0: MSI count : 0 re0: MSI-X count : 0 re0: Chip rev. 0x74800000 re0: MAC rev. 0x00000000 re0: Mapping IOMMU domain 0x80000000 miibus0: on re0 rlphy0: PHY 0 on miibus0 rlphy0: OUI 0x000000, model 0x0000, rev. 0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow random: harvesting attach, 8 bytes (4 bits) from rlphy0 random: harvesting attach, 8 bytes (4 bits) from miibus0 re0: Using defaults for TSO: 65518/35/2048 re0: bpf attached re0: Ethernet address: 52:54:00:1a:cd:48 random: harvesting attach, 8 bytes (4 bits) from re0 random: harvesting attach, 8 bytes (4 bits) from pci0 random: harvesting attach, 8 bytes (4 bits) from pcib0 rtas0: on ofwbus0 rtas0: registered as a time-of-day clock (resolution 2000us, adjustment 0.001000000s) random: harvesting attach, 8 bytes (4 bits) from rtas0 vdevice0: on ofwbus0 vscsi0: irq 16781319 on vdevice0 vscsi0: Mapping IOMMU domain 0x2000 vscsi0: Queue depth 22 commands random: harvesting attach, 8 bytes (4 bits) from vscsi0 uart0: irq 16781320 on vdevice0 random: harvesting attach, 8 bytes (4 bits) from uart0 random: harvesting attach, 8 bytes (4 bits) from vdevice0 ofwbus0: compat linux,kvm (no driver attached) procfs registered Timecounter "timebase" frequency 512000000 Hz quality 0 Event timer "decrementer" frequency 512000000 Hz quality 1000 Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining tcp_init: net.inet.tcp.tcbhashsize auto tuned to 16384 lo0: bpf attached usbus0: 12Mbps Full Speed USB v1.0 (probe0:vscsi0:0:0:0): Down reving Protocol Version from 6 to 5? ugen0.1: at usbus0 uhub0: on usbus0 (probe0:vscsi0:0:0:2): Down reving Protocol Version from 6 to 5? (probe0:vscsi0:0:0:1): Down reving Protocol Version from 6 to 5? pass0 at vscsi0 bus 0 scbus0 target 0 lun 0 pass0: Fixed Uninstalled SPC-3 SCSI device (offline) pass0: 150.000MB/s transfers pass1 at vscsi0 bus 0 scbus0 target 0 lun 1 pass1: Removable CD-ROM SPC-3 SCSI device pass1: 150.000MB/s transfers pass2 at vscsi0 bus 0 scbus0 target 0 lun 2 pass2: Fixed Direct Access SPC-3 SCSI device pass2: 150.000MB/s transfers cd0 at vscsi0 bus 0 scbus0 target 0 lun 1 cd0: Removable CD-ROM SPC-3 SCSI device cd0: 150.000MB/s transfers cd0: 695MB (356002 2048 byte sectors) da0 at vscsi0 bus 0 scbus0 target 0 lun 2 da0: Fixed Direct Access SPC-3 SCSI device da0: 150.000MB/s transfers da0: 20480MB (41943040 512 byte sectors) Adding CPU 0, pir=28, awake=1 Waking up CPU 8 (dev=7e5e08d8) Adding CPU 8, pir=20, awake=1 Waking up CPU 16 (dev=7e5e10f8) Adding CPU 16, pir=20, awake=1 Waking up CPU 24 (dev=7e5e1918) Adding CPU 24, pir=20, awake=1 Waking up CPU 32 (dev=7e5e2138) Adding CPU 32, pir=20, awake=1 Waking up CPU 40 (dev=7e5e2958) Adding CPU 40, pir=20, awake=1 SMP: AP CPU #8 launched SMP: AP CPU #32 launched SMP: AP CPU #16 launched SMP: AP CPU #24 launched SMP: AP CPU #40 launched Cheers, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Tue Jun 7 16:51:30 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75FD6B6E804 for ; Tue, 7 Jun 2016 16:51:30 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3D5031139 for ; Tue, 7 Jun 2016 16:51:29 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3rPHdy58G3zRRqV for ; Tue, 7 Jun 2016 18:51:34 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id 6R+CzXKEk5YP for ; Tue, 7 Jun 2016 18:51:34 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3rPHdy4QkZzRRqT for ; Tue, 7 Jun 2016 18:51:34 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 7E9561B7483 for ; Tue, 7 Jun 2016 18:51:28 +0200 (CEST) Date: Tue, 7 Jun 2016 18:51:28 +0200 From: Luciano Mannucci To: freebsd-ppc@freebsd.org Subject: Re: IBM KVM on P8 saga: FreeBSD-11.0-ALPHA1-powerpc-powerpc64-20160528-r300895 won't boot In-Reply-To: <8826c4e2-0115-fee0-7aef-776b9548b0e4@freebsd.org> References: <3r9Zbp6spTz1cXL0@baobab.bilink.it> <3rJNSk16Hjz1cXKx@baobab.bilink.it> <254582a5-efe3-4ec9-785f-b158b350ec95@freebsd.org> <3rJpbK0kp5z1cXL0@baobab.bilink.it> <3fc108e2-d56a-baa2-dae1-54e0704fe789@freebsd.org> <3rPGPK21Fyz1cXKx@baobab.bilink.it> <8826c4e2-0115-fee0-7aef-776b9548b0e4@freebsd.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3rPHdy4QkZzRRqT@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2016 16:51:30 -0000 On Tue, 7 Jun 2016 09:11:00 -0700 Nathan Whitehorn wrote: > It would be great if you could file a PR. Ok, PR filed. Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Wed Jun 8 10:00:30 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B802B6FF60 for ; Wed, 8 Jun 2016 10:00:30 +0000 (UTC) (envelope-from peter.turay@vgtelecomreports.com) Received: from smtp.vgtelecomreports.com (smtp.vgtelecomreports.com [202.0.103.126]) by mx1.freebsd.org (Postfix) with ESMTP id A1B271F4B for ; Wed, 8 Jun 2016 10:00:24 +0000 (UTC) (envelope-from peter.turay@vgtelecomreports.com) X-SmarterMail-Authenticated-As: admin@vgtelecomreports.com DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; d=vgtelecomreports.com; s=smtp; h=received:from:to:message-id:subject:date:mime-version:reply-to :content-type; b=UxgT1U+wmxbEFys+ZExt571ALUUWQKOt+1RsJ7byUwOF+mwElFcOZvldZcAgfvVnO wBYNTtJYd7s0msF8dRq1OQI/ouB9+P5WKTxclSlCjbZTa8BXhHekFlzMQgrq3omJ5 y1a4BzRyhhEtT8g0x4ghNVP8JGYpaBH0O1oSWod6o= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vgtelecomreports.com; s=smtp; h= content-type:reply-to:mime-version:date:subject:message-id:to:from; bh=79l6p5f1AGY7eh7iVvr9/B5Q0ClRIE8Jj82E6uJTsD4=; b=fWmrd1pDKlV03XRbZ1Z9z2UhT73zFTFwmgHJU8cCo4zLgwZ1tl9QQRqxLHSKTO6p4 y2z4q2KzKye1erfbNoFtqj6Lv6+ZulA6mUOsKpuvyPYTQpHFkMq1sahdt/hKjsjFa Ppu0mxyhGJSJYYP3+/OgIjoub1JKRW58lqs8tr42M= Received: from WIN-ASQ29B6R1EP (WIN-ASQ29B6R1EP [202.0.103.127]) by smtp.vgtelecomreports.com with SMTP; Tue, 7 Jun 2016 10:10:44 +0100 From: Peter Turay To: freebsd-ppc@freebsd.org Message-Id: <20160607101044.385901688@vgtelecomreports.com> Subject: Report - Mobile Health (MHealth) Market Forecast 2015-2020 Date: Tue, 7 Jun 2016 10:10:44 +0100 MIME-Version: 1.0 Reply-To: peter.turay@vgtelecomreports.com Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2016 10:00:30 -0000 Mobile Health (MHealth) Market Forecast 2015-2020 Leading Companies in eHealth, Telemedicine, Connected Health, Informatics, EHR, PHR, Fitness Monitoring, & Remote Diagnostics Telecoms Report Publication date: 17th April 2015 Number of Pages: 179 ------------------------------------------------------------ The advent of connected devices and M2M offers a tremendous opportunity for healthcare professionals. Near-ubiquitous mobile networks are allowing carers to diagnose, monitor, and communicate with patients with unprecedented speed and efficacy. The emergence of low-cost smartphones have allowed wider access to app stores, which are now home to over 100,000 unique mHealth apps. These range between freemium apps geared around diet and daily fitness routines, scaling up to costly premium apps with elaborate clinical reference points, images, diagnostic, and monitoring functions. Austerity measures have forced many health departments worldwide to manage their costs, and find more cost-effective ways of operating. Enabling them to diagnose, monitor, and communicate with patients remotely, mHealth promises extensive cost-savings for healthcare professionals and institutions. Furthermore, this new industry pays dividends to network operators, software developers, and data platform management providers who may turn their core competencies onto the medical field. Visiongain calculates the global mHealth market will reach $10.33 billion in 2015. Why order Mobile Health (mHealth) Market 2015-2020: Leading Companies in eHealth, Telemedicine, Connected Health, Informatics, EHR, PHR, Fitness Monitoring, & Remote Diagnostics? What is the future of the mHealth market? Visiongain’s comprehensive analysis contains highly quantitative content that delivers solid conclusions, thereby benefiting your analysis and illustrating new opportunities in the competitive mobile environment. This definitive report will enhance your decision making and help to direct your future business strategy. Our 179-page report will provide you with the following key information: • View global mHealth market forecasts and analysis from 2015-2020, keeping you updated with the latest knowledge and ensure you exploit key business opportunities - Detailed sales projections of the market, its competitors, and the commercial drivers and restraints allowing for more enhanced competitiveness in the marketplace. In addition, our new study shows current market data, original critical analysis, and revealing insight into commercial developments. - Global mHealth revenue forecast - Global mHealth connections forecast • Examine 140 tables, charts, and graphs. - A thorough assessment of the current and future, mHealth market prospects. - Achieve quicker, easier understanding as you gain from our industry expertise, allowing you to demonstrate your authority on the mHealth sector. • Sales predictions for the key end use submarkets from 2015-2020 - What are the dynamics of the mHealth industry? Which submarkets prove to be most lucrative for investment? Use our forecasts and expertise to grow your business and give you more industry influence. Find where you can gain and how your organisation can succeed. Stay informed about the potential for each of these mHealth submarkets with individual forecasts and analysis from 2015-2020. - Medical information, Health records, and Administration submarket forecast 2015-2020 - Remote consultation and Diagnostics submarket forecast 2015-2020 - M2M, Wearable technology, and monitoring submarket forecast 2015-2020 - Disease treatment submarket forecast 2015-2020 • Learn about the market prospects for the leading ecosystem member types from 2015-2020 - How will various value chain members perform over the forecast period? Discover where the highest revenue potential lies from 2015-2020, learning about how mHealth revenue generates through the various market segments. These forecasts will also reveal the competitive landscape. Observe what is happening, including challenges, trends, and market opportunities experienced. Our report reveals forecasts for the 4 leading ecosystem member types as follows : - Network operator revenue forecast 2015-2020 - Device vendor revenue forecast 2015-2020 - Content developer revenue forecast 2015-2020 - Healthcare provider revenue forecast 2015-2020 • Understand the prospects for the 5 regional and the leading 11 national mHealth markets - Learn about the mHealth market's potential in both developed and developing countries from 2015 onwards. Discover where and how opportunities exists for 11 leading national markets by revenue and connections - North America mHealth revenue forecast 2015-2020 - North America mHealth connections forecast 2015-2020 - US mHealth revenue forecast 2015-2020 - US mHealth connections forecast 2015-2020 - Canada mHealth revenue forecast 2015-2020 - Canada mHealth connections forecast 2015-2020 - Latin America mHealth revenue forecast 2015-2020 - Latin America mHealth connections forecast 2015-2020 - Asia Pacific mHealth revenue forecast 2015-2020 - Asia Pacific mHealth connections forecast 2015-2020 - China mHealth revenue forecast 2015-2020 - China mHealth connections forecast 2015-2020 - Japan mHealth revenue forecast 2015-2020 - Japan mHealth connections forecast 2015-2020 - India mHealth revenue forecast 2015-2020 - India mHealth connections forecast 2015-2020 - Australia mHealth revenue forecast 2015-2020 - Australia mHealth connections forecast 2015-2020 - Rest of Asia Pacific mHealth revenue forecast 2015-2020 - Rest of Asia Pacific mHealth connections forecast 2015-2020 - European mHealth revenue forecast 2015-2020 - European mHealth connections forecast 2015-2020 - Germany mHealth revenue forecast 2015-2020 - Germany mHealth connections forecast 2015-2020 - UK mHealth revenue forecast 2015-2020 - UK mHealth connections forecast 2015-2020 - France mHealth revenue forecast 2015-2020 - France mHealth connections forecast 2015-2020 - Italy mHealth revenue forecast 2015-2020 - Italy mHealth connections forecast 2015-2020 - Russia mHealth revenue forecast 2015-2020 - Russia mHealth connections forecast 2015-2020 - Rest of Europe mHealth revenue forecast 2015-2020 - Rest of Europe mHealth connections forecast 2015-2020 - Middle Eastern & Africa mHealth revenue forecast 2015-2020 - Middle Eastern & Africa mHealth connections forecast 2015-2020 • Explore factors affecting mHealth product developers and other stakeholders within the value chain. Learn about the forces influencing market dynamics. - Discover what the present and future outlook for business will be. Learn about the following business critical issues - Research and development (R&D) strategy - Technological issues and constraints. - Competition from new product types - Increasing specialisation by leading players - Increasing industry consolidation. - Advances in product quality - Analysis of barriers to entry • Identify the leading companies are in the mHealth industry - Our report reveals the technologies and companies holding the greatest potential. In particular, exploring and analysing these company's activities. View Visiongain’s assessment of the prospects for established competitors, upcoming companies, and new market entrants. Gain a thorough understanding of the competitive landscape with profiles of 10 leading mHealth companies, examining their positioning, capabilities, product portfolios, R&D activity, services, focus, strategies, M&A activity, and future outlook. - Apple - AT&T - Athenahealth - Boston Scientific - CardioNet - Epocrates - Fitbit - Jawbone - Nike - Vodafone Discover invaluable information found in this independent, mHealth market assessment The Mobile Health (mHealth) Market 2015-2020: Leading Companies in eHealth, Telemedicine, Connected Health, Informatics, EHR, PHR, Fitness Monitoring, & Remote Diagnostics report provides impartial mHealth sector analysis. With our independent business intelligence, you will discover where profitable investments and prospects are. Our new research provides you with key strategic advantages; informed forecasts, independent and objective analysis, exclusive interviews and revealing company profiles, provide you with substantial awareness for effective business execution in the long-term. What makes this report unique? Visiongain’s research methodology involves an exclusive blend of primary and secondary sources providing informed analysis. This allows insight into the key drivers and restraints behind market dynamics and competitive developments. The report therefore presents an ideal balance of qualitative analysis combined with extensive quantitative data, thereby bringing clarity and convenience during the R&D stages. Why choose Visiongain business intelligence? Visiongain’s increasingly, diverse sector coverage strengthens our research portfolio. The growing cross-sector convergence and the interplay of game-changing technologies across multiple industries are creating new synergies, resulting in new business opportunities for you to leverage. As such, Visiongain’s in-house analyst team supplies a wealth of knowledge and experience to inform your strategic business decisions. Order our report - Mobile Health (mHealth) Market 2015-2020: Leading Companies in eHealth, Telemedicine, Connected Health, Informatics, EHR, PHR, Fitness Monitoring, & Remote Diagnostics. ------------------------------------------------------------ Table of Contents 1. Report Overview 1.1 Current mHealth Market Overview 1.2 MHealth Market Segmentation 1.3 Why You Should Read This Report 1.4 How This Report Delivers 1.5 Key Questions Answered by This Analytical Report Include: 1.6 Benefits of this Report 1.7 Who is This Report For? 1.8 Methodology 1.9 Frequently Asked Questions (FAQ) 1.10 Associated Visiongain Reports 1.11 About Visiongain 2. Introduction to the Mobile Health (mHealth) Market 2.1 mHealth Market Structure Overview 2.1.1 Opportunities for Mobile Operators 2.2 Key Definitions 2.2.1 mHealth Definition 2.2.2 eHealth Definition 2.2.3 Telemedicine Definition 2.2.4 Health Informatics Definition 2.3 mHealth Drivers 2.3.1 The role of Developed Economies on the mHealth Market? 2.4 Expected Impact of mHealth 2.5 mHealth App Categories 3. The Global Mobile Health (mHealth) Market Forecasts 2015-2020 3.1 mHealth initiative 3.2 Extensive Growth in mHealth Revenue from 2015-2020 3.2.1 Global mHealth Revenue Forecast by Ecosystem Member Shares 3.2.2 Global mHealth Revenue Forecast by Ecosystem Members 2015-2020 3.2.3 MHealth Revenue by Submarket Share 2015-2020 3.2.4 MHealth Submarket Revenue Forecast 2015-2020 3.3 User Growth in the mHealth Ecosystem 2015-2020 4. Regional and National mHealth Markets 2015-2020 4.1 Regional mHealth Markets Forecast 2015-2020 4.2 Regional mHealth Connection Forecast 2015-2020 4.3 Regional mHealth ARPU Forecast 2015-2020 4.4 The North American mHealth Market 2015-2020 4.4.1 North American mHealth Revenue Forecast 2015-2020 4.4.1.1 US National mHealth Revenue Forecast 2015-2020 4.4.1.2 Canadian National mHealth Revenue Forecast 2015-2020 4.4.2 North American mHealth Connection Forecast 2015-2020 4.4.2.1 US National mHealth Connection Forecast 2015-2020 4.4.2.2 Canadian National mHealth Connection Forecast 2015-2020 4.5 The Latin American mHealth Market 2015-2020 4.5.1 Latin American mHealth Revenue Forecast 2015-2020 4.5.2 Latin American mHealth Connection Forecast 2015-2020 4.6 The Asia-Pacific mHealth Market 2015-2020 4.6.1 Asia-Pacific mHealth Revenue Forecast 2015-2020 4.6.1.1 Leading National Asia-Pacific Markets Revenue Forecast 2015-2020 4.6.2 Asia-Pacific mHealth Connection Forecast 2015-2020 4.6.2.1 Leading National APAC Markets Connection Forecast 2015-2020 4.7 The European mHealth Market 2015-2020 4.7.1 European mHealth Revenue Forecast 2015-2020 4.7.1.1 Leading European National mHealth Markets Revenue 2015-2020 4.7.2 European mHealth Connection Forecast 2015-2020 4.7.2.1 Leading European National mHealth Markets Connection Forecast 2015-2020 4.8 The Middle East and African mHealth Market 2015-2020 4.8.1 Middle East and Africa mHealth Revenue Forecast 2015-2020 4.8.2 Middle East and Africa mHealth Connection Forecast 2015-2020 4.5.3 Middle East and Africa mHealth Projects and Schemes 5. Leading mHealth Companies: Innovators, Disruptors, and Incumbents 5.1 Apple 5.1.1 Apple’s mHealth Strategy 5.1.2 mHealth Apps – Does Apple Have a Monopoly? 5.1.3 Apple and the Healthcare Industry 5.1.4 New Devices, Strategies, and Partnerships 5.1.4.1 Health App a Major First Step for Apple into Fitness 5.1.4.2 Apple Watch 5.1.4.3 Apple Healthkit 5.2 AT&T ForHealth 5.2.1 AT&T mHealth Solutions 5.2.2 Creating Connected mHealth Apps 5.2.3 mHealth Pilot Programs 5.2.3.1 Smart Slippers 5.2.3.2 Employee Diabetes Management 5.2.4 Mobile Resource Management 5.2.5 AT&T Vitality GlowCaps 5.2.6 HipLink 5.3 Athenahealth Inc. 5.3.1 Discovering New Revenue Opportunities in the Digital Age 5.3.2 Reinventing the Healthcare Practice 5.3.3 Athenahealth Current Offerings 5.3.4 Athenahealth Acquires Epocrates 5.3.5 Plunging Deeper into the Hospital Market 5.4 Boston Scientific 5.4.1 Latitude NXT 5.4.2 Partnerships and Remote Monitoring Products at Multi-National Scale 5.5 CardioNet 5.5.1 CardioNet MCOT 5.5.2 MCOT Study 5.5.3 Event and Holter Monitoring 5.6 Epocrates 5.6.1 Epocrates mHealth Offerings 5.6.2 The New “Epocrates Bugs + Drugs” App 5.6.3 Epocrates Monetising mHealth Offerings – Analysis 5.7 Fitbit 5.7.1 Fitbit Tracker 5.7.2 Fitbit Flex 5.7.2.1 Fitbit Force 5.7.3 Fitbit Charge 5.7.3.1 Charge App 5.7.4 Fitbit Surge: Lateral Shift into the Smartwatch Arena 5.7.5 Analysis of the Fitbit Business Model 5.8 Jawbone 5.8.1 Jawbone’s UP Product Line 5.8.1.1 UP24 and Improvements on the Platform 5.8.2 UP 3.0 and UP24 – New Wristband Addition 5.8.3 Jawbone mHealth Acquisitions 5.9 Nike 5.9.1 Nike mHealth Product Overview 5.9.2 Nike+ FuelBand 5.9.2.1The Nike / Apple Monopoly 5.9.2.2 Barriers to FuelBand Uptake 5.9.3 Situating the FuelBand in Nike’s Brand Strategy 5.9.4 FuelBand Analysis and Market Standing 5.10 Vodafone mHealth Solutions 5.10.1 Vodafone mHealth Case Studies 5.10.1.1 TRxCARE and Vodafone Help Improve Patient Care 5.10.1.2 mHealth Clinical Research Patient Reported Outcomes 5.10.2 Vodafone mHealth Professional 5.10.3 Vodafone mHealth Partnerships 5.11 Other mHealth Companies and Leading Products 6. Conclusions and Recommendations 6.1 Mobile Devices Have the Potential to Become Powerful Medical Tools 6.2 Untapped Potential for mHealth 6.3 Overcoming Obstacles to mHealth Uptake 6.4 Recommended Actions for Increasing mHealth Uptake 6.4.1 Maintain Low Costs 6.4.2 Gain the Approval of the Healthcare Industry 6.4.3 Solutions Should Offer Ease of Use and Increased Efficiency 7. Glossary ------------------------------------------------------------ List of Charts Chart 1.1: Italian mHealth Revenue Forecast 2015-2020 ($ bn; AGR %) Chart 3.1: Global mHealth Market Forecast 2015-2020 ($ bn, AGR %) Chart 3.2: Global mHealth Revenue Forecast by Ecosystem Member Shares 2015 (%) Chart 3.3: Global mHealth Revenue Forecast by Ecosystem Member Shares 2017 (%) Chart 3.4: Global mHealth Revenue Forecast by Ecosystem Member Shares 2020 (%) Chart 3.5: Global mHealth Revenue Forecast by Ecosystem Member 2015-2020 (%) Chart 3.6: Global mHealth Revenue Forecast by Submarket Shares 2015 (%) Chart 3.7: Global mHealth Revenue Forecast by Submarket Shares 2017 (%) Chart 3.8: Global mHealth Revenue Forecast by Submarket Share 2020 (%) Chart 3.9: Global mHealth Revenue Forecast by Submarket 2015-2020 (%) Chart 3.10: Global mHealth Connection Forecast 2015-2020 (millions; AGR %) Chart 4.1: Regional mHealth Market Forecast 2015-2020 ($ bn; AGR %) Chart 4.2: Regional mHealth Market Share Forecast 2015 (%) Chart 4.3: Regional mHealth Market Share Forecast 2017 (%) Chart 4.4: Regional mHealth Market Share Forecast 2020 (%) Chart 4.5: Regional mHealth Connection Forecast 2015-2020 (millions; AGR %) Chart 4.6: Regional mHealth Connection Share Forecast 2015 (%) Chart 4.7: Regional mHealth Connection Share Forecast 2017 (%) Chart 4.8: Regional mHealth Connection Share Forecast 2020 (%) Chart 4.9: Regional mHealth ARPU Forecast 2015-2020 ($/year; AGR %) Chart 4.10: North American mHealth Revenue Forecast 2015-2020 ($ bn; AGR %) Chart 4.11: US and Canada National mHealth Revenue Forecast 2015-2020 ($ bn) Chart 4.12: US National mHealth Revenue Forecast 2015-2020 ($ bn; AGR %) Chart 4.13: Canadian National mHealth Revenue Forecast 2015-2020 ($ bn; AGR %) Chart 4.14: North American mHealth Connection Forecast 2015-2020 (million users; AGR %) Chart 4.15: US and Canada National mHealth Connection Forecast 2015-2020 (million users) Chart 4.16: US National mHealth Connection Forecast 2015-2020 (million users; AGR %) Chart 4.17: Canadian National mHealth Connection Forecast 2015-2020 (million users; AGR %) Chart 4.18: Latin American mHealth Revenue Forecast 2015-2020 ($ bn; AGR %) Chart 4.19: Latin American mHealth Connection Forecast 2015-2020 (million users; AGR %) Chart 4.20: Asia-Pacific mHealth Revenue Forecast 2015-2020 ($ bn; AGR %) Chart 4.21: Leading APAC National mHealth Markets, Revenue Forecast 2015-2020 ($ bn) Chart 4.22: Leading APAC National mHealth Markets Revenue Share Forecast 2015 (%) Chart 4.23: Leading APAC National mHealth Markets Revenue Share Forecast 2017 (%) Chart 4.24: Leading APAC National mHealth Markets Revenue Share Forecast 2020 (%) Chart 4.25: Asia-Pacific mHealth Connection Forecast 2015-2020 (million users; AGR %) Chart 4.26: Leading APAC National mHealth Markets, Connection Forecast 2015-2020 (millions) Chart 4.27: Leading APAC National mHealth Markets Connection Share Forecast 2015 (%) Chart 4.28: Leading APAC National mHealth Markets Connection Share Forecast 2017 (%) Chart 4.29: Leading APAC National mHealth Markets Connection Share Forecast 2020 (%) Chart 4.30: European mHealth Revenue Forecast 2015-2020 ($ bn; AGR %) Chart 4.31: Leading European National mHealth Markets, Revenue Forecast 2015-2020 ($ bn) Chart 4.32: Leading European National mHealth Markets Revenue Share Forecast 2015 (%) Chart 4.33: Leading European National mHealth Markets Revenue Share Forecast 2017 (%) Chart 4.34: Leading European National mHealth Markets Revenue Share Forecast 2020 (%) Chart 4.35: European mHealth Connection Forecast 2015-2020 (million users; AGR %) Chart 4.36: Leading European National mHealth Markets, Connection Forecast 2015-2020 (million users; AGR %) Chart 4.37: Leading European National mHealth Markets Connection Share Forecast 2015 (%) Chart 4.38: Leading European National mHealth Markets Connection Share Forecast 2017 (%) Chart 4.39: Leading European National mHealth Markets Connection Share Forecast 2020 (%) Chart 4.40: Middle East and Africa mHealth Revenue Forecast 2015-2020 ($ bn; AGR %) Chart 4.41: Middle East and Africa mHealth Connection Forecast 2015-2020 (million users; AGR %) -------------------------------------------------------------------------- List of Figures Figure 1.1 Global mHealth Market Structure Overview Figure 2.1 Global mHealth Market Structure Overview Figure 2.2 Telecare vs. Telehealth Infographic Figure 2.3: Categorisation and Use Cases for mHealth Technology ------------------------------------------------------------ List of Tables Table 2.1 eHealth Definitions and Variations Table 2.2: eHealth Definitions and Variations Table 3.1: Global mHealth Market Forecast 2015-2020 ($ bn, AGR %, CAGR%, Connections Added) Table 3.2: MHealth Ecosystem Members Described Table 3.3: Global mHealth Revenue Forecast by Ecosystem Member Shares 2015-2020 (%) Table 3.4: Global mHealth Revenue Forecast by Ecosystem Member 2015-2020 ($ bn; AGR %) Table 3.5: Global mHealth Revenue Forecast by Submarket Shares 2015-2020 (%) Table 3.6: Global mHealth Revenue Forecast by Submarket 2015-2020 ($ bn; AGR %) Table 3.7: Global mHealth Connection Forecast 2015-2020 (millions, AGR %, CAGR%, Connections Added) Table 4.1: Regional mHealth Market Forecast 2015-2020 ($ bn; AGR %) Table 4.2: Regional mHealth Connection Forecast 2015-2020 (millions; AGR %) Table 4.3: Regional mHealth ARPU Forecast 2015-2020 ($/year; AGR %) Table 4.4: North American mHealth Revenue Forecast 2015-2020 ($ bn, AGR %, CAGR%, Connections Added) Table 4.5: US/Canada mHealth Revenue Share Forecast 2015-2020 (%) Table 4.6: US National mHealth Revenue Forecast 2015-2020 ($ bn, AGR %, CAGR%, Connections Added) Table 4.7: Canadian National mHealth Revenue Forecast 2015-2020 ($ bn, AGR %, CAGR%, Connections Added) Table 4.8: North American mHealth Connection Forecast 2015-2020 (millions, AGR %, CAGR%, Connections Added) Table 4.9: US/Canada mHealth Connection Share Forecast 2015-2020 (%) Table 4.10: US National mHealth Connection Forecast 2015-2020 (millions, AGR %, CAGR%, Connections Added) Table 4.11: Canadian National mHealth Connection Forecast 2015-2020 (millions, AGR %, CAGR%, Connections Added) Table 4.12: Latin American mHealth Schemes and Operations 2014 (Project, Partners and Sponsors, Application, Activity) Table 4.13: Latin American mHealth Revenue Forecast 2015-2020 ($ bn, AGR %, CAGR%, Connections Added) Table 4.14: Latin American National mHealth Connection Forecast 2015-2020 (millions, AGR %, CAGR%, Connections Added) Table 4.15: Asia-Pacific mHealth Revenue Forecast 2015-2020 ($ bn, AGR %, CAGR%, Connections Added) Table 4.16: Leading APAC National mHealth Markets, Revenue Forecast 2015-2020 ($ bn; AGR %) Table 4.17: Asia-Pacific mHealth Connection Forecast 2015-2020 (millions, AGR %, CAGR%, Connections Added) Table 4.18: Leading APAC National mHealth Markets, Connection Forecast 2015-2020 (millions; AGR %) Table 4.19: European mHealth Revenue Forecast 2015-2020 ($ bn, AGR %, CAGR%, Connections Added) Table 4.20: Leading European National mHealth Markets, Revenue Forecast 2015-2020 ($ bn; AGR %) Table 4.21: European mHealth Connection Forecast 2015-2020 (millions, AGR %, CAGR%, Connections Added) Table 4.22: Leading European National mHealth Markets, Connection Forecast 2015-2020 (millions; AGR %) Table 4.23: Middle East and Africa mHealth Revenue Forecast 2015-2020 ($ bn, AGR %, CAGR%, Connections Added) Table 4.24: Middle East and Africa mHealth Connection Forecast 2015-2020 (millions, AGR %, CAGR%, Connections Added) Table 4.25: Middle East and Africa mHealth Schemes and Operations 2014 (Project, Partners and Sponsors, Application, Activity) Table 5.1: AT&T Mobile Resource Management Table 5.2: AT&T HipLink USPs Table 5.3: Athenahealth Current Offerings 2015 (Service, Product, Use) Table 5.4: CardioNet Product Offering Table 5.5: Epocrates mHealth Offering for devices Running on Apple iOS (Product, Price $, Application) Table 5.6: Epocrates mHealth Offering for devices Running on Android OS (Product, Price $, Application) Table 5.7: Selected Nike+ mHealth Products Table 5.8: Vodafone mHealth Solutions 2013 Table 5.9: Vodafone and TRxCARE Case Study Table 5.10: Clinical Research Patient Reported Outcomes Case Study Table 5.11: Connected mHealth Devices (Device Name, Type, Company, and Description) ------------------------------------------------------------ Companies Listed 3M A&D Medical Abbott Accenture Adidas Aerotel AFrame DIGITAL AlcoSystem Alive Technologies AliveCor Ambisea AMM Technologies Andreessen Horowitz ANT+ Wireless (owned by Garmin) Apple Apple Inc. Asthmapolis AT&T AT&T Mobility Athenahealth Inc. BAM Labs Basis Baxter Healthcare Bayer Beam Technologies Bebetel Belkin BI Bio Telemetry Biotronik BlackBerry Body Media Body Trace Bodybugg BodyTel Boston LifeLabs Boston Scientific Braemar Cambridge Consultant Cambridge Temperature Concepts Limited Card Guard CardioCom CardioNet Care Technology Systems Cell Novo Cell-Life Cerner CHOICE Electronic Technology ChoiceMMed ClickDiagnostics Coca-Cola Compliance Meds Technologies Corscience Corventis Curvus Cypak DayaMed Dayton Industrial DELTA Diabetech Digifit Dimagi Inc. D-Tree International eCardio Diagnostics Echo Therapeutics ElectricFoxy Entra Health Systems Ephone International Epic Systems Epocrates ERT Everist Genomics Everist Health Exmovere Facebook FedEx Fitbit Fitbug Fora Care Foundry Group Gavi Alliance Genesis Health Technologies (GHT) Geneva Healthcare GlaxoSmithKline (GSK) Glooko Google HealthPia HealthyCircles HeathStats Hewlett-Packard Hidalgo Honeywell HomMed Hospital Corporation of America iBaby IBM ICEdot Ideal Life iDiagnosis IEM iHealth iMonSys Ingram Micro Intelesens Iqua (Savox Group) iTMP Technology Jawbone Johnson & Johnson Khosla Ventures Kiwok Nordic AB Kyto Electronic Lark LifeScan LifeWatch LUMOback Massive Health MedApps Medical Electronic Medical International Research Medisana Mednethealth Medtronic Microsoft Microsoft Research Mobisante Motorola mPedigree MTN New Element Nike Nokia Nonin Medical Novartis nSpire Numera Numera Omron Onyx II Orange Business Services Pancreum Perfect Third Philips Philosys PHT Corp PinMed Polar Electro PositiveID Preventice Pro Plus Proteus Digital Health Qualcomm Qualcomm Life Qualcomm Ventures RazorInsights Reebok Reka Health Remnart Technologies Rescue Alert Roche Diagnostics RS Tech Medic Runtastic Samsung Electronics Sanofi Aventis SAP Ventures Scosche Sensaris Sequoia Capital SHL Telemedicine Simavita SmartHF Softbank Capital SoftTech VC Solutions4Health Sony Ericsson Sotera Wireless Sports Tracker St. Jude Medical Strava Tanita TelCare TelCel Telcomed The Mayo Clinic Thinklabs Toumaz True Ventures Tunstall TZ Medical UFFE Medical Under Armour Visere Vitality Vitalograph Vitaphone Vodacom Vodafone Global Enterprises Vodafone Group Vodafone UK Voxiva Vyzin Electronics Private Limited Wahoo Fitness WebMD Welldoc Westminster International Ltd Withings Y-Cam Zain Zensorium Zeo Zephyr Zydacron Other Organisations Mentioned in this Report AED Satellife American Hospital Association BabyCenter Bill & Melinda Gates Foundation CARE Nicaragua Clinton Health Access Initiative (CHAI) Colorado State University Columbia University’s Mailman School of Public Health DARPA Duke University Elsevier Foundation Evangelical Lutheran Church of Tanzania Gavi Alliance Ghana Health Service Global Business Coalition (GBC) Government of Kenya Grameen Foundation GSM Association Development Fund Hospitalito Atitlan Imperial College London Institute for International Cooperation and Development (IICD) Instituto Carso Salud International Development Research Centre (IDRC) International Telecommunication Union John Hopkins Health & Education in South Africa Makerere University Massachusetts Institute of Technology (MIT) Medical Clinica Medical University of Graz Millennium Villages Project Ministry of Health / National Institutes of Health, Mozambique. National Institutes of Health (NIH) Pathfinder International President’s Emergency Plan for AIDS Relief (PEPFAR) Right to Care Rwandan Ministry of Health SMS2Printer Stanford University Tanzania Ministry of Health and Social Welfare The Earth Institute at Columbia University The Raith Foundation The SHM Foundation. The Wellcome Trust Treatment and Research AIDS Centre (TRAC) Rwanda Uganda Chartered HealthNet UNICEF United States Food and Drug Administration Universidad Autonoma de Yucatan Universidad Peruana Cayetano, Heredia Lima University of Botswana University of Pennsylvania University of Pennsylvania Libraries University of Pennsylvania School of Medicine University of Southern Maine University of Washington US Centres for Disease Control and Prevention (CDC) US Forces US President’s Emergency Plan for AIDS Relief USAID World Health Organisation ------------------------------------------------------------ Pricing Single User License: Single user copies of this report are available for EUR2249/ USD2699/ GBP1099 Departmental License: Entitles up to 5 individual users to access this report for EUR3599/ USD4499/ GBP2999 (Not suitable for library usage) Site License: Allow your company to have access to this report at one location for EUR5999/ USD7499/ GBP4999 (Suitable for library storage and use) Global License: Have your whole company worldwide to access this information for EUR8399/ USD9999/ GBP6999 ------------------------------------------------------------ Ordering To order this report, contact Peter Turay on: Telephone: +44(0)207 549 0537 or email: peter.turay@vgtelecomreports.com And provide the following information: Report Title: Report License (Single User/Departmental/Site/Global): Name: User Email: Job Title: Company: Invoice Address: Telephone and Fax number: EEC VAT Number (only for E.U.): Please contact me should you have any questions or wish to receive an executive summary of this report. I look forward to hearing from you. Best Regards, Peter Turay Telecoms Industry Consultant Terms and Conditions By replying to this e-mail submitting your order for this product you have agreed without limitation or qualification to be bound by and to comply with these Terms and Conditions. You agree that you will not fail to complete any transaction after submitting an order to purchase a product or submit any order to purchase a product where you do not intend to complete the transaction. Management Reports will only be sent on receipt of payment. You are currently subscribed to this list as freebsd-ppc@freebsd.org . As a valued contact or customer, you are receiving this email with information that we believe will be relevant to you. If however, you wish to stop future messages, please reply to this email typing "REMOVE" in the subject box. Registered Office: BSG House, 230 City Road, London, EC1V 2QY, U.K. From owner-freebsd-ppc@freebsd.org Thu Jun 9 13:09:21 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA989B6F157 for ; Thu, 9 Jun 2016 13:09:21 +0000 (UTC) (envelope-from bacon4000@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A606E1FB0 for ; Thu, 9 Jun 2016 13:09:21 +0000 (UTC) (envelope-from bacon4000@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id z189so153483064itg.0 for ; Thu, 09 Jun 2016 06:09:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=VyvDS8VvQudSIHEPJnAQc5PMBrPBQpIY6MHpuANxl2c=; b=EvKjj94brnwxbHrQXys39JUWEXcxik95WHSd/RwAlqLf5MMaDEkoY9MpIsdKy+aCh3 IpQil8e/pnhLIMnkyUBLfmRiK3xXf6OkORba8fG+0Jua5hKM1o5C087nd5Mdvw36XxpX FCa6PbIPpPdB6E8DmSa1i7rkIAhMHUBukKMvWC454r409rExIUTr/rxbNSKAl2dn1j7x nl2hPHqJaaJAqvv2PH7blgDL9VTE5udyCAQm1IhYIvaSg1RhRRONRw+dNFo+EJ90s8EX 6wu/tpfV3sCEaLpvvZRynzu1ymAicHF3PHS/kXWhf6zzJ7p13D/cRiILqp7mtKm2YRsu PsAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=VyvDS8VvQudSIHEPJnAQc5PMBrPBQpIY6MHpuANxl2c=; b=Qlkzx4sNK0KbR9I3uJGlckgcWFyZLEFksDxgDnTEhN2TgJIxewGKcEQ006EPyemM92 f4BLUPCTDIcdE84i7ma2BLyvp8C+2MMjUt5bdnUQrPep9ABp4Na2SoElj5A2BheBZz3S cev5iR3DjatraUV0pVtkHF162dlUWqIIPmFYiu7THw9GSxf42K1w1J1ACGRDC6lFH3Uh I1+nHi3hlKBiyTlbj7A+n/HaASZlXNiw0jskiyjZcjjvu8XrKXJ3Rr+e722qLhtQTVK6 RQ7x5zLy50nzJUZ67uvwmif2OmR7z1rN81tzpAsxTWlBx0ptlVYu9xU7neN2ohOg+jPH nMmA== X-Gm-Message-State: ALyK8tKjaMTU0L6GDxFGN4/11f8d/Byzp+I4K8yC7FXPvLTIv3KuPUBMGGv0Vm7nE4ObLA== X-Received: by 10.36.16.67 with SMTP id 64mr17389107ity.88.1465477760909; Thu, 09 Jun 2016 06:09:20 -0700 (PDT) Received: from imacbsd.acadix.biz (cpe-174-102-163-140.wi.res.rr.com. [174.102.163.140]) by smtp.gmail.com with ESMTPSA id 127sm3153493iov.34.2016.06.09.06.09.20 for (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Jun 2016 06:09:20 -0700 (PDT) To: "freebsd-ppc@freebsd.org" From: Jason Bacon Subject: Detecting Power7 in C Message-ID: <765d3292-78ae-8b02-8a5b-43bafc68d9e8@gmail.com> Date: Thu, 9 Jun 2016 08:09:19 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2016 13:09:21 -0000 I'm porting the SLURM task/affinity plugin to FreeBSD and wondering what's the best way to detect whether we're running on a power7 processor. The Linux code is below. I could do something similar with dmesg.boot on FreeBSD, but hoping there's a more elegant way within a C program. If I have to use dmesg.boot, what string would I be looking for? I don't have a power7 installation at the moment. Thanks, Jason FILE *cpu_info_file; char buffer[128]; char* _cpuinfo_path = "/proc/cpuinfo"; cpu_info_file = fopen(_cpuinfo_path, "r"); if (cpu_info_file == NULL) { error("_get_is_power: error %d opening %s", errno, _cpuinfo_path); return false; /* assume not power processor */ } is_power = 0; while (fgets(buffer, sizeof(buffer), cpu_info_file) != NULL) { if (strstr(buffer, "POWER7")) { is_power = 1; break; } } fclose(cpu_info_file); -- All wars are civil wars, because all men are brothers ... Each one owes infinitely more to the human race than to the particular country in which he was born. -- Francois Fenelon From owner-freebsd-ppc@freebsd.org Thu Jun 9 15:47:33 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0DBCAEFE47 for ; Thu, 9 Jun 2016 15:47:33 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB4031EDA for ; Thu, 9 Jun 2016 15:47:33 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-it0-x232.google.com with SMTP id a5so41034080ita.1 for ; Thu, 09 Jun 2016 08:47:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=cc:message-id:from:to:in-reply-to:content-transfer-encoding :mime-version:subject:date:references; bh=huL4xRLXkI2qrX4Gu50yuDuVqJV+yOaYAwmCz55ghRw=; b=AV3TMUMjMgxGfLR7lntS5v2xLWKRF0mfGYN2OV08IPAt+gfr0T/x2vIC95wSz6EJ5Z rgxso9SaZZ9uHjrMgXwXYMGykU9TpUgNCm52BcM7KfZYObaCi5t6oLrlATk4bvV39IOU iqVeo0G/K1zvIet+jAKXe29A/I5GROvGoird12yOEd4e95hNtrqDYUCUzlc2pG0aFgVO 5r1s4b5JrsOvwTd4b7P2YuE2qmwzWGEZkKIZg8A5fwICWvqYhFHPauDLfgfdHpirn1I1 MbLhx9PI0+oWJpIEn67IelJxfnnvu/eaLRz1BaZ3iV5zgkMC76fDCytDiKM6ER1U7rba heHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:cc:message-id:from:to:in-reply-to :content-transfer-encoding:mime-version:subject:date:references; bh=huL4xRLXkI2qrX4Gu50yuDuVqJV+yOaYAwmCz55ghRw=; b=KezG1e8XayfF2Qwpo9VDYZ2mJXJrP5Bz8nSlrC2ffzzr5TmJWsZJlKnLI2TlxqBh00 jZ49qU2y6DLN6KZkgpxqMOeWytNevIUD8wNel0i5jBNUTp65+bH4lNPscm+WBqrFZXiM C6TgqrKjtNkDqbS//GjOj5liWom6TK1wJ2pVz4//wISQv4RrDaSPgClpXEkeSapABgRb smbwJwrfybxgcck6ZtMZjCpSG1Jgxyrcvp+YOqlSeN/n/i3eeuj5JLehW8A6GQaUe5wd 1puR+3sdzoHzQbt66u45wBP+O9Em9aIW2+9racXFrudSB9FlCeSsEM2rRukxnHjZ6Z+0 vr5A== X-Gm-Message-State: ALyK8tLI+p/2oLa4LfH96k1pKxyJ72TOQtu+CVvdDE7R7TwUXkJxVYIrVVFoaUvIuzadEg== X-Received: by 10.36.11.84 with SMTP id 81mr18527629itd.89.1465487252986; Thu, 09 Jun 2016 08:47:32 -0700 (PDT) Received: from [10.65.211.198] ([137.122.64.8]) by smtp.gmail.com with ESMTPSA id u21sm19871377itc.1.2016.06.09.08.47.30 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 09 Jun 2016 08:47:32 -0700 (PDT) Cc: "freebsd-ppc@freebsd.org" Message-Id: <3FD85BCC-4304-4DBA-8B72-5A6A79C120A6@gmail.com> From: Justin Hibbits To: Jason Bacon In-Reply-To: <765d3292-78ae-8b02-8a5b-43bafc68d9e8@gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: Detecting Power7 in C Date: Thu, 9 Jun 2016 11:47:29 -0400 References: <765d3292-78ae-8b02-8a5b-43bafc68d9e8@gmail.com> X-Mailer: Apple Mail (2.936) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2016 15:47:34 -0000 On Jun 9, 2016, at 9:09 AM, Jason Bacon wrote: > > I'm porting the SLURM task/affinity plugin to FreeBSD and wondering > what's the best way to detect whether we're running on a power7 > processor. > > The Linux code is below. I could do something similar with > dmesg.boot on FreeBSD, but hoping there's a more elegant way within > a C program. > > If I have to use dmesg.boot, what string would I be looking for? I > don't have a power7 installation at the moment. > > Thanks, > > Jason > > FILE *cpu_info_file; > > char buffer[128]; > char* _cpuinfo_path = "/proc/cpuinfo"; > cpu_info_file = fopen(_cpuinfo_path, "r"); > if (cpu_info_file == NULL) { > error("_get_is_power: error %d opening %s", > errno, > _cpuinfo_path); > return false; /* assume not power processor > */ > } > > is_power = 0; > while (fgets(buffer, sizeof(buffer), cpu_info_file) ! > = NULL) { > if (strstr(buffer, "POWER7")) { > is_power = 1; > break; > } > } > fclose(cpu_info_file); You can use the hw.model sysctl. For POWER7, the string you would receive is "POWER7". For all the model strings you can get, see the strings in the models[] table in sys/powerpc/powerpc/cpu.c . - Justin From owner-freebsd-ppc@freebsd.org Thu Jun 9 18:43:52 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9262FB7055F for ; Thu, 9 Jun 2016 18:43:52 +0000 (UTC) (envelope-from bacon4000@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6476C10D3 for ; Thu, 9 Jun 2016 18:43:52 +0000 (UTC) (envelope-from bacon4000@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id a5so45382650ita.1 for ; Thu, 09 Jun 2016 11:43:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=CT6iAZdJnBfBeD3yDlFxzxvBP3Mhn1lY8HanfVZxjJo=; b=YM5fp4i8rM5/Dtl5pW5Jd8GfiGiPmy3b3hA7Gc8p+cyGMukY9Xcy9PTUDKHC3AKuqE jLI3/yCgA+SNcdnw0OVYMHQg0wITY5OeIowJW2aIX7BP1LRF+E0URHgsbbQ542VET1n9 Lt6kDwHywmto66wmKASxT6pVKVi9HMt84BWZUYwt9Qy74Jz/+rD1TjW4baApduW8Dc86 vv6EyNHItCQljCNh9Pa9d79fTzl+9zbNfC/Z5mYcYsJfwFk3/c+ziRTtzZZvLxI/anMX OePEvCLm7tGolNoCrR/6ZaNwCQkfmudCrwj1UPN1SmjH8VY3coi5v7IhNvEXR91CpBja tihw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=CT6iAZdJnBfBeD3yDlFxzxvBP3Mhn1lY8HanfVZxjJo=; b=BCp3YbMGkwsEyy/uvd764OdMUZ9ZEzr4INEra4xGxDAq0ZrxNx35qb4FYl3nWqWNGb +2FLNAV5aAMyJ7zWPT1EDlaiUrF3v8+IEc4qO/ntSCHBkWgqqfwnJuCsgd4RrBi6mI1z 9VZnfR0hRP7bj6YTVGJHYgewFDt3aQIYzNJSy4TfSOz9Q/sSlMbL2bUVJfSlasm1FYS/ CVYfopd9GjQbYgAtkBwcy2ej5z1W6g5HoZtr2pp5E48pwEzOAN6eeEmj2jb6q6i4q9/3 HNat3/7MD4zjztoPQcgSTljbh5T5VqJo/ExrnF6zKJq9j428hPyIguQkSCHeOFS7e8xh Hb2g== X-Gm-Message-State: ALyK8tLtNsSVF+Y746gEuWPaZ7xa55oydfnp9zySbi2JX+d6tlf9u22nA8/xew3HKYRQMQ== X-Received: by 10.36.149.137 with SMTP id m131mr25361958itd.94.1465497831731; Thu, 09 Jun 2016 11:43:51 -0700 (PDT) Received: from imacbsd.acadix.biz (cpe-174-102-163-140.wi.res.rr.com. [174.102.163.140]) by smtp.gmail.com with ESMTPSA id b190sm3764054itc.3.2016.06.09.11.43.51 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Jun 2016 11:43:51 -0700 (PDT) Subject: Re: Detecting Power7 in C To: Justin Hibbits References: <765d3292-78ae-8b02-8a5b-43bafc68d9e8@gmail.com> <3FD85BCC-4304-4DBA-8B72-5A6A79C120A6@gmail.com> Cc: "freebsd-ppc@freebsd.org" From: Jason Bacon Message-ID: Date: Thu, 9 Jun 2016 13:43:50 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <3FD85BCC-4304-4DBA-8B72-5A6A79C120A6@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2016 18:43:52 -0000 On 06/09/16 10:47, Justin Hibbits wrote: > On Jun 9, 2016, at 9:09 AM, Jason Bacon wrote: > >> >> I'm porting the SLURM task/affinity plugin to FreeBSD and wondering >> what's the best way to detect whether we're running on a power7 >> processor. >> >> The Linux code is below. I could do something similar with >> dmesg.boot on FreeBSD, but hoping there's a more elegant way within a >> C program. >> >> If I have to use dmesg.boot, what string would I be looking for? I >> don't have a power7 installation at the moment. >> >> Thanks, >> >> Jason >> >> FILE *cpu_info_file; >> >> char buffer[128]; >> char* _cpuinfo_path = "/proc/cpuinfo"; >> cpu_info_file = fopen(_cpuinfo_path, "r"); >> if (cpu_info_file == NULL) { >> error("_get_is_power: error %d opening %s", >> errno, >> _cpuinfo_path); >> return false; /* assume not power processor */ >> } >> >> is_power = 0; >> while (fgets(buffer, sizeof(buffer), cpu_info_file) != >> NULL) { >> if (strstr(buffer, "POWER7")) { >> is_power = 1; >> break; >> } >> } >> fclose(cpu_info_file); > > You can use the hw.model sysctl. For POWER7, the string you would > receive is "POWER7". For all the model strings you can get, see the > strings in the models[] table in sys/powerpc/powerpc/cpu.c . > > - Justin Very nice. Confirmed with the test driver below... Thanks, Jason #include #include #include #include #define BUFFLEN 128 int main(int argc,char *argv[]) { char buff[BUFFLEN+1]; size_t len = BUFFLEN; sysctlbyname("hw.model", buff, &len, NULL, 0); puts(buff); return EX_OK; } -- All wars are civil wars, because all men are brothers ... Each one owes infinitely more to the human race than to the particular country in which he was born. -- Francois Fenelon