qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Fam Zheng <fam@euphon.net>, Hannes Reinecke <hare@suse.com>,
	qemu-block@nongnu.org, David Hildenbrand <david@redhat.com>,
	qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
	Yuval Shaia <yuval.shaia.ml@gmail.com>,
	Klaus Jensen <its@irrelevant.dk>, Keith Busch <kbusch@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [PATCH v2 0/9] hw/dma: Use dma_addr_t type definition when relevant
Date: Thu, 6 Jan 2022 06:08:37 -0500	[thread overview]
Message-ID: <20220106060800-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220104085431.2122999-1-f4bug@amsat.org>

On Tue, Jan 04, 2022 at 09:54:22AM +0100, Philippe Mathieu-Daudé wrote:
> Since v1:
> - Addressed David review comment (stick to dma_addr_t type)
> - Addressed Peter review comment (incorrect doc string)


PCI things:

Reviewed-by: Michael S. Tsirkin <mst@redhat.com>

who's merging all this? Yourself?

> Hi,
> 
> This series aims to clarify a bit the DMA API, in particular the
> 'size' argument which is not clear enough (as we use multiple types
> for it). This helps avoiding build failures on 32-bit host [*] (and
> likely overflows calculation too IMO).
> 
> Some units using the DMA API are first removed from user-mode
> emulation to avoid build failure (they shouldn't be there in
> the first place).
> 
> Then some variables are renamed for clarity (no functional change).
> 
> Finally we replace misuses with dma_addr_t typedef. The previous
> patch which failed on 32-bit host applied on top (not failing anymore).
> 
> Regards,
> 
> Phil.
> 
> [*] https://www.mail-archive.com/qemu-devel@nongnu.org/msg858825.html
> 
> Supersedes: <20211231114901.976937-1-philmd@redhat.com>
> 
> Philippe Mathieu-Daudé (9):
>   hw/nvram: Restrict stub to sysemu and tools
>   hw/pci: Restrict pci-bus stub to sysemu
>   hw/pci: Document pci_dma_map()
>   hw/dma: Remove CONFIG_USER_ONLY check
>   hw/rdma/rdma_utils: Rename rdma_pci_dma_map 'len' argument
>   hw/scsi: Rename SCSIRequest::resid as 'residual'
>   hw/dma: Fix format string issues using dma_addr_t
>   hw/dma: Use dma_addr_t type definition when relevant
>   hw/dma: Let dma_buf_read() / dma_buf_write() propagate MemTxResult
> 
>  hw/rdma/rdma_utils.h   |  2 +-
>  include/hw/pci/pci.h   | 12 ++++++
>  include/hw/scsi/scsi.h |  4 +-
>  include/sysemu/dma.h   | 31 ++++++++-------
>  hw/ide/ahci.c          | 10 ++---
>  hw/nvme/ctrl.c         |  6 +--
>  hw/rdma/rdma_utils.c   | 14 +++----
>  hw/scsi/megasas.c      | 85 +++++++++++++++++++++++++++++-------------
>  hw/scsi/scsi-bus.c     | 12 +++---
>  hw/scsi/scsi-disk.c    |  4 +-
>  softmmu/dma-helpers.c  | 34 +++++++----------
>  hw/nvram/meson.build   |  6 ++-
>  hw/rdma/trace-events   |  2 +-
>  stubs/meson.build      |  4 +-
>  14 files changed, 134 insertions(+), 92 deletions(-)
> 
> -- 
> 2.33.1
> 



  parent reply	other threads:[~2022-01-06 11:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04  8:54 [PATCH v2 0/9] hw/dma: Use dma_addr_t type definition when relevant Philippe Mathieu-Daudé
2022-01-04  8:54 ` [PATCH v2 1/9] hw/nvram: Restrict stub to sysemu and tools Philippe Mathieu-Daudé
2022-01-07  0:17   ` Richard Henderson
2022-01-11 10:43     ` Philippe Mathieu-Daudé
2022-01-04  8:54 ` [PATCH v2 2/9] hw/pci: Restrict pci-bus stub to sysemu Philippe Mathieu-Daudé
2022-01-07  0:18   ` Richard Henderson
2022-01-10  8:43   ` David Hildenbrand
2022-01-04  8:54 ` [PATCH v2 3/9] hw/pci: Document pci_dma_map() Philippe Mathieu-Daudé
2022-01-07  0:20   ` Richard Henderson
2022-01-04  8:54 ` [PATCH v2 4/9] hw/dma: Remove CONFIG_USER_ONLY check Philippe Mathieu-Daudé
2022-01-07  0:20   ` Richard Henderson
2022-01-10  8:45   ` David Hildenbrand
2022-01-04  8:54 ` [PATCH v2 5/9] hw/rdma/rdma_utils: Rename rdma_pci_dma_map 'len' argument Philippe Mathieu-Daudé
2022-01-07  0:21   ` Richard Henderson
2022-01-10  8:46   ` David Hildenbrand
2022-01-04  8:54 ` [PATCH v2 6/9] hw/scsi: Rename SCSIRequest::resid as 'residual' Philippe Mathieu-Daudé
2022-01-07  0:22   ` Richard Henderson
2022-01-10  8:46   ` David Hildenbrand
2022-01-04  8:54 ` [PATCH v2 7/9] hw/dma: Fix format string issues using dma_addr_t Philippe Mathieu-Daudé
2022-01-07  0:24   ` Richard Henderson
2022-01-10  8:47   ` David Hildenbrand
2022-01-04  8:54 ` [PATCH v2 8/9] hw/dma: Use dma_addr_t type definition when relevant Philippe Mathieu-Daudé
2022-01-04  9:55   ` Peter Xu
2022-01-10  8:49   ` David Hildenbrand
2022-01-10  9:05     ` Philippe Mathieu-Daudé
2022-01-04  8:54 ` [PATCH v2 9/9] hw/dma: Let dma_buf_read() / dma_buf_write() propagate MemTxResult Philippe Mathieu-Daudé
2022-01-10  8:51   ` David Hildenbrand
2022-01-10  9:07     ` Philippe Mathieu-Daudé
2022-01-06 11:08 ` Michael S. Tsirkin [this message]
2022-01-11 18:47   ` [PATCH v2 0/9] hw/dma: Use dma_addr_t type definition when relevant Philippe Mathieu-Daudé

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=20220106060800-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=david@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --cc=hare@suse.com \
    --cc=its@irrelevant.dk \
    --cc=jsnow@redhat.com \
    --cc=kbusch@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=yuval.shaia.ml@gmail.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;
as well as URLs for NNTP newsgroup(s).