Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1408230pxb; Thu, 28 Jan 2021 16:11:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJx/32bQTMdhlysErQQL7vurLFmecMVb0ytd8IsBgAQkoM279Z0RJu0uijnu8deERj0UzthP X-Received: by 2002:a50:ec05:: with SMTP id g5mr2360530edr.182.1611879083398; Thu, 28 Jan 2021 16:11:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611879083; cv=none; d=google.com; s=arc-20160816; b=JtmDZnPpg7jU4rcUVXqU8zEbgfudo2dviB0SAVtJ3IamrlH2BwgygJV1pYbG0Vu3Vm WDwFP1aYdRBhJsG1Vu0sY42j/KIpT7P95QnuYg/xN1KrjeGUyewRqsH9cjaLj/72GlBS gS5V7eWUU78+Ifpn3PaDZuHiH5Djab7FedggwyhESYYnr3KHNkpZtyDf8euuR6G3Cuif Arn1B8zwLDaoy3d0Gu4BsVqOIHGeQr6JCY1amht2qEdS+YTYopFZkFSu7+05Fd2nokKu V55KHEgNZavyY4U3iHmyXDOafvGmQVtceQOIJXwOwpSBKbgEjXpbONIFmS3O3BFSI2Ox iHpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=5ILX5b+RrV4AiVEpHFwN5sXUa5ubqo8Aj21NjAeDVw8=; b=jPteBEeHYSfRGhMNWGwBV2U5AW/vLO88fmKGNTbG3yF4nbkoc4lievokLglZxafJ6z Wov4G4+IH6YMojTaH7tEwwZ8YyEj7S5aomXmQcYoWDYODKGabZarlHwzyY/6rs0VYyDL cXj16eczjAuPBTDNc+MtqR6AFp8PSp5ehGkT8NfLMfShttXY0UZHkDIyCer7qfOlzUkC sIow8m5kx2Fej9Dc/WSE/BkLIBXtjvE3YrglKnGwjvnPx7KnKjfHMN+pMzpWIvr7tZ52 HRC/Vop0h8zj+GQ/b4kjDZmZBW9u8B9UCtFEHAzNDQFwV4f3yJQ4ZhYJjtRryLo9+Nlj UU5Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=V4GAHau9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w12si3991429edr.414.2021.01.28.16.10.51; Thu, 28 Jan 2021 16:11:23 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=V4GAHau9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229854AbhA2AIX (ORCPT + 99 others); Thu, 28 Jan 2021 19:08:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54378 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229757AbhA2AIT (ORCPT ); Thu, 28 Jan 2021 19:08:19 -0500 Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A09C8C061573; Thu, 28 Jan 2021 16:07:39 -0800 (PST) Received: by mail-ot1-x32e.google.com with SMTP id v1so7014862ott.10; Thu, 28 Jan 2021 16:07:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=5ILX5b+RrV4AiVEpHFwN5sXUa5ubqo8Aj21NjAeDVw8=; b=V4GAHau9okbpK6XGG3KiHomAbwbMBxMKryjJwX9TnkZnDtcA6LrdLM2sC/t2zLQPxJ GZzp9qLpHojfqJna7Zdce17l9auN+5WwynFxLmsi/nmB+t3BcaV3lPfeSfK04nmPNOOi VoS7kz9jADhp+43HxTn/9ySNbyFQcrS3viKPcbadbztu1a0u6w/LnOMc03JGVeIFNv9Z niHbtFJs/7nLv4C6YXrOSkS/Z1DlPKIepKi6QR6gXcsVpEUwNUF33tbLLsgE2feZlJYQ sPA3JUos47pVUQ4+kH2zsJCkSqKxbQ+qrlyjiKsHnGJiTufDwASeoiqY0o1eoUdt/NA4 90YQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=5ILX5b+RrV4AiVEpHFwN5sXUa5ubqo8Aj21NjAeDVw8=; b=roi+r+sqyLfUN34qKyWXmrWlQesXl80q+Rn8eLJSG3FDaMwdhHp3Qo3PfEg4jPZ3Bq 1mXCDtwhsp2+k+R2bXl9MLpvi+pISa8MG93vEzSTjfaY/WdgpcJQzyPZHevauvB5U5XY NS7aQmthgm83/r0xZiLIo07gfNr+KRBCZSOSaMiO9BtNMtRMR9KKCfmc/hanWrhOZ56T 6UvH7O1tC0g/ow4LMIscd+AjHWDKIARz5B68UY0aYFmpjTSAxQzdabEkoPOOxdsxgBMG ajkv9xd+V8WUp8uS5P2yZh/ehgp3HGauZrm1cpOLi6+VNo8/XlA81yXkd6gtAtHpbTDN 6PWw== X-Gm-Message-State: AOAM530TRiwnH9G/xDSsxs/3aGI0yJB81MQDjz0BNfgt+MIdyc3aZWMI uylzcLJb9bGPsaCahFKthPE= X-Received: by 2002:a9d:4c9a:: with SMTP id m26mr1261144otf.7.1611878859004; Thu, 28 Jan 2021 16:07:39 -0800 (PST) Received: from nuclearis2-1.gtech (c-98-195-139-126.hsd1.tx.comcast.net. [98.195.139.126]) by smtp.gmail.com with ESMTPSA id r1sm1610314ooq.16.2021.01.28.16.07.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Jan 2021 16:07:38 -0800 (PST) Subject: Re: Issues with "PCI/LINK: Report degraded links via link bandwidth notification" To: Sinan Kaya , Bjorn Helgaas , Alexandru Gagniuc , Keith Busch Cc: Jan Vesely , Lukas Wunner , Alex Williamson , Austin Bolen , Shyam Iyer , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Christoph Hellwig , Lucas Stach , Dave Airlie , Ben Skeggs , Alex Deucher , Myron Stowe , "A. Vladimirov" References: <20210128233929.GA39660@bjorn-Precision-5520> <6bfe3128-4f4d-6447-ab91-1bc54a02e16f@kernel.org> From: "Alex G." Message-ID: Date: Thu, 28 Jan 2021 18:07:36 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <6bfe3128-4f4d-6447-ab91-1bc54a02e16f@kernel.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/28/21 5:51 PM, Sinan Kaya wrote: > On 1/28/2021 6:39 PM, Bjorn Helgaas wrote: >> AFAICT, this thread petered out with no resolution. >> >> If the bandwidth change notifications are important to somebody, >> please speak up, preferably with a patch that makes the notifications >> disabled by default and adds a parameter to enable them (or some other >> strategy that makes sense). >> >> I think these are potentially useful, so I don't really want to just >> revert them, but if nobody thinks these are important enough to fix, >> that's a possibility. > > Hide behind debug or expert option by default? or even mark it as BROKEN > until someone fixes it? > Instead of making it a config option, wouldn't it be better as a kernel parameter? People encountering this seem quite competent in passing kernel arguments, so having a "pcie_bw_notification=off" would solve their problems. As far as marking this as broken, I've seen no conclusive evidence of to tell if its a sw bug or actual hardware problem. Could we have a sysfs to disable this on a per-downstream-port basis? e.g. echo 0 > /sys/bus/pci/devices/0000:00:04.0/bw_notification_enabled This probably won't be ideal if there are many devices downtraining their links ad-hoc. At worst we'd have a way to silence those messages if we do encounter such devices. Alex