From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D6195A0093 for ; Fri, 17 Jun 2022 16:08:18 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CEF2940F19; Fri, 17 Jun 2022 16:08:18 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 8878D40F19 for ; Fri, 17 Jun 2022 16:08:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655474896; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=S4Pf59uuXufXMNqk9OLgAWd4q7Kd7NvrQxYAvXooPI8=; b=RXFm/6Q8ZTCBNW3GlH5D03uLRbmsNrWq+lvuHPZUaw8vRAEywEVbGDr+UDShqBKrB9zQX8 m8OGdrNjNbdUQVOeAnfXYt83HfigshHPHN5+HEP2P0FHVA5bcXuTEFYcW6HM2jpSYMQql+ oPIGlKkSJYLVKYwzEvqr5yqOlyEBgBg= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-258-f9R-tYqeNR68eUYUuOOQ-w-1; Fri, 17 Jun 2022 10:08:14 -0400 X-MC-Unique: f9R-tYqeNR68eUYUuOOQ-w-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 01541963E2E; Fri, 17 Jun 2022 14:07:59 +0000 (UTC) Received: from [10.39.208.34] (unknown [10.39.208.34]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A1FD5C44AF0; Fri, 17 Jun 2022 14:07:57 +0000 (UTC) Message-ID: Date: Fri, 17 Jun 2022 16:07:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH v3] vdpa/mlx5: workaround var offset within page To: Yajun Wu , matan@nvidia.com Cc: dev@dpdk.org, thomas@monjalon.net, rasland@nvidia.com, roniba@nvidia.com, stable@dpdk.org References: <20220314014414.251869-1-yajunw@nvidia.com> <20220615100227.358768-1-yajunw@nvidia.com> From: Maxime Coquelin In-Reply-To: <20220615100227.358768-1-yajunw@nvidia.com> X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org On 6/15/22 12:02, 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 > Acked-by: Matan Azrad > Reviewed-by: Maxime Coquelin > --- > drivers/vdpa/mlx5/mlx5_vdpa.c | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) > Applied to dpdk-next-virtio/main. Thanks, Maxime