Received: by 2002:a05:7412:419a:b0:f3:1519:9f41 with SMTP id i26csp4466021rdh; Wed, 29 Nov 2023 02:12:47 -0800 (PST) X-Google-Smtp-Source: AGHT+IFvZLmij4+BdaqhQHZheaUJ/zzJBXreoGbYtHM7OutMWzCXNA+KJ0WHmzYoERYQgoS/pHkS X-Received: by 2002:a05:6a00:1d88:b0:6c9:88ee:1d87 with SMTP id z8-20020a056a001d8800b006c988ee1d87mr29606312pfw.17.1701252766818; Wed, 29 Nov 2023 02:12:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701252766; cv=none; d=google.com; s=arc-20160816; b=DZf+19ATqTIFAeDOohgK76gW2GHIj1QJZUgS/xx/aBITVNtdL0J2ui7IJi/S4QLLnC FZSNO0D94PqQ2KebMDWdwPbB4ztrGtgAi7G7/WK+FCOMZ2/UIRl3pmD6x5dgxOsA1Ict X/4RCxRX5a3XbM3OPXsOLtwTjUq/9tbqVWQMMnoMONlJriOO5fLDh0tEMng8P53PBNkR ycOwoGmvr5VzxcdMJK1eGfXgc/DQ0ZHHHFqj5IFyiZnc10mlQuC33I3CDTdIz6ANVBxW /QaJlSOF+swjUQeVrkYHRqUpvCUQo++mcYpZ9Z7CLNgz8BKqDI72iFAkq51Rf/51AeC7 Zj2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=j2neceFZZHPGwxGk/eOuduL5XSDtw2pWzZS4sJ1UEVQ=; fh=hlra+5HwQe0uhZnTDvhg1j+X19+vh/U3MS1MiE+pkEY=; b=VBa7LtTimJPIWwWHibhOh0sic0aIUX7x8J5i7mu9+ZIglnU4jSZYUQQq7tMrHWeI6h VqS/dmkJvzvYODOz8hgIMgNd2cTsc+m1QRYmAg70dWFnSVkXqX04J6Xf0uv+P0M1f+wm FIa4aVzC/IdHKsidLEywOe8hxdy6EIqNSGwNFBsQB2+LGOAzZBQVQaELjk2KgjXo5cnS Jc7lvL1zBm9PNTrHg4rhdEbgKcBdtqjpcwEvXkXOSl7fp/cSf7hmHqE/jpzzSIYL8dAo KDtEQ+pG3AzI23tt4IsYrt53PtTlTl/U1dk/IHm4NdnZGkXcSHjsJcEO8mhQJwOni9YL cAHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=PivL9517; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from groat.vger.email (groat.vger.email. [2620:137:e000::3:5]) by mx.google.com with ESMTPS id r9-20020a63fc49000000b005be209ac7fesi13812337pgk.744.2023.11.29.02.12.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Nov 2023 02:12:46 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=PivL9517; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id 1F1CB8098639; Wed, 29 Nov 2023 02:12:44 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229656AbjK2KM0 (ORCPT + 99 others); Wed, 29 Nov 2023 05:12:26 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60330 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229488AbjK2KMZ (ORCPT ); Wed, 29 Nov 2023 05:12:25 -0500 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EC3981AD; Wed, 29 Nov 2023 02:12:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1701252752; x=1732788752; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=T/nE2PLN0CkqTzjNu7omvvMU4nDr0lpxOaDVDfchUJ4=; b=PivL9517X6vLt2ioRxCA3WMCQq6ZkuxOpoYuve1Hkkoq0hwxZKUVScbU +lFZhFon4EldryJVEfKQO1pMLsxdq18VfeZcUvNxAFEKG9Q4kj/1NLYrY GxUoW7cPteVpVtqiY0+EYK0oV4nS9WPZMuN+uBeLsGks+MVvgxp0Sl2FQ 6tisoUUpP4btNkksqZnCaBTMRri/DZ3SFty53vI27HQPa2OyUwnLKOkMW G0hpoWhz171QU7tOpdXcF9geoRfLyRhytIL9WWXKLpT2KCO6KaxCdng9V 5zcKJsyhk8YRAYx56dYKllQqoKEdbrsw6Lf5HqvUWJAq4SV5ifuk80Xi0 A==; X-IronPort-AV: E=McAfee;i="6600,9927,10908"; a="397037842" X-IronPort-AV: E=Sophos;i="6.04,235,1695711600"; d="scan'208";a="397037842" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Nov 2023 02:12:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10908"; a="886798488" X-IronPort-AV: E=Sophos;i="6.04,235,1695711600"; d="scan'208";a="886798488" Received: from hongyuni-mobl.ccr.corp.intel.com (HELO [10.238.2.21]) ([10.238.2.21]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Nov 2023 02:12:27 -0800 Message-ID: <6f84bbad-62f9-43df-8134-a6836cc3b66c@linux.intel.com> Date: Wed, 29 Nov 2023 18:12:25 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [GIT PULL] virtio: features Content-Language: en-US To: Jason Wang Cc: "Michael S. Tsirkin" , xuanzhuo@linux.alibaba.com, Linus Torvalds , 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 References: <20230903181338-mutt-send-email-mst@kernel.org> <647701d8-c99b-4ca8-9817-137eaefda237@linux.intel.com> From: "Ning, Hongyu" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Wed, 29 Nov 2023 02:12:44 -0800 (PST) On 2023/11/29 17:16, Jason Wang wrote: > On Wed, Nov 29, 2023 at 5:05 PM Ning, Hongyu > 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 >>> >>> ---------------------------------------------------------------- >>> 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(-) >>> >> >