All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: aik@ozlabs.ru, pbonzini@redhat.com, alex.williamson@redhat.com,
	mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 0/2] VFIO: Make 8-byte accesses atomic
Date: Thu, 20 Apr 2017 00:19:23 -0700	[thread overview]
Message-ID: <a8eb495d-7c03-2d6f-c8df-3970f08bc05d@twiddle.net> (raw)
In-Reply-To: <1492631083-23965-1-git-send-email-joserz@linux.vnet.ibm.com>

On 04/19/2017 12:44 PM, Jose Ricardo Ziviani wrote:
> This patchset has two patches:
> [1] 8-byte writes to non-mapped MMIO are broken into pairs of 4-byte writes, this patch makes such pairs atomic.
>
> [2] Enable 8-byte accesses in vfio_region_write and vfio_region_read.
>
> Patches based on master.
>
> Jose Ricardo Ziviani (2):
>   vfio: Set MemoryRegionOps:max_access_size and min_access_size
>   vfio: enable 8-byte reads/writes to vfio
>
>  hw/vfio/common.c | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>

I think these patches need to be squashed to be bisectable.


r~

  parent reply	other threads:[~2017-04-20  7:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 19:44 [Qemu-devel] [PATCH 0/2] VFIO: Make 8-byte accesses atomic Jose Ricardo Ziviani
2017-04-19 19:44 ` [Qemu-devel] [PATCH 1/2] vfio: Set MemoryRegionOps:max_access_size and min_access_size Jose Ricardo Ziviani
2017-04-19 19:44 ` [Qemu-devel] [PATCH 2/2] vfio: enable 8-byte reads/writes to vfio Jose Ricardo Ziviani
2017-04-20  7:19 ` Richard Henderson [this message]
2017-04-20 16:03   ` [Qemu-devel] [PATCH 0/2] VFIO: Make 8-byte accesses atomic Alex Williamson
2017-04-21 10:06     ` Paolo Bonzini
2017-04-21 15:51       ` Richard Henderson
2017-05-03  2:41       ` joserz
2017-05-03  2:52         ` Alex Williamson

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=a8eb495d-7c03-2d6f-c8df-3970f08bc05d@twiddle.net \
    --to=rth@twiddle.net \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=joserz@linux.vnet.ibm.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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.