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=-2.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 138D1C3F2D7 for ; Wed, 4 Mar 2020 18:50:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D9C8620870 for ; Wed, 4 Mar 2020 18:50:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="K1STWgSZ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730146AbgCDSup (ORCPT ); Wed, 4 Mar 2020 13:50:45 -0500 Received: from mail-qv1-f68.google.com ([209.85.219.68]:34629 "EHLO mail-qv1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729600AbgCDSup (ORCPT ); Wed, 4 Mar 2020 13:50:45 -0500 Received: by mail-qv1-f68.google.com with SMTP id o18so1273697qvf.1; Wed, 04 Mar 2020 10:50:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=tuKeD8w66KIDzJ6/Silhroq3Yhej0TOjlxLZqNMh/QM=; b=K1STWgSZRij5Bsdjl9V2EgJs+J4iSVnfdNGfBDMF3VM4W1yBesmPlhQBeCIAEPoAIG UKdX5a5JpcF1I0AwopypkUDjo2YD1SdgU3aj+54kL1E0T0y+jwAf+RIprktg2kdRlYet +VZkbdPAHsJzlYHJ7dZX7TgJ+pJKfSgjH4ejwDfBOEHMQMK4PBSBDZBV2RqTwu+v5yRk l1QxwcdJAT2wGgHSsgzhrLrgA7K9vtpGGKe+oRm+smgX5PjaItVnANiJD/MAssgGZOen syKJx9ycWoI6Io4rfbz74u0LITlLoAVSNdtnP6c4Unxj5fWFH/Wn0fb0m2KCLlvR3Oj4 EErQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:date:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=tuKeD8w66KIDzJ6/Silhroq3Yhej0TOjlxLZqNMh/QM=; b=HCf0+ww7O8wtnA/6cLGQ0Kkko6SzIqsKD5sRUIU5AVgZgLssaUvPusi3C3LdSi/peg 6ydHbgkILldtcz3JtzU/F7agXPctBH2uJyGN4792YwgehXGJHoQsgMGNzFVqaxZ8LFim BiukQonzZ88z27w3hSQXFs4sA4qhNNpa36gJZB3FvuFyqtSEKqXBDcx6l7mF7ti6jgJ3 U8Ttd2OradKMVXL5GbLQtC3WXNrkNcpOnrj86JCF+k9dWYYuRf9U3Y9Sq2xFtPDMDD4m C3xb6V0ufMPkutyhZhy3yWvC4vofZMsvusZl7oVVaAuXeq3J6323RXm50/iZUOvVN276 U24A== X-Gm-Message-State: ANhLgQ1xbZ+q+wZTH+3DFemKylKihue/o36W/OrTsd6LGaAHi/Ame+Rq Q5m5mR3kvj4LEhjY9t6MFs8= X-Google-Smtp-Source: ADFU+vvcHTTpUmq/oVhZPERdJnhVc0CitiLhAmu8LJV5u9LJLmOoWzbIy7cua1LZX3gHfG90YayF/Q== X-Received: by 2002:a05:6214:1933:: with SMTP id es19mr3223597qvb.14.1583347844236; Wed, 04 Mar 2020 10:50:44 -0800 (PST) Received: from rani.riverdale.lan ([2001:470:1f07:5f3::b55f]) by smtp.gmail.com with ESMTPSA id 202sm14061573qkg.132.2020.03.04.10.50.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Mar 2020 10:50:44 -0800 (PST) From: Arvind Sankar X-Google-Original-From: Arvind Sankar Date: Wed, 4 Mar 2020 13:50:42 -0500 To: Ard Biesheuvel Cc: Arvind Sankar , Dave Hansen , Andy Lutomirski , Peter Zijlstra , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , the arch/x86 maintainers , linux-efi , Linux Kernel Mailing List Subject: Re: [PATCH 1/4] x86/mm/pat: Handle no-GBPAGES case correctly in populate_pud Message-ID: <20200304185042.GA281042@rani.riverdale.lan> References: <20200303205445.3965393-1-nivedita@alum.mit.edu> <20200303205445.3965393-2-nivedita@alum.mit.edu> <20200304154908.GB998825@rani.riverdale.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 04, 2020 at 07:44:50PM +0100, Ard Biesheuvel wrote: > > I've tried a couple of different ways, but I can't seem to get my > memory map organized in the way that will trigger the error. What does yours look like? efi_merge_regions doesn't merge everything that will eventually be mapped the same way, so if there are some non-conventional memory regions scattered over the address space, it might be breaking up the mappings to the point where this doesn't trigger.