qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Farhan Ali <alifm@linux.ibm.com>, qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, stefanha@redhat.com,
	mjrosato@linux.ibm.com, schnelle@linux.ibm.com,
	philmd@linaro.org, kwolf@redhat.com, hreitz@redhat.com,
	fam@euphon.net
Subject: Re: [PATCH v5 3/3] block/nvme: Use host PCI MMIO API
Date: Fri, 25 Apr 2025 11:22:38 +0200	[thread overview]
Message-ID: <a80e2c09-41c1-4c1b-9524-60ad5d2d038d@redhat.com> (raw)
In-Reply-To: <20250417173801.827-4-alifm@linux.ibm.com>

On 17/04/2025 19.38, Farhan Ali wrote:
> Use the host PCI MMIO functions to read/write
> to NVMe registers, rather than directly accessing
> them.
> 
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
> ---
>   block/nvme.c | 41 +++++++++++++++++++++++------------------
>   1 file changed, 23 insertions(+), 18 deletions(-)

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2025-04-25  9:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 17:37 [PATCH v5 0/3] Enable QEMU NVMe userspace driver on s390x Farhan Ali
2025-04-17 17:37 ` [PATCH v5 1/3] util: Add functions for s390x mmio read/write Farhan Ali
2025-04-25  9:00   ` Thomas Huth
2025-04-25 10:29     ` Niklas Schnelle
2025-04-25 14:09       ` Heiko Carstens
2025-04-30 16:42         ` Farhan Ali
2025-04-17 17:38 ` [PATCH v5 2/3] include: Add a header to define host PCI MMIO functions Farhan Ali
2025-04-22 14:45   ` Stefan Hajnoczi
2025-04-25  9:17   ` Thomas Huth
2025-04-30 16:47     ` Farhan Ali
2025-04-30 17:52       ` Thomas Huth
2025-04-30 18:32         ` Farhan Ali
2025-04-30 18:38           ` Thomas Huth
2025-04-17 17:38 ` [PATCH v5 3/3] block/nvme: Use host PCI MMIO API Farhan Ali
2025-04-25  9:22   ` Thomas Huth [this message]
2025-04-24 16:24 ` [PATCH v5 0/3] Enable QEMU NVMe userspace driver on s390x Farhan Ali
2025-04-25  9:24   ` Thomas Huth
2025-04-25  9:59   ` 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=a80e2c09-41c1-4c1b-9524-60ad5d2d038d@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=alifm@linux.ibm.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=schnelle@linux.ibm.com \
    --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 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).