DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: xuan.ding@intel.com, chenbo.xia@intel.com
Cc: dev@dpdk.org, ktraynor@redhat.com, ferruh.yigit@intel.com,
	jiayu.hu@intel.com, yuanx.wang@intel.com
Subject: Re: [PATCH v4 0/2] vhost: fix async address mapping
Date: Thu, 17 Feb 2022 09:54:09 +0100	[thread overview]
Message-ID: <35d535be-88fb-a8f4-93cf-f98e75a19dc4@redhat.com> (raw)
In-Reply-To: <20220216022854.39057-1-xuan.ding@intel.com>



On 2/16/22 03:28, xuan.ding@intel.com wrote:
> From: Xuan Ding <xuan.ding@intel.com>
> 
> This patchset fixes the issue of incorrect DMA mapping in PA mode.
> Due to the ambiguity of host_phys_addr naming in the guest page
> struct, rename it to host_iova.
> 
> v4:
> * Fix the patch timezone.
> 
> v3:
> * Fix some format issues.
> 
> v2:
> * Change the order of patch.
> 
> Xuan Ding (2):
>    vhost: fix field naming in guest page struct
>    vhost: fix physical address mapping
> 
>   lib/vhost/vhost.h      |  11 ++--
>   lib/vhost/vhost_user.c | 133 ++++++++++++++++++++---------------------
>   lib/vhost/virtio_net.c |  11 ++--
>   3 files changed, 76 insertions(+), 79 deletions(-)
> 

Applied to dpdk-next-virtio/main.

Thanks,
Maxime


      parent reply	other threads:[~2022-02-17  8:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 16:11 [PATCH 0/2] vhost: fix physical " xuan.ding
2022-01-14 16:11 ` [PATCH 1/2] " xuan.ding
2022-01-14 16:12 ` [PATCH 2/2] vhost: rename field in guest page struct xuan.ding
2022-02-16  2:28 ` [PATCH v4 0/2] vhost: fix async address mapping xuan.ding
2022-02-16  2:28   ` [PATCH v4 1/2] vhost: fix field naming in guest page struct xuan.ding
2022-02-16  2:28   ` [PATCH v4 2/2] vhost: fix physical address mapping xuan.ding
2022-02-17  8:54   ` Maxime Coquelin [this message]

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=35d535be-88fb-a8f4-93cf-f98e75a19dc4@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jiayu.hu@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=xuan.ding@intel.com \
    --cc=yuanx.wang@intel.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).