From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 95EA3C4321D for ; Fri, 24 Aug 2018 05:44:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 23A1A2156E for ; Fri, 24 Aug 2018 05:44:47 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 23A1A2156E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727484AbeHXJRq convert rfc822-to-8bit (ORCPT ); Fri, 24 Aug 2018 05:17:46 -0400 Received: from ozlabs.org ([203.11.71.1]:42569 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726475AbeHXJRq (ORCPT ); Fri, 24 Aug 2018 05:17:46 -0400 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 41xVbZ4s3kz9rvt; Fri, 24 Aug 2018 15:44:42 +1000 (AEST) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au From: Michael Ellerman To: Segher Boessenkool , Andrew Donnellan Cc: Russell Currey , "Aneesh Kumar K.V" , Benjamin Herrenschmidt , Paul Mackerras , aneesh.kumar@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Christophe LEROY Subject: Re: [PATCH v2 3/4] powerpc/mm: fix a warning when a cache is common to PGD and hugepages In-Reply-To: <20180823144118.GU24439@gate.crashing.org> References: <2f96bf1a8df1091c642de099ed07c34b5ab9b90a.1534258290.git.christophe.leroy@c-s.fr> <4aaca2d27429e6bdadc340fd3b96e7c350c4b2f4.1534258290.git.christophe.leroy@c-s.fr> <6dea8d0c-c4ab-49aa-da26-a729c18fa818@linux.ibm.com> <006e5f33-b816-7508-faac-da26a860659c@c-s.fr> <3e6412ac-c645-908f-a3bb-c9a2a72f4b68@linux.ibm.com> <20180823103625.GR24439@gate.crashing.org> <8ada20e9-3bc1-fdaf-d78f-2f5a317e8216@c-s.fr> <87a7pdl2jy.fsf@concordia.ellerman.id.au> <20180823144118.GU24439@gate.crashing.org> Date: Fri, 24 Aug 2018 15:44:42 +1000 Message-ID: <87r2iojp2t.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Segher Boessenkool writes: > On Thu, Aug 23, 2018 at 11:32:16PM +1000, Andrew Donnellan wrote: >> On 23/08/18 21:56, Michael Ellerman wrote: >> >Christophe LEROY writes: >> > >> >>Le 23/08/2018 à 12:36, Segher Boessenkool a écrit : >> >>>On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christophe LEROY wrote: >> >>>>The only small problème I have is that some version of GCC seems to >> >>>>complain about big memset() (132k and 256k ones). Is there a way to tell >> >>>>GCC we really want to do it ? >> >>> >> >>>I'm not sure what you mean. Complain, is that a warning, is that an >> >>>error? >> >>>What does it say? Do you have some example code to reproduce it? Etc. >> >> >> >>I saw the warnings in the checks at >> >>https://patchwork.ozlabs.org/patch/957566/ >> >>Unfortunatly the link is now broken. >> > >> >ruscur/ajd any idea what happened to the snowpatch links here? >> >> I think they've disappeared because our log rotation is too fast - I've >> now upped it to 30 days. I guess over time we'll figure out what we need >> in this regard, ideally we'd keep logs indefinitely but they're several >> megs per build. >> >> I've kicked off another build for this series and the links in Patchwork >> should update to point to the new job when it's done (probably in the >> next couple of hours). > > It's back, thanks Andrew! > > The warnings are not from GCC at all: the warnings are from sparse. We really need to split them out so it's less confusing. cheers