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=-8.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 571A1C433E0 for ; Sun, 24 Jan 2021 02:11:20 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id B6966229F0 for ; Sun, 24 Jan 2021 02:11:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B6966229F0 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 4DNc1J1w06zDrNW for ; Sun, 24 Jan 2021 13:11:16 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=linux-foundation.org (client-ip=198.145.29.99; helo=mail.kernel.org; envelope-from=akpm@linux-foundation.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=linux-foundation.org header.i=@linux-foundation.org header.a=rsa-sha256 header.s=korg header.b=JupcgCB/; dkim-atps=neutral Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4DNbz3530YzDqkL for ; Sun, 24 Jan 2021 13:09:17 +1100 (AEDT) Received: by mail.kernel.org (Postfix) with ESMTPSA id 6FA3B229F0; Sun, 24 Jan 2021 02:09:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1611454154; bh=NoOjEaGp85QcxUqBSDOe0ipjgea3PrHuHrnXFNVCOGo=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=JupcgCB/e52p8vQoWbH826PMyiDiMnQ6vnNe1BbDf2dY+wnkR5tkKG2eCWovj16mg v9GqEW/1Lme9ZLgF+wRxV8qLFFFeMQyby0X3GdKKz03k2DKYNO7IKusRjn0EVhYInL RV/vFF0dvv2I1+m5dCnTh4jMCeap8kD7LytqMOAs= Date: Sat, 23 Jan 2021 18:09:11 -0800 From: Andrew Morton To: Thiago Jung Bauermann Subject: Re: [PATCH v2 2/2] memblock: do not start bottom-up allocations with kernel_end Message-Id: <20210123180911.aafa8404a3a7a30779713456@linux-foundation.org> In-Reply-To: <20210122043714.266075-1-bauerman@linux.ibm.com> References: <20201220064959.GB392325@kernel.org> <20210122043714.266075-1-bauerman@linux.ibm.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: riel@surriel.com, kernel-team@fb.com, Ram Pai , linux-kernel@vger.kernel.org, mhocko@kernel.org, linux-mm@kvack.org, Satheesh Rajendran , Konrad Rzeszutek Wilk , iamjoonsoo.kim@lge.com, linuxppc-dev@lists.ozlabs.org, guro@fb.com, rppt@kernel.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Fri, 22 Jan 2021 01:37:14 -0300 Thiago Jung Bauermann wrote: > Mike Rapoport writes: > > > > Signed-off-by: Roman Gushchin > > > > Reviewed-by: Mike Rapoport > > I've seen a couple of spurious triggers of the WARN_ONCE() removed by this > patch. This happens on some ppc64le bare metal (powernv) server machines with > CONFIG_SWIOTLB=y and crashkernel=4G, as described in a candidate patch I posted > to solve this issue in a different way: > > https://lore.kernel.org/linuxppc-dev/20201218062103.76102-1-bauerman@linux.ibm.com/ > > Since this patch solves that problem, is it possible to include it in the next > feasible v5.11-rcX, with the following tag? We could do this, if we're confident that this patch doesn't depend on [1/2] "mm: cma: allocate cma areas bottom-up"? I think it is... > Fixes: 8fabc623238e ("powerpc: Ensure that swiotlb buffer is allocated from low memory") I added that.