public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Xiong Zhou <xzhou@redhat.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
	fstests@vger.kernel.org, jmoyer@redhat.com,
	linux-nvdimm@ml01.01.org
Subject: Re: [PATCH v4 0/2] mmap dio and DAX
Date: Fri, 3 Feb 2017 14:29:52 +0800	[thread overview]
Message-ID: <20170203062952.GZ1859@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170203055717.acjivw4o4zmxhd64@XZHOUW.usersys.redhat.com>

On Fri, Feb 03, 2017 at 01:57:17PM +0800, Xiong Zhou wrote:

> > I just wanted to let you know that I'm testing with these new xfstests right
> > now, and so far I've been unable to successfully get any PMD faults.  I'm
> > looking into why that is right now, and should hopefully have some changes so
> > we can do both PTE and PMD testing with this set.
> 
> Thank you very much for looking into this!
> 
> Adding a printk msg in dax_iomap_pmd_fault in fs/dax.c shows that
> these 2 cases called this function, so do __radix_tree_insert
> in lib/radix-tree.c with order > 0.  I must have missed something..
> 
> > 
> > Also, it looks like the test number "generic/405" was already used in
> > xfstests/master by this commit:
> > 
> > 66768bc generic/405: test mkfs against thin provision device
> > 
> > So this may need to be generic/406. :)
> 
> Ya, i can update this or Eryu can handle it while applying.

I'll do renumber after patch being reviewed, no need to update patch
only to change the seq number. (Better to use latest tree when writing
new case though.)

Thanks,
Eryu

  reply	other threads:[~2017-02-03  6:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  3:07 [PATCH 0/4] mmap dio and DAX Xiong Zhou
2017-01-18  3:07 ` [PATCH 1/4] common/rc: add _require_scratch_dax Xiong Zhou
2017-01-19  4:17   ` Eryu Guan
2017-01-18  3:07 ` [PATCH 2/4] src/t_mmap_dio: add mmap dio test Xiong Zhou
2017-01-18  3:07 ` [PATCH 3/4] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-01-19  4:24   ` Eryu Guan
2017-01-18  3:07 ` [PATCH 4/4] generic: test mmap dio through DAX and non-DAX Xiong Zhou
2017-01-19  5:54   ` Eryu Guan
2017-01-19 10:13     ` [PATCH v2 0/2] mmap dio and DAX Xiong Zhou
2017-01-19 10:13       ` [PATCH v2 1/2] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-01-19 20:49         ` Ross Zwisler
2017-01-20  1:15           ` Xiong Zhou
2017-01-20  2:21           ` [PATCH v3] " Xiong Zhou
2017-01-20  6:15             ` [PATCH v4 0/2] mmap dio and DAX Xiong Zhou
2017-01-20  6:15               ` [PATCH v4 1/2] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-02-04 15:17                 ` [PATCH] fixup! " Ross Zwisler
2017-02-05  6:21                   ` [PATCH v5 0/2] mmap dio and DAX Xiong Zhou
2017-02-05  6:21                     ` [PATCH v5 1/2] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-02-06 19:13                       ` Ross Zwisler
2017-02-05  6:21                     ` [PATCH v5 2/2] generic: test mmap io through DAX and non-DAX Xiong Zhou
2017-02-06 19:17                       ` Ross Zwisler
2017-02-08  4:11                         ` [PATCH v6 0/2] mmap dio and DAX Xiong Zhou
2017-02-08  4:11                           ` [PATCH v6 1/2] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-02-08  4:11                           ` [PATCH v6 2/2] generic: test mmap io through DAX and non-DAX Xiong Zhou
2017-02-17  6:46                             ` Eryu Guan
2017-02-17  6:52                               ` Xiong Zhou
2017-01-20  6:15               ` [PATCH v4 " Xiong Zhou
2017-01-24 22:28               ` [PATCH v4 0/2] mmap dio and DAX Ross Zwisler
2017-02-03  5:57                 ` Xiong Zhou
2017-02-03  6:29                   ` Eryu Guan [this message]
2017-02-03 16:57                   ` Ross Zwisler
2017-02-04 10:14                     ` Xiong Zhou
2017-01-19 10:13       ` [PATCH v2 2/2] generic: test mmap dio through DAX and non-DAX Xiong Zhou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170203062952.GZ1859@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=jmoyer@redhat.com \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=xzhou@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox