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=-0.8 required=3.0 tests=BAYES_40,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,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 6F838C433E0 for ; Fri, 31 Jul 2020 15:29:15 +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 446C022B3F for ; Fri, 31 Jul 2020 15:29:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=intel-com.20150623.gappssmtp.com header.i=@intel-com.20150623.gappssmtp.com header.b="rU/7m59T" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 446C022B3F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com 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 11D3212905FC9; Fri, 31 Jul 2020 08:29:15 -0700 (PDT) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::541; helo=mail-ed1-x541.google.com; envelope-from=dan.j.williams@intel.com; receiver= Received: from mail-ed1-x541.google.com (mail-ed1-x541.google.com [IPv6:2a00:1450:4864:20::541]) (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 A71ED118D2A43 for ; Fri, 31 Jul 2020 08:29:11 -0700 (PDT) Received: by mail-ed1-x541.google.com with SMTP id v22so11849214edy.0 for ; Fri, 31 Jul 2020 08:29:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3k2Qozw9K7T3ULHctZF2uRyGbKqkev5Yvd3i8BwLL6Q=; b=rU/7m59TNeq5RpPtiUF/ooEfv7y67ob0BFihzDNxqzyOmEpsLDWpdRWM7a1Ta8diX9 7/KmEpDzjGcJg/Pwvj5CJyOTsZLukJCMCLa8+AoMszs4qJ2ovqLeTB8tvugBUABNICT+ eDx8T4FKQBB7a3AF6wXJM4aILfpBArYOrJuEN4lkQy4uwl9e0jQGD8SXyeGbMZNORy2L yAShufuKVBs3/3TERLOxaa0ePPEogNjB9YElAimeP98Z0X7DEawjgep2fVgs0yc7Su75 36fuiJkQisHXPKWkagRGrmyt7j/f6VdTzQ17F84MaIPjL3U9bAoqmxQ5O1LyXMSuNHUw J1DA== 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=3k2Qozw9K7T3ULHctZF2uRyGbKqkev5Yvd3i8BwLL6Q=; b=QVdWVNJJBSmtqlCeFD7aklnYBHl7MeDQRa3wnZct0aW8hTDkbflkr0QIevws11LX0V A8Oel+ga0HYnmPm/pe757h590kUk9KK1B4c5yFnrRuRzItUW1SFoBstwpeXGTnMrCkqV 0AJps8/D4WrHyr2LJ+mI4JGYSTOtLYKrEpUgLmzY5wNHytMPTBwv5O2q8te+BG9kBMym P8HLLO7w8ynTeMMswRP4dJGdn7UUcm6p2w+6/q8bqXKUK1g3Py7C4d2rCz8/eBSYzQ6o bYx3zm1jsPAMeJefNVewVGp3SL/3s46lO+omc/jcKVWkUXDAcXcehwplM1wwxFdwvLYO E9mA== X-Gm-Message-State: AOAM5319QUpA9eHVv1SXCKAR40EuXeEOTrTv+2TzsUWBVZAZPYHhGMBL kzcB9G5lqFJt9QTkt4Bpm+c+EU3EludUfJC15BeasQ== X-Google-Smtp-Source: ABdhPJz0P/lPp3nduBpCI463CmMAzDxLqlASXNACZIK8CQVQjVPCG9CcO/+9HjqSM/KyFs+VY+csHhR3WhxQTYkaNqE= X-Received: by 2002:a50:d51e:: with SMTP id u30mr2058575edi.296.1596209349842; Fri, 31 Jul 2020 08:29:09 -0700 (PDT) MIME-Version: 1.0 References: <20200709020629.91671-1-justin.he@arm.com> In-Reply-To: <20200709020629.91671-1-justin.he@arm.com> From: Dan Williams Date: Fri, 31 Jul 2020 08:28:58 -0700 Message-ID: Subject: Re: [PATCH v3 0/6] Fix and enable pmem as RAM device on arm64 To: Jia He Message-ID-Hash: J75AIHLD65GQRTYWQM7DDUU65H4S4A3X X-Message-ID-Hash: J75AIHLD65GQRTYWQM7DDUU65H4S4A3X X-MailFrom: dan.j.williams@intel.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: Catalin Marinas , Will Deacon , Tony Luck , Fenghua Yu , Yoshinori Sato , Rich Felker , Dave Hansen , Andy Lutomirski , Peter Zijlstra , Thomas Gleixner , Ingo Molnar , Borislav Petkov , David Hildenbrand , X86 ML , "H. Peter Anvin" , Andrew Morton , Baoquan He , Chuhong Yuan , Mike Rapoport , Masahiro Yamada , Michal Hocko , Linux ARM , Linux Kernel Mailing List , linux-ia64@vger.kernel.org, Linux-sh , linux-nvdimm , Linux MM , Jonathan Cameron , Kaly Xin 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 Wed, Jul 8, 2020 at 7:06 PM Jia He wrote: > > This fixies a few issues when I tried to enable pmem as RAM device on arm64. What NVDIMM bus driver is being used in this case? The ACPI NFIT driver? I'm just looking to see if currently deployed phys_to_target_node() is sufficient, or if this is coming in a new driver? _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-leave@lists.01.org