From: Pankaj Gupta <pagupta@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: cohuck@redhat.com, kvm@vger.kernel.org, mst@redhat.com,
jasowang@redhat.com, david@fromorbit.com, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org,
adilger kernel <adilger.kernel@dilger.ca>,
zwisler@kernel.org, aarcange@redhat.com,
linux-nvdimm@lists.01.org, david@redhat.com, willy@infradead.org,
hch@infradead.org, linux-acpi@vger.kernel.org,
linux-ext4@vger.kernel.org, lenb@kernel.org, kilobyte@angband.pl,
riel@surriel.com, yuval shaia <yuval.shaia@oracle.com>,
stefanha@redhat.com, pbonzini@redhat.com, lcapitulino@redhat.com,
kwolf@redhat.com, nilal@redhat.com, tytso@mit.edu,
xiaoguangrong eric <xiaoguangrong.eric@gmail.com>,
darrick wong <darrick.wong@oracle.com>,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
imammedo@redhat.com
Subject: Re: [PATCH v5 4/6] dax: check synchronous mapping is supported
Date: Wed, 10 Apr 2019 04:31:19 -0400 (EDT) [thread overview]
Message-ID: <299038321.20701113.1554885079188.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190410082504.GF1426@quack2.suse.cz>
> > This patch introduces 'daxdev_mapping_supported' helper
> > which checks if 'MAP_SYNC' is supported with filesystem
> > mapping. It also checks if corresponding dax_device is
> > synchronous. Virtio pmem device is asynchronous and
> > does not not support VM_SYNC.
> >
> > Suggested-by: Jan Kara <jack@suse.cz>
> > Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> > ---
> > include/linux/dax.h | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/include/linux/dax.h b/include/linux/dax.h
> > index b896706a5ee9..4a2a60ffec86 100644
> > --- a/include/linux/dax.h
> > +++ b/include/linux/dax.h
> > @@ -38,6 +38,24 @@ void kill_dax(struct dax_device *dax_dev);
> > void dax_write_cache(struct dax_device *dax_dev, bool wc);
> > bool dax_write_cache_enabled(struct dax_device *dax_dev);
> > bool dax_synchronous(struct dax_device *dax_dev);
> > +
> > +/*
> > + * Callers check if synchronous mapping is enabled for DAX file
> > + * and attached dax device is also synchronous.
> > + *
> > + * dax_synchronous function verifies if dax device is synchronous.
> > + * Currently, only virtio pmem device supports asynchronous device
> > + * flush.
> > + */
>
> Thanks for the patch! I'd restructure this comment like:
>
> /*
> * Check if given mapping is supported by the file / underlying device.
> */
Sure.
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
>
> /* Everyone supports non-sync mappings */
> > + if (!(vma->vm_flags & VM_SYNC))
> > + return true;
> /* Sync mappings are supported only for files using DAX */
> > + if (!IS_DAX(file_inode(vma->vm_file)))
> > + return false;
> /* Underlying device must support persisting through CPU instructions */
> > + return dax_synchronous(dax_dev);
> > +}
> > #else
> > static inline struct dax_device *dax_get_by_host(const char *host)
> > {
> > @@ -69,6 +87,11 @@ static inline bool dax_synchronous(struct dax_device
> > *dax_dev)
> > {
> > return true;
> > }
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
> > + return true;
>
> This looks wrong. Shouldn't it rather be:
>
> return !(vma->flags & VM_SYNC);
>
> ?
Right. I will correct this.
Thanks,
Pankaj
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Pankaj Gupta <pagupta@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-acpi@vger.kernel.org,
qemu-devel@nongnu.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org,
dan j williams <dan.j.williams@intel.com>,
zwisler@kernel.org, vishal l verma <vishal.l.verma@intel.com>,
dave jiang <dave.jiang@intel.com>,
mst@redhat.com, jasowang@redhat.com, willy@infradead.org,
rjw@rjwysocki.net, hch@infradead.org, lenb@kernel.org,
tytso@mit.edu, adilger kernel <adilger.kernel@dilger.ca>,
darrick wong <darrick.wong@oracle.com>,
lcapitulino@redhat.com, kwolf@redhat.com, imammedo@redhat.com,
jmoyer@redhat.com, nilal@redhat.com, riel@surriel.com,
stefanha@redhat.com, aarcange@redhat.com, david@redhat.c
Subject: Re: [PATCH v5 4/6] dax: check synchronous mapping is supported
Date: Wed, 10 Apr 2019 04:31:19 -0400 (EDT) [thread overview]
Message-ID: <299038321.20701113.1554885079188.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190410082504.GF1426@quack2.suse.cz>
> > This patch introduces 'daxdev_mapping_supported' helper
> > which checks if 'MAP_SYNC' is supported with filesystem
> > mapping. It also checks if corresponding dax_device is
> > synchronous. Virtio pmem device is asynchronous and
> > does not not support VM_SYNC.
> >
> > Suggested-by: Jan Kara <jack@suse.cz>
> > Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> > ---
> > include/linux/dax.h | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/include/linux/dax.h b/include/linux/dax.h
> > index b896706a5ee9..4a2a60ffec86 100644
> > --- a/include/linux/dax.h
> > +++ b/include/linux/dax.h
> > @@ -38,6 +38,24 @@ void kill_dax(struct dax_device *dax_dev);
> > void dax_write_cache(struct dax_device *dax_dev, bool wc);
> > bool dax_write_cache_enabled(struct dax_device *dax_dev);
> > bool dax_synchronous(struct dax_device *dax_dev);
> > +
> > +/*
> > + * Callers check if synchronous mapping is enabled for DAX file
> > + * and attached dax device is also synchronous.
> > + *
> > + * dax_synchronous function verifies if dax device is synchronous.
> > + * Currently, only virtio pmem device supports asynchronous device
> > + * flush.
> > + */
>
> Thanks for the patch! I'd restructure this comment like:
>
> /*
> * Check if given mapping is supported by the file / underlying device.
> */
Sure.
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
>
> /* Everyone supports non-sync mappings */
> > + if (!(vma->vm_flags & VM_SYNC))
> > + return true;
> /* Sync mappings are supported only for files using DAX */
> > + if (!IS_DAX(file_inode(vma->vm_file)))
> > + return false;
> /* Underlying device must support persisting through CPU instructions */
> > + return dax_synchronous(dax_dev);
> > +}
> > #else
> > static inline struct dax_device *dax_get_by_host(const char *host)
> > {
> > @@ -69,6 +87,11 @@ static inline bool dax_synchronous(struct dax_device
> > *dax_dev)
> > {
> > return true;
> > }
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
> > + return true;
>
> This looks wrong. Shouldn't it rather be:
>
> return !(vma->flags & VM_SYNC);
>
> ?
Right. I will correct this.
Thanks,
Pankaj
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
>
WARNING: multiple messages have this Message-ID (diff)
From: Pankaj Gupta <pagupta@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-acpi@vger.kernel.org,
qemu-devel@nongnu.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org,
dan j williams <dan.j.williams@intel.com>,
zwisler@kernel.org, vishal l verma <vishal.l.verma@intel.com>,
dave jiang <dave.jiang@intel.com>,
mst@redhat.com, jasowang@redhat.com, willy@infradead.org,
rjw@rjwysocki.net, hch@infradead.org, lenb@kernel.org,
tytso@mit.edu, adilger kernel <adilger.kernel@dilger.ca>,
darrick wong <darrick.wong@oracle.com>,
lcapitulino@redhat.com, kwolf@redhat.com, imammedo@redhat.com,
jmoyer@redhat.com, nilal@redhat.com, riel@surriel.com,
stefanha@redhat.com, aarcange@redhat.com, david@redhat.com,
david@fromorbit.com, cohuck@redhat.com,
xiaoguangrong eric <xiaoguangrong.eric@gmail.com>,
pbonzini@redhat.com, kilobyte@angband.pl,
yuval shaia <yuval.shaia@oracle.com>
Subject: Re: [PATCH v5 4/6] dax: check synchronous mapping is supported
Date: Wed, 10 Apr 2019 04:31:19 -0400 (EDT) [thread overview]
Message-ID: <299038321.20701113.1554885079188.JavaMail.zimbra@redhat.com> (raw)
Message-ID: <20190410083119.GnsNfD1m4VlaRPxkKEXSggCfc9YxvMPs3ZdNgC_W42w@z> (raw)
In-Reply-To: <20190410082504.GF1426@quack2.suse.cz>
> > This patch introduces 'daxdev_mapping_supported' helper
> > which checks if 'MAP_SYNC' is supported with filesystem
> > mapping. It also checks if corresponding dax_device is
> > synchronous. Virtio pmem device is asynchronous and
> > does not not support VM_SYNC.
> >
> > Suggested-by: Jan Kara <jack@suse.cz>
> > Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> > ---
> > include/linux/dax.h | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/include/linux/dax.h b/include/linux/dax.h
> > index b896706a5ee9..4a2a60ffec86 100644
> > --- a/include/linux/dax.h
> > +++ b/include/linux/dax.h
> > @@ -38,6 +38,24 @@ void kill_dax(struct dax_device *dax_dev);
> > void dax_write_cache(struct dax_device *dax_dev, bool wc);
> > bool dax_write_cache_enabled(struct dax_device *dax_dev);
> > bool dax_synchronous(struct dax_device *dax_dev);
> > +
> > +/*
> > + * Callers check if synchronous mapping is enabled for DAX file
> > + * and attached dax device is also synchronous.
> > + *
> > + * dax_synchronous function verifies if dax device is synchronous.
> > + * Currently, only virtio pmem device supports asynchronous device
> > + * flush.
> > + */
>
> Thanks for the patch! I'd restructure this comment like:
>
> /*
> * Check if given mapping is supported by the file / underlying device.
> */
Sure.
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
>
> /* Everyone supports non-sync mappings */
> > + if (!(vma->vm_flags & VM_SYNC))
> > + return true;
> /* Sync mappings are supported only for files using DAX */
> > + if (!IS_DAX(file_inode(vma->vm_file)))
> > + return false;
> /* Underlying device must support persisting through CPU instructions */
> > + return dax_synchronous(dax_dev);
> > +}
> > #else
> > static inline struct dax_device *dax_get_by_host(const char *host)
> > {
> > @@ -69,6 +87,11 @@ static inline bool dax_synchronous(struct dax_device
> > *dax_dev)
> > {
> > return true;
> > }
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
> > + return true;
>
> This looks wrong. Shouldn't it rather be:
>
> return !(vma->flags & VM_SYNC);
>
> ?
Right. I will correct this.
Thanks,
Pankaj
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
>
WARNING: multiple messages have this Message-ID (diff)
From: Pankaj Gupta <pagupta@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-acpi@vger.kernel.org,
qemu-devel@nongnu.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org,
dan j williams <dan.j.williams@intel.com>,
zwisler@kernel.org, vishal l verma <vishal.l.verma@intel.com>,
dave jiang <dave.jiang@intel.com>,
mst@redhat.com, jasowang@redhat.com, willy@infradead.org,
rjw@rjwysocki.net, hch@infradead.org, lenb@kernel.org,
tytso@mit.edu, adilger kernel <adilger.kernel@dilger.ca>,
darrick wong <darrick.wong@oracle.com>,
lcapitulino@redhat.com, kwolf@redhat.com, imammedo@redhat.com,
jmoyer@redhat.com, nilal@redhat.com, riel@surriel.com,
stefanha@redhat.com, aarcange@redhat.com, david@redhat.com,
david@fromorbit.com, cohuck@redhat.com,
xiaoguangrong eric <xiaoguangrong.eric@gmail.com>,
pbonzini@redhat.com, kilobyte@angband.pl,
yuval shaia <yuval.shaia@oracle.com>
Subject: Re: [Qemu-devel] [PATCH v5 4/6] dax: check synchronous mapping is supported
Date: Wed, 10 Apr 2019 04:31:19 -0400 (EDT) [thread overview]
Message-ID: <299038321.20701113.1554885079188.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190410082504.GF1426@quack2.suse.cz>
> > This patch introduces 'daxdev_mapping_supported' helper
> > which checks if 'MAP_SYNC' is supported with filesystem
> > mapping. It also checks if corresponding dax_device is
> > synchronous. Virtio pmem device is asynchronous and
> > does not not support VM_SYNC.
> >
> > Suggested-by: Jan Kara <jack@suse.cz>
> > Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> > ---
> > include/linux/dax.h | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/include/linux/dax.h b/include/linux/dax.h
> > index b896706a5ee9..4a2a60ffec86 100644
> > --- a/include/linux/dax.h
> > +++ b/include/linux/dax.h
> > @@ -38,6 +38,24 @@ void kill_dax(struct dax_device *dax_dev);
> > void dax_write_cache(struct dax_device *dax_dev, bool wc);
> > bool dax_write_cache_enabled(struct dax_device *dax_dev);
> > bool dax_synchronous(struct dax_device *dax_dev);
> > +
> > +/*
> > + * Callers check if synchronous mapping is enabled for DAX file
> > + * and attached dax device is also synchronous.
> > + *
> > + * dax_synchronous function verifies if dax device is synchronous.
> > + * Currently, only virtio pmem device supports asynchronous device
> > + * flush.
> > + */
>
> Thanks for the patch! I'd restructure this comment like:
>
> /*
> * Check if given mapping is supported by the file / underlying device.
> */
Sure.
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
>
> /* Everyone supports non-sync mappings */
> > + if (!(vma->vm_flags & VM_SYNC))
> > + return true;
> /* Sync mappings are supported only for files using DAX */
> > + if (!IS_DAX(file_inode(vma->vm_file)))
> > + return false;
> /* Underlying device must support persisting through CPU instructions */
> > + return dax_synchronous(dax_dev);
> > +}
> > #else
> > static inline struct dax_device *dax_get_by_host(const char *host)
> > {
> > @@ -69,6 +87,11 @@ static inline bool dax_synchronous(struct dax_device
> > *dax_dev)
> > {
> > return true;
> > }
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
> > + return true;
>
> This looks wrong. Shouldn't it rather be:
>
> return !(vma->flags & VM_SYNC);
>
> ?
Right. I will correct this.
Thanks,
Pankaj
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
>
WARNING: multiple messages have this Message-ID (diff)
From: Pankaj Gupta <pagupta@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: cohuck@redhat.com, kvm@vger.kernel.org, mst@redhat.com,
jasowang@redhat.com, david@fromorbit.com, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org,
adilger kernel <adilger.kernel@dilger.ca>,
zwisler@kernel.org, aarcange@redhat.com,
dave jiang <dave.jiang@intel.com>,
linux-nvdimm@lists.01.org,
vishal l verma <vishal.l.verma@intel.com>,
david@redhat.com, willy@infradead.org, hch@infradead.org,
linux-acpi@vger.kernel.org, jmoyer@redhat.com,
linux-ext4@vger.kernel.org, lenb@kernel.org, kilobyte@angband.pl,
riel@surriel.com, yuval shaia <yuval.shaia@oracle.com>,
stefanha@redhat.com, pbonzini@redhat.com,
dan j williams <dan.j.williams@intel.com>,
lcapitulino@redhat.com, kwolf@redhat.com, nilal@redhat.com,
tytso@mit.edu, xiaoguangrong eric <xiaoguangrong.eric@gmail.com>,
darrick wong <darrick.wong@oracle.com>,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 4/6] dax: check synchronous mapping is supported
Date: Wed, 10 Apr 2019 04:31:19 -0400 (EDT) [thread overview]
Message-ID: <299038321.20701113.1554885079188.JavaMail.zimbra@redhat.com> (raw)
Message-ID: <20190410083119.P-0FY-r8LTAliWHf_3qubYduEiuEXP_9kXddoAjWGcU@z> (raw)
In-Reply-To: <20190410082504.GF1426@quack2.suse.cz>
> > This patch introduces 'daxdev_mapping_supported' helper
> > which checks if 'MAP_SYNC' is supported with filesystem
> > mapping. It also checks if corresponding dax_device is
> > synchronous. Virtio pmem device is asynchronous and
> > does not not support VM_SYNC.
> >
> > Suggested-by: Jan Kara <jack@suse.cz>
> > Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> > ---
> > include/linux/dax.h | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/include/linux/dax.h b/include/linux/dax.h
> > index b896706a5ee9..4a2a60ffec86 100644
> > --- a/include/linux/dax.h
> > +++ b/include/linux/dax.h
> > @@ -38,6 +38,24 @@ void kill_dax(struct dax_device *dax_dev);
> > void dax_write_cache(struct dax_device *dax_dev, bool wc);
> > bool dax_write_cache_enabled(struct dax_device *dax_dev);
> > bool dax_synchronous(struct dax_device *dax_dev);
> > +
> > +/*
> > + * Callers check if synchronous mapping is enabled for DAX file
> > + * and attached dax device is also synchronous.
> > + *
> > + * dax_synchronous function verifies if dax device is synchronous.
> > + * Currently, only virtio pmem device supports asynchronous device
> > + * flush.
> > + */
>
> Thanks for the patch! I'd restructure this comment like:
>
> /*
> * Check if given mapping is supported by the file / underlying device.
> */
Sure.
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
>
> /* Everyone supports non-sync mappings */
> > + if (!(vma->vm_flags & VM_SYNC))
> > + return true;
> /* Sync mappings are supported only for files using DAX */
> > + if (!IS_DAX(file_inode(vma->vm_file)))
> > + return false;
> /* Underlying device must support persisting through CPU instructions */
> > + return dax_synchronous(dax_dev);
> > +}
> > #else
> > static inline struct dax_device *dax_get_by_host(const char *host)
> > {
> > @@ -69,6 +87,11 @@ static inline bool dax_synchronous(struct dax_device
> > *dax_dev)
> > {
> > return true;
> > }
> > +static inline bool daxdev_mapping_supported(struct vm_area_struct *vma,
> > + struct dax_device *dax_dev)
> > +{
> > + return true;
>
> This looks wrong. Shouldn't it rather be:
>
> return !(vma->flags & VM_SYNC);
>
> ?
Right. I will correct this.
Thanks,
Pankaj
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
>
next prev parent reply other threads:[~2019-04-10 8:31 UTC|newest]
Thread overview: 221+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 4:08 [PATCH v5 0/6] virtio pmem driver Pankaj Gupta
2019-04-10 4:08 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` [PATCH v5 1/6] libnvdimm: nd_region flush callback support Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-11 14:51 ` Dan Williams
2019-04-11 14:51 ` Dan Williams
2019-04-11 14:51 ` [Qemu-devel] " Dan Williams
2019-04-11 14:51 ` Dan Williams
2019-04-11 14:51 ` Dan Williams
2019-04-11 14:51 ` Dan Williams
2019-04-11 15:57 ` [Qemu-devel] " Pankaj Gupta
2019-04-11 15:57 ` Pankaj Gupta
2019-04-11 15:57 ` Pankaj Gupta
2019-04-11 15:57 ` Pankaj Gupta
2019-04-11 16:09 ` Dan Williams
2019-04-11 16:09 ` Dan Williams
2019-04-11 16:09 ` Dan Williams
2019-04-11 16:09 ` Dan Williams
2019-04-11 16:09 ` Dan Williams
2019-04-11 16:23 ` Pankaj Gupta
2019-04-11 16:23 ` Pankaj Gupta
2019-04-11 16:23 ` Pankaj Gupta
2019-04-11 16:23 ` Pankaj Gupta
2019-04-11 16:23 ` Pankaj Gupta
2019-04-11 15:57 ` Pankaj Gupta
2019-04-12 8:32 ` Jan Kara
2019-04-12 8:32 ` [Qemu-devel] " Jan Kara
2019-04-12 8:32 ` Jan Kara
2019-04-12 8:32 ` Jan Kara
2019-04-12 8:32 ` Jan Kara
2019-04-12 13:12 ` Jeff Moyer
2019-04-12 13:12 ` Jeff Moyer
2019-04-12 13:12 ` [Qemu-devel] " Jeff Moyer
2019-04-12 13:12 ` Jeff Moyer
2019-04-12 13:12 ` Jeff Moyer
2019-04-12 13:12 ` Jeff Moyer
2019-04-18 6:27 ` [Qemu-devel] " Pankaj Gupta
2019-04-18 6:27 ` Pankaj Gupta
2019-04-18 6:27 ` Pankaj Gupta
2019-04-18 6:27 ` Pankaj Gupta
2019-04-18 16:05 ` Dan Williams
2019-04-18 16:05 ` [Qemu-devel] " Dan Williams
2019-04-18 16:05 ` Dan Williams
2019-04-18 16:05 ` Dan Williams
2019-04-18 16:05 ` Dan Williams
2019-04-18 16:10 ` Jeff Moyer
2019-04-18 16:10 ` [Qemu-devel] " Jeff Moyer
2019-04-18 16:10 ` Jeff Moyer
2019-04-18 16:10 ` Jeff Moyer
2019-04-18 16:10 ` Jeff Moyer
2019-04-18 16:10 ` Jeff Moyer
2019-04-18 16:18 ` Christoph Hellwig
2019-04-18 16:18 ` Christoph Hellwig
2019-04-18 16:18 ` [Qemu-devel] " Christoph Hellwig
2019-04-18 16:18 ` Christoph Hellwig
2019-04-18 16:18 ` Christoph Hellwig
2019-04-18 16:18 ` Christoph Hellwig
2019-04-18 18:14 ` Dan Williams
2019-04-18 18:14 ` Dan Williams
2019-04-18 18:14 ` [Qemu-devel] " Dan Williams
2019-04-18 18:14 ` Dan Williams
2019-04-18 18:14 ` Dan Williams
2019-04-18 18:14 ` Dan Williams
2019-04-22 15:51 ` Jeff Moyer
2019-04-22 15:51 ` Jeff Moyer
2019-04-22 15:51 ` [Qemu-devel] " Jeff Moyer
2019-04-22 15:51 ` Jeff Moyer
2019-04-22 15:51 ` Jeff Moyer
2019-04-22 15:51 ` Jeff Moyer
2019-04-22 19:44 ` Dan Williams
2019-04-22 19:44 ` [Qemu-devel] " Dan Williams
2019-04-22 19:44 ` Dan Williams
2019-04-22 19:44 ` Dan Williams
2019-04-22 19:44 ` Dan Williams
2019-04-22 21:03 ` Jeff Moyer
2019-04-22 21:03 ` Jeff Moyer
2019-04-22 21:03 ` [Qemu-devel] " Jeff Moyer
2019-04-22 21:03 ` Jeff Moyer
2019-04-22 21:03 ` Jeff Moyer
2019-04-22 21:03 ` Jeff Moyer
2019-04-23 4:07 ` Pankaj Gupta
2019-04-23 4:07 ` [Qemu-devel] " Pankaj Gupta
2019-04-23 4:07 ` Pankaj Gupta
2019-04-23 4:07 ` Pankaj Gupta
2019-04-23 4:07 ` Pankaj Gupta
2019-04-23 4:07 ` Pankaj Gupta
2019-04-22 19:44 ` Dan Williams
2019-04-18 16:05 ` Dan Williams
2019-04-12 8:32 ` Jan Kara
2019-04-10 4:08 ` [PATCH v5 2/5] virtio-pmem: Add virtio pmem driver Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 12:24 ` Cornelia Huck
2019-04-10 12:24 ` Cornelia Huck
2019-04-10 12:24 ` [Qemu-devel] " Cornelia Huck
2019-04-10 12:24 ` Cornelia Huck
2019-04-10 12:24 ` Cornelia Huck
2019-04-10 12:24 ` Cornelia Huck
2019-04-10 14:38 ` Yuval Shaia
2019-04-10 14:38 ` Yuval Shaia
2019-04-10 14:38 ` [Qemu-devel] " Yuval Shaia
2019-04-10 14:38 ` Yuval Shaia
2019-04-10 14:38 ` Yuval Shaia
2019-04-10 14:38 ` Yuval Shaia
2019-04-10 14:38 ` Yuval Shaia
2019-04-10 15:44 ` Pankaj Gupta
2019-04-10 15:44 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 15:44 ` Pankaj Gupta
2019-04-10 15:44 ` Pankaj Gupta
2019-04-10 15:44 ` Pankaj Gupta
2019-04-10 15:44 ` Pankaj Gupta
2019-04-10 15:38 ` Pankaj Gupta
2019-04-10 15:38 ` Pankaj Gupta
2019-04-10 15:38 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 15:38 ` Pankaj Gupta
2019-04-10 15:38 ` Pankaj Gupta
2019-04-10 15:38 ` Pankaj Gupta
2019-04-10 13:12 ` Michael S. Tsirkin
2019-04-10 13:12 ` Michael S. Tsirkin
2019-04-10 13:12 ` [Qemu-devel] " Michael S. Tsirkin
2019-04-10 13:12 ` Michael S. Tsirkin
2019-04-10 13:12 ` Michael S. Tsirkin
2019-04-10 13:12 ` Michael S. Tsirkin
2019-04-10 14:03 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 14:03 ` Pankaj Gupta
2019-04-10 14:03 ` Pankaj Gupta
2019-04-10 14:03 ` Pankaj Gupta
2019-04-10 14:31 ` Cornelia Huck
2019-04-10 14:31 ` Cornelia Huck
2019-04-10 14:31 ` Cornelia Huck
2019-04-10 14:31 ` Cornelia Huck
2019-04-10 14:31 ` Cornelia Huck
2019-04-10 16:46 ` Michael S. Tsirkin
2019-04-10 16:46 ` Michael S. Tsirkin
2019-04-10 16:46 ` Michael S. Tsirkin
2019-04-10 16:46 ` Michael S. Tsirkin
2019-04-10 16:52 ` Cornelia Huck
2019-04-10 16:52 ` Cornelia Huck
2019-04-10 16:52 ` Cornelia Huck
2019-04-10 16:52 ` Cornelia Huck
2019-04-10 16:52 ` Cornelia Huck
2019-04-10 16:46 ` Michael S. Tsirkin
2019-04-10 14:03 ` Pankaj Gupta
2019-04-10 14:41 ` Yuval Shaia
2019-04-10 14:41 ` Yuval Shaia
2019-04-10 14:41 ` [Qemu-devel] " Yuval Shaia
2019-04-10 14:41 ` Yuval Shaia
2019-04-10 14:41 ` Yuval Shaia
2019-04-10 14:41 ` Yuval Shaia
2019-04-10 4:08 ` [PATCH v5 3/6] libnvdimm: add dax_dev sync flag Pankaj Gupta
2019-04-10 4:08 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 8:28 ` Jan Kara
2019-04-10 8:28 ` [Qemu-devel] " Jan Kara
2019-04-10 8:28 ` Jan Kara
2019-04-10 8:28 ` Jan Kara
2019-04-10 8:28 ` Jan Kara
2019-04-10 8:38 ` Pankaj Gupta
2019-04-10 8:38 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 8:38 ` Pankaj Gupta
2019-04-10 8:38 ` Pankaj Gupta
2019-04-10 8:38 ` Pankaj Gupta
2019-04-10 8:38 ` Pankaj Gupta
2019-04-10 8:28 ` Jan Kara
2019-04-11 14:56 ` Dan Williams
2019-04-11 14:56 ` [Qemu-devel] " Dan Williams
2019-04-11 14:56 ` Dan Williams
2019-04-11 14:56 ` Dan Williams
2019-04-11 14:56 ` Dan Williams
2019-04-11 15:39 ` Pankaj Gupta
2019-04-11 15:39 ` [Qemu-devel] " Pankaj Gupta
2019-04-11 15:39 ` Pankaj Gupta
2019-04-11 15:39 ` Pankaj Gupta
2019-04-11 15:39 ` Pankaj Gupta
2019-04-11 15:39 ` Pankaj Gupta
2019-04-11 14:56 ` Dan Williams
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` [PATCH v5 4/6] dax: check synchronous mapping is supported Pankaj Gupta
2019-04-10 4:08 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 8:25 ` Jan Kara
2019-04-10 8:25 ` Jan Kara
2019-04-10 8:25 ` [Qemu-devel] " Jan Kara
2019-04-10 8:25 ` Jan Kara
2019-04-10 8:25 ` Jan Kara
2019-04-10 8:25 ` Jan Kara
2019-04-10 8:31 ` Pankaj Gupta [this message]
2019-04-10 8:31 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 8:31 ` Pankaj Gupta
2019-04-10 8:31 ` Pankaj Gupta
2019-04-10 8:31 ` Pankaj Gupta
2019-04-10 8:31 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` [PATCH v5 5/6] ext4: disable map_sync for async flush Pankaj Gupta
2019-04-10 4:08 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` [PATCH v5 6/6] xfs: " Pankaj Gupta
2019-04-10 4:08 ` [Qemu-devel] " Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
2019-04-10 4:08 ` Pankaj Gupta
[not found] ` <20190410040826.24371-1-pagupta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2019-04-10 8:08 ` [PATCH v5 0/6] virtio pmem driver Arkadiusz Miśkiewicz
2019-04-10 8:08 ` [Qemu-devel] " Arkadiusz Miśkiewicz
2019-04-10 8:08 ` Arkadiusz Miśkiewicz
2019-04-10 8:08 ` Arkadiusz Miśkiewicz
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=299038321.20701113.1554885079188.JavaMail.zimbra@redhat.com \
--to=pagupta@redhat.com \
--cc=aarcange@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=cohuck@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=david@redhat.com \
--cc=hch@infradead.org \
--cc=imammedo@redhat.com \
--cc=jack@suse.cz \
--cc=jasowang@redhat.com \
--cc=kilobyte@angband.pl \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nilal@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riel@surriel.com \
--cc=rjw@rjwysocki.net \
--cc=stefanha@redhat.com \
--cc=tytso@mit.edu \
--cc=virtualization@lists.linux-foundation.org \
--cc=willy@infradead.org \
--cc=xiaoguangrong.eric@gmail.com \
--cc=yuval.shaia@oracle.com \
--cc=zwisler@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.