From owner-freebsd-ppc@freebsd.org Mon Feb 13 11:04: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 31170CDD28A for ; Mon, 13 Feb 2017 11:04:45 +0000 (UTC) (envelope-from gabriel.diaz@vgtelecomreports.com) Received: from smtp.vgtelecomreports.com (smtp.vgtelecomreports.com [202.0.103.127]) by mx1.freebsd.org (Postfix) with ESMTP id C69F6B83 for ; Mon, 13 Feb 2017 11:04:40 +0000 (UTC) (envelope-from gabriel.diaz@vgtelecomreports.com) X-SmarterMail-Authenticated-As: admin@vgtelecomreports.com DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; d=vgtelecomreports.com; s=smtp; h=received:from:to:message-id:subject:date:mime-version:reply-to :content-type; b=qgQI3XEaCQJ6cYeqmM5t9RbIGkJTduwzddl/7fgeo8ITHeFlM+SuGamQYjhM5PzBn fRxQDTAFBxmxswNHC9sXqczG5FfuTwo6RO3nDmkrAq4+HprwFrqp+sV5+maRMiOAr kJQ7uzjcCYnSsiRoTAmVuBfzXnoS1U57hPH8+gYJ8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vgtelecomreports.com; s=smtp; h= content-type:reply-to:mime-version:date:subject:message-id:to:from; bh=GG08TLDtoJpVBsL7YFz8RwxPFnEhgYGq+ZmORJruVp8=; b=DU3dci2ECY54PRxA9jr1Btywa4SeJAm15ImPdvNDhfV3G8pHhTvvDhCWDN7dot1HV zuguiAGuFI0toEkTJPEHmRW6GvonJ2Bdp/cufyTBiH03odBocZM9ke4RrxAtAVkaQ h8H2mZJZL4KEse7kX7l7F39v+dW7SnBDFuhabUpAI= Received: from WIN-ASQ29B6R1EP (WIN-ASQ29B6R1EP [202.0.103.127]) by smtp.vgtelecomreports.com with SMTP; Mon, 13 Feb 2017 07:09:02 +0000 From: Gabriel Diaz To: freebsd-ppc@freebsd.org Message-Id: <20170213070902.987064520@vgtelecomreports.com> Subject: Power Bank Market Report 2017-2027 Date: Mon, 13 Feb 2017 07:09:02 +0000 MIME-Version: 1.0 Reply-To: gabriel.diaz@vgtelecomreports.com Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit 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: Mon, 13 Feb 2017 11:04:45 -0000 Visiongain - Business Report Updates Speak to our consultant now: +44 (0)20 8781 6961 Power Bank Market Report 2017-2027 Forecasts By Power Rating (Below 3,500 mAh, 3,501 - 20,000 mAh, Above 20,000 mAh) By Battery Type (Lithium-Ion (Li-Ion), Lithium-Polymer (Li-Po)) By Type (Portable, Battery Case, Solar(PV)), Plus Analysis of Leading Companies Developing Technologies For Laptops, Tablets, Smartphones & Other Mobile Devices The global power bank market will see sales of $15.1bn in 2017. The quick discharge rate of batteries in smartphones, tablets, MP3 players, and laptops due to the increased power and usage of such devices has stimulated the demand for portable battery sources. Power banks or external batteries are increasingly being adopted as a portable source of battery for devices with USB capability. These are majorly based on either lithium-ion or lithium-polymer batteries with power ratings that range below 3,500 mAh to above 20,000 mAh. The power bank market signifies a promising picture for the portable chargers’ industry. The current business scenario has witnessed an upsurge in the adoption of this technology in developed as well as the developing regions. The growth of the power bank market is propelled and attributed to the introduction of new power banks which are comparatively low-priced. Although few factors that are hindering the growth of the market includes adoption of wireless charging technology in smart devices, and power banks with inefficient battery quality. The impact of these factors will be minimal due to introduction of new techniques in power banks. How this 138 page report delivers: - Contains 138 tables, charts and graphs that add visual analysis in order to explain developing trends within the power bank market. - Visiongain provides forecasts for the period 2017-2027 for the leading power bank submarkets, a) by power rating (Below 3,500 mAh, 3,501 - 20,000 mAh, Above 20,000 mAh), b) by battery type (Lithium-Ion (Li-Ion), Lithium-Polymer (Li-Po)) c) by type (Portable, Battery Case, Solar(PV)), - Market forecasts and analysis for 4 regions and 11 leading national markets and the rest of the world markets. - A dedicated leading companies’ chapter covering 10 companies leading the field in power banks. For more information and orders please contact gabriel.diaz@vgtelecomreports.com How to purchase our reports Select the license from the list below and send your details Licensing options: Single User GBP 2499 Dept. (5 Users) GBP 2999 Site GBP 4999 Global GBP 6999 Table of Contents - Power Bank Market Report 2017-2027 1. Report Overview 2. Introduction to the Power Bank Market 2.1 Power Bank Market Structure 2.2 Power Bank Market Definition 2.3 Power Bank Submarkets 2.3.1 Power Bank, By Type 2.3.1.1 Portable Power Bank 2.3.1.2 Battery Case Power Bank 2.3.1.3 Solar Charger Power Bank 2.3.2 Power Bank, By Power Rating 2.3.2.1 Power Bank Below 3,500mAh Power Rating 2.3.2.2 Power Bank 3,500-20,000mAh Power Rating 2.3.2.3 Power Bank Above 20,000mAh Power Rating 2.3.3 Power Bank, By Battery Type 2.3.3.1 Power Bank Lithium-ion Battery Type 2.3.3.2 Power Bank Lithium-polymer Battery Type 2.4 Power Bank Market Drivers 2.4.1 Increased Growth in Demand For Smart Devices 2.4.2 Introduction of New Power Banks Which Are Comparatively Low-Priced 2.4.3 Increasing Digitization and Penetration of Wireless Services 2.5 Power Bank Market Restraints 2.5.1 Introduction of Advanced Devices Reduces The Need For Power Banks 2.5.2 Wireless Charging Capability In Smart Devices 2.5.3 Power Banks With Inefficient Battery Quality 2.6 Power Bank Market Opportunities 2.6.1 Innovative Ideas And Techniques in Power Banks 2.6.2 Growth Through E-Commerce 3. Porters Five Forces Analysis of Global Power Bank Market 3.1.1 More Concentrated Suppliers And Price-Oriented Buyers Have Led To Moderate Bargaining Power Among Suppliers 3.1.2 Easy Access To Distribution Channel And Well-Known Brand Names Have Led To Moderate Threat Of New Entrants In The Market 3.1.3 Superior Substitute Product Quality And More Expensive Substitute Product Have Led To Moderate Threat Of Substitutes In The Market 3.1.4 Numerous Competitors And Insignificant Brand Loyalty Have Led To High Rivalry In The Market 3.1.5 Price-Sensitive And Less Educated Buyers Have Led To Moderate Bargaining Power Among Buyers 4. Global Power Bank Type Market Forecast 2017-2027 4.1 Portable Power Bank Market 2017-2027 4.1.1 Portable Power Bank Key Drivers & Opportunities 4.1.2 Portable Power Bank Market Size & Forecast 2017-2027 4.2 Battery Case Power Bank Market 2017-2027 4.2.1 Battery Case Power Bank Key Drivers & Opportunities 4.2.2 Battery Case Power Bank Market Size & Forecast 2017-2027 4.3 Solar Power Bank Market 2017-2027 4.3.1 Solar Power Bank Key Drivers & Opportunities 4.3.2 Solar Power Bank Market Size & Forecast 2017-2027 5. Global Power Bank Battery Type Market Forecast 2017-2027 5.1 Lithium-Ion Power Bank Market 2017-2027 5.1.1 Lithium-Ion Power Bank Key Drivers & Opportunities 5.1.2 Lithium-Ion Power Bank Market Size & Forecast 2017-2027 5.2 Lithium-Polymer Power Bank Market 2017-2027 5.2.1 Lithium-Polymer Power Bank Key Drivers & Opportunities 5.2.2 Lithium-Polymer Power Bank Market Size & Forecast 2017-2027 6. Global Power Bank Power Rating Market 2017-2027 6.1 Below 3,500mAh Power Bank Market 2017-2027 6.1.1 Below 3,500mAh Power Bank Key Drivers & Opportunities 6.1.2 Below 3,500mAh Power Bank Market Size & Forecast 2017-2027 6.2 3,501-20,000mAh Power Bank Market 2017-2027 6.2.1 3,501-20,000mAh Power Bank Key Drivers & Opportunities 6.2.2 3,501-20,000mAh Power Bank Market Size & Forecast 2017-2027 6.3 3,501-20,000mAh Power Bank Market 2017-2027 6.3.1 Above 20,000mAh Power Bank Key Drivers & Opportunities 6.3.2 Above 20,000mAh Power Bank Market Size & Forecast 2017-2027 7. Regional Power Bank Market Forecasts 2017-2027 7.1 North America Power Bank Market 2017-2027 7.1.1 U.S. Power Bank Market 2017-2027 7.1.2 Canada Power Bank Market 2017-2027 7.1.3 Mexico Power Bank Market 2017-2027 7.2 Europe Power Bank Market 2017-2027 7.2.1 United Kingdom Power Bank Market 2017-2027 7.2.2 Germany Power Bank Market 2017-2027 7.2.3 France Power Bank Market 2017-2027 7.2.4 Russia Power Bank Market 2017-2027 7.2.5 Rest of Europe Power Bank Market 2017-2027 7.3 Asia-Pacific Power Bank Market 2017-2027 7.3.1 China Power Bank Market 2017-2027 7.3.2 Japan Power Bank Market 2017-2027 7.3.3 India Power Bank Market 2017-2027 7.3.4 Australia Power Bank Market 2017-2027 7.3.5 Rest of Asia-Pacific Power Bank Market 2017-2027 7.4 Latin America, Middle East & Africa (LAMEA) Power Bank Market 2017-2027 7.4.1 Latin America Power Bank Market 2017-2027 7.4.2 Middle East Power Bank Market 2017-2027 7.4.3 Africa Power Bank Market 2017-2027 8. Leading 10 Power Bank Companies 8.1 Panasonic Corporation 8.1.1 Panasonic Corporation Company Overview 8.1.2 Panasonic Corporation Business Performance 8.1.3 Panasonic Corporation Key Developments 8.1.4 Panasonic Corporation Products / Services 8.2 Samsung Electronics Co. Ltd. 8.2.1 Samsung Electronics Co. Ltd. Company Overview 8.2.2 Samsung Electronics Co. Ltd. Business Performance 8.2.3 Samsung Electronics Co. Ltd. Key Developments 8.2.4 Samsung Electronics Co. Ltd. Products / Services 8.3. Microsoft Corporation 8.3.1 Microsoft Corporation Company Overview 8.3.2 Microsoft Corporation Business Performance 8.3.3 Microsoft Corporation Key Developments 8.3.4 Microsoft Corporation Products / Services 8.4 Apacer Technology Inc. 8.4.1 Apacer Technology Inc. Company Overview 8.4.2 Apacer Technology Inc. Business Performance 8.4.3 Apacer Technology Inc. Key Developments 8.4.4 Apacer Technology Inc. Products / Services 8.5 Xiaomi Inc. 8.5.1 Xiaomi Inc. Company Overview 8.5.2 Xiaomi Inc. Business Performance 8.5.3 Xiaomi Inc. Key Developments 8.5.4 Xiaomi Inc. Products / Services 8.6 Sony Corporation 8.6.1 Sony Corporation Company Overview 8.6.2 Sony Corporation Business Performance 8.6.3 Sony Corporation Key Developments 8.6.4 Sony Corporation Products / Services 8.7 GP Batteries International Ltd 8.7.1 GP Batteries International Ltd. Company Overview 8.7.2 GP Batteries International Ltd. Business Performance 8.7.3 GP Batteries International Ltd. Key Developments 8.7.4 GP Batteries International Ltd. Products / Services 8.8 Anker Technology Co. Limited 8.8.1 Anker Technology Co. Limited Company Overview 8.8.2 Anker Technology Co. Limited Business Performance 8.8.3 Anker Technology Co. Limited Key Developments 8.8.4 Anker Technology Co. Limited Products / Services 8.9 OnePlus 8.9.1 OnePlus Company Overview 8.9.2 OnePlus. Business Performance 8.9.3 OnePlus. Key Developments 8.9.4 OnePlus. Products / Services 8.10 Hitachi Maxwell Ltd. 8.10.1 Hitachi Maxwell Ltd. Company Overview 8.10.2 Hitachi Maxwell Ltd. Business Performance 8.10.3 Hitachi Maxwell Ltd. Key Developments 8.10.4 Hitachi Maxwell Ltd. Products / Services 8.11 Other Power Bank Companies 9. Conclusions & Recommendations 10. Glossary List of Tables Table 1. Global Power Bank Market by Regional Market Forecast 2017-2027 (US$m, YOY %, Cumulative) Table 2 Global Power Bank Type Submarket Forecast 2017-2027 (US$m, AGR%, CAGR%) Table 3 Global Power Bank Type Submarket by Regional Market Forecast 2016-2026 (US$m, AGR%, CAGR%) Table 4 Global Power Bank Battery Type Submarket Forecast 2017-2027 (US$m, AGR%, CAGR%) Table 5 Global Power Bank Battery Type Submarket by Regional Market Forecast 2017-2027 (US$m, AGR%, CAGR%) Table 6 Global Power Bank Power Rating Submarket Forecast 2017-2027 (US$m, AGR%, CAGR%) Table 7 Global Power Bank Power Rating Submarket by Regional Market Forecast 2016-2026 (US$m, AGR%, CAGR%) Table 8 North American Power Bank Market Forecast, By Type 2017-2027 (US$m, CAGR%) Table 9 North American Power Bank Market Forecast, By Battery Type 2017-2027 (US$m, CAGR%) Table 10 North American Power Bank Market Forecast, By Power Rating 2017-2027 (US$m, CAGR%) Table 11 North American Power Bank Market Forecast, By Country 2017-2027 (US$m, AGR %, CAGR%) Table 12 Europe Power Bank Market Forecast, By Type 2017-2027 (US$m, CAGR%) Table 13 Europe Power Bank Market Forecast, By Battery Type 2017-2027 (US$m, CAGR%) Table 14 Europe Power Bank Market Forecast, By Power Rating 2017-2027 (US$m, CAGR%) Table 15 European Power Bank Market Forecast, By Country 2017-2027 (US$m, AGR%, CAGR%) Table 16 Asia-Pacific Power Bank Market Forecast, By Type 2017-2027 (US$m, CAGR%) Table 17 Asia-Pacific Power Bank Market Forecast, By Battery Type 2017-2027 (US$m, CAGR%) Table 18 Asia-Pacific Power Bank Market Forecast, By Power Rating 2017-2027 (US$m, CAGR%) Table 19 Asia-Pacific Power Bank Market Forecast, By Country 2017-2027 (US$m, AGR%, CAGR%) Table 20 LAMEA Power Bank Market Forecast, By Type 2017-2027 (US$m, CAGR%) Table 21 LAMEA Power Bank Market Forecast, By Battery Type 2017-2027 (US$m, CAGR%) Table 22 LAMEA Power Bank Market Forecast, By Power Rating 2017-2027 (US$m, CAGR%) Table 23 LAMEA Power Bank Market Forecast, By Country 2017-2027 (US$m, AGR%, CAGR %) Table 24 Panasonic Corporation Company Profile 2015 (CEO, Total Company Sales US$m Net Income US$m, Strongest Business Region, Business Segment in the Market, Submarket Involvement, HQ, Founded, No. of Employees, IR Contact, Ticker, Website) Table 25 Panasonic Corporation Products / Services Table 26 Samsung Electronics Co. Ltd. Company Profile 2014 (CEO, Total Company Sales US$m, Net Income US$m, Strongest Business Region, Business Segment in the Market, Submarket Involvement, HQ, Founded, No. of Employees, Ticker, Website) Table 27 Samsung Electronics Co., Ltd., Products / Services Table 28 Microsoft Corporation Company Profile 2015 (CEO, Total Company Sales US$m, Net Income US$m, Strongest Business Region, Business Segment in the Market, Submarket Involvement, HQ, Founded, No. of Employees, IR Contact, Ticker, Website) Table 29 Microsoft Corporation, Products / Services Table 30 Apacer Technology Inc. Company Profile Table 31 Microsoft Corporation, Products / Services Table 32 Xiaomi Inc. Company Profile 2015 Table 33 Microsoft Corporation, Products / Services Table 34 Sony Corporation Company Profile 2015 (CEO, Total Company Sales US$m, Net Income US$m, Strongest Business Region, Business Segment in the Market, HQ, Founded, No. of Employees, IR Contact, Ticker, Website) Table 35 Microsoft Corporation Products / Services Table 36 GP Batteries International Ltd. Company Profile 2015 (CEO, Total Company Sales US$m, Strongest Business Region, Business Segment in the Market, Submarket Involvement, HQ, Founded, No. of Employees, IR Contact, Ticker, Website) Table 37 GP Batteries International Ltd., Products / Services Table 38 Anker Technology Co. Ltd. Company Profile Table 39 Anker Technology Co. Limited., Products /Services Table 40 OnePlus Company Profile Table 41 OnePlus, Products / Services Table 42 Hitachi Maxwell Ltd. Company Profile 2015 (CEO, Total Company Sales US$m, Net Income US$m, Strongest Business Region, HQ, Founded, No. of Employees, Ticker, Website) Table 43 Hitachi Maxwell Ltd., Products / Services List of Figures Figure 1. Power Bank Market by Regional Market Share Forecast 2017, 2022, 2027 (% Share) Figure 2. Global Power Bank Market Segmentation Overview Figure 3. Global Power Bank Market, By Type Figure 4. Global Power Bank Market, By Power Rating Figure 5. Global Power Bank Market, By Battery Type Figure 6. Power Bank Market Drivers Figure 7. Power Bank Market Restraints Figure 8. Power Bank Market Opportunities Figure 9. Porter’s Five Forces Analysis Figure 10 Global Power Bank Portable Type Submarket Forecast 2017-2027 (US$m) Figure 11 Global Power Bank Battery Case Type Submarket Forecast 2017-2027 (US$m) Figure 12 Global Power Bank Solar Type Submarket Forecast 2017-2027(US$m) Figure 13 North America Power Bank Portable Type Submarket Forecast 2017-2027(US$m) Figure 14 Europe Power Bank Portable Type Submarket Forecast 2017-2027(US$m) Figure 15 Asia-Pacific Power Bank Portable Type Submarket Forecast 2017-2027(US$m) Figure 16 LAMEA Power Bank Portable Type Submarket Forecast 2017-2027(US$m) Figure 17 North America Power Bank Battery Case Type Submarket Forecast 2017-2027(US$m) Figure 18 Europe Power Bank Battery Case Type Submarket Forecast 2017-2027(US$m) Figure 19 Asia-Pacific Power Bank Battery Case Type Submarket Forecast 2017-2027(US$m) Figure 20 LAMEA Power Bank Battery Case Type Submarket Forecast 2017-2027(US$m) Figure 21 North America Power Bank Solar Type Submarket Forecast 2017-2027(US$m) Figure 22 Europe Power Bank Solar Type Submarket Forecast 2017-2027(US$m) Figure 23 Asia-Pacific Power Bank Solar Type Submarket Forecast 2017-2027(US$m) Figure 24 LAMEA Power Bank Solar Type Submarket Forecast 2017-2027(US$m) Figure 25 Global Power Bank Type Submarket Share Forecast 2017 (% Share) Figure 26 Global Power Bank Type Submarket Share Forecast 2022 (% Share) Figure 27 Global Power Bank Type Submarket Share Forecast 2027 (% Share) Figure 28 Global Power Bank Lithium-Ion Battery Type Submarket Forecast 2017-2027 (US$m) Figure 29 Global Power Bank Lithium-Polymer Submarket Forecast 2017-2027 (US$m) Figure 30 North America Power Bank Lithium-Ion Battery Type Submarket Forecast 2017-2027(US$m) Figure 31 Europe Power Bank Lithium-Ion Battery Type Submarket Forecast 2017-2027(US$m) Figure 32 Asia-Pacific Power Bank Lithium-Ion Battery Type Submarket Forecast 2017-2027(US$m) Figure 33 LAMEA Power Bank Lithium-Ion Battery Type Submarket Forecast 2017-2027(US$m) Figure 34 North America Power Bank Lithium-Polymer Battery Type Submarket Forecast 2017-2027(US$m) Figure 35 Europe Power Bank Lithium-Polymer Battery Type Submarket Forecast 2017-2027(US$m) Figure 36 Asia-Pacific Power Bank Lithium-Polymer Battery Type Submarket Forecast 2017-2027(US$m) Figure 37 LAMEA Power Bank Lithium-Polymer Battery Type Submarket Forecast 2017-2027(US$m) Figure 38 Global Power Bank Battery Type Submarket Share Forecast 2017 (% Share) Figure 39 Global Power Bank Battery Type Submarket Share Forecast 2022 (% Share) Figure 40 Global Power Bank Battery Type Submarket Share Forecast 2027 (% Share) Figure 41 Global Power Bank Below 3,500mAh Power Rating Submarket Forecast 2017-2027 (US$m) Figure 42 Global Power Bank 3,501-20,000mAh Power Rating Submarket Forecast 2017-2027 (US$m) Figure 43 Global Power Bank Above 20,000mAh Power Rating Submarket Forecast 2017-2027 (US$m) Figure 44 North America Power Bank Below 3,500mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 45 Europe Power Bank Below 3,500mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 46 Asia-Pacific Power Bank Below 3,500mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 47 LAMEA Power Bank Below 3,500mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 48 North America Power Bank 3,500-20,000mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 49 Europe Power Bank 3,500-20,000mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 50 Asia-Pacific Power Bank 3,500-20,000mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 51 LAMEA Power Bank 3,500-20,000mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 52 North America Power Bank Above 20,000mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 53 Europe Power Bank Above 20,000mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 54 Asia-Pacific Power Bank Above 20,000mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 55 LAMEA Power Bank Above 20,000mAh Power Rating Submarket Forecast 2017-2027(US$m) Figure 56 Global Power Bank Power Rating Submarket Share Forecast 2017 (% Share) Figure 57 Global Power Bank Power Rating Submarket Share Forecast 2022 (% Share) Figure 58 Global Power Bank Power Rating Submarket Share Forecast 2027 (% Share) Figure 59 North American Power Bank Market Revenue, 2017-2027(US$m) Figure 60 North American Power Bank Market Revenue, By Country, 2017-2027(US$m) Figure 61 U.S. Power Bank Market Revenue, 2017-2027(US$m) Figure 62 Canada Power Bank Market Revenue, 2017-2027(US$m) Figure 63 Mexico Power Bank Market Revenue, 2017-2027(US$m) Figure 64 European Power Bank Market Revenue, 2017-2027(US$m) Figure 65 U.K. Power Bank Market Revenue, 2017-2027(US$m) Figure 66 Germany Power Bank Market Revenue, 2017-2027(US$m) Figure 67 France Power Bank Market Revenue, 2017-2027(US$m) Figure 68 Russia Power Bank Market Revenue, 2017-2027(US$m) Figure 69 Rest of Europe Power Bank Market Revenue, 2017-2027(US$m) Figure 70 Asia-Pacific Power Bank Market Revenue, 2017-2027(US$m) Figure 71 China Power Bank Market Revenue, 2017-2027(US$m) Figure 72 India Power Bank Market Revenue, 2017-2027(US$m) Figure 73 Japan Power Bank Market Revenue, 2017-2027(US$m) Figure 74 Australia Power Bank Market Revenue, 2017-2027(US$m) Figure 75 Rest of Asia-Pacific Power Bank Market Revenue, 2017-2027(US$m) Figure 76 LAMEA Power Bank Market Revenue, 2017-2027(US$m) Figure 77 Latin America Power Bank Market Revenue, 2017-2027(US$m) Figure 78 Middle East Power Bank Market Revenue, 2017-2027(US$m) Figure 79 Africa Power Bank Market Revenue, 2017-2027(US$m) Figure 80 Panasonic Corporation, Net Sales, 2013-2015 Figure 81 Panasonic Corporation, Business Segment, 2015(%) Figure 82 Samsung Electronics Co., Ltd., Net Sales, 2012-2014 Figure 83 Samsung Electronics Co., Ltd., Business Segment, 2014(%) Figure 84 Samsung Electronics Co., Ltd., Geography, 2014(%) Figure 85 Microsoft Corporation, Net Sales, 2012-2015 Figure 86 Microsoft Corporation, Business Segment, 2015(%) Figure 87 Microsoft Corporation, Geography, 2015(%) Figure 88 Sony Corporation, Net Sales, 2013-2015 Figure 89 Sony Corporation, Business Segment, 2015(%) Figure 90 Sony Corporation, Geography, 2015(%) Figure 91 GP Batteries International Ltd., Net Sales, 2012-2015 Figure 92 GP Batteries International Ltd., Business Segment, 2015(%) Figure 93 GP Batteries International Ltd., Geography, 2015(%) Figure 94 Hitachi Maxwell Ltd., Net Sales, 2012-2015 Figure 95 Hitachi Maxwell Ltd, Geography, 2015(%) Companies Mentioned in this Report Adcom HiTech Amazon Anker Technology Co. Limited Apacer Technology Inc. Ascent Solar Technologies, Inc. Asus Aukey Bangladesh Computer Society (BCS) Better Energy Systems (BES) Bluetimes Technology Co., Ltd. Bracketron BuffaloGrid, Cheero China Bank market Coolreall Dongguan Haolisheng Precision Mould Factory EasyAcc EC Technology Elecomm Electronics Group Co. Ltd Elefull Emtec Ericsson eZelleron, Fenix International Flipkart Goldleaf Technology Co., Ltd GP Batteries International Ltd Guangzhou Longdu Electronics Co. Ltd Hello Tech Hitachi Maxwell Ltd Holison Industrial Co., Ltd Huntkey Enterprise Group Hyper Power Holdings Ltd Imuto Intocircuit King Power Technology Co. Ltd Kinps Landi Electronic Technology Co., Ltd. Lepow Pie Levin LG Lonchi Technology Trade Co. Ltd. Make4u Co., Ltd. Maplin Electronics Marinsa Corporation Micro Power Bank (HK) Limited Microsoft MyFC Ningbo Dongying Industrial & Trading Co. Ltd OnePlus Panasonic Corporation Pandas Tehnology Technology Co. Ltd P-Mega P-Mega PNY Portable Charger Portronics powerAdd RAVPower ROMOSS Technology Co. Ltd. Samsung Electronics Co. Ltd. Shenzhen Qianhai Cooostar Technology Co. Ltd Shenzhen Runwell Technology Co., Ltd. Shenzhen Sipode Film Engineering Co., Ltd. Skiva Skyel Technology Co., Ltd Skygen Co., Limited Snapdeal Sony Corporation Sunrine Technology Co, Ltd TeckNet THZY TP-Link Canada Inc. Trusda UIMI Tech Ultrics Underwriters Laboratories Inc.(UL) USBGift Verizon Vessel Company Vinsic VIVAN ViViPowerbank Vodacom Xiaomi Inc. Xingtaida Electronic Technology Co. Ltd. Xtorm Zhanlite Electronic Technology Co. Ltd. Zhuotop Zilus For more information and orders please contact gabriel.diaz@vgtelecomreports.com Terms and Conditions By replying to this e-mail submitting your order for this product you have agreed without limitation or qualification to be bound by and to comply with these Terms and Conditions. You agree that you will not fail to complete any transaction after submitting an order to purchase a product or submit any order to purchase a product where you do not intend to complete the transaction. Management Reports will only be sent on receipt of payment. Our mailing address is: 230 City Road. EC1V 2QY, London, UK. As a valued contact or customer, you are receiving this email with information that we believe will be relevant to you. If however, you wish to stop future messages you can unsubscribe from this list From owner-freebsd-ppc@freebsd.org Thu Feb 16 16:28:43 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 6A9F4CDC156 for ; Thu, 16 Feb 2017 16:28:43 +0000 (UTC) (envelope-from digit9@digit9.co.in) Received: from digit9.co.in (unknown [IPv6:2a01:4f8:201:82ac::2]) (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 3A05D1697 for ; Thu, 16 Feb 2017 16:28:43 +0000 (UTC) (envelope-from digit9@digit9.co.in) Received: by digit9.co.in (Postfix, from userid 10000) id 2B68B118B4BB; Thu, 16 Feb 2017 21:58:27 +0530 (IST) To: freebsd-ppc@freebsd.org Subject: [iTunes-Connect]=?UTF-8?Q?=E2=9C=89_?=Someone has been logged into your account from another country X-PHP-Originating-Script: 10000:12.php From: AppleID Message-Id: <20170216162828.2B68B118B4BB@digit9.co.in> Date: Thu, 16 Feb 2017 21:58:27 +0530 (IST) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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, 16 Feb 2017 16:28:43 -0000 From owner-freebsd-ppc@freebsd.org Sat Feb 18 12:18:15 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 07411CE4DC0 for ; Sat, 18 Feb 2017 12:18:15 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-76.reflexion.net [208.70.210.76]) (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 AA97217CF for ; Sat, 18 Feb 2017 12:18:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19932 invoked from network); 18 Feb 2017 12:18:06 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 18 Feb 2017 12:18:06 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Sat, 18 Feb 2017 07:18:06 -0500 (EST) Received: (qmail 24895 invoked from network); 18 Feb 2017 12:18:06 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 18 Feb 2017 12:18:06 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id E5578EC7EC3; Sat, 18 Feb 2017 04:18:05 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-Id: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> Date: Sat, 18 Feb 2017 04:18:05 -0800 To: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current X-Mailer: Apple Mail (2.3259) 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, 18 Feb 2017 12:18:15 -0000 [Note: I experiment with clang based powerpc64 builds, reporting problems that I find. Justin is familiar with this, as is Nathan.] I tried to update the PowerMac G5 (a so-called "Quad Core") that I have access to from head -r312761 to -r313864 and ended up with random panics and hang ups in fairly short order after booting. Some approximate bisecting for the kernel lead to: (sometimes getting part way into a buildkernel attempt for a different version before a failure happens) -r313266: works (just before use of atomic_fcmpset) vs. -r313271: fails (last of the "use atomic_fcmpset" check-ins) (I did not try -r313268 through -r313270 as the use was gradually added.) So I'm currently running a -r313864 world with a -r313266 kernel. No kernel that I tried that was from before -r313266 had the problems. Any kernel that I tried that was from after -r313271 had the problems. Of course I did not try them all in other direction. :) === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Feb 18 20:49:33 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 E63D0CE31C4 for ; Sat, 18 Feb 2017 20:49:33 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-76.reflexion.net [208.70.210.76]) (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 91C0CC94 for ; Sat, 18 Feb 2017 20:49:32 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 17464 invoked from network); 18 Feb 2017 20:51:35 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 18 Feb 2017 20:51:35 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Sat, 18 Feb 2017 15:49:31 -0500 (EST) Received: (qmail 11745 invoked from network); 18 Feb 2017 20:49:31 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 18 Feb 2017 20:49:31 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 59599EC807D; Sat, 18 Feb 2017 12:49:30 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> Date: Sat, 18 Feb 2017 12:49:29 -0800 Cc: svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current Content-Transfer-Encoding: 7bit Message-Id: References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> To: mjg@freebsd.org, Justin Hibbits X-Mailer: Apple Mail (2.3259) 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, 18 Feb 2017 20:49:34 -0000 On 2017-Feb-18, at 4:18 AM, Mark Millard wrote: > [Note: I experiment with clang based powerpc64 builds, > reporting problems that I find. Justin is familiar > with this, as is Nathan.] > > I tried to update the PowerMac G5 (a so-called "Quad Core") > that I have access to from head -r312761 to -r313864 and > ended up with random panics and hang ups in fairly short > order after booting. > > Some approximate bisecting for the kernel lead to: > (sometimes getting part way into a buildkernel attempt > for a different version before a failure happens) > > -r313266: works (just before use of atomic_fcmpset) > vs. > -r313271: fails (last of the "use atomic_fcmpset" check-ins) > > (I did not try -r313268 through -r313270 as the use was > gradually added.) > > So I'm currently running a -r313864 world with a -r313266 > kernel. > > No kernel that I tried that was from before -r313266 had the > problems. > > Any kernel that I tried that was from after -r313271 had the > problems. > > Of course I did not try them all in other direction. :) [Of course: "either direction".] I'll note that the -r313864 buildworld was without MALLOC_PRODUCTION being defined. (Unusual for me but I'm testing if a jemalloc assert problem on arm64 also happens on powerpc64.) By contrast the buildkernels were production style (as is normal for me unless I'm trying to track something down that I think might be exposed by the extra checks). === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Feb 18 20:58:32 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 95D28CE35D2; Sat, 18 Feb 2017 20:58:32 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-lf0-x241.google.com (mail-lf0-x241.google.com [IPv6:2a00:1450:4010:c07::241]) (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 16A56119D; Sat, 18 Feb 2017 20:58:32 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-lf0-x241.google.com with SMTP id z134so42630lff.3; Sat, 18 Feb 2017 12:58:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=rt53Xsm9IestMXEo0DfjcrGdtqEWo922J6ohJKIDsgc=; b=sm7ajQQRNNj+ZgR+fPvubXlunyxKdqMPmjTdVGCuk/J/bibQbkLUZmo2qkh174+f/V wDILeiTQ0w/urSGz2b2/GRL+waooWk3trHQKBwegD+daupxhpAewTajfG08umMagrKNM G07AKM4bhqlpdQeYC1d/kg1F4EHGZfmJZDovlZIsOUOMHX4P5aKiLn2Err73Y8yf50YG vFL+lm/YFYCmqAA8wV+P41X2E20k3v9if6vPvugQoQmveNeTUXrFHrCbPICJ5N+Lmnum 9cvj+Klpmcc8F9aWcwYk004ORN4V6Q476WsFvSy/V6CbbErttmKGYjYjXTJXyhCnORHy MLYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=rt53Xsm9IestMXEo0DfjcrGdtqEWo922J6ohJKIDsgc=; b=ApAzPdsUHnl3CUtVzeo37+MUdcof8SkH/+15WDfRQEtJzJKD2+2wlwpEyWmdLheVve 1oy0P0puuBmQPxWV2IT5x4JaqMwvwIpvbHpFWkati9/nAlSmFo1SnW0zjuxx2NO0LXJ6 sK0hifC54wcT39dyhamAdh2ViG90j6penp4YhURAPqMde//XhPOgHcvPN2ys6TfsZWWm o97b6g0XyW7qB6EcDve+EOzp5M3XqCQdPO8Jurx4UQbEFd09R3C4nqNsOA21J8mAflDx 4pGy9YrMRmV4OsAky5mo2tBEjKT8HB8Tqi2jBmOl1kJ/RpSldHl39U91d1hIE0E+oaC5 2QtQ== X-Gm-Message-State: AMke39kEFb/GoCSJkNPJcTS2XaT6t10c1ZAjdPaIz/FvKskp+LpfyfTkIMQ6f0Hi1VLkEA== X-Received: by 10.25.153.69 with SMTP id b66mr2789241lfe.85.1487451509645; Sat, 18 Feb 2017 12:58:29 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id a71sm3776775lfe.36.2017.02.18.12.58.28 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Sat, 18 Feb 2017 12:58:29 -0800 (PST) Date: Sat, 18 Feb 2017 21:58:25 +0100 From: Mateusz Guzik To: Mark Millard Cc: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170218205825.GA24384@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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, 18 Feb 2017 20:58:32 -0000 On Sat, Feb 18, 2017 at 12:49:29PM -0800, Mark Millard wrote: > On 2017-Feb-18, at 4:18 AM, Mark Millard wrote: > > > [Note: I experiment with clang based powerpc64 builds, > > reporting problems that I find. Justin is familiar > > with this, as is Nathan.] > > > > I tried to update the PowerMac G5 (a so-called "Quad Core") > > that I have access to from head -r312761 to -r313864 and > > ended up with random panics and hang ups in fairly short > > order after booting. > > > > Some approximate bisecting for the kernel lead to: > > (sometimes getting part way into a buildkernel attempt > > for a different version before a failure happens) > > > > -r313266: works (just before use of atomic_fcmpset) > > vs. > > -r313271: fails (last of the "use atomic_fcmpset" check-ins) > > > > (I did not try -r313268 through -r313270 as the use was > > gradually added.) > > > > So I'm currently running a -r313864 world with a -r313266 > > kernel. > > > > No kernel that I tried that was from before -r313266 had the > > problems. > > > > Any kernel that I tried that was from after -r313271 had the > > problems. > > > > Of course I did not try them all in other direction. :) > > [Of course: "either direction".] > > I'll note that the -r313864 buildworld was without > MALLOC_PRODUCTION being defined. (Unusual for me but > I'm testing if a jemalloc assert problem on arm64 > also happens on powerpc64.) > > By contrast the buildkernels were production style > (as is normal for me unless I'm trying to track > something down that I think might be exposed by > the extra checks). > Well either the primitive itself is buggy or the somewhat (now) unusual condition of not providing the failed value (but possibly a stale one) is not handled correctly in locking code. That said, I would start with putting barriers "on both sides" of powerpc's fcmpset for debugging purposes and if the problem persists I can add some debugs to locking priitmives. -- Mateusz Guzik From owner-freebsd-ppc@freebsd.org Sat Feb 18 21:58:58 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 994E0CE4AE3 for ; Sat, 18 Feb 2017 21:58:58 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-71.reflexion.net [208.70.210.71]) (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 46F5C1A6D for ; Sat, 18 Feb 2017 21:58:57 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 20257 invoked from network); 18 Feb 2017 21:59:31 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 18 Feb 2017 21:59:31 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Sat, 18 Feb 2017 16:58:51 -0500 (EST) Received: (qmail 6976 invoked from network); 18 Feb 2017 21:58:51 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 18 Feb 2017 21:58:51 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 719EDEC8AB7; Sat, 18 Feb 2017 13:58:50 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <20170218205825.GA24384@dft-labs.eu> Date: Sat, 18 Feb 2017 13:58:49 -0800 Cc: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current Content-Transfer-Encoding: 7bit Message-Id: References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170218205825.GA24384@dft-labs.eu> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) 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, 18 Feb 2017 21:58:58 -0000 On 2017-Feb-18, at 12:58 PM, Mateusz Guzik wrote: > On Sat, Feb 18, 2017 at 12:49:29PM -0800, Mark Millard wrote: >> On 2017-Feb-18, at 4:18 AM, Mark Millard wrote: >> >>> [Note: I experiment with clang based powerpc64 builds, >>> reporting problems that I find. Justin is familiar >>> with this, as is Nathan.] >>> >>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>> that I have access to from head -r312761 to -r313864 and >>> ended up with random panics and hang ups in fairly short >>> order after booting. >>> >>> Some approximate bisecting for the kernel lead to: >>> (sometimes getting part way into a buildkernel attempt >>> for a different version before a failure happens) >>> >>> -r313266: works (just before use of atomic_fcmpset) >>> vs. >>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>> >>> (I did not try -r313268 through -r313270 as the use was >>> gradually added.) >>> >>> So I'm currently running a -r313864 world with a -r313266 >>> kernel. >>> >>> No kernel that I tried that was from before -r313266 had the >>> problems. >>> >>> Any kernel that I tried that was from after -r313271 had the >>> problems. >>> >>> Of course I did not try them all in other direction. :) >> >> [Of course: "either direction".] >> >> I'll note that the -r313864 buildworld was without >> MALLOC_PRODUCTION being defined. (Unusual for me but >> I'm testing if a jemalloc assert problem on arm64 >> also happens on powerpc64.) >> >> By contrast the buildkernels were production style >> (as is normal for me unless I'm trying to track >> something down that I think might be exposed by >> the extra checks). >> > > Well either the primitive itself is buggy or the somewhat (now) unusual > condition of not providing the failed value (but possibly a stale one) > is not handled correctly in locking code. > > That said, I would start with putting barriers "on both sides" of > powerpc's fcmpset for debugging purposes and if the problem persists I > can add some debugs to locking priitmives. > > -- > Mateusz Guzik I currently have the only powerpc64 that I have access to for now doing a test that will likely finish tonight sometime (if it has no problems). Also I'm not so familiar with powerpc64 details as to be able insert proper barriers and the like off the top of my head: It is more of a research subject for me. Side note: It looks like contexts like __rw_wlock_hard(c,v,tid,file,line) now needs the caller to do an equivalent of: __rw_wlock_hard(c,RW_READ_VALUE(rwlock2rw(c)),file,line) in order for the code behavior to match the old behavior that was based on the original local-v's initialization before v was used: rw = rwlock2rw(c); v = RW_READ_VALUE(rw); /* this line no longer exists */ This means that checking for equivalence is no longer local to the routine but involves checking all the usage of the routine. I've not done such so for all I know such usage is always in place: This is not a claim of a problem. The other routines in kern_rwlock.c still have local variables and the original initializations. I just thought that this was interesting. I've not looked at other files yet. === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Feb 18 22:36: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 88FFECE54C4 for ; Sat, 18 Feb 2017 22:36:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D147153B for ; Sat, 18 Feb 2017 22:36:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id A76F82F2C; Sat, 18 Feb 2017 22:36:06 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 9130A2F2B for ; Sat, 18 Feb 2017 22:36:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 AA9F91537 for ; Sat, 18 Feb 2017 22:36:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1IMa5Sn084030 for ; Sat, 18 Feb 2017 22:36:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-powerpc@FreeBSD.org Subject: [Bug 217215] graphics/argyllcms broken on powerpc64 Date: Sat, 18 Feb 2017 22:36:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hamiltcl@verizon.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: kwm@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 18 Feb 2017 22:36:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217215 Bug ID: 217215 Summary: graphics/argyllcms broken on powerpc64 Product: Ports & Packages Version: Latest Hardware: powerpc OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: kwm@FreeBSD.org Reporter: hamiltcl@verizon.net CC: freebsd-powerpc@FreeBSD.org Flags: maintainer-feedback?(kwm@FreeBSD.org) CC: freebsd-powerpc@FreeBSD.org Assignee: kwm@FreeBSD.org Created attachment 180129 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180129&action= =3Dedit Patch to fix build on powerpc64 graphics/argyllcms is marked as broken on powerpc64. The attached patch al= lows port to build on freebsd/powerpc64 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Feb 18 22:59:46 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 B81E3CE5A0B; Sat, 18 Feb 2017 22:59:46 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (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 4E12E1D87; Sat, 18 Feb 2017 22:59:46 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-wr0-x243.google.com with SMTP id q39so8557367wrb.2; Sat, 18 Feb 2017 14:59:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Xws76ODFOvxKhlWJVz2K0OnEKHYLRgsxuNXguUb3WaU=; b=riyFnzfzL2hULu2rgp9kiOP8/ODJC0CscYOz6boRBhc7YTiCzbfT/gYWSXdJnwNTpa A0oGw2dDiAggdJY+4oHzTG94g7io78mUzECG/UJ1ZL6F2qfg2uDynQaEneddT2e1VHBm 68dVhn4GfALV1LNtmTUAlSvdXkTgdF/HuvXN5VWioxIiRznwjq2WTJ0ZbNwXAZuj43R4 FpeXxlPI0/6jLg4Zn5eJRSFkpW2h8OaAJ0wpOkGfaSqQ55lZsLAWdX5VVk8uY4epDzf7 P0ZZhCXCbqLdmXsdDTGeMFJtwrv0mnRMic1fud9aLniSGSx7abcT63/X6e/vsrg0KNmE N4+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=Xws76ODFOvxKhlWJVz2K0OnEKHYLRgsxuNXguUb3WaU=; b=ZYZkV5dvokkN8SagGQefpl88qDgkoKDxFjIGbuephdjzSFfbBb0znS7zM0yl7H6clQ vuad3HCQ+KFp+0ftZ1LBtrSLq5CAZg7xBXihL6acX+JG1VMdb8gAJIjX2Te1JVXpNuhR 4vzaMgp6gVDnuZ20Ahv/LjKmSyLoyMIDvSrMUl7lQnd3o3JVV5u7G/ZYiwLzrl4litue 3sneRqBSgh6PKzqOKwGLZK00vRkDMKOdri9IiUAt6+oyX4yhilD+BsElSz0yJdMGThub M95arM8vknY8KHiJcHbf5HIcEClGMeIrHtex+QmET8k4R9E7MLzPgv3P2EKnxMzyV84n DLzg== X-Gm-Message-State: AMke39kfIPZ9h9w6lzdieIkiOt5xOUEYiDWc/Pn0qMGVwa+hbC/o5NfvWJdgvRcrRnNnBA== X-Received: by 10.223.150.110 with SMTP id c43mr4244778wra.5.1487458783727; Sat, 18 Feb 2017 14:59:43 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id 40sm18541534wry.22.2017.02.18.14.59.42 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Sat, 18 Feb 2017 14:59:42 -0800 (PST) Date: Sat, 18 Feb 2017 23:59:40 +0100 From: Mateusz Guzik To: Mark Millard Cc: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170218225940.GB24384@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170218205825.GA24384@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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, 18 Feb 2017 22:59:46 -0000 On Sat, Feb 18, 2017 at 01:58:49PM -0800, Mark Millard wrote: > On 2017-Feb-18, at 12:58 PM, Mateusz Guzik wrote: > > Well either the primitive itself is buggy or the somewhat (now) unusual > > condition of not providing the failed value (but possibly a stale one) > > is not handled correctly in locking code. > > > > That said, I would start with putting barriers "on both sides" of > > powerpc's fcmpset for debugging purposes and if the problem persists I > > can add some debugs to locking priitmives. > > > > I currently have the only powerpc64 that I have access > to for now doing a test that will likely finish tonight > sometime (if it has no problems). > > Also I'm not so familiar with powerpc64 details as to be > able insert proper barriers and the like off the top of > my head: It is more of a research subject for me. > This was a suggestion to jhibbits@. Looking at the code it is not hard to slap them in for testing purposes, or maybe there is an "obvious now that I look at it" braino in there, or maybe he has a better idea. Now that I wrote it I can get myself access to powerpc boxes. While I wont be able to run bsd on them, I can hack around in userapce and see. That's unless jhibbits@ steps in. I have no clue about ppc. > It looks like contexts like __rw_wlock_hard(c,v,tid,file,line) > now needs the caller to do an equivalent of: > > __rw_wlock_hard(c,RW_READ_VALUE(rwlock2rw(c)),file,line) > > in order for the code behavior to match the old behavior > that was based on the original local-v's initialization > before v was used: > > rw = rwlock2rw(c); > v = RW_READ_VALUE(rw); /* this line no longer exists */ > > This means that checking for equivalence is no longer > local to the routine but involves checking all the > usage of the routine. > Not reading the argument locally was the entire point of introducing fcmpset. Otherwise the 'v' argument would be a waste of time. Some primitives can attempt grabbing the lock and if they fail, we have the lock value to work with (e.g. check who owns the lock and see if they are running). In particular amd64 will give us the value it found. An explicit read requires whoever owns the cachelilne to lose the exclusive ownership and if the lock is contended (multiple cpus doing fcmpset), this makes the cachelilne ping-pong between cores. This destroys performance especially on systems with many cores and especially so with multiple numa nodes. Other primitives don't have inline variants. This concerns read-write locks which try to: retry: r = lock_value(lock); if (!locked(r)) { if (!cmpset(lock, r, r + ONE_READER)) goto retry; } That is, if multiple cpus try to get the lock for reading, one will fail and willl lbe forced to compute the new value to be set. The longer the time between attempts the more likely it is other core showed up trying to do the same thing with the same value, causing another failed attempt. So here there are no inlilnes so that the time is shorter and fcmpset alllows NOT reading the lock value explicitely - it was already provided by hardware. Note this is still significantly slower than it has to be in principle - the lock can 'blilndly increment by ONE_READER and see what happens', but that requires several changes and is a subject for another e-mail. I'm working on it though. -- Mateusz Guzik