From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
mreitz@redhat.com, keith.busch@intel.com, stefanha@redhat.com,
krister@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/6] block: Add VFIO based driver for NVMe device
Date: Thu, 6 Jul 2017 22:36:23 +0800 [thread overview]
Message-ID: <20170706143623.GA28118@lemon.lan> (raw)
In-Reply-To: <1ff791c6-a914-2a26-e5d2-683cacc82b86@redhat.com>
On Thu, 07/06 16:22, Paolo Bonzini wrote:
>
>
> On 06/07/2017 16:06, no-reply@patchew.org wrote:
> > ERROR: Use of volatile is usually wrong: see Documentation/volatile-considered-harmful.txt
> > #843: FILE: block/nvme.c:40:
> > + volatile uint32_t *doorbell;
> >
> > ERROR: Use of volatile is usually wrong: see Documentation/volatile-considered-harmful.txt
> > #869: FILE: block/nvme.c:66:
> > +typedef volatile struct {
>
> Indeed volatile should not be necessary, since we use memory barriers
> appropriately. But these are hardware registers (like, host hardware)
> so I guess it's okay for this special case.
I think I used it because we don't have ACCESS_ONCE (maybe we should?).
Fam
next prev parent reply other threads:[~2017-07-06 14:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 13:36 [Qemu-devel] [PATCH v3 0/6] block: Add VFIO based driver for NVMe device Fam Zheng
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 1/6] stubs: Add stubs for ram block API Fam Zheng
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 2/6] block: Add VFIO based NVMe driver Fam Zheng
2017-07-06 17:38 ` Keith Busch
2017-07-06 23:27 ` Fam Zheng
2017-07-07 10:06 ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2017-07-07 17:15 ` [Qemu-devel] " Stefan Hajnoczi
2017-07-10 14:55 ` Stefan Hajnoczi
2017-07-12 2:14 ` Fam Zheng
2017-07-12 10:49 ` Stefan Hajnoczi
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 3/6] block: Introduce bdrv_dma_map and bdrv_dma_unmap Fam Zheng
2017-07-10 14:57 ` Stefan Hajnoczi
2017-07-10 15:07 ` Stefan Hajnoczi
2017-07-10 15:08 ` Paolo Bonzini
2017-07-11 10:05 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-07-11 10:28 ` Paolo Bonzini
2017-07-12 1:07 ` Fam Zheng
2017-07-12 14:03 ` Paolo Bonzini
2017-07-14 13:37 ` Stefan Hajnoczi
2017-07-14 13:46 ` Paolo Bonzini
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 4/6] block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap Fam Zheng
2017-07-10 14:59 ` Stefan Hajnoczi
2017-07-10 15:09 ` Paolo Bonzini
2017-07-11 10:04 ` Stefan Hajnoczi
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 5/6] qemu-img: Map bench buffer Fam Zheng
2017-07-05 13:36 ` [Qemu-devel] [PATCH v3 6/6] block: Move NVMe spec definitions to a separate header Fam Zheng
2017-07-05 13:39 ` Paolo Bonzini
2017-07-10 15:01 ` Stefan Hajnoczi
2017-07-05 13:41 ` [Qemu-devel] [PATCH v3 0/6] block: Add VFIO based driver for NVMe device Paolo Bonzini
2017-07-06 14:06 ` no-reply
2017-07-06 14:22 ` Paolo Bonzini
2017-07-06 14:36 ` Fam Zheng [this message]
2017-07-06 14:44 ` Paolo Bonzini
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=20170706143623.GA28118@lemon.lan \
--to=famz@redhat.com \
--cc=keith.busch@intel.com \
--cc=krister@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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.