Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp1381858pxv; Fri, 16 Jul 2021 08:08:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxK6KR6LEQw3MmeY0BJutKjLtVYCbMrmYtxKQEOmv20t6cwYx7ZK0kmtt2RI9TeHmzm3qPX X-Received: by 2002:a5d:5103:: with SMTP id s3mr12620775wrt.180.1626448106753; Fri, 16 Jul 2021 08:08:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626448106; cv=none; d=google.com; s=arc-20160816; b=InQIdKR5ptoKCjOHIVFKTf8UKZ4un8T5NAnbgqKerxk3ICeif1hf/o4PhZftWUi5yg IjKQNdZOs3oKbv45CTkRjwZSO9f93ZG4gm1Beg7X1s9JgCdOowxGC4CcsY5R85P+1fWc z+5ju2s//8kC/C7W/RX6VBZ7goUxuIl/WUvN+4wVcLi5yfJMSZO5VWrJZvUTA/6wPTZg KCiLKhLG0icskzmHhR5Wb1a1ivVHf6uOAUgCDrdugEZFX6KEuFhp6K+eq5Jdvw5rT7bc YL10j/96DSh4m30gOm4m9HwuaqJM5CDI6xfACxDoES0Nf6tE9ESMB+Nph2bbcuaq7UOm BIpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=NR/k1hcO60vXsu5gSuWsvD6sSU3dao3fudneFMZR54o=; b=C47oEaJJ/lOJWDQi7YQm1X8orgbNnMxZxFlOgWU0VhUy7ct+3UN79UmT+eAPO4PHvQ i6fXFd+UB/dlqtpYXqvxcpdB2prMH0pmPYPy1x9oMsuoTULbZUg3EEIyD94P/2Sm63ix RaTvCcZAXiHx76D4KXXAKJbWzDcB0oKxY5mob5SoDxH7FeiSzOJCydRcH7r0xFliMlAr DTMVxSo0erbXCjtEvj4ouIAH5MgqU/fUDCFmkxzn36sGEldHf6LwOC4RutlvLwdeDS18 f1BjgJL6yZQoTo+HGxuyLp/5OqdnKS4VtZVxAjOotOwGi5PS7z6g9kioWWFPTUeUfDZZ lxPQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 5si10890766ejh.535.2021.07.16.08.08.02; Fri, 16 Jul 2021 08:08:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240293AbhGPPKx (ORCPT + 99 others); Fri, 16 Jul 2021 11:10:53 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:57661 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S240493AbhGPPKw (ORCPT ); Fri, 16 Jul 2021 11:10:52 -0400 Received: from callcc.thunk.org (96-65-121-81-static.hfc.comcastbusiness.net [96.65.121.81]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 16GF7fnw014809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 16 Jul 2021 11:07:42 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id D6FEA4202F5; Fri, 16 Jul 2021 11:07:40 -0400 (EDT) Date: Fri, 16 Jul 2021 11:07:40 -0400 From: "Theodore Y. Ts'o" To: Felix Kuehling Cc: Alex Sierra , akpm@linux-foundation.org, linux-mm@kvack.org, rcampbell@nvidia.com, linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, hch@lst.de, jgg@nvidia.com, jglisse@redhat.com Subject: Re: [PATCH v3 0/8] Support DEVICE_GENERIC memory in migrate_vma_* Message-ID: References: <20210617151705.15367-1-alex.sierra@amd.com> <905418d1-9099-0ea8-a6e6-84cc8ef3d0b0@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <905418d1-9099-0ea8-a6e6-84cc8ef3d0b0@amd.com> Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Wed, Jun 23, 2021 at 05:49:55PM -0400, Felix Kuehling wrote: > > I can think of two ways to test the changes for MEMORY_DEVICE_GENERIC in > this patch series in a way that is reproducible without special hardware and > firmware: > > For the reference counting changes we could use the dax driver with hmem and > use efi_fake_mem on the kernel command line to create some DEVICE_GENERIC > pages. I'm open to suggestions for good user mode tests to exercise dax > functionality on this type of memory. Sorry for the thread necromancy, but now that the merge window is past.... Today I test ext4's dax support, without having any $$$ DAX hardware, by using the kernel command line "memmap=4G!9G:memmap=9G!14G" which reserves memory so that creates two pmem device and then I run xfstests with DAX enabled using qemu or using a Google Compute Engine VM, using TEST_DEV=/dev/pmem0 and SCRATCH_DEV=/dev/pmem1. If you can give me a recipe for what kernel configs I should enable, and what magic kernel command line arguments to use, then I'd be able to test your patch set with ext4. Cheers, - Ted