From: "Michael S. Tsirkin" <mst@redhat.com>
To: Pankaj Gupta <pagupta@redhat.com>
Cc: cohuck@redhat.com, jack@suse.cz, kvm@vger.kernel.org,
david@redhat.com, jasowang@redhat.com, david@fromorbit.com,
qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org,
dm-devel@redhat.com, adilger.kernel@dilger.ca,
zwisler@kernel.org, aarcange@redhat.com, dave.jiang@intel.com,
jstaron@google.com, linux-nvdimm@lists.01.org,
vishal.l.verma@intel.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,
rdunlap@infradead.org, riel@surriel.com, yuval.shaia@oracle.com,
stefanha@redhat.com, pbonzini@redhat.com,
dan.j.williams@intel.com, lcapitulino@redhat.com,
kwolf@redhat.com, nilal@redhat.com, tytso@mit.edu,
xiaoguangrong.eric@gmail.com, snitzer@redhat.com,
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 v10 2/7] virtio-pmem: Add virtio pmem driver
Date: Tue, 21 May 2019 09:51:35 -0400 [thread overview]
Message-ID: <20190521094543-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190521133713.31653-3-pagupta@redhat.com>
On Tue, May 21, 2019 at 07:07:08PM +0530, Pankaj Gupta wrote:
> diff --git a/include/uapi/linux/virtio_pmem.h b/include/uapi/linux/virtio_pmem.h
> new file mode 100644
> index 000000000000..7a3e2fe52415
> --- /dev/null
> +++ b/include/uapi/linux/virtio_pmem.h
> @@ -0,0 +1,35 @@
> +/* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
> +/*
> + * Definitions for virtio-pmem devices.
> + *
> + * Copyright (C) 2019 Red Hat, Inc.
> + *
> + * Author(s): Pankaj Gupta <pagupta@redhat.com>
> + */
> +
> +#ifndef _UAPI_LINUX_VIRTIO_PMEM_H
> +#define _UAPI_LINUX_VIRTIO_PMEM_H
> +
> +#include <linux/types.h>
> +#include <linux/virtio_types.h>
> +#include <linux/virtio_ids.h>
> +#include <linux/virtio_config.h>
> +
> +struct virtio_pmem_config {
> + __le64 start;
> + __le64 size;
> +};
> +
config generally should be __u64.
Are you sure sparse does not complain?
> +#define VIRTIO_PMEM_REQ_TYPE_FLUSH 0
> +
> +struct virtio_pmem_resp {
> + /* Host return status corresponding to flush request */
> + __virtio32 ret;
> +};
> +
> +struct virtio_pmem_req {
> + /* command type */
> + __virtio32 type;
> +};
> +
> +#endif
> --
> 2.20.1
Sorry why are these __virtio32 not __le32?
--
MST
next prev parent reply other threads:[~2019-05-21 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 13:37 [Qemu-devel] [PATCH v10 0/7] virtio pmem driver Pankaj Gupta
2019-05-21 13:37 ` [Qemu-devel] [PATCH v10 1/7] libnvdimm: nd_region flush callback support Pankaj Gupta
2019-05-21 13:37 ` [Qemu-devel] [PATCH v10 2/7] virtio-pmem: Add virtio pmem driver Pankaj Gupta
2019-05-21 13:51 ` Michael S. Tsirkin [this message]
2019-05-21 16:24 ` Pankaj Gupta
2019-05-21 13:37 ` [Qemu-devel] [PATCH v10 3/7] libnvdimm: add dax_dev sync flag Pankaj Gupta
2019-05-21 13:37 ` [Qemu-devel] [PATCH v10 4/7] dm: enable synchronous dax Pankaj Gupta
2019-06-01 6:28 ` Dan Williams
2019-06-10 5:08 ` Pankaj Gupta
2019-05-21 13:37 ` [Qemu-devel] [PATCH v10 5/7] dax: check synchronous mapping is supported Pankaj Gupta
2019-05-21 13:37 ` [Qemu-devel] [PATCH v10 6/7] ext4: disable map_sync for async flush Pankaj Gupta
2019-05-21 13:37 ` [Qemu-devel] [PATCH v10 7/7] xfs: " Pankaj Gupta
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=20190521094543-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aarcange@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=cohuck@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=darrick.wong@oracle.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=david@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=imammedo@redhat.com \
--cc=jack@suse.cz \
--cc=jasowang@redhat.com \
--cc=jmoyer@redhat.com \
--cc=jstaron@google.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=nilal@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rdunlap@infradead.org \
--cc=riel@surriel.com \
--cc=rjw@rjwysocki.net \
--cc=snitzer@redhat.com \
--cc=stefanha@redhat.com \
--cc=tytso@mit.edu \
--cc=virtualization@lists.linux-foundation.org \
--cc=vishal.l.verma@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).