From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 79BB0C54E60 for ; Tue, 19 Mar 2024 06:09:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=iCxZIFatrY4dWK6MKKS+UcUgXhOpxoY7DllU+4xDVYA=; b=r/hjCTqREYgtao YFFpFDGjNOMTA29ehS1rzBIuC3qaTSsTw10bBQN1A3W7ydacIeIju467RxbH4ODF7wYUkBiH7HR4K lbl/GdiYjutpB+a7MCg8IPCRPwfM722NOZOLFNCaVEaDTVDks4/kyg/6ZDM/CIfX7wuac4uxQEAj3 9rAeOqV5/PEJCDBLWAWpLE7TdE56DXtJZYAkg1g4nGc7MN9dcPewDNmmodzyaLBD24MSv4EDyPBWj Ali4j3lDfpPBWOT0biL6WeY7HJxY3GsPrGr60nB+6p4pKaOJOgEUF1nw3BlgmRK82WfJPLxGh+sdK imH7QIvLYlzN15YDBLQw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rmSfT-0000000BS4v-3Q9y; Tue, 19 Mar 2024 06:09:48 +0000 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rmSfP-0000000BS3d-2Pgz for linux-arm-kernel@lists.infradead.org; Tue, 19 Mar 2024 06:09:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1710828580; 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: in-reply-to:in-reply-to:references:references; bh=4gAjOoqwe4WiMjHGtvLfdIjhk3lra6uGlC6+BOty9fk=; b=RlwkvVYdGg6Zrakx1YlWLNyo9Om/CIrmcnnZBF2htB7jkCAJBhnTI+aVtU+3tQaqvOnSZy CQeMhm2z+lcAHZfsDqh7R2iw6G3/r0f5FQxLMRlYiUtRe4Zy6l5CwBRxz8CEY3Vj673KDW LIDigfrGWDZsShx8znNDbHrM6SV3jc4= Received: from mail-ej1-f70.google.com (mail-ej1-f70.google.com [209.85.218.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-261-8pnfEef1Pgeux9uDETgMaw-1; Tue, 19 Mar 2024 02:09:36 -0400 X-MC-Unique: 8pnfEef1Pgeux9uDETgMaw-1 Received: by mail-ej1-f70.google.com with SMTP id a640c23a62f3a-a46bae02169so177576766b.1 for ; Mon, 18 Mar 2024 23:09:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710828575; x=1711433375; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=4gAjOoqwe4WiMjHGtvLfdIjhk3lra6uGlC6+BOty9fk=; b=pTzR/QqY32qvDLvnvUvWqzTIoHv59ki7GLeIicSvtjeNCfQFDpunqTuQSRnm38xKVt 4w5UpYv1xy38SLZgaN/hh9MHN6PFnDI/dxhoUzjIO4ocpZn6Qfku3IhkCnYRNcj9nuBc 4V6+k053Jv4tD3hcJPWWaqYoBaYdLI44QpkjwpJ/4k/ei5eRthRFBX85iJHLbEUcX56W DHQ5M7pjz2mDcTNGoXiqAtWVG09ZcEAokVTrRRfVxO93fH4r0P8ykIjFxW+0JQ5yXxKp 4DIxiwvELgUgDyYBkQlHnDmQ5pxp2CnlvNkDadMCF32tQRuB2QXO1IxkUR92shbKzCTN egyA== X-Forwarded-Encrypted: i=1; AJvYcCX6goYbXrl5mImd9N8658sCZaL6m4k+UN41JyW7YXYtK/tnIDdMcXTQxKZtzbx/zXsLGvxqFeuzLZfHQUksvJZ0MJPHQ62uC3qaHL/kuFlIx2N6p4A= X-Gm-Message-State: AOJu0YyI44EnzpepGVcZPxQxr0VdlJV4AZbGDkworLDjdwJGHM+9800/ VDDMlLh+tZIjE6XOgf81JYDziIij/ZqKg0j6B6gpz9cCDweEO9PDuY5DJIfIB7FJcG7YXZTkhk2 uBZvJirVevIcyWWtH2ve7x/Gs0no4OId3JyN1/ywMKGwOJD8XQqWs0NlvDpmxelvtl79bSpln X-Received: by 2002:a17:906:124b:b0:a46:ba8f:bcdc with SMTP id u11-20020a170906124b00b00a46ba8fbcdcmr1669815eja.8.1710828574813; Mon, 18 Mar 2024 23:09:34 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGw2+yzvjo1VeEiJREnOUKPOQ5D+EoiV8KYmOyYmQdeAA6iIav3ruMjKj36kIfnfcmj2dr5aA== X-Received: by 2002:a17:906:124b:b0:a46:ba8f:bcdc with SMTP id u11-20020a170906124b00b00a46ba8fbcdcmr1669795eja.8.1710828574200; Mon, 18 Mar 2024 23:09:34 -0700 (PDT) Received: from redhat.com ([2a02:14f:175:ca2b:adb0:2501:10a9:c4b2]) by smtp.gmail.com with ESMTPSA id d10-20020a1709067f0a00b00a413d1eda4bsm5647087ejr.87.2024.03.18.23.09.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 Mar 2024 23:09:33 -0700 (PDT) Date: Tue, 19 Mar 2024 02:09:28 -0400 From: "Michael S. Tsirkin" To: Gavin Shan Cc: Will Deacon , virtualization@lists.linux.dev, linux-kernel@vger.kernel.org, jasowang@redhat.com, xuanzhuo@linux.alibaba.com, yihyu@redhat.com, shan.gavin@gmail.com, linux-arm-kernel@lists.infradead.org, Catalin Marinas , mochs@nvidia.com Subject: Re: [PATCH] virtio_ring: Fix the stale index in available ring Message-ID: <20240319020905-mutt-send-email-mst@kernel.org> References: <20240314074923.426688-1-gshan@redhat.com> <20240318165924.GA1824@willie-the-truck> <35a6bcef-27cf-4626-a41d-9ec0a338fe28@redhat.com> MIME-Version: 1.0 In-Reply-To: <35a6bcef-27cf-4626-a41d-9ec0a338fe28@redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240318_230943_754594_1F0D5019 X-CRM114-Status: GOOD ( 43.29 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Mar 19, 2024 at 02:59:23PM +1000, Gavin Shan wrote: > On 3/19/24 02:59, Will Deacon wrote: > > On Thu, Mar 14, 2024 at 05:49:23PM +1000, Gavin Shan wrote: > > > The issue is reported by Yihuang Yu who have 'netperf' test on > > > NVidia's grace-grace and grace-hopper machines. The 'netperf' > > > client is started in the VM hosted by grace-hopper machine, > > > while the 'netperf' server is running on grace-grace machine. > > > > > > The VM is started with virtio-net and vhost has been enabled. > > > We observe a error message spew from VM and then soft-lockup > > > report. The error message indicates the data associated with > > > the descriptor (index: 135) has been released, and the queue > > > is marked as broken. It eventually leads to the endless effort > > > to fetch free buffer (skb) in drivers/net/virtio_net.c::start_xmit() > > > and soft-lockup. The stale index 135 is fetched from the available > > > ring and published to the used ring by vhost, meaning we have > > > disordred write to the available ring element and available index. > > > > > > /home/gavin/sandbox/qemu.main/build/qemu-system-aarch64 \ > > > -accel kvm -machine virt,gic-version=host \ > > > : \ > > > -netdev tap,id=vnet0,vhost=on \ > > > -device virtio-net-pci,bus=pcie.8,netdev=vnet0,mac=52:54:00:f1:26:b0 \ > > > > > > [ 19.993158] virtio_net virtio1: output.0:id 135 is not a head! > > > > > > Fix the issue by replacing virtio_wmb(vq->weak_barriers) with stronger > > > virtio_mb(false), equivalent to replaced 'dmb' by 'dsb' instruction on > > > ARM64. It should work for other architectures, but performance loss is > > > expected. > > > > > > Cc: stable@vger.kernel.org > > > Reported-by: Yihuang Yu > > > Signed-off-by: Gavin Shan > > > --- > > > drivers/virtio/virtio_ring.c | 12 +++++++++--- > > > 1 file changed, 9 insertions(+), 3 deletions(-) > > > > > > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c > > > index 49299b1f9ec7..7d852811c912 100644 > > > --- a/drivers/virtio/virtio_ring.c > > > +++ b/drivers/virtio/virtio_ring.c > > > @@ -687,9 +687,15 @@ static inline int virtqueue_add_split(struct virtqueue *_vq, > > > avail = vq->split.avail_idx_shadow & (vq->split.vring.num - 1); > > > vq->split.vring.avail->ring[avail] = cpu_to_virtio16(_vq->vdev, head); > > > - /* Descriptors and available array need to be set before we expose the > > > - * new available array entries. */ > > > - virtio_wmb(vq->weak_barriers); > > > + /* > > > + * Descriptors and available array need to be set before we expose > > > + * the new available array entries. virtio_wmb() should be enough > > > + * to ensuere the order theoretically. However, a stronger barrier > > > + * is needed by ARM64. Otherwise, the stale data can be observed > > > + * by the host (vhost). A stronger barrier should work for other > > > + * architectures, but performance loss is expected. > > > + */ > > > + virtio_mb(false); > > > vq->split.avail_idx_shadow++; > > > vq->split.vring.avail->idx = cpu_to_virtio16(_vq->vdev, > > > vq->split.avail_idx_shadow); > > > > Replacing a DMB with a DSB is _very_ unlikely to be the correct solution > > here, especially when ordering accesses to coherent memory. > > > > In practice, either the larger timing different from the DSB or the fact > > that you're going from a Store->Store barrier to a full barrier is what > > makes things "work" for you. Have you tried, for example, a DMB SY > > (e.g. via __smb_mb()). > > > > We definitely shouldn't take changes like this without a proper > > explanation of what is going on. > > > > Thanks for your comments, Will. > > Yes, DMB should work for us. However, it seems this instruction has issues on > NVidia's grace-hopper. It's hard for me to understand how DMB and DSB works > from hardware level. I agree it's not the solution to replace DMB with DSB > before we fully understand the root cause. > > I tried the possible replacement like below. __smp_mb() can avoid the issue like > __mb() does. __ndelay(10) can avoid the issue, but __ndelay(9) doesn't. > > static inline int virtqueue_add_split(struct virtqueue *_vq, ...) > { > : > /* Put entry in available array (but don't update avail->idx until they > * do sync). */ > avail = vq->split.avail_idx_shadow & (vq->split.vring.num - 1); > vq->split.vring.avail->ring[avail] = cpu_to_virtio16(_vq->vdev, head); > > /* Descriptors and available array need to be set before we expose the > * new available array entries. */ > // Broken: virtio_wmb(vq->weak_barriers); > // Broken: __dma_mb(); > // Work: __mb(); > // Work: __smp_mb(); > // Work: __ndelay(100); > // Work: __ndelay(10); > // Broken: __ndelay(9); > > vq->split.avail_idx_shadow++; > vq->split.vring.avail->idx = cpu_to_virtio16(_vq->vdev, > vq->split.avail_idx_shadow); What if you stick __ndelay here? > vq->num_added++; > > pr_debug("Added buffer head %i to %p\n", head, vq); > END_USE(vq); > : > } > > I also tried to measure the consumed time for various barrier-relative instructions using > ktime_get_ns() which should have consumed most of the time. __smb_mb() is slower than > __smp_wmb() but faster than __mb() > > Instruction Range of used time in ns > ---------------------------------------------- > __smp_wmb() [32 1128032] > __smp_mb() [32 1160096] > __mb() [32 1162496] > > Thanks, > Gavin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel