From owner-freebsd-ppc@freebsd.org Mon Jun 5 05:07:55 2017 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 9C2BABF6E17 for ; Mon, 5 Jun 2017 05:07:55 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-4.reflexion.net [208.70.210.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43C9970E77 for ; Mon, 5 Jun 2017 05:07:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 18850 invoked from network); 5 Jun 2017 05:07:53 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 5 Jun 2017 05:07:53 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Mon, 05 Jun 2017 01:07:53 -0400 (EDT) Received: (qmail 23400 invoked from network); 5 Jun 2017 05:07:53 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 5 Jun 2017 05:07:53 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 706B8EC805D; Sun, 4 Jun 2017 22:07:52 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: 32-bit powerpc FreeBSD address 0x0-0xff content (physical addresses): What is the explanation? Message-Id: Date: Sun, 4 Jun 2017 22:07:51 -0700 To: Justin Hibbits , Nathan Whitehorn , FreeBSD PowerPC ML , freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2017 05:07:55 -0000 I've been trying to get evidence for periodic/random panics in the likes of head -r317820 for 32-bit powerpc FreeBSD used on an old PowerMac G5 so-called "Quad Core". One thing that I've noticed that looks odd is that the vmcore.* files (debug.minidump=0) show content that looks like the following for physical address range 0x0..0xff (via a hacked-to-work-a-little kgdb for physical address access to such a vmcore.* file): (kgdb) x/128wx 0x0 0x0: 0x00000000 0x00000000 0x00000000 0x00000000 0x10: 0x00000000 0xffa35e50 0xffa35ee8 0x00000000 0x20: 0x00000000 0x00000000 0x00000000 0x00000000 0x30: 0x00000000 0x00000000 0x00000000 0x00000000 0x40: 0x00000000 0x00000000 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x00000090 0x7ff7c080 0x7fc9e7c8 0x00000000 0x90: 0x3c007ff7 0x6000c100 0x7c0903a6 0x4e800421 0xa0: 0x00000000 0x00000000 0x00000000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 . . . Or viewed as instructions when the bit patterns fit such (with added NOTE's): (kgdb) x/128i 0x0 0x0: .long 0x0 0x4: .long 0x0 0x8: .long 0x0 0xc: .long 0x0 0x10: .long 0x0 0x14: .long 0xffa35e50 0x18: .long 0xffa35ee8 0x1c: .long 0x0 0x20: .long 0x0 0x24: .long 0x0 0x28: .long 0x0 0x2c: .long 0x0 0x30: .long 0x0 0x34: .long 0x0 0x38: .long 0x0 0x3c: .long 0x0 0x40: .long 0x0 0x44: .long 0x0 0x48: .long 0x0 0x4c: .long 0x0 0x50: .long 0x0 0x54: .long 0x0 0x58: .long 0x0 0x5c: .long 0x0 0x60: .long 0x0 0x64: .long 0x0 0x68: .long 0x0 0x6c: .long 0x0 0x70: .long 0x0 0x74: .long 0x0 0x78: .long 0x0 0x7c: .long 0x0 0x80: .long 0x90 0x84: .long 0x7ff7c080 0x88: .long 0x7fc9e7c8 0x8c: .long 0x0 0x90: lis r0,32759 (NOTE: 32759==0x7ff7) 0x94: ori r0,r0,49408 (NOTE: 49408==0xC100) 0x98: mtctr r0 (NOTE: So ctr==r0==0x7ff7C100) 0x9c: bctrl (NOTE: So to 0x7ff7C100 virtual address) 0xa0: .long 0x0 (NOTE: lr would end up pointing here.) 0xa4: .long 0x0 0xa8: .long 0x0 0xac: .long 0x0 0xb0: .long 0x0 0xb4: .long 0x0 0xb8: .long 0x0 0xbc: .long 0x0 0xc0: .long 0x0 0xc4: .long 0x0 0xc8: .long 0x0 0xcc: .long 0x0 0xd0: .long 0x0 0xd4: .long 0x0 0xd8: .long 0x0 0xdc: .long 0x0 0xe0: .long 0x0 0xe4: .long 0x0 0xe8: .long 0x0 0xec: .long 0x0 0xf0: .long 0x0 0xf4: .long 0x0 0xf8: .long 0x0 0xfc: .long 0x0 . . . Is this deliberate? If yes: What is it for? (I've not found what writes those bytes.) I do not make the claim that the above is tied to the periodic/random panics. It just seems unusual. === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Jun 5 20:54:18 2017 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 D5FEEB7A4B5 for ; Mon, 5 Jun 2017 20:54:18 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B3E536A8FE for ; Mon, 5 Jun 2017 20:54:18 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AFF84B7A4B4; Mon, 5 Jun 2017 20:54:18 +0000 (UTC) Delivered-To: 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 ADDB6B7A4B3 for ; Mon, 5 Jun 2017 20:54:18 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (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 63F0D6A8FD for ; Mon, 5 Jun 2017 20:54:18 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-qt0-x230.google.com with SMTP id u12so80495439qth.0 for ; Mon, 05 Jun 2017 13:54:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=yHoZZJnwZMBSLw5XjOnXjY2Ls/gyy6H98miduYx+ypA=; b=rSglgsE0345rPrYK2o/8JVZfj3mJC76GAD2toIFpXgBK6iwz1UHC6e+xibRAFoMx3d Czf2Ud8+hOAet6s5oFLCWy/Sb5smxyXPnbrzvWVvh20Jm68At/+TNIw0MYsQir2IhfJj ALQ4xOFDq1zldqWqgy+r1Q8pkUyixNO/tvN7xoOWj2yhyjNw3FdYKBrm00jHPkwjztEE 4tuFNoTNGOl83o4iH4K5HcF2PLy+v1oytvQooC5tpH5K8xiInFlUjZru+CwXKoWdpMcQ 7o9G/8xwMA2T7j9Jl7SF3cX1TcIzQ7zRFEePYbyXi97LylLdxxbxakM7M6DCHyPyIxt4 ykoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=yHoZZJnwZMBSLw5XjOnXjY2Ls/gyy6H98miduYx+ypA=; b=lPAGr5p5pmPwHyr8tocSi92TEwtVT1EvCQrwsuVH3gtmOCUHqUjA8V+1XOAZluPSCC HxiYuqa60w34uDRfcULek+YHJYF7IlzXFxYTV5BgQ+FEK40HRIcNMSBLhrPVBswxtPXG 9OuSfZKs+Y/23cBoWkwykssMxjV9tsbenWE5ittuIxQdMidWk1YpPL9OZl+Kd78vzRyD i49FFjILzJtiSH1vn8QWxI9InyREPhW9yZ+OxvXOXFbdApO7c+ZbC/DchB1tJtyXA4p3 ENA4eGSb1Fe2LhLqDxRW+OZHcWlWvyfy1NBXjVpYabIHzokYhLXjamqCVRBx4EfjUiMl wmEg== X-Gm-Message-State: AODbwcBefwVKZNkFjVU5Udp3DKaEMN+I4Yrf9pivDViA/AAbp9WiyJDd li99i4sR3hoo2vIr39Nt0yJ3r/sB654f X-Received: by 10.200.56.136 with SMTP id f8mr27880291qtc.234.1496696057405; Mon, 05 Jun 2017 13:54:17 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.12.168.154 with HTTP; Mon, 5 Jun 2017 13:54:16 -0700 (PDT) In-Reply-To: References: From: Justin Hibbits Date: Mon, 5 Jun 2017 15:54:16 -0500 X-Google-Sender-Auth: PhLOsD7cwCdfxDtTnga2oSN0C7c Message-ID: Subject: Re: 64-bit time_t on 32-bit powerpc To: ppc@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2017 20:54:18 -0000 On Fri, Jun 2, 2017 at 11:45 PM, Justin Hibbits wrote: > Calling all powerpc(32) users, > > Attached is a patch which changes the size of time_t from 32-bit to 64-bit > on powerpc. ARM and MIPS already use 64-bit time_t, the only other holdout > is i386, which cannot be changed. I want to get this in soon so there's > plenty of soak time before 12 is branched. It works well enough for my > cases, but I want others to poke, prod, and try to break it. Especially try > your favorite ports builds, and make sure things still a) build, and b) work > as expected. > > Almost forgot, too... With powerpc64 users, the compat32 has been updated as > well, obviously. So, some testing of that is needed, too. > > - Justin I was just informed I forgot a very crucial part of the patch -- the update to UPDATING: 20170612: The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is a very major incompatible change, so users of FreeBSD/powerpc must be careful when performing source upgrades. It is best to run 'make installworld' from an alternate root system, either a live CD/memory stick, or a temporary root partition. Additionally, all ports must be recompiled. In short: Do _not_ try to reboot to the new kernel with existing userland. Boot to an alternate userland and install from there. Also, shortly after I sent out the patch, I realized I hadn't tested with TARGET_ARCH=powerpc64, which broke. I'll send out an updated patch later tonight. - Justin From owner-freebsd-ppc@freebsd.org Mon Jun 5 22:59:06 2017 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 28627B7BEE0 for ; Mon, 5 Jun 2017 22:59:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0E2267061F for ; Mon, 5 Jun 2017 22:59:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: by mailman.ysv.freebsd.org (Postfix) id 0A4C9B7BEDF; Mon, 5 Jun 2017 22:59:06 +0000 (UTC) Delivered-To: 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 09E4BB7BEDE for ; Mon, 5 Jun 2017 22:59:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-4.reflexion.net [208.70.210.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AFBA87061D for ; Mon, 5 Jun 2017 22:59:04 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 22172 invoked from network); 5 Jun 2017 23:02:49 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 5 Jun 2017 23:02:49 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Mon, 05 Jun 2017 18:58:58 -0400 (EDT) Received: (qmail 5948 invoked from network); 5 Jun 2017 22:58:57 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 5 Jun 2017 22:58:57 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 55505EC8675; Mon, 5 Jun 2017 15:58:57 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: 64-bit time_t on 32-bit powerpc From: Mark Millard In-Reply-To: Date: Mon, 5 Jun 2017 15:58:56 -0700 Cc: ppc@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Justin Hibbits X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2017 22:59:06 -0000 On 2017-Jun-5, at 1:54 PM, Justin Hibbits wrote: > On Fri, Jun 2, 2017 at 11:45 PM, Justin Hibbits = wrote: >> Calling all powerpc(32) users, >>=20 >> Attached is a patch which changes the size of time_t from 32-bit to = 64-bit >> on powerpc. ARM and MIPS already use 64-bit time_t, the only other = holdout >> is i386, which cannot be changed. I want to get this in soon so = there's >> plenty of soak time before 12 is branched. It works well enough for = my >> cases, but I want others to poke, prod, and try to break it. = Especially try >> your favorite ports builds, and make sure things still a) build, and = b) work >> as expected. >>=20 >> Almost forgot, too... With powerpc64 users, the compat32 has been = updated as >> well, obviously. So, some testing of that is needed, too. >>=20 >> - Justin >=20 > I was just informed I forgot a very crucial part of the patch -- the > update to UPDATING: >=20 > 20170612: > The FreeBSD/powerpc platform now uses a 64-bit type for time_t. = This is > a very major incompatible change, so users of FreeBSD/powerpc = must be > careful when performing source upgrades. It is best to run = 'make > installworld' from an alternate root system, either a live = CD/memory > stick, or a temporary root partition. Additionally, all ports = must be > recompiled. >=20 > In short: Do _not_ try to reboot to the new kernel with existing > userland. Boot to an alternate userland and install from there. What timing as far as live-update contexts go. . . ino64 requires a new kernel boot with an old world still in use: world must not have been updated first. So it appears one should not try to jump from pre-ino64 to post-powerpc-64-bit-time_t in one step via a live-system update sequence. > Also, shortly after I sent out the patch, I realized I hadn't tested > with TARGET_ARCH=3Dpowerpc64, which broke. I'll send out an updated > patch later tonight. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Tue Jun 6 02:50:07 2017 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 9BD3ABD334C for ; Tue, 6 Jun 2017 02:50:07 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 75E8C79517 for ; Tue, 6 Jun 2017 02:50:07 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 754C5BD3342; Tue, 6 Jun 2017 02:50:07 +0000 (UTC) Delivered-To: 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 74F83BD3341 for ; Tue, 6 Jun 2017 02:50:07 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 30BE279516 for ; Tue, 6 Jun 2017 02:50:07 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-qt0-x22c.google.com with SMTP id u19so55483207qta.3 for ; Mon, 05 Jun 2017 19:50:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=L84xCmHIVAd56FiPauv1Ddp0jw2XTRPgbZ6UyJEWi/0=; b=R0boi5DyBCTSiynp8XSK3CFi2DwM4+9hpD6JytB6ay8RHTKrPF1CGey1M6FcJ9ki4d AUaW/Xp8h28qMBQ+Z9k2R0/6zrGVZO6kaNn69tMzXweo4A5AhfYflNkNQ7uLDAFfndrt Wy2lfX1feOMtwIQNgmAp8ARpLOiGNady9vot5UM2lFywGNmle6RSy+BcZYKII8WvkpV5 Knx/WoULxSs3Jdqg7wbIgaIrQ8k86TKGoLsQ8PE48QjEP+otJKFajsrF1c64UEmPwWUT GfUO5wydwEQUyk5D2MEGPNpsKJdYdukgOGBsEND0kbra3OFkM3+sv82e4EpA1Bg+xQsY Pg4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=L84xCmHIVAd56FiPauv1Ddp0jw2XTRPgbZ6UyJEWi/0=; b=IkfQVNaXE4JGGe+l676lDSXQkr0VlUweUqP3VR1wlCjY0xI58ldekJqB5XM1Md18IF qllN8bAmFgaKGFsgjLMgU7yhXSSvwWuhXcVoEgZQRjuJAfnNDxuLqQGlKJ6PzyxqB5sG o1MFWJVFH8eGdq8NEYy7g2h6dQ5VWsG1i/tQsV8+LwsKuMmi2dMaG9YTbrb/rhD3Er74 BP4l3cOvg86jwcz0L/oleZHEEsngpz7bexTBAImB6jq6aW2MKfIhcA9R/WarQo0fXy/6 3gS3ersmbCTdv211ksnM1FZ6TucHW7EmCaKZoou2KcLvjHFhfWuSzS/0gRHJwOwVicDV cJMg== X-Gm-Message-State: AKS2vOymiqlTIKOSMS/YTrs+JFktcU/Y0+D29cLGkVAoj1IXtux4SV+U nSjZIGLsg+ERldQ06rVdE0HoMDEOvA== X-Received: by 10.55.115.69 with SMTP id o66mr26030823qkc.120.1496717405854; Mon, 05 Jun 2017 19:50:05 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.12.168.154 with HTTP; Mon, 5 Jun 2017 19:50:05 -0700 (PDT) In-Reply-To: References: From: Justin Hibbits Date: Mon, 5 Jun 2017 21:50:05 -0500 X-Google-Sender-Auth: X5bkooIug1k_95mfk963qD38Mtw Message-ID: Subject: Re: 64-bit time_t on 32-bit powerpc To: Mark Millard Cc: "ppc@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2017 02:50:07 -0000 On Monday, June 5, 2017, Mark Millard wrote: > > On 2017-Jun-5, at 1:54 PM, Justin Hibbits > wrote: > > > On Fri, Jun 2, 2017 at 11:45 PM, Justin Hibbits > wrote: > >> Calling all powerpc(32) users, > >> > >> Attached is a patch which changes the size of time_t from 32-bit to > 64-bit > >> on powerpc. ARM and MIPS already use 64-bit time_t, the only other > holdout > >> is i386, which cannot be changed. I want to get this in soon so there's > >> plenty of soak time before 12 is branched. It works well enough for my > >> cases, but I want others to poke, prod, and try to break it. > Especially try > >> your favorite ports builds, and make sure things still a) build, and b) > work > >> as expected. > >> > >> Almost forgot, too... With powerpc64 users, the compat32 has been > updated as > >> well, obviously. So, some testing of that is needed, too. > >> > >> - Justin > > > > I was just informed I forgot a very crucial part of the patch -- the > > update to UPDATING: > > > > 20170612: > > The FreeBSD/powerpc platform now uses a 64-bit type for time_t. > This is > > a very major incompatible change, so users of FreeBSD/powerpc > must be > > careful when performing source upgrades. It is best to run 'make > > installworld' from an alternate root system, either a live > CD/memory > > stick, or a temporary root partition. Additionally, all ports > must be > > recompiled. > > > > In short: Do _not_ try to reboot to the new kernel with existing > > userland. Boot to an alternate userland and install from there. > > What timing as far as live-update contexts go. . . > > ino64 requires a new kernel boot with an old world still > in use: world must not have been updated first. > > So it appears one should not try to jump from pre-ino64 > to post-powerpc-64-bit-time_t in one step via a > live-system update sequence. > Correct. You cannot migrate to 64-bit time_t with a live system update anyway, it's an ABI/KBI/syscall change, so you have to perform a two-stage upgrade with this. You can migrate along with the ino64 change, but you have to use an alternate root regardless of any other changes made. > > > Also, shortly after I sent out the patch, I realized I hadn't tested > > with TARGET_ARCH=powerpc64, which broke. I'll send out an updated > > patch later tonight. > As promised, you can find the updated patch at https://people.freebsd.org/~jhibbits/time_t_32.diff - Justin From owner-freebsd-ppc@freebsd.org Tue Jun 6 10:46:27 2017 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 98755BFCC7B for ; Tue, 6 Jun 2017 10:46:27 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-5.reflexion.net [208.70.210.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CFE82E04 for ; Tue, 6 Jun 2017 10:46:27 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 24974 invoked from network); 6 Jun 2017 10:47:42 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 6 Jun 2017 10:47:42 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Tue, 06 Jun 2017 06:46:20 -0400 (EDT) Received: (qmail 29898 invoked from network); 6 Jun 2017 10:46:20 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 6 Jun 2017 10:46:20 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id BB335EC7B76; Tue, 6 Jun 2017 03:46:19 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: A different 32-bit powerpc head -r317820 panic on old PowerMac G5: dual backtraces from "timeout stopping cpus" (dump failed though): any comments? Message-Id: Date: Tue, 6 Jun 2017 03:46:19 -0700 To: Justin Hibbits , Nathan Whitehorn , FreeBSD PowerPC ML , freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2017 10:46:27 -0000 I'm not sure what to make of this. May be someone has some idea. One of the bt's is for "irq53: smudoorbell0" (tid 100055) the other is = for usb. spinlock 0xefbbf00 (sched lock 1) held by 0x593d6c0 (tid 100055) too = long spinlock 0xxf2e1f8 (sleepq chain) help by 0x17606c0 (tid 100049) too = long timeout stopping cpus usb. . . (I omit any "at kdb_backtrace" lines) 0xe56636d0: at vpanic+0x210 0xe5663740: at panic+0x54 0xe5663790: at _mtx_lock_spin_failed_+0x54 0xe56637b0: at _mtx_lock_spin_cookie+0x19c 0xe5663810: at sched_add+0x140 0xe5663850: at sched_wakeup+0xa4 0xe5663870: at setrunnable+0x9c 0xe5663890: at sleepq_resume_thread+0x17c 0xe56638c0: at sleepq_signal+0xa4 0xe56638f0: at cv_signal+0x94 0xe5663910: at usbd_do_request_callback+0x80 0xe5663930: at usb_request_callback_0x28 0xe5663950: at usbd_callback_wrapper+0xa98 0xe5663990: at usb_command_wrapper+0x14c 0xe56639d0: at usb_callback_proc+0x190 0xe5663a00: at usb_process+0x1d0 0xe5663a50: at fork_exit+0xf4 0xe5663a80: at fork_trampoline+0xc irq53: smudoorbell0. . . 0xe56e4460: at vpanic+0x22c 0xe56e44d0: at panic+0x54 0xe56e4520: at _mtx_lock_spin_failed+0x54 0xe56e4540: at thread_lock_flags_0x1bc 0xe56e45b0: at sleepq_timeout+0x44 0xe56e45f0: at softclock_call_cc+0x1bc 0xe56e4660: at callout_process+0x27c 0xe56e46c0: at handleevents+0x2ac 0xe56e4710: at timercb+0x4c4 0xe56e4790: at decr_intr+0xf0 0xe56e47b0: at powerpc_intrerrupt+0xf4 0xe56e47e0: at kernel DECR trap by _mtx_lock_spin_cookie+0x194 srr1=3D 0x9032 r1=3D 0xe56e48a0 cr=3D 0x20000002 xer=3D 0 ctr=3D 0 0xe56e48a0: at _mtx_lock+_spin_cookie+0x190 0xe56e4900: at sleepq_lock+0xac 0xe56e4930: at wakeup+0x24 0xe56e4950: at smu_doorbell_intr+0x128 0xe56e4980: at intr_event_execute_handler+0x220 0xe56e49f0: at ithread_loop+0xf0 0xe56e4a50: at fork_exit+0xf4 0xe56e4a80: at fork_trampoline+0xc For reference acttrace also reported (that looks odd after the first 2 stack lines): powerpd pid 960 tid 100097 td 0x5ba1999 (CPU 2) 0xd2418510: at uma_zalloc_arg+0x178 0xd2418580: at mmu_unmapdev+desc+0x8 0x00fcf9dc: at primes+0x68 0x00d026b0: at moe64_page_exists_quick+0x1d8 0x00ce0ff8: at mmu_unmapdev_desc+0x8 (CPU3 had an empty backtrace for pid 11's tid 100006.) I had another example of sorts but it did not get far before hanging up: spinlock 0xefbbf00 (sched lock 1) held by 0x146d360 (tid 100004) too = long spinlock 0xefbbf00 (sched lock 1) held by 0x146d360 (tid 100004) too = long (Note: Two different colored lines above but the same otherwise.) timeout stopping cpus Note: The partial backtrace was: ("cpuid =3D 2", all in the first color above) 0xdf6bb5c0: at vpanic+0x210 0xdf6bb630: at panic++0x54 0xdf6bb680: at _mtx_lock_spin_failed+0x54 0xdf6bb6a0: at _mtx_lock_spin_cookie+0x190 0xdf6bb700: at sched_add+0x140 0xdf6bb740: at sched_wakeup+0xa4 0xdf6bb760: at=20 (and that is as far as it got for the backtrace(s)) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Tue Jun 6 18:16:01 2017 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 24178BF229C for ; Tue, 6 Jun 2017 18:16:01 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-12.reflexion.net [208.70.210.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D212C75D29 for ; Tue, 6 Jun 2017 18:16:00 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29943 invoked from network); 6 Jun 2017 18:09:19 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 6 Jun 2017 18:09:19 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Tue, 06 Jun 2017 14:09:19 -0400 (EDT) Received: (qmail 1220 invoked from network); 6 Jun 2017 18:09:18 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 6 Jun 2017 18:09:18 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 11DB4EC8B8B; Tue, 6 Jun 2017 11:09:18 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: A different 32-bit powerpc head -r317820 panic on old PowerMac G5: dual backtraces from "timeout stopping cpus" (dump failed though): any comments? Date: Tue, 6 Jun 2017 11:09:17 -0700 References: To: Justin Hibbits , Nathan Whitehorn , FreeBSD PowerPC ML , freebsd-hackers@freebsd.org In-Reply-To: Message-Id: <1F1E52BD-375E-47CC-BF06-ECB1092121B4@dsl-only.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2017 18:16:01 -0000 On 2017-Jun-6, at 3:46 AM, Mark Millard wrote: > I'm not sure what to make of this. May be someone has > some idea. >=20 > One of the bt's is for "irq53: smudoorbell0" (tid 100055) the other is = for usb. >=20 > spinlock 0xefbbf00 (sched lock 1) held by 0x593d6c0 (tid 100055) too = long > spinlock 0xxf2e1f8 (sleepq chain) help by 0x17606c0 (tid 100049) too = long > timeout stopping cpus >=20 > usb. . . > (I omit any "at kdb_backtrace" lines) >=20 > 0xe56636d0: at vpanic+0x210 > 0xe5663740: at panic+0x54 > 0xe5663790: at _mtx_lock_spin_failed_+0x54 > 0xe56637b0: at _mtx_lock_spin_cookie+0x19c > 0xe5663810: at sched_add+0x140 > 0xe5663850: at sched_wakeup+0xa4 > 0xe5663870: at setrunnable+0x9c > 0xe5663890: at sleepq_resume_thread+0x17c > 0xe56638c0: at sleepq_signal+0xa4 > 0xe56638f0: at cv_signal+0x94 > 0xe5663910: at usbd_do_request_callback+0x80 > 0xe5663930: at usb_request_callback_0x28 > 0xe5663950: at usbd_callback_wrapper+0xa98 > 0xe5663990: at usb_command_wrapper+0x14c > 0xe56639d0: at usb_callback_proc+0x190 > 0xe5663a00: at usb_process+0x1d0 > 0xe5663a50: at fork_exit+0xf4 > 0xe5663a80: at fork_trampoline+0xc >=20 > irq53: smudoorbell0. . . >=20 > 0xe56e4460: at vpanic+0x22c > 0xe56e44d0: at panic+0x54 > 0xe56e4520: at _mtx_lock_spin_failed+0x54 > 0xe56e4540: at thread_lock_flags_0x1bc > 0xe56e45b0: at sleepq_timeout+0x44 > 0xe56e45f0: at softclock_call_cc+0x1bc > 0xe56e4660: at callout_process+0x27c > 0xe56e46c0: at handleevents+0x2ac > 0xe56e4710: at timercb+0x4c4 > 0xe56e4790: at decr_intr+0xf0 > 0xe56e47b0: at powerpc_intrerrupt+0xf4 > 0xe56e47e0: at kernel DECR trap > by _mtx_lock_spin_cookie+0x194 > srr1=3D 0x9032 > r1=3D 0xe56e48a0 > cr=3D 0x20000002 > xer=3D 0 > ctr=3D 0 > 0xe56e48a0: at _mtx_lock+_spin_cookie+0x190 > 0xe56e4900: at sleepq_lock+0xac > 0xe56e4930: at wakeup+0x24 > 0xe56e4950: at smu_doorbell_intr+0x128 > 0xe56e4980: at intr_event_execute_handler+0x220 > 0xe56e49f0: at ithread_loop+0xf0 > 0xe56e4a50: at fork_exit+0xf4 > 0xe56e4a80: at fork_trampoline+0xc >=20 > For reference acttrace also reported > (that looks odd after the first 2 > stack lines): >=20 > powerpd pid 960 tid 100097 td 0x5ba1999 (CPU 2) > 0xd2418510: at uma_zalloc_arg+0x178 > 0xd2418580: at mmu_unmapdev+desc+0x8 > 0x00fcf9dc: at primes+0x68 > 0x00d026b0: at moe64_page_exists_quick+0x1d8 > 0x00ce0ff8: at mmu_unmapdev_desc+0x8 >=20 > (CPU3 had an empty backtrace for pid 11's > tid 100006.) >=20 >=20 > I had another example of sorts but it did not > get far before hanging up: >=20 > spinlock 0xefbbf00 (sched lock 1) held by 0x146d360 (tid 100004) too = long > spinlock 0xefbbf00 (sched lock 1) held by 0x146d360 (tid 100004) too = long >=20 > (Note: Two different colored lines above but the > same otherwise.) >=20 > timeout stopping cpus >=20 > Note: The partial backtrace was: > ("cpuid =3D 2", all in the first color above) >=20 > 0xdf6bb5c0: at vpanic+0x210 > 0xdf6bb630: at panic++0x54 > 0xdf6bb680: at _mtx_lock_spin_failed+0x54 > 0xdf6bb6a0: at _mtx_lock_spin_cookie+0x190 > 0xdf6bb700: at sched_add+0x140 > 0xdf6bb740: at sched_wakeup+0xa4 > 0xdf6bb760: at=20 >=20 > (and that is as far as it got for the backtrace(s)) FYI: I'm currently doing an approximate binary search for localizing part of the panic problem. This is based on the classic panics that are instead from jumping to a non-code area. . . At a given point in my other experiments I was getting: srr0=3D0x90a0f0 etext+0xb8fc Adding (unused) code somewhat before that etext (so increasing etext) got: srr0=3D0x90a0f0 etext+0xb8a8 (The additional code was larger than I now use.) But instead adding some code earlier (by around 0x100000 in this example) got: srr0=3D0x90a110 etext+0xb8fc So comparing to the starting conditions in each case: The bad-address accessed in one case stayed constant but the etext offset decreased: in essence the only thing that happened is etext increased (matching the offset decrease). In the other case the etext offset stayed constant but the bad-address and etext increased by the same amount. Unfortunately this will take a while: A) It typically takes hours for a failure to happen, I've had up to between 7 hours and 8 hours. (I've had minutes-to-failure but it is rare.) B) I'd let it go 24 hours before concluding that a test combination was not likely to produce an obvious form of failure (such as the panic). (I've had (B) in some earlier forms of testing variations of things.) Another time-taker is that I need to be around because I avoid leaving the PowerMac G5 panicked with the fans going fill-speed for long periods. Currently I'm adding code by adding: void HACKISH_EXTRA_CODE(void) {} to one .c file from /usr/src/sys/. . . based which file gets to within a ballpark of a more accurate binary search position. (Large binary search jumps currently: I'm not being picky about where in the .c the addition is made yet.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Wed Jun 7 04:49:45 2017 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 B1C64BFB249 for ; Wed, 7 Jun 2017 04:49:45 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-13.reflexion.net [208.70.210.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7761111AA for ; Wed, 7 Jun 2017 04:49:45 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 7555 invoked from network); 7 Jun 2017 04:49:43 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 7 Jun 2017 04:49:43 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Wed, 07 Jun 2017 00:49:43 -0400 (EDT) Received: (qmail 5344 invoked from network); 7 Jun 2017 04:49:43 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 7 Jun 2017 04:49:43 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id AC81FEC7A6F; Tue, 6 Jun 2017 21:49:42 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: 32-bit powerpc FreeBSD head -r317820 panic example: Example showing register r10 having been trashed during set_affinity's time frame Message-Id: <1738C902-7A9C-4711-A2F7-D302249C9AF8@dsl-only.net> Date: Tue, 6 Jun 2017 21:49:42 -0700 To: Justin Hibbits , Nathan Whitehorn , FreeBSD PowerPC ML , freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2017 04:49:45 -0000 Summary of the analysis below: Something trashed the r10 value during set_affinity, effectively replacing a struct td_sched * value with what happened to be a struct thread * value. That in turn lead to what should have been a cpuid (for one of 4 CPUs) to instead be a struct td_sched * value. And that in turn lead to a data storage interrupt from the indexing into cpuid_to_pcpu being way out of bounds. Context: 32-bit powerpc head -r317820 used on a old PowerMac G5 so-called "Quad Core". The analysis from a panic's dump and from pictures of ddb output and using the kernel debug file. . . I got a panic that it looked like I could back calculate a ways to see what was odd somewhat earlier. This is that back calculation sequence. This will start in ipi_cpu where the panic occurred and progress backwards into sched_affinity. void ipi_cpu(int cpu, u_int ipi) { ipi_send(cpuid_to_pcpu[cpu], ipi); } was: (kgdb) x/90i ipi_cpu 0x8eb0dc : stwu r1,-32(r1) 0x8eb0e0 : mflr r0 0x8eb0e4 : stw r30,24(r1) 0x8eb0e8 : stw r31,28(r1) 0x8eb0ec : stw r0,36(r1) 0x8eb0f0 : mr r31,r1 0x8eb0f4 : bcl- 20,4*cr7+so,0x8eb0f8 0x8eb0f8 : mflr r30 0x8eb0fc : lwz r0,-32(r30) 0x8eb100 : add r30,r0,r30 0x8eb104 : rlwinm r3,r3,2,0,29 0x8eb108 : lwz r9,-32756(r30) 0x8eb10c : lwzx r3,r3,r9 0x8eb110 : bl 0x8eb018 0x8eb114 : lwz r11,0(r1) 0x8eb118 : lwz r0,4(r11) 0x8eb11c : mtlr r0 0x8eb120 : lwz r30,-8(r11) 0x8eb124 : lwz r31,-4(r11) 0x8eb128 : mr r1,r11 0x8eb12c : blr 0x8eb130 : .long 0x43ce40 The point of failure (srr0 value) is: 0x8eb10c : lwzx r3,r3,r9 (Note: This is a form of r3:=3DMEM(r3+r9,4). Luckily r3 was not updated because of the bad r3+r9 value.) Note that the only prior instruction modifying r3 in ipi_cpu is: 0x8eb104 : rlwinm r3,r3,2,0,29 The "show reg r3" result was: 0x51f2880. So prior to the shift by 2 and masking off of the least significant 2 bits its value was: r3=3D0x147CA20 I will note that the 0x51f2880 + the "show reg r9" value 0xf2c9fc (i.e., &cpuid_to_pcpu) produces: 0x611f27c -- and the exception was reported as being for virtual address 0x611f27c . By the source code structure r3 was supposed to be one of the values: 0x0, 0x1, 0x2 or 0x3 instead. (The PowerMac G5 "Quad Core" has 4 cpus.) With the "show reg r4" result being 0x1 it means that the call to ipi_cpu was apparently (by values passed): ipi_cpu(0x147CA20, 0x1) "Show allpcpu" reported that cpuid=3D3 had: curthread =3D 0x147ca20: pid 11 tid 100006 "idle: cpu3" idlethread =3D 0x147ca20: did 100006 "idle: cpu3" where 0x147d000 (for cpuid 2) has 0x147d008 holding a 0x147ca20 value. So somehow a thread address for cpuid 3 was given to ipi_cpu instead of 0x3 . The backtrace shows that the caller of ipi_cpu was sched_affinity: void sched_affinity(struct thread *td) { #ifdef SMP struct td_sched *ts; THREAD_LOCK_ASSERT(td, MA_OWNED); ts =3D td_get_sched(td); if (THREAD_CAN_SCHED(td, ts->ts_cpu)) return; if (TD_ON_RUNQ(td)) { sched_rem(td); sched_add(td, SRQ_BORING); return; } if (!TD_IS_RUNNING(td)) return; /* * Force a switch before returning to userspace. If the * target thread is not running locally send an ipi to force * the issue. */ td->td_flags |=3D TDF_NEEDRESCHED; if (td !=3D curthread) ipi_cpu(ts->ts_cpu, IPI_PREEMPT); #endif } So the implication is that ts->ts_cpu had the value 0x147ca20 instead of the value 3 at the time of the call sequence. sched_affinity was: 0x535ab8 : stwu r1,-32(r1) 0x535abc : mflr r0 0x535ac0 : stw r29,20(r1) 0x535ac4 : stw r30,24(r1) 0x535ac8 : stw r31,28(r1) 0x535acc : stw r0,36(r1) 0x535ad0 : mr r31,r1 0x535ad4 : mr r29,r3 0x535ad8 : lwz r0,0(r3) 0x535adc : addi r10,r3,808 0x535ae0 : lwz r9,8(r10) 0x535ae4 : lwz r11,48(r3) 0x535ae8 : rlwinm r0,r9,29,3,29 0x535aec : clrlwi r9,r9,27 0x535af0 : lwzx r0,r11,r0 0x535af4 : sraw r0,r0,r9 0x535af8 : andi. r9,r0,1 0x535afc : bne- 0x535b4c 0x535b00 : lwz r0,652(r3) 0x535b04 : cmpwi cr7,r0,3 0x535b08 : bne+ cr7,0x535b20 = 0x535b0c : bl 0x5341c0 0x535b10 : mr r3,r29 0x535b14 : li r4,0 0x535b18 : bl 0x53583c 0x535b1c : b 0x535b4c 0x535b20 : cmpwi cr7,r0,4 0x535b24 : bne- cr7,0x535b4c = 0x535b28 : lwz r0,156(r3) 0x535b2c : oris r0,r0,1 0x535b30 : stw r0,156(r3) 0x535b34 : mr r0,r2 0x535b38 : cmpw cr7,r3,r0 0x535b3c : beq- cr7,0x535b4c = 0x535b40 : lwz r3,8(r10) 0x535b44 : li r4,1 0x535b48 : bl 0x8eb0dc 0x535b4c : lwz r11,0(r1) 0x535b50 : lwz r0,4(r11) 0x535b54 : mtlr r0 0x535b58 : lwz r29,-12(r11) 0x535b5c : lwz r30,-8(r11) 0x535b60 : lwz r31,-4(r11) 0x535b64 : mr r1,r11 0x535b68 : blr 0x535b6c : .long 0x7e7f18 The only call executed by sched_affinity was to ipi_cpu given what is inlined and the fact that it made it to do the ipi_cpu bl instruction. Since ipi_cpu leaves various registers alone some register values from sched_affinity were preserved for "show reg" use. r10 is an example in: 0x535ad4 : mr r29,r3 . . . 0x535adc : addi r10,r3,808 . . . 0x535b40 : lwz r3,8(r10) 0x535b44 : li r4,1 0x535b48 : bl 0x8eb0dc (r29 is another register value that is preserved in what sched_affinity called. r29 reports what r3 was when sched_affinity was called: 0x147d000, which makes sense. Also 808 is in decimal notation.) That sched_affinity code corresponds to (r10 for ts below): sched_affinity(struct thread *td) . . . struct td_sched *ts; . . . ts =3D td_get_sched(td); . . . ipi_cpu(ts->ts_cpu, IPI_PREEMPT); where "show reg r10" reported: 0x147d000, which matched the "show allpcpu" for cpuid=3D2: curthread =3D 0x147d000: pid11 tid 100005 "idle: cpu2" But it should not match that. . . r10 should have been 0x147d328 (0x147d00+0x328) but is reported as 0x147d000 and the behavior reported for ipi_cpu agrees with 0x147d000: 8(r10) then extracts a 0x0147ca20 value from 0x147d008 instead of a 0x0 from 0x147d328 . So something trashed r10 before: 0x535b40 : lwz r3,8(r10) and so effectively replaced ts with the td value. Trashing r3 so that r3+808=3D=3D0x147d000 when 0x535adc executes seems unlikely but is a technical possibility for how r10 ends up trashed. Other notes: Some of the details not shown above are: static __inline __pure2 struct td_sched * td_get_sched(struct thread *td) { =20 return ((struct td_sched *)&td[1]); } and: /* * Thread scheduler specific section. All fields are protected * by the thread lock. */ struct td_sched { struct runq *ts_runq; /* Run-queue we're queued on. */ short ts_flags; /* TSF_* flags. */ int ts_cpu; /* CPU that we have affinity = for. */ int ts_rltick; /* Real last tick, for affinity. = */ int ts_slice; /* Ticks of slice remaining. */ u_int ts_slptime; /* Number of ticks we vol. slept = */ u_int ts_runtime; /* Number of ticks we were = running */ int ts_ltick; /* Last tick that we were = running on */ int ts_ftick; /* First tick that we were = running on */ int ts_ticks; /* Tick count */ #ifdef KTR char ts_name[TS_NAME_LEN]; #endif }; where td_sched is a suffix after a "struct thread", such as the space reserved in: struct thread0_storage { struct thread t0st_thread; uint64_t t0st_sched[10]; }; and checked by: _Static_assert(sizeof(struct thread) + sizeof(struct td_sched) <=3D sizeof(struct thread0_storage), "increase struct thread0_storage.t0st_sched size"); =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu Jun 8 08:24:56 2017 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 22110BF97B5 for ; Thu, 8 Jun 2017 08:24:56 +0000 (UTC) (envelope-from andy.silva@snsreports.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C7A30795DE for ; Thu, 8 Jun 2017 08:24:55 +0000 (UTC) (envelope-from andy.silva@snsreports.com) X-MSFBL: dA05H5WWoQAGeIThlJ22ajXNuNfhZ8HqStzLKZxRjHU=|eyJyIjoiZnJlZWJzZC1 wcGNAZnJlZWJzZC5vcmciLCJnIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbCI sImIiOiI3NF85MV84NV8yMzgifQ== Received: from [192.168.80.22] ([192.168.80.22:42526] helo=rs-ord-mta02-in2.smtp.com) by rs-ord-mta01-out2.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id D0/E5-04808-0D909395; Thu, 08 Jun 2017 08:24:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=snsresearchreports.com; s=snskey; c=relaxed/simple; q=dns/txt; i=@snsresearchreports.com; t=1496910288; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=K1ddUQcMm8en+HOhzt3t9quyIwoLSNoBGxVqM3xIdfQ=; b=qbi/uuYH6Y2cQTDjvoROpvm3A3K38Jnwg2XKDlbuzDwPbFiZIfddSbY6NtivZKJz vfjkdgfx1NjPgQKRqK7lLN++HIhbx6XVkcekqCpXJfRP/GiJc/x0w1l4K3y9rXXk xxKaj2V+ioAWjzUC4U2sP7p5XEiRp/ZlT+p/B6a/w6F2N02vyviUpDz7/1W659w2 5SRYGJflDr//bjIYNwYQ7Cqf8yaNgDhqeYCU46GtloQIDLLXL51lEY4VH8Bj6CKW M46ENicrZyjUrKZ+aNk7WDeH2cft/a0C005snHyQvpPVMyl6AkSY2pFGF0217/FZ 89drqm8rKxCo2YJUjuLIOQ==; Received: from [205.250.228.1] ([205.250.228.1:34996] helo=d205-250-228-1.bchsia.telus.net) by rs-ord-mta02-in2.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id 10/34-11013-0D909395; Thu, 08 Jun 2017 08:24:48 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsreports.com To: freebsd-ppc@freebsd.org Subject: The Big Data Market: 2017 - 2030 - Opportunities, Challenges, Strategies, Industry Verticals & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Thu, 8 Jun 2017 01:24:47 -0700 Message-ID: <418724251026161368629203@Ankur> X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation. X-SMTPCOM-Tracking-Number: 54a9a4c1-aef8-4473-aff6-13f7181ec89d X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2017 08:24:56 -0000 The Big Data Market: 2017 =96 2030 =96 Opportunities, Challenges, Strategie= s, Industry Verticals & Forecasts (Report) Hello Please find the latest SNS Research report summary to you and your team, " = The Big Data Market: 2017 =96 2030 =96 Opportunities, Challenges, Strategie= s, Industry Verticals & Forecasts" Below is the report highlight and if you= like I can send you sample pages for your details inside. =20 Our reports are compiled with primary and secondary informations to produce= an overall industry outlook. Despite challenges relating to privacy concer= ns and organizational resistance, Big Data investments continue to gain mom= entum throughout the globe. SNS Research estimates that Big Data investment= s will account for over $57 Billion in 2017 alone. These investments are fu= rther expected to grow at a CAGR of approximately 10% over the next three y= ears. Report Information: Release Date: April 2017 Number of Pages: 498 Number of Tables and Figures: 89 Key Questions Answered: How big is the Big Data ecosystem=3F How is the ecosystem evolving by segment and region=3F What will the market size be in 2020 and at what rate will it grow=3F What trends, challenges and barriers are influencing its growth=3F Who are the key Big Data software, hardware and services vendors and what a= re their strategies=3F How much are vertical enterprises investing in Big Data=3F What opportunities exist for Big Data analytics=3F Which countries and verticals will see the highest percentage of Big Data i= nvestments=3F Key Findings: The report has the following key findings: In 2017, Big Data vendors will pocket over $57 Billion from hardware, softw= are and professional services revenues. These investments are further expec= ted to grow at a CAGR of approximately 10% over the next four years, eventu= ally accounting for over $76 Billion by the end of 2020. As part of wider plans to revitalize their economies, countries across the = world are incorporating legislative initiatives to capitalize on Big Data. = For example, the Japanese government is engaged in developing intellectual = property protection and dispute resolution frameworks for Big Data assets, = in a bid to encourage data sharing and accelerate the development of domest= ic industries. By the end of 2017, SNS Research estimates that as much as 30% of all Big D= ata workloads will be processed via cloud services as enterprises seek to a= void large-scale infrastructure investments and security issues associated = with on-premise implementations. The vendor arena is continuing to consolidate with several prominent M&A de= als such as computer hardware giant Dell's $60 Billion merger with data sto= rage specialist EMC. The report covers the following topics: Big Data ecosystem Market drivers and barriers Big Data technology, standardization and regulatory initiatives Big Data industry roadmap and value chain Analysis and use cases for 14 vertical markets Big Data analytics technology and case studies Big Data vendor market share Company profiles and strategies of over 240 Big Data ecosystem players Strategic recommendations for Big Data hardware, software and professional = services vendors, and enterprises Market analysis and forecasts from 2017 till 2030 Forecast Segmentation: Market forecasts and historical figures are provided for each of the follow= ing submarkets and their categories: Hardware, Software & Professional Services=20 Hardware=20 Software=20 Professional Services Horizontal Submarkets=20 Storage & Compute Infrastructure=20 Networking Infrastructure=20 Hadoop & Infrastructure Software=20 SQL=20 NoSQL=20 Analytic Platforms & Applications=20 Cloud Platforms=20 Professional Services Vertical Submarkets=20 Automotive, Aerospace & Transportation=20 Banking & Securities=20 Defense & Intelligence=20 Education=20 Healthcare & Pharmaceutical=20 Smart Cities & Intelligent Buildings=20 Insurance=20 Manufacturing & Natural Resources=20 Web, Media & Entertainment=20 Public Safety & Homeland Security=20 Public Services=20 Retail & Hospitality=20 Telecommunications=20 Utilities & Energy=20 Wholesale Trade=20 Others Regional Markets=20 Asia Pacific=20 Eastern Europe=20 Latin & Central America=20 Middle East & Africa=20 North America=20 Western Europe Country Markets=20 Argentina, Australia, Brazil, Canada, China, Czech Republic, Denmark, Finla= nd, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mex= ico, Netherlands, Norway, Pakistan, Philippines, Poland, Qatar, Russia, Sau= di Arabia, Singapore, South Africa, South Korea, Spain, Sweden, Taiwan, Tha= iland, UAE, UK, USA=20 Report Pricing: =20 Single User License: USD 2,500 Company Wide License: USD 3,500 =20 Ordering Process: =20 Please provide the following information: Report Title - Big Data Market: 2017 =96 2030 Report License - (Single User/Company Wide) Name - Email - Job Title - Company - Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents, List of figures and List of companies mentioned in report = are given below for more inside. I look forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom andy.silva@snsreports.com _________________________________________________________________________ Table of Contents: =20 1 Chapter 1: Introduction 1.1 Executive Summary 1.2 Topics Covered 1.3 Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 2 Chapter 2: An Overview of Big Data 2.1 What is Big Data=3F 2.2 Key Approaches to Big Data Processing 2.2.1 Hadoop 2.2.2 NoSQL 2.2.3 MPAD (Massively Parallel Analytic Databases) 2.2.4 In-Memory Processing 2.2.5 Stream Processing Technologies 2.2.6 Spark 2.2.7 Other Databases & Analytic Technologies 2.3 Key Characteristics of Big Data 2.3.1 Volume 2.3.2 Velocity 2.3.3 Variety 2.3.4 Value 2.4 Market Growth Drivers 2.4.1 Awareness of Benefits 2.4.2 Maturation of Big Data Platforms 2.4.3 Continued Investments by Web Giants, Governments & Enterprises 2.4.4 Growth of Data Volume, Velocity & Variety 2.4.5 Vendor Commitments & Partnerships 2.4.6 Technology Trends Lowering Entry Barriers 2.5 Market Barriers 2.5.1 Lack of Analytic Specialists 2.5.2 Uncertain Big Data Strategies 2.5.3 Organizational Resistance to Big Data Adoption 2.5.4 Technical Challenges: Scalability & Maintenance 2.5.5 Security & Privacy Concerns =20 3 Chapter 3: Big Data Analytics 3.1 What are Big Data Analytics=3F 3.2 The Importance of Analytics 3.3 Reactive vs. Proactive Analytics 3.4 Customer vs. Operational Analytics 3.5 Technology & Implementation Approaches 3.5.1 Grid Computing 3.5.2 In-Database Processing 3.5.3 In-Memory Analytics 3.5.4 Machine Learning & Data Mining 3.5.5 Predictive Analytics 3.5.6 NLP (Natural Language Processing) 3.5.7 Text Analytics 3.5.8 Visual Analytics 3.5.9 Social Media, IT & Telco Network Analytics =20 4 Chapter 4: Big Data in Automotive, Aerospace & Transportation 4.1 Overview & Investment Potential 4.2 Key Applications 4.2.1 Autonomous Driving 4.2.2 Warranty Analytics for Automotive OEMs 4.2.3 Predictive Aircraft Maintenance & Fuel Optimization 4.2.4 Air Traffic Control 4.2.5 Transport Fleet Optimization 4.2.6 UBI (Usage Based Insurance) 4.3 Case Studies 4.3.1 Delphi Automotive: Monetizing Connected Vehicles with Big Data 4.3.2 Boeing: Making Flying More Efficient with Big Data 4.3.3 BMW: Eliminating Defects in New Vehicle Models with Big Data 4.3.4 Toyota Motor Corporation: Powering Smart Cars with Big Data 4.3.5 Ford Motor Company: Making Efficient Transportation Decisions with Bi= g Data =20 5 Chapter 5: Big Data in Banking & Securities 5.1 Overview & Investment Potential 5.2 Key Applications 5.2.1 Customer Retention & Personalized Product Offering 5.2.2 Risk Management 5.2.3 Fraud Detection 5.2.4 Credit Scoring 5.3 Case Studies 5.3.1 HSBC Group: Avoiding Regulatory Penalties with Big Data 5.3.2 JPMorgan Chase & Co.: Improving Business Processes with Big Data 5.3.3 OTP Bank: Reducing Loan Defaults with Big Data 5.3.4 CBA (Commonwealth Bank of Australia): Providing Personalized Services= with Big Data =20 6 Chapter 6: Big Data in Defense & Intelligence 6.1 Overview & Investment Potential 6.2 Key Applications 6.2.1 Intelligence Gathering 6.2.2 Battlefield Analytics 6.2.3 Energy Saving Opportunities in the Battlefield 6.2.4 Preventing Injuries on the Battlefield 6.3 Case Studies 6.3.1 U.S. Air Force: Providing Actionable Intelligence to Warfighters with= Big Data 6.3.2 Royal Navy: Empowering Submarine Warfare with Big Data 6.3.3 NSA (National Security Agency): Capitalizing on Big Data to Detect Th= reats 6.3.4 Ministry of State Security, China: Predictive Policing with Big Data 6.3.5 French DGSE (General Directorate for External Security): Enhancing In= telligence with Big Data =20 7 Chapter 7: Big Data in Education 7.1 Overview & Investment Potential 7.2 Key Applications 7.2.1 Information Integration 7.2.2 Identifying Learning Patterns 7.2.3 Enabling Student-Directed Learning 7.3 Case Studies 7.3.1 Purdue University: Ensuring Successful Higher Education Outcomes with= Big Data 7.3.2 Nottingham Trent University: Successful Student Outcomes with Big Data 7.3.3 Edith Cowen University: Increasing Student Retention with Big Data =20 8 Chapter 8: Big Data in Healthcare & Pharma 8.1 Overview & Investment Potential 8.2 Key Applications 8.2.1 Managing Population Health Efficiently 8.2.2 Improving Patient Care with Medical Data Analytics 8.2.3 Improving Clinical Development & Trials 8.2.4 Drug Development: Improving Time to Market 8.3 Case Studies 8.3.1 Amino: Healthcare Transparency with Big Data 8.3.2 Novartis: Digitizing Healthcare with Big Data 8.3.3 GSK (GlaxoSmithKline): Accelerating Drug Discovering with Big Data 8.3.4 Pfizer: Developing Effective and Targeted Therapies with Big Data 8.3.5 Roche: Personalizing Healthcare with Big Data 8.3.6 Sanofi: Proactive Diabetes Care with Big Data =20 9 Chapter 9: Big Data in Smart Cities & Intelligent Buildings 9.1 Overview & Investment Potential 9.2 Key Applications 9.2.1 Energy Optimization & Fault Detection 9.2.2 Intelligent Building Analytics 9.2.3 Urban Transportation Management 9.2.4 Optimizing Energy Production 9.2.5 Water Management 9.2.6 Urban Waste Management 9.3 Case Studies 9.3.1 Singapore: Building a Smart Nation with Big Data 9.3.2 Glasgow City Council: Promoting Smart City Efforts with Big Data 9.3.3 OVG Real Estate: Powering the World=92s Most Intelligent Building wit= h Big Data =20 10 Chapter 10: Big Data in Insurance 10.1 Overview & Investment Potential 10.2 Key Applications 10.2.1 Claims Fraud Mitigation 10.2.2 Customer Retention & Profiling 10.2.3 Risk Management 10.3 Case Studies 10.3.1 Zurich Insurance Group: Enhancing Risk Management with Big Data 10.3.2 RSA Group: Improving Customer Relations with Big Data 10.3.3 Primerica: Improving Insurance Sales Force Productivity with Big Data =20 11 Chapter 11: Big Data in Manufacturing & Natural Resources 11.1 Overview & Investment Potential 11.2 Key Applications 11.2.1 Asset Maintenance & Downtime Reduction 11.2.2 Quality & Environmental Impact Control 11.2.3 Optimized Supply Chain 11.2.4 Exploration & Identification of Natural Resources 11.3 Case Studies 11.3.1 Intel Corporation: Cutting Manufacturing Costs with Big Data 11.3.2 Dow Chemical Company: Optimizing Chemical Manufacturing with Big Data 11.3.3 Michelin: Improving the Efficiency of Supply Chain and Manufacturing= with Big Data 11.3.4 Brunei: Saving Natural Resources with Big Data =20 12 Chapter 12: Big Data in Web, Media & Entertainment 12.1 Overview & Investment Potential 12.2 Key Applications 12.2.1 Audience & Advertising Optimization 12.2.2 Channel Optimization 12.2.3 Recommendation Engines 12.2.4 Optimized Search 12.2.5 Live Sports Event Analytics 12.2.6 Outsourcing Big Data Analytics to Other Verticals 12.3 Case Studies 12.3.1 Netflix: Improving Viewership with Big Data 12.3.2 NFL (National Football League): Improving Stadium Experience with Bi= g Data 12.3.3 Walt Disney Company: Enhancing Theme Park Experience with Big Data 12.3.4 Baidu: Reshaping Search Capabilities with Big Data 12.3.5 Constant Contact: Effective Marketing with Big Data =20 13 Chapter 13: Big Data in Public Safety & Homeland Security 13.1 Overview & Investment Potential 13.2 Key Applications 13.2.1 Cyber Crime Mitigation 13.2.2 Crime Prediction Analytics 13.2.3 Video Analytics & Situational Awareness 13.3 Case Studies 13.3.1 DHS (U.S. Department of Homeland Security): Identifying Threats to P= hysical and Network Infrastructure with Big Data 13.3.2 Dubai Police: Locating Wanted Vehicles More Efficiently with Big Data 13.3.3 Memphis Police Department: Crime Reduction with Big Data =20 14 Chapter 14: Big Data in Public Services 14.1 Overview & Investment Potential 14.2 Key Applications 14.2.1 Public Sentiment Analysis 14.2.2 Tax Collection & Fraud Detection 14.2.3 Economic Analysis 14.2.4 Predicting & Mitigating Disasters 14.3 Case Studies 14.3.1 ONS (Office for National Statistics): Exploring the UK Economy with = Big Data 14.3.2 New York State Department of Taxation and Finance: Increasing Tax Re= venue with Big Data 14.3.3 Alameda County Social Services Agency: Benefit Fraud Reduction with = Big Data 14.3.4 City of Chicago: Improving Government Productivity with Big Data 14.3.5 FDNY (Fire Department of the City of New York): Fighting Fires with = Big Data 14.3.6 Ambulance Victoria: Improving Patient Survival Rates with Big Data =20 15 Chapter 15: Big Data in Retail, Wholesale & Hospitality 15.1 Overview & Investment Potential 15.2 Key Applications 15.2.1 Customer Sentiment Analysis 15.2.2 Customer & Branch Segmentation 15.2.3 Price Optimization 15.2.4 Personalized Marketing 15.2.5 Optimizing & Monitoring the Supply Chain 15.2.6 In-Field Sales Analytics 15.3 Case Studies 15.3.1 Walmart: Making Smarter Stocking Decision with Big Data 15.3.2 Tesco: Reducing Supermarket Energy Bills with Big Data 15.3.3 Marriott International: Elevating Guest Services with Big Data 15.3.4 JJ Food Service: Predictive Wholesale Shopping Lists with Big Data =20 16 Chapter 16: Big Data in Telecommunications 16.1 Overview & Investment Potential 16.2 Key Applications 16.2.1 Network Performance & Coverage Optimization 16.2.2 Customer Churn Prevention 16.2.3 Personalized Marketing 16.2.4 Tailored Location Based Services 16.2.5 Fraud Detection 16.3 Case Studies 16.3.1 BT Group: Hunting Down Nuisance Callers with Big Data 16.3.2 AT&T: Smart Network Management with Big Data 16.3.3 T-Mobile USA: Cutting Down Churn Rate with Big Data 16.3.4 TEOCO: Helping Service Providers Save Millions with Big Data 16.3.5 Freedom Mobile: Optimizing Video Quality with Big Data 16.3.6 Coriant: SaaS Based Analytics with Big Data =20 17 Chapter 17: Big Data in Utilities & Energy 17.1 Overview & Investment Potential 17.2 Key Applications 17.2.1 Customer Retention 17.2.2 Forecasting Energy 17.2.3 Billing Analytics 17.2.4 Predictive Maintenance 17.2.5 Maximizing the Potential of Drilling 17.2.6 Production Optimization 17.3 Case Studies 17.3.1 Royal Dutch Shell: Developing Data-Driven Oil Fields with Big Data 17.3.2 British Gas: Improving Customer Service with Big Data 17.3.3 Oncor Electric Delivery: Intelligent Power Grid Management with Big = Data =20 18 Chapter 18: Big Data Industry Roadmap & Value Chain 18.1 Big Data Industry Roadmap 18.1.1 2017 =96 2020: Investments in Predictive Analytics & SaaS-Based Big = Data Offerings 18.1.2 2020 =96 2025: Growing Focus on Cognitive & Personalized Analytics 18.1.3 2025 =96 2030: Convergence with Future IoT Applications 18.2 The Big Data Value Chain 18.2.1 Hardware Providers 18.2.1.1 Storage & Compute Infrastructure Providers 18.2.1.2 Networking Infrastructure Providers 18.2.2 Software Providers 18.2.2.1 Hadoop & Infrastructure Software Providers 18.2.2.2 SQL & NoSQL Providers 18.2.2.3 Analytic Platform & Application Software Providers 18.2.2.4 Cloud Platform Providers 18.2.3 Professional Services Providers 18.2.4 End-to-End Solution Providers 18.2.5 Vertical Enterprises =20 19 Chapter 19: Standardization & Regulatory Initiatives 19.1 ASF (Apache Software Foundation) 19.1.1 Management of Hadoop 19.1.2 Big Data Projects Beyond Hadoop 19.2 CSA (Cloud Security Alliance) 19.2.1 BDWG (Big Data Working Group) 19.3 CSCC (Cloud Standards Customer Council) 19.3.1 Big Data Working Group 19.4 DMG (Data Mining Group) 19.4.1 PMML (Predictive Model Markup Language) Working Group 19.4.2 PFA (Portable Format for Analytics) Working Group 19.5 IEEE (Institute of Electrical and Electronics Engineers) =96Big Data I= nitiative 19.6 INCITS (InterNational Committee for Information Technology Standards) 19.6.1 Big Data Technical Committee 19.7 ISO (International Organization for Standardization) 19.7.1 ISO/IEC JTC 1/SC 32: Data Management and Interchange 19.7.2 ISO/IEC JTC 1/SC 38: Cloud Computing and Distributed Platforms 19.7.3 ISO/IEC JTC 1/SC 27: IT Security Techniques 19.7.4 ISO/IEC JTC 1/WG 9: Big Data 19.7.5 Collaborations with Other ISO Work Groups 19.8 ITU (International Telecommunications Union) 19.8.1 ITU-T Y.3600: Big Data =96 Cloud Computing Based Requirements and Ca= pabilities 19.8.2 Other Deliverables Through SG (Study Group) 13 on Future Networks 19.8.3 Other Relevant Work 19.9 Linux Foundation 19.9.1 ODPi (Open Ecosystem of Big Data) 19.10 NIST (National Institute of Standards and Technology) 19.10.1 NBD-PWG (NIST Big Data Public Working Group) 19.11 OASIS (Organization for the Advancement of Structured Information Sta= ndards) 19.11.1 Technical Committees 19.12 ODaF (Open Data Foundation) 19.12.1 Big Data Accessibility 19.13 ODCA (Open Data Center Alliance) 19.13.1 Work on Big Data 19.14 OGC (Open Geospatial Consortium) 19.14.1 Big Data DWG (Domain Working Group) 19.15 TM Forum 19.15.1 Big Data Analytics Strategic Program 19.16 TPC (Transaction Processing Performance Council) 19.16.1 TPC-BDWG (TPC Big Data Working Group) 19.17 W3C (World Wide Web Consortium) 19.17.1 Big Data Community Group 19.17.2 Open Government Community Group =20 20 Chapter 20: Market Analysis & Forecasts 20.1 Global Outlook for the Big Data Market 20.2 Submarket Segmentation 20.2.1 Storage and Compute Infrastructure 20.2.2 Networking Infrastructure 20.2.3 Hadoop & Infrastructure Software 20.2.4 SQL 20.2.5 NoSQL 20.2.6 Analytic Platforms & Applications 20.2.7 Cloud Platforms 20.2.8 Professional Services 20.3 Vertical Market Segmentation 20.3.1 Automotive, Aerospace & Transportation 20.3.2 Banking & Securities 20.3.3 Defense & Intelligence 20.3.4 Education 20.3.5 Healthcare & Pharmaceutical 20.3.6 Smart Cities & Intelligent Buildings 20.3.7 Insurance 20.3.8 Manufacturing & Natural Resources 20.3.9 Media & Entertainment 20.3.10 Public Safety & Homeland Security 20.3.11 Public Services 20.3.12 Retail, Wholesale & Hospitality 20.3.13 Telecommunications 20.3.14 Utilities & Energy 20.3.15 Other Sectors 20.4 Regional Outlook 20.5 Asia Pacific 20.5.1 Country Level Segmentation 20.5.2 Australia 20.5.3 China 20.5.4 India 20.5.5 Indonesia 20.5.6 Japan 20.5.7 Malaysia 20.5.8 Pakistan 20.5.9 Philippines 20.5.10 Singapore 20.5.11 South Korea 20.5.12 Taiwan 20.5.13 Thailand 20.5.14 Rest of Asia Pacific 20.6 Eastern Europe 20.6.1 Country Level Segmentation 20.6.2 Czech Republic 20.6.3 Poland 20.6.4 Russia 20.6.5 Rest of Eastern Europe 20.7 Latin & Central America 20.7.1 Country Level Segmentation 20.7.2 Argentina 20.7.3 Brazil 20.7.4 Mexico 20.7.5 Rest of Latin & Central America 20.8 Middle East & Africa 20.8.1 Country Level Segmentation 20.8.2 Israel 20.8.3 Qatar 20.8.4 Saudi Arabia 20.8.5 South Africa 20.8.6 UAE 20.8.7 Rest of the Middle East & Africa 20.9 North America 20.9.1 Country Level Segmentation 20.9.2 Canada 20.9.3 USA 20.10 Western Europe 20.10.1 Country Level Segmentation 20.10.2 Denmark 20.10.3 Finland 20.10.4 France 20.10.5 Germany 20.10.6 Italy 20.10.7 Netherlands 20.10.8 Norway 20.10.9 Spain 20.10.10 Sweden 20.10.11 UK 20.10.12 Rest of Western Europe =20 21 Chapter 21: Vendor Landscape 21.1 1010data 21.2 Absolutdata 21.3 Accenture 21.4 Actian Corporation 21.5 Adaptive Insights 21.6 Advizor Solutions 21.7 AeroSpike 21.8 AFS Technologies 21.9 Alation 21.10 Algorithmia 21.11 Alluxio 21.12 Alpine Data 21.13 Alteryx 21.14 AMD (Advanced Micro Devices) 21.15 Apixio 21.16 Arcadia Data 21.17 Arimo 21.18 ARM 21.19 AtScale 21.20 Attivio 21.21 Attunity 21.22 Automated Insights 21.23 AWS (Amazon Web Services) 21.24 Axiomatics 21.25 Ayasdi 21.26 Basho Technologies 21.27 BCG (Boston Consulting Group) 21.28 Bedrock Data 21.29 BetterWorks 21.30 Big Cloud Analytics 21.31 Big Panda 21.32 Birst 21.33 Bitam 21.34 Blue Medora 21.35 BlueData Software 21.36 BlueTalon 21.37 BMC Software 21.38 BOARD International 21.39 Booz Allen Hamilton 21.40 Boxever 21.41 CACI International 21.42 Cambridge Semantics 21.43 Capgemini 21.44 Cazena 21.45 Centrifuge Systems 21.46 CenturyLink 21.47 Chartio 21.48 Cisco Systems 21.49 Civis Analytics 21.50 ClearStory Data 21.51 Cloudability 21.52 Cloudera 21.53 Clustrix 21.54 CognitiveScale 21.55 Collibra 21.56 Concurrent Computer Corporation 21.57 Confluent 21.58 Contexti 21.59 Continuum Analytics 21.60 Couchbase 21.61 CrowdFlower 21.62 Databricks 21.63 DataGravity 21.64 Dataiku 21.65 Datameer 21.66 DataRobot 21.67 DataScience 21.68 DataStax 21.69 DataTorrent 21.70 Datawatch Corporation 21.71 Datos IO 21.72 DDN (DataDirect Networks) 21.73 Decisyon 21.74 Dell Technologies 21.75 Deloitte 21.76 Demandbase 21.77 Denodo Technologies 21.78 Digital Reasoning Systems 21.79 Dimensional Insight 21.80 Dolphin Enterprise Solutions Corporation 21.81 Domino Data Lab 21.82 Domo 21.83 DriveScale 21.84 Dundas Data Visualization 21.85 DXC Technology 21.86 Eligotech 21.87 Engineering Group (Engineering Ingegneria Informatica) 21.88 EnterpriseDB 21.89 eQ Technologic 21.90 Ericsson 21.91 EXASOL 21.92 Facebook 21.93 FICO (Fair Isaac Corporation) 21.94 Fractal Analytics 21.95 Fujitsu 21.96 Fuzzy Logix 21.97 Gainsight 21.98 GE (General Electric) 21.99 Glassbeam 21.100 GoodData Corporation 21.101 Google 21.102 Greenwave Systems 21.103 GridGain Systems 21.104 Guavus 21.105 H2O.ai 21.106 HDS (Hitachi Data Systems) 21.107 Hedvig 21.108 Hortonworks 21.109 HPE (Hewlett Packard Enterprise) 21.110 Huawei 21.111 IBM Corporation 21.112 iDashboards 21.113 Impetus Technologies 21.114 Incorta 21.115 InetSoft Technology Corporation 21.116 Infer 21.117 Infor 21.118 Informatica Corporation 21.119 Information Builders 21.120 Infosys 21.121 Infoworks 21.122 Insightsoftware.com 21.123 InsightSquared 21.124 Intel Corporation 21.125 Interana 21.126 InterSystems Corporation 21.127 Jedox 21.128 Jethro 21.129 Jinfonet Software 21.130 Juniper Networks 21.131 KALEAO 21.132 Keen IO 21.133 Kinetica 21.134 KNIME 21.135 Kognitio 21.136 Kyvos Insights 21.137 Lavastorm 21.138 Lexalytics 21.139 Lexmark International 21.140 Logi Analytics 21.141 Longview Solutions 21.142 Looker Data Sciences 21.143 LucidWorks 21.144 Luminoso Technologies 21.145 Maana 21.146 Magento Commerce 21.147 Manthan Software Services 21.148 MapD Technologies 21.149 MapR Technologies 21.150 MariaDB Corporation 21.151 MarkLogic Corporation 21.152 Mathworks 21.153 MemSQL 21.154 Metric Insights 21.155 Microsoft Corporation 21.156 MicroStrategy 21.157 Minitab 21.158 MongoDB 21.159 Mu Sigma 21.160 Neo Technology 21.161 NetApp 21.162 Nimbix 21.163 Nokia 21.164 NTT Data Corporation 21.165 Numerify 21.166 NuoDB 21.167 Nutonian 21.168 NVIDIA Corporation 21.169 Oblong Industries 21.170 OpenText Corporation 21.171 Opera Solutions 21.172 Optimal Plus 21.173 Oracle Corporation 21.174 Palantir Technologies 21.175 Panorama Software 21.176 Paxata 21.177 Pentaho Corporation 21.178 Pepperdata 21.179 Phocas Software 21.180 Pivotal Software 21.181 Prognoz 21.182 Progress Software Corporation 21.183 PwC (PricewaterhouseCoopers International) 21.184 Pyramid Analytics 21.185 Qlik 21.186 Quantum Corporation 21.187 Qubole 21.188 Rackspace 21.189 Radius Intelligence 21.190 RapidMiner 21.191 Recorded Future 21.192 Red Hat 21.193 Redis Labs 21.194 RedPoint Global 21.195 Reltio 21.196 RStudio 21.197 Ryft Systems 21.198 Sailthru 21.199 Salesforce.com 21.200 Salient Management Company 21.201 Samsung Group 21.202 SAP 21.203 SAS Institute 21.204 ScaleDB 21.205 ScaleOut Software 21.206 SCIO Health Analytics 21.207 Seagate Technology 21.208 Sinequa 21.209 SiSense 21.210 SnapLogic 21.211 Snowflake Computing 21.212 Software AG 21.213 Splice Machine 21.214 Splunk 21.215 Sqrrl 21.216 Strategy Companion Corporation 21.217 StreamSets 21.218 Striim 21.219 Sumo Logic 21.220 Supermicro (Super Micro Computer) 21.221 Syncsort 21.222 SynerScope 21.223 Tableau Software 21.224 Talena 21.225 Talend 21.226 Tamr 21.227 TARGIT 21.228 TCS (Tata Consultancy Services) 21.229 Teradata Corporation 21.230 ThoughtSpot 21.231 TIBCO Software 21.232 Tidemark 21.233 Toshiba Corporation 21.234 Trifacta 21.235 Unravel Data 21.236 VMware 21.237 VoltDB 21.238 Waterline Data 21.239 Western Digital Corporation 21.240 WiPro 21.241 Workday 21.242 Xplenty 21.243 Yellowfin International 21.244 Yseop 21.245 Zendesk 21.246 Zoomdata 21.247 Zucchetti =20 22 Chapter 22: Conclusion & Strategic Recommendations 22.1 Big Data Technology: Beyond Data Capture & Analytics 22.2 Transforming IT from a Cost Center to a Profit Center 22.3 Can Privacy Implications Hinder Success=3F 22.4 Maximizing Innovation with Careful Regulation 22.5 Battling Organizational & Data Silos 22.6 Moving Big Data to the Cloud 22.7 Software vs. Hardware Investments 22.8 Vendor Share: Who Leads the Market=3F 22.9 Moving Towards Consolidation: Review of M&A Activity in the Vendor Are= na 22.10 Big Data Driving Wider IT Industry Investments 22.11 Assessing the Impact of IoT & M2M 22.12 Recommendations 22.12.1 Big Data Hardware, Software & Professional Services Providers 22.12.2 Enterprises =20 List of Figures: =20 Figure 1: Hadoop Architecture Figure 2: Reactive vs. Proactive Analytics Figure 3: Big Data Industry Roadmap Figure 4: Big Data Value Chain Figure 5: Key Aspects of Big Data Standardization Figure 6: Global Big Data Revenue: 2017 - 2030 ($ Million) Figure 7: Global Big Data Revenue by Submarket: 2017 - 2030 ($ Million) Figure 8: Global Big Data Storage and Compute Infrastructure Submarket Reve= nue: 2017 - 2030 ($ Million) Figure 9: Global Big Data Networking Infrastructure Submarket Revenue: 2017= - 2030 ($ Million) Figure 10: Global Big Data Hadoop & Infrastructure Software Submarket Reven= ue: 2017 - 2030 ($ Million) Figure 11: Global Big Data SQL Submarket Revenue: 2017 - 2030 ($ Million) Figure 12: Global Big Data NoSQL Submarket Revenue: 2017 - 2030 ($ Million) Figure 13: Global Big Data Analytic Platforms & Applications Submarket Reve= nue: 2017 - 2030 ($ Million) Figure 14: Global Big Data Cloud Platforms Submarket Revenue: 2017 - 2030 (= $ Million) Figure 15: Global Big Data Professional Services Submarket Revenue: 2017 - = 2030 ($ Million) Figure 16: Global Big Data Revenue by Vertical Market: 2017 - 2030 ($ Milli= on) Figure 17: Global Big Data Revenue in the Automotive, Aerospace & Transport= ation Sector: 2017 - 2030 ($ Million) Figure 18: Global Big Data Revenue in the Banking & Securities Sector: 2017= - 2030 ($ Million) Figure 19: Global Big Data Revenue in the Defense & Intelligence Sector: 20= 17 - 2030 ($ Million) Figure 20: Global Big Data Revenue in the Education Sector: 2017 - 2030 ($ = Million) Figure 21: Global Big Data Revenue in the Healthcare & Pharmaceutical Secto= r: 2017 - 2030 ($ Million) Figure 22: Global Big Data Revenue in the Smart Cities & Intelligent Buildi= ngs Sector: 2017 - 2030 ($ Million) Figure 23: Global Big Data Revenue in the Insurance Sector: 2017 - 2030 ($ = Million) Figure 24: Global Big Data Revenue in the Manufacturing & Natural Resources= Sector: 2017 - 2030 ($ Million) Figure 25: Global Big Data Revenue in the Media & Entertainment Sector: 201= 7 - 2030 ($ Million) Figure 26: Global Big Data Revenue in the Public Safety & Homeland Security= Sector: 2017 - 2030 ($ Million) Figure 27: Global Big Data Revenue in the Public Services Sector: 2017 - 20= 30 ($ Million) Figure 28: Global Big Data Revenue in the Retail, Wholesale & Hospitality S= ector: 2017 - 2030 ($ Million) Figure 29: Global Big Data Revenue in the Telecommunications Sector: 2017 -= 2030 ($ Million) Figure 30: Global Big Data Revenue in the Utilities & Energy Sector: 2017 -= 2030 ($ Million) Figure 31: Global Big Data Revenue in Other Vertical Sectors: 2017 - 2030 (= $ Million) Figure 32: Big Data Revenue by Region: 2017 - 2030 ($ Million) Figure 33: Asia Pacific Big Data Revenue: 2017 - 2030 ($ Million) Figure 34: Asia Pacific Big Data Revenue by Country: 2017 - 2030 ($ Million) Figure 35: Australia Big Data Revenue: 2017 - 2030 ($ Million) Figure 36: China Big Data Revenue: 2017 - 2030 ($ Million) Figure 37: India Big Data Revenue: 2017 - 2030 ($ Million) Figure 38: Indonesia Big Data Revenue: 2017 - 2030 ($ Million) Figure 39: Japan Big Data Revenue: 2017 - 2030 ($ Million) Figure 40: Malaysia Big Data Revenue: 2017 - 2030 ($ Million) Figure 41: Pakistan Big Data Revenue: 2017 - 2030 ($ Million) Figure 42: Philippines Big Data Revenue: 2017 - 2030 ($ Million) Figure 43: Singapore Big Data Revenue: 2017 - 2030 ($ Million) Figure 44: South Korea Big Data Revenue: 2017 - 2030 ($ Million) Figure 45: Taiwan Big Data Revenue: 2017 - 2030 ($ Million) Figure 46: Thailand Big Data Revenue: 2017 - 2030 ($ Million) Figure 47: Big Data Revenue in the Rest of Asia Pacific: 2017 - 2030 ($ Mil= lion) Figure 48: Eastern Europe Big Data Revenue: 2017 - 2030 ($ Million) Figure 49: Eastern Europe Big Data Revenue by Country: 2017 - 2030 ($ Milli= on) Figure 50: Czech Republic Big Data Revenue: 2017 - 2030 ($ Million) Figure 51: Poland Big Data Revenue: 2017 - 2030 ($ Million) Figure 52: Russia Big Data Revenue: 2017 - 2030 ($ Million) Figure 53: Big Data Revenue in the Rest of Eastern Europe: 2017 - 2030 ($ M= illion) Figure 54: Latin & Central America Big Data Revenue: 2017 - 2030 ($ Million) Figure 55: Latin & Central America Big Data Revenue by Country: 2017 - 2030= ($ Million) Figure 56: Argentina Big Data Revenue: 2017 - 2030 ($ Million) Figure 57: Brazil Big Data Revenue: 2017 - 2030 ($ Million) Figure 58: Mexico Big Data Revenue: 2017 - 2030 ($ Million) Figure 59: Big Data Revenue in the Rest of Latin & Central America: 2017 - = 2030 ($ Million) Figure 60: Middle East & Africa Big Data Revenue: 2017 - 2030 ($ Million) Figure 61: Middle East & Africa Big Data Revenue by Country: 2017 - 2030 ($= Million) Figure 62: Israel Big Data Revenue: 2017 - 2030 ($ Million) Figure 63: Qatar Big Data Revenue: 2017 - 2030 ($ Million) Figure 64: Saudi Arabia Big Data Revenue: 2017 - 2030 ($ Million) Figure 65: South Africa Big Data Revenue: 2017 - 2030 ($ Million) Figure 66: UAE Big Data Revenue: 2017 - 2030 ($ Million) Figure 67: Big Data Revenue in the Rest of the Middle East & Africa: 2017 -= 2030 ($ Million) Figure 68: North America Big Data Revenue: 2017 - 2030 ($ Million) Figure 69: North America Big Data Revenue by Country: 2017 - 2030 ($ Millio= n) Figure 70: Canada Big Data Revenue: 2017 - 2030 ($ Million) Figure 71: USA Big Data Revenue: 2017 - 2030 ($ Million) Figure 72: Western Europe Big Data Revenue: 2017 - 2030 ($ Million) Figure 73: Western Europe Big Data Revenue by Country: 2017 - 2030 ($ Milli= on) Figure 74: Denmark Big Data Revenue: 2017 - 2030 ($ Million) Figure 75: Finland Big Data Revenue: 2017 - 2030 ($ Million) Figure 76: France Big Data Revenue: 2017 - 2030 ($ Million) Figure 77: Germany Big Data Revenue: 2017 - 2030 ($ Million) Figure 78: Italy Big Data Revenue: 2017 - 2030 ($ Million) Figure 79: Netherlands Big Data Revenue: 2017 - 2030 ($ Million) Figure 80: Norway Big Data Revenue: 2017 - 2030 ($ Million) Figure 81: Spain Big Data Revenue: 2017 - 2030 ($ Million) Figure 82: Sweden Big Data Revenue: 2017 - 2030 ($ Million) Figure 83: UK Big Data Revenue: 2017 - 2030 ($ Million) Figure 84: Big Data Revenue in the Rest of Western Europe: 2017 - 2030 ($ M= illion) Figure 85: Global Big Data Workload Distribution by Environment: 2017 - 203= 0 (%) Figure 86: Global Big Data Revenue by Hardware, Software & Professional Ser= vices: 2017 - 2030 ($ Million) Figure 87: Big Data Vendor Market Share (%) Figure 88: Global IT Expenditure Driven by Big Data Investments: 2017 - 203= 0 ($ Million) Figure 89: Global M2M Connections by Access Technology: 2017 - 2030 (Millio= ns) =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com =20 From owner-freebsd-ppc@freebsd.org Sat Jun 10 16:09:24 2017 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 AC00EBF09D8 for ; Sat, 10 Jun 2017 16:09:24 +0000 (UTC) (envelope-from ipc@peercorpstrust.org) Received: from server210.webhostingpad.com (server210mail.webhostingpad.com [69.65.33.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86C987DC6B for ; Sat, 10 Jun 2017 16:09:23 +0000 (UTC) (envelope-from ipc@peercorpstrust.org) Received: from 87-92-243-246.bb.dnainternet.fi ([87.92.243.246]:4668 helo=[192.168.1.28]) by server210.webhostingpad.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from ) id 1dJiKs-00481t-N9 for freebsd-ppc@freebsd.org; Sat, 10 Jun 2017 10:29:58 -0500 To: freebsd-ppc@freebsd.org From: PeerCorps Trust Fund Subject: FreeBSD on OPENPOWER Organization: PeerCorps Trust Fund Message-ID: Date: Sat, 10 Jun 2017 18:29:56 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server210.webhostingpad.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - peercorpstrust.org X-Get-Message-Sender-Via: server210.webhostingpad.com: authenticated_id: ipc@peercorpstrust.org X-Authenticated-Sender: server210.webhostingpad.com: ipc@peercorpstrust.org X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jun 2017 16:09:24 -0000 Hi, Is there a document or other reference material concerning the status (intended or otherwise) of FreeBSD on OpenPower 8/9? Are there others interested in this? Mike From owner-freebsd-ppc@freebsd.org Sat Jun 10 16:16:27 2017 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 90157BF0DC3 for ; Sat, 10 Jun 2017 16:16:27 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::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 5E27F7E16C for ; Sat, 10 Jun 2017 16:16:27 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-ot0-x22a.google.com with SMTP id i31so50900813ota.3 for ; Sat, 10 Jun 2017 09:16:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CkA/0y0N5r+IDjO7+lH0ffRHWrlBPK9mgBLxAW4atrg=; b=RwojgDwCRV2hvG+6+mmNoQsv2BBMSuvs9zBZ9xzWAmz/ugz+5pOJQS+hMwSJPWnclL qWdH+MJSw3PpF/XEEzwq8PlNM/fWpH9YStkort8OE5MF9HprQJI1n5eu02yXMt1ONOYo 7nAchlXVdp6a0gV+GkIj3ht4p71PjPmwAaY9o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CkA/0y0N5r+IDjO7+lH0ffRHWrlBPK9mgBLxAW4atrg=; b=nRh95ZCr9uQhyTbKAriKXGiJAPVdqcou+LxeWSEU4QVsfMsyA+SgJeLqqjwPLeG2Xh ZXhOIAHb4RHvItJLtaIWOsmJZeJBowlaUV2lvgc8MkC0kTHc0JC5h1yJQb5ZTM4ASlNM N5djHdhzHEU9ZNX14iBWb3JTTj0gQd0tadKzW05vnrlTahY1sGizpo8uBCtA9AFfdO/t svHYjOmfvDpeJo3bbmz1SInLJQCwz4cs/lLXv7hNsUrHLxQJzB5hPpoEXFoWIMteX92J 5toHBdTAcz32QBfy9IQjv2A8qeS7rya+MXd1+/IGg3g8gcm20VY0vvAiaxwGx1f3brUI V8wQ== X-Gm-Message-State: AODbwcAEWZmkuPbxmvMc5NzwDZARQq0tGKabBoV8m9ggHVM9mBqDwvIq ZpefgmJw26s6CPRbn8OWZUc2SJ5GojR7 X-Received: by 10.157.24.68 with SMTP id t4mr12994425ott.230.1497111386548; Sat, 10 Jun 2017 09:16:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.33.77 with HTTP; Sat, 10 Jun 2017 09:16:26 -0700 (PDT) In-Reply-To: References: From: Kevin Bowling Date: Sat, 10 Jun 2017 09:16:26 -0700 Message-ID: Subject: Re: FreeBSD on OPENPOWER To: PeerCorps Trust Fund Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jun 2017 16:16:27 -0000 I am interested in it commercially. I am attempting to work with IBM to fund SemiHalf to do most of the bring up but don't have any definitive answer as to whether this will actually happen yet. If you have a commercial use case, I would recommend bubbling it up through your sales channel. Regards, On Sat, Jun 10, 2017 at 8:29 AM, PeerCorps Trust Fund < ipc@peercorpstrust.org> wrote: > Hi, > > Is there a document or other reference material concerning the status > (intended or otherwise) of FreeBSD on OpenPower 8/9? Are there others > interested in this? > > Mike > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > From owner-freebsd-ppc@freebsd.org Sat Jun 10 17:15:35 2017 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 0206DBF23E6 for ; Sat, 10 Jun 2017 17:15:35 +0000 (UTC) (envelope-from ipc@peercorpstrust.org) Received: from server210.webhostingpad.com (server210mail.webhostingpad.com [69.65.33.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D235A802C5 for ; Sat, 10 Jun 2017 17:15:34 +0000 (UTC) (envelope-from ipc@peercorpstrust.org) Received: from 87-92-243-246.bb.dnainternet.fi ([87.92.243.246]:45155 helo=[192.168.1.28]) by server210.webhostingpad.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from ) id 1dJjz1-000CGL-52; Sat, 10 Jun 2017 12:15:31 -0500 Subject: Re: FreeBSD on OPENPOWER To: Kevin Bowling References: Cc: FreeBSD PowerPC ML From: PeerCorps Trust Fund Organization: PeerCorps Trust Fund Message-ID: Date: Sat, 10 Jun 2017 20:15:28 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server210.webhostingpad.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - peercorpstrust.org X-Get-Message-Sender-Via: server210.webhostingpad.com: authenticated_id: ipc@peercorpstrust.org X-Authenticated-Sender: server210.webhostingpad.com: ipc@peercorpstrust.org X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jun 2017 17:15:35 -0000 Hello! Happy to hear this. Out of curiosity what exactly is needed for the FreeBSD bring up? On 06/10/2017 07:16 PM, Kevin Bowling wrote: > I am interested in it commercially. I am attempting to work with IBM to > fund SemiHalf to do most of the bring up but don't have any definitive > answer as to whether this will actually happen yet. If you have a > commercial use case, I would recommend bubbling it up through your sales > channel. > > Regards, > > On Sat, Jun 10, 2017 at 8:29 AM, PeerCorps Trust Fund < > ipc@peercorpstrust.org> wrote: > >> Hi, >> >> Is there a document or other reference material concerning the status >> (intended or otherwise) of FreeBSD on OpenPower 8/9? Are there others >> interested in this? >> >> Mike >> _______________________________________________ >> freebsd-ppc@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >> > From owner-freebsd-ppc@freebsd.org Sat Jun 10 18:25:03 2017 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 8E077BF38D2 for ; Sat, 10 Jun 2017 18:25:03 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-153.reflexion.net [208.70.211.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4EE6882898 for ; Sat, 10 Jun 2017 18:25:02 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 26828 invoked from network); 10 Jun 2017 18:22:17 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 10 Jun 2017 18:22:17 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Sat, 10 Jun 2017 14:18:22 -0400 (EDT) Received: (qmail 5009 invoked from network); 10 Jun 2017 18:18:22 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 10 Jun 2017 18:18:22 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6C234EC80E9; Sat, 10 Jun 2017 11:18:21 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: FreeBSD on OPENPOWER From: Mark Millard In-Reply-To: Date: Sat, 10 Jun 2017 11:18:20 -0700 Cc: Kevin Bowling , FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <541DD61B-2613-47EC-95DA-7B28438211E9@dsl-only.net> References: To: PeerCorps Trust Fund X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jun 2017 18:25:03 -0000 On 2017-Jun-10, at 10:15 AM, PeerCorps Trust Fund = wrote: > Hello! >=20 > Happy to hear this. Out of curiosity what exactly is needed for the = FreeBSD bring up? There is an old (2015-Jan-31) page: https://wiki.freebsd.org/POWER8 I expect things have progressed since then. An old 2015-May status report was ( = https://lists.freebsd.org/pipermail/freebsd-announce/2015-May/001637.html = ): > FreeBSD on POWER8 >=20 > URL:=20 > http://www.tyan.com/campaign/openpower/ >=20 >=20 > Contact: Nathan Whitehorn < > nwhitehorn at freebsd.org > > > Contact: Justin Hibbits < > jhibbits at freebsd.org > > > Contact: Adrian Chadd < > adrian at freebsd.org > > >=20 > IBM and the OpenPOWER Foundation are pushing for a wider software = and > hardware ecosystem for POWER8-based systems. Starting in January = 2014, > we have been doing bringup work on a Tyan GN70-BP010 POWER8 server, = a > quad-core 3 GHz system with a total of 32 hardware threads. >=20 > Updates since the previous report: > * FreeBSD now boots under a hypervisor with the virtual SCSI = block > device; the issue previously preventing this has been fixed. > * The powerpc64 pmap code was rewritten to be more scalable, as = the > previous pmap code did not scale beyond a small number of CPUs. > * Initial support for IBM's Vector-Scalar Extensions (VSX) was = added. > * The FreeBSD kernel was made completely position independent for > powerpc64, and later powerpc32 as well. >=20 > This project is sponsored by The FreeBSD Foundation. >=20 > Open tasks: >=20 > 1. Get FreeBSD booting natively, rather than under KVM. This = requires > writing OPAL drivers for the various hardware devices in the > system. > 2. Integrate loader(8) with petitboot. http://adrianchadd.blogspot.de/2015/02/freebsd-on-power8-its-alive.html = says, in part: > Fast forward a few weeks - he's figured out the KVM issues, their lack = of support for some mandated hypervisor APIs and other bugs - FreeBSD = now boots inside of the hypervisor environment and seems stable enough = to do development on. >=20 > He then found the existing powerpc pmap (physical memory management) = code wasn't very SMP friendly - it works fine on one and two CPU powerpc = machines, but this POWER8 evaluation board is a 4-core, 32-thread CPU. = So a few days of development went by and he rewrote most of the pmap = code to be much more fine grained locked and scale much, much better = than the existing code. (He also found the PS3 hypervisor layer isn't = thread-safe.) >=20 > What's been done thus far? >=20 > =E2=80=A2 FreeBSD boots inside the hypervisor environment; > =E2=80=A2 Virtualised console, networking and storage all work; > =E2=80=A2 (in progress) new, scalable pmap implementation; > =E2=80=A2 Initial support for the Vector-Scalar Extension (VSX) = that's found on POWER7 and POWER8. > So, I'm impressed. Nathan's done a fantastic job bringing the whole = thing up. There's some further work on the new powerpc technology that = needs doing (things like the new vector processing units, performance = counter support and such) and I'm sure Justin and Nathan will poke = powerpc dtrace support into further good shape. I'm going to see if we = can fix a chelsio 40G NIC into one of these and work with their = developers to fix any endian/busdma issues that creep up, and then do = some network stack scaling testing with it. There's also the missing = hardware/hypervisor support to run FreeBSD on the bare metal, which = would be a fantastic achievement. A 2016-Mar note ( = https://lists.freebsd.org/pipermail/freebsd-ppc/2016-March/008113.html ) was: > We boot multiuser without problems in the simulator. There are some=20 > remaining issues involving the bootloader that need to be resolved for=20= > real hardware. > -Nathan There was: = http://freebsd-bugs.freebsd.narkive.com/xZOoCt9C/bug-210106-current-won-t-= boot-on-ppc64-power8-under-ibm-kvm about "[Bug 210106] Current won't boot on PPC64 Power8 under IBM KVM" and its fix. I'll note list the material here. I'll stop searching with that. I do not know current details. I've never had access to such hardware. > On 06/10/2017 07:16 PM, Kevin Bowling wrote: >> I am interested in it commercially. I am attempting to work with IBM = to >> fund SemiHalf to do most of the bring up but don't have any = definitive >> answer as to whether this will actually happen yet. If you have a >> commercial use case, I would recommend bubbling it up through your = sales >> channel. >>=20 >> Regards, >>=20 >> On Sat, Jun 10, 2017 at 8:29 AM, PeerCorps Trust Fund < >> ipc@peercorpstrust.org> wrote: >>=20 >>> Hi, >>>=20 >>> Is there a document or other reference material concerning the = status >>> (intended or otherwise) of FreeBSD on OpenPower 8/9? Are there = others >>> interested in this? >>>=20 >>> Mike =3D=3D=3D Mark Millard markmi at dsl-only.net