From: "Ning, Hongyu" <hongyu.ning@linux.intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
xuanzhuo@linux.alibaba.com,
Linus Torvalds <torvalds@linux-foundation.org>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
eperezma@redhat.com, shannon.nelson@amd.com,
yuanyaogoog@chromium.org, yuehaibing@huawei.com,
kirill.shutemov@linux.intel.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
alexander.shishkin@linux.intel.com
Subject: Re: [GIT PULL] virtio: features
Date: Wed, 29 Nov 2023 18:12:25 +0800 [thread overview]
Message-ID: <6f84bbad-62f9-43df-8134-a6836cc3b66c@linux.intel.com> (raw)
In-Reply-To: <CACGkMEvoGOO0jtq5T7arAjRoB_0_fHB2+hPJe1JsPqcAuvr98w@mail.gmail.com>
On 2023/11/29 17:16, Jason Wang wrote:
> On Wed, Nov 29, 2023 at 5:05 PM Ning, Hongyu
> <hongyu.ning@linux.intel.com> wrote:
>>
>>
>>
>> On 2023/9/4 6:13, Michael S. Tsirkin wrote:
>>> The following changes since commit 2dde18cd1d8fac735875f2e4987f11817cc0bc2c:
>>>
>>> Linux 6.5 (2023-08-27 14:49:51 -0700)
>>>
>>> are available in the Git repository at:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
>>>
>>> for you to fetch changes up to 1acfe2c1225899eab5ab724c91b7e1eb2881b9ab:
>>>
>>> virtio_ring: fix avail_wrap_counter in virtqueue_add_packed (2023-09-03 18:10:24 -0400)
>>>
>>> ----------------------------------------------------------------
>>> virtio: features
>>>
>>> a small pull request this time around, mostly because the
>>> vduse network got postponed to next relase so we can be sure
>>> we got the security store right.
>>>
>>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>>>
>>> ----------------------------------------------------------------
>>> Eugenio Pérez (4):
>>> vdpa: add VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK flag
>>> vdpa: accept VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK backend feature
>>> vdpa: add get_backend_features vdpa operation
>>> vdpa_sim: offer VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK
>>>
>>> Jason Wang (1):
>>> virtio_vdpa: build affinity masks conditionally
>>>
>>> Xuan Zhuo (12):
>>> virtio_ring: check use_dma_api before unmap desc for indirect
>>> virtio_ring: put mapping error check in vring_map_one_sg
>>> virtio_ring: introduce virtqueue_set_dma_premapped()
>>> virtio_ring: support add premapped buf
>>> virtio_ring: introduce virtqueue_dma_dev()
>>> virtio_ring: skip unmap for premapped
>>> virtio_ring: correct the expression of the description of virtqueue_resize()
>>> virtio_ring: separate the logic of reset/enable from virtqueue_resize
>>> virtio_ring: introduce virtqueue_reset()
>>> virtio_ring: introduce dma map api for virtqueue
>>> virtio_ring: introduce dma sync api for virtqueue
>>> virtio_net: merge dma operations when filling mergeable buffers
>>
>> Hi,
>> above patch (upstream commit 295525e29a5b) seems causing a virtnet
>> related Call Trace after WARNING from kernel/dma/debug.c.
>>
>> details (log and test setup) tracked in
>> https://bugzilla.kernel.org/show_bug.cgi?id=218204
>>
>> it's recently noticed in a TDX guest testing since v6.6.0 release cycle
>> and can still be reproduced in latest v6.7.0-rc3.
>>
>> as local bisects results show, above WARNING and Call Trace is linked
>> with this patch, do you mind to take a look?
>
> Looks like virtqueue_dma_sync_single_range_for_cpu() use
> DMA_BIDIRECTIONAL unconditionally.
>
> We should use dir here.
>
> Mind to try?
>
> Thanks
>
sure, but what I see in the code
virtqueue_dma_sync_single_range_for_cpu() is using DMA_FROM_DEVICE,
probably I misunderstood your point?
Please let me know any patch/setting to try here.
>>
>>>
>>> Yuan Yao (1):
>>> virtio_ring: fix avail_wrap_counter in virtqueue_add_packed
>>>
>>> Yue Haibing (1):
>>> vdpa/mlx5: Remove unused function declarations
>>>
>>> drivers/net/virtio_net.c | 230 ++++++++++++++++++---
>>> drivers/vdpa/mlx5/core/mlx5_vdpa.h | 3 -
>>> drivers/vdpa/vdpa_sim/vdpa_sim.c | 8 +
>>> drivers/vhost/vdpa.c | 15 +-
>>> drivers/virtio/virtio_ring.c | 412 ++++++++++++++++++++++++++++++++-----
>>> drivers/virtio/virtio_vdpa.c | 17 +-
>>> include/linux/vdpa.h | 4 +
>>> include/linux/virtio.h | 22 ++
>>> include/uapi/linux/vhost_types.h | 4 +
>>> 9 files changed, 625 insertions(+), 90 deletions(-)
>>>
>>
>
next prev parent reply other threads:[~2023-11-29 10:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 22:13 [GIT PULL] virtio: features Michael S. Tsirkin
2023-09-04 18:43 ` pr-tracker-bot
2023-09-26 13:04 ` Michael Roth
2023-09-27 1:47 ` Xuan Zhuo
2023-09-27 5:28 ` Michael Roth
2023-09-27 13:18 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-09-29 11:12 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-29 9:03 ` Ning, Hongyu
2023-11-29 9:16 ` Jason Wang
2023-11-29 10:12 ` Ning, Hongyu [this message]
2023-11-29 10:20 ` Jason Wang
2023-11-29 10:45 ` Ning, Hongyu
2023-11-30 9:44 ` Michael S. Tsirkin
2023-12-01 5:15 ` Jason Wang
2023-11-29 9:47 ` Michael S. Tsirkin
2023-11-29 9:58 ` Ning, Hongyu
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=6f84bbad-62f9-43df-8134-a6836cc3b66c@linux.intel.com \
--to=hongyu.ning@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=shannon.nelson@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yuanyaogoog@chromium.org \
--cc=yuehaibing@huawei.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).