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 X-Spam-Level: X-Spam-Status: No, score=-4.6 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D4222C4727E for ; Wed, 30 Sep 2020 15:08:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 830822076B for ; Wed, 30 Sep 2020 15:08:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1601478492; bh=6QqV+ps2byZU4rC+O9EPuG5NtciAPCEeD4gdtKBD0V8=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=iI3PLrZR0aKP6mnh+NA+MXGDcZ3CiNhKzupvtJVuhXFXFpr2gBGOK9/T7JkujVi5c yVDiGlU+KEaJmrt+zDk/db+cVo3t/x8l9I/g9aKlciH2Dic09Z02oerqD71Rq0qQK4 q3hJ9AShAzwBLNMJ/vu71wLaEezDaxReeM+4ZFjg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728480AbgI3PIL (ORCPT ); Wed, 30 Sep 2020 11:08:11 -0400 Received: from mail.kernel.org ([198.145.29.99]:33320 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725385AbgI3PIL (ORCPT ); Wed, 30 Sep 2020 11:08:11 -0400 Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 17EDB2076B; Wed, 30 Sep 2020 15:08:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1601478491; bh=6QqV+ps2byZU4rC+O9EPuG5NtciAPCEeD4gdtKBD0V8=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=A/ivvxVa7Lw2T1yu1urk7UClaBhy0Oxhld0Oi/R59aBUlQYOSgRnn3e5XkE6gGSKk rg2DyNJrcQeKFp9HT57WyYGU+Uz+BYjh0JVagdB2kBzeg0MiiUi0Q6mkixYcsdOAH9 6YHijAkeVYgXNQFyX75GqYhfsqet0wuli9JzkKIc= Received: by mail-ot1-f51.google.com with SMTP id n61so2121324ota.10; Wed, 30 Sep 2020 08:08:11 -0700 (PDT) X-Gm-Message-State: AOAM530AwIcolv0SkYZdw+3KUKAC0ufHiKUO5NkhkBWQbRZVDqalSmjg z1aUgZe+OSSkW6S0b50pRkcGc+XSKmwnttXknw== X-Google-Smtp-Source: ABdhPJxR8X69n4RLWzWvWtjlNHfj6t2hbM954Jp9nfbLK/knvYLAEl3iGmFm2iq7eVu7IxfjcLQLw9d0+fG5PpGV/sQ= X-Received: by 2002:a9d:6ada:: with SMTP id m26mr1897519otq.192.1601478490346; Wed, 30 Sep 2020 08:08:10 -0700 (PDT) MIME-Version: 1.0 References: <20200929131328.13779-1-Zhiqiang.Hou@nxp.com> <6e6d021b-bc46-63b4-7e84-6ca2c8e631f9@ti.com> In-Reply-To: <6e6d021b-bc46-63b4-7e84-6ca2c8e631f9@ti.com> From: Rob Herring Date: Wed, 30 Sep 2020 10:07:58 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] PCI: layerscape: Change back to the default error response behavior To: Kishon Vijay Abraham I Cc: Zhiqiang Hou , PCI , "linux-kernel@vger.kernel.org" , linux-arm-kernel , Lorenzo Pieralisi , Bjorn Helgaas , Minghuan Lian , Roy Zang , Mingkai Hu , Yang-Leo Li Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Wed, Sep 30, 2020 at 8:29 AM Kishon Vijay Abraham I wrote: > > Hi Hou, > > On 29/09/20 6:43 pm, Zhiqiang Hou wrote: > > From: Hou Zhiqiang > > > > In the current error response behavior, it will send a SLVERR response > > to device's internal AXI slave system interface when the PCIe controller > > experiences an erroneous completion (UR, CA and CT) from an external > > completer for its outbound non-posted request, which will result in > > SError and crash the kernel directly. > > This patch change back it to the default behavior to increase the > > robustness of the kernel. In the default behavior, it always sends an > > OKAY response to the internal AXI slave interface when the controller > > gets these erroneous completions. And the AER driver will report and > > try to recover these errors. > > I don't think not forwarding any error interrupts is a good idea. Interrupts would be fine. Abort/SError is not. I think it is pretty clear what the correct behavior is for config accesses. > Maybe > you could disable it while reading configuration space registers > (vendorID and deviceID) and then enable error forwarding back? To add to the locking (or lack of) problems in config accesses? Rob