From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Yajun Wu <yajunw@nvidia.com>,
orika@nvidia.com, viacheslavo@nvidia.com, matan@nvidia.com,
shahafs@nvidia.com
Cc: dev@dpdk.org, thomas@monjalon.net, rasland@nvidia.com,
roniba@nvidia.com, stable@dpdk.org
Subject: Re: [PATCH v2] vdpa/mlx5: workaround var offset within page
Date: Wed, 1 Jun 2022 11:46:45 +0200 [thread overview]
Message-ID: <f190fa44-2b39-2a2c-3b18-d255a6e38807@redhat.com> (raw)
In-Reply-To: <85d52a01-116f-832e-7e5a-2f5d03cabe51@redhat.com>
On 6/1/22 09:55, Maxime Coquelin wrote:
> Hi Yajun,
>
> On 3/15/22 03:47, Yajun Wu wrote:
>> vDPA driver first uses kernel driver to allocate doorbell(VAR) area for
>> each device. Then uses var->mmap_off and var->length to mmap uverbs
>> device
>> file as doorbell userspace virtual address.
>>
>> Current kernel driver provides var->mmap_off equal to page start of VAR.
>> It's fine with x86 4K page server, because VAR physical address is
>> only 4K
>> aligned thus locate in 4K page start.
>>
>> But with aarch64 64K page server, the actual VAR physical address has
>> offset within page(not locate in 64K page start). So vDPA driver need add
>> this within page offset(caps.doorbell_bar_offset) to get right VAR
>> virtual
>> address.
>>
>> Fixes: 62c813706e4 ("vdpa/mlx5: map doorbell")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Yajun Wu <yajunw@nvidia.com>
>> Acked-by: Matan Azrad <matan@nvidia.com>
>> ---
>> drivers/vdpa/mlx5/mlx5_vdpa_virtq.c | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> Thanks,
> Maxime
>
The patch does not apply, could you please rebase it on top of next-
virtio?
Thanks in advance,
Maxime
next prev parent reply other threads:[~2022-06-01 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 1:44 [PATCH] " Yajun Wu
2022-03-15 2:47 ` [PATCH v2] " Yajun Wu
2022-06-01 7:55 ` Maxime Coquelin
2022-06-01 9:46 ` Maxime Coquelin [this message]
2022-06-14 9:45 ` Maxime Coquelin
2022-06-15 10:02 ` [PATCH v3] " Yajun Wu
2022-06-17 14:07 ` Maxime Coquelin
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=f190fa44-2b39-2a2c-3b18-d255a6e38807@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=roniba@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=yajunw@nvidia.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).