From: "Ding, Xuan" <xuan.ding@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Hu, Jiayu" <jiayu.hu@intel.com>,
"Wang, YuanX" <yuanx.wang@intel.com>,
Kevin Traynor <ktraynor@redhat.com>
Subject: RE: [PATCH v2 0/2] vhost: fix async address mapping
Date: Fri, 11 Feb 2022 02:48:28 +0000 [thread overview]
Message-ID: <BN9PR11MB551302DB634D48A282D95E84E7309@BN9PR11MB5513.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2066fabe-36e2-d18a-cad1-c1c0a02aae71@redhat.com>
Hi Maxime & Kevin,
> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: 2022年2月4日 18:57
> To: Ding, Xuan <xuan.ding@intel.com>; Xia, Chenbo <chenbo.xia@intel.com>
> Cc: dev@dpdk.org; Hu, Jiayu <jiayu.hu@intel.com>; Wang, YuanX
> <yuanx.wang@intel.com>
> Subject: Re: [PATCH v2 0/2] vhost: fix async address mapping
>
>
>
> On 1/19/22 16:10, 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.
> >
> > v2:
> > * Change the order of patch.
The consideration of changing the order here is to avoid the fix patch
using the previous variable name(host_phys_addr), so rename the variable first.
> >
> > Xuan Ding (2):
> > vhost: rename field in guest page struct
> > vhost: fix physical address mapping
> >
> > lib/vhost/vhost.h | 11 ++--
> > lib/vhost/vhost_user.c | 130 ++++++++++++++++++++---------------------
> > lib/vhost/virtio_net.c | 11 ++--
> > 3 files changed, 75 insertions(+), 77 deletions(-)
> >
>
> I was willing to apply the series, but it does not apply.
> Could you please rebase with taking our comments into account?
Thanks for your comments, I will send a new patch set applied with your comments.
Regards,
Xuan
>
> Thanks,
> Maxime
prev parent reply other threads:[~2022-02-11 2:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 15:10 xuan.ding
2022-01-19 15:10 ` [PATCH v2 1/2] vhost: rename field in guest page struct xuan.ding
2022-02-01 8:47 ` Maxime Coquelin
2022-01-19 15:10 ` [PATCH v2 2/2] vhost: fix physical address mapping xuan.ding
2022-02-01 8:51 ` Maxime Coquelin
2022-02-04 10:43 ` Maxime Coquelin
2022-02-01 8:28 ` [PATCH v2 0/2] vhost: fix async " Maxime Coquelin
2022-02-01 11:29 ` Kevin Traynor
2022-02-04 10:43 ` Maxime Coquelin
2022-02-04 10:56 ` Maxime Coquelin
2022-02-11 2:48 ` Ding, Xuan [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=BN9PR11MB551302DB634D48A282D95E84E7309@BN9PR11MB5513.namprd11.prod.outlook.com \
--to=xuan.ding@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.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).