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=MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 AAF9CC43331 for ; Wed, 25 Mar 2020 10:03:14 +0000 (UTC) Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (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 7FE852078D for ; Wed, 25 Mar 2020 10:03:14 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7FE852078D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvdimm-bounces@lists.01.org Received: from ml01.vlan13.01.org (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id 429B410FC36C4; Wed, 25 Mar 2020 03:04:04 -0700 (PDT) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.167.195; helo=mail-oi1-f195.google.com; envelope-from=rjwysocki@gmail.com; receiver= Received: from mail-oi1-f195.google.com (mail-oi1-f195.google.com [209.85.167.195]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id E010310FC3192 for ; Wed, 25 Mar 2020 03:04:01 -0700 (PDT) Received: by mail-oi1-f195.google.com with SMTP id w13so1556343oih.4 for ; Wed, 25 Mar 2020 03:03:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RbxsF3iTBYd8Alr5a+AtfnDNHQ5nhFVuguNGxWvurh0=; b=Dwp/3YmUYTaV77Oucd0mT1bzg82U1VI3d8dEeX366DHDPOEH/lOjx49w9vBDCFDNuP u0AyFUXZ2j5eDWnQIYaMwIDS0DnyIefSGw4ZQ2jf/oEXAGCU9TJepfM54NTOL77hZdf3 fl2aoEv/a3T5qliZ2BakkufcP7UzgdM0f9D08izWDCpFekUehAa0TUY0a3D5sTF1gMPh 0n90FmE8dZVdRYpr+MNrPTTjAaZTOLRf7aKjlEsgdp8hM6NX1YF1LEPfGgLTYzb41Lrf 83qcOVoUJ8A7khIS1zYKZwWf5Epg/8TQ5puTgj9acmo5lGFtn6JCHFGJvWOACacNyXFT nUDg== X-Gm-Message-State: ANhLgQ3uJrx+rSRxmuxa8MQ3R5l5kBS+zvdugsAcJiGM05K8Y3grYWOm uqU/15Xtov57jjYVRdGcuPu7hz9wWxF4b+6Bsho= X-Google-Smtp-Source: ADFU+vtK7XJIlmRTJBKFQ3UQeLQAPRvyeRH/mRzKTpmVW/rXoTpLQXCBWXpdUAN8zvQ1FBWw76QivKVZ5CBpzMoO6GI= X-Received: by 2002:aca:f07:: with SMTP id 7mr207477oip.68.1585130590326; Wed, 25 Mar 2020 03:03:10 -0700 (PDT) MIME-Version: 1.0 References: <158489354353.1457606.8327903161927980740.stgit@dwillia2-desk3.amr.corp.intel.com> In-Reply-To: <158489354353.1457606.8327903161927980740.stgit@dwillia2-desk3.amr.corp.intel.com> From: "Rafael J. Wysocki" Date: Wed, 25 Mar 2020 11:02:58 +0100 Message-ID: Subject: Re: [PATCH v2 0/6] Manual definition of Soft Reserved memory devices To: Dan Williams Message-ID-Hash: JX3QXWO42DIZZ3O74PP2OF5XVF5ODWQO X-Message-ID-Hash: JX3QXWO42DIZZ3O74PP2OF5XVF5ODWQO X-MailFrom: rjwysocki@gmail.com X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation CC: ACPI Devel Maling List , Jason Gunthorpe , "Rafael J. Wysocki" , Peter Zijlstra , Ard Biesheuvel , Jonathan Cameron , Borislav Petkov , the arch/x86 maintainers , "H. Peter Anvin" , Brice Goglin , Thomas Gleixner , Catalin Marinas , Ingo Molnar , Dave Hansen , Will Deacon , "Rafael J. Wysocki" , Ard Biesheuvel , Andy Lutomirski , Tom Lendacky , "linux-nvdimm@lists.01.org" , Linux Kernel Mailing List , Joao Martins X-Mailman-Version: 3.1.1 Precedence: list List-Id: "Linux-nvdimm developer list." Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Sun, Mar 22, 2020 at 5:28 PM Dan Williams wrote: > > Changes since v1 [1]: > - Kill the ifdef'ery in arch/x86/mm/numa.c (Rafael) > > - Add a dummy phys_to_target_node() for ARM64 (0day-robot) > > - Initialize ->child and ->sibling to NULL in the resource returned by > find_next_iomem_res() (Inspired by Tom's feedback even though it does > not set them like he suggested) > > - Collect Ard's Ack > > [1]: http://lore.kernel.org/r/158318759687.2216124.4684754859068906007.stgit@dwillia2-desk3.amr.corp.intel.com > > --- > > My primary motivation is making the dax_kmem facility useful to > shipping platforms that have performance differentiated memory, but > may not have EFI-defined soft-reservations / HMAT (or > non-EFI-ACPI-platform equivalent). I'm anticipating HMAT enabled > platforms where the platform firmware policy for what is > soft-reserved, or not, is not the policy the system owner would pick. > I'd also highlight Joao's work [2] (see the TODO section) as an > indication of the demand for custom carving memory resources and > applying the device-dax memory management interface. > > Given the current dearth of systems that supply an ACPI HMAT table, and > the utility of being able to manually define device-dax "hmem" instances > via the efi_fake_mem= option, relax the requirements for creating these > devices. Specifically, add an option (numa=nohmat) to optionally disable > consideration of the HMAT and update efi_fake_mem= to behave like > memmap=nn!ss in terms of delimiting device boundaries. > > [2]: https://lore.kernel.org/lkml/20200110190313.17144-1-joao.m.martins@oracle.com/ > > With Ard's and Rafael's ack I'd feel ok taking this through the nvdimm > tree, please holler if anything still needs some fixups. Acked-by: Rafael J. Wysocki for the whole series. Thanks! _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-leave@lists.01.org