Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1870082imm; Sat, 2 Jun 2018 10:58:30 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLxFjQ9Abo4hMgkOOXrid6pIiE82Q09YBwoxwSCqVthvBEdB3pFfFnMnyhDKzfE8OtjopzQ X-Received: by 2002:a63:7d51:: with SMTP id m17-v6mr12381657pgn.245.1527962310817; Sat, 02 Jun 2018 10:58:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527962310; cv=none; d=google.com; s=arc-20160816; b=UamigUtjTC7denuMGcGJeB3SCF7dEcdL4FnL9DHiIwdpx6kSd8vbfPrI/nFhkDF6Cq CK2H/AW1UVMjKYgj01psxGjhFQ7ExvDESKeVXTDVwuqRZyRO/QbffWjy04mNaFO/GwA3 CubcoUEZ2azV+n74DmxLvNLQih5kO4FrcOlBHaiaR4CYnc0HbWIkt+U5vSVUShIOK0YW mWppzY6jhR4ICnSBV2G45tj9ZVbrvnGF3YOOJ21EtS2qoHs0PsCOAxyfHavUGAdLSTSg rm27mIt8fAIVgyfAp+XtL7uPPAsvEbtVUMe0FYiEKfAZY595+RsRxrKxy7b0F6PKyz8D dYYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=jZTskaEUHGn9OCs/t3yHTu197GoF5R5yvb+UFopZnO4=; b=mzBXOr/WHVxVrhBR0rF47gsoo8VLTvdAs4WLduaBARmBGaVWNrnXinPNc4TPQ3hOWc 7sAA5q1+jRA8DLmGbff/6cAL7cbYN0eOFPf8NjgR/GHUW/S6wAb0/n2e5MpblAZzLlQ8 s6viHAP05qgCCerDpGrHfzKnarWB9rC+mYCWKppK/T7PVbqylnV2/QOhPA6g9jzPV6CE 75qGrpEKB9Bh9jYY7nuKMT57KMiiVVucpcVndW9uRsqaYzPIHKZsq2oEKefwntAPQ/t8 X01dHPK66hCHVQUKr9poL/5UJ0rEBcKWFwJ+CHIxGb/dGVTwyJDnnr6Mzx2mlE6DZHhk HxeQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=HRVslMRq; dkim=pass header.i=@codeaurora.org header.s=default header.b=Dj9bMWG+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q10-v6si13123502pfh.17.2018.06.02.10.58.15; Sat, 02 Jun 2018 10:58:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=HRVslMRq; dkim=pass header.i=@codeaurora.org header.s=default header.b=Dj9bMWG+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751932AbeFBR5Y (ORCPT + 99 others); Sat, 2 Jun 2018 13:57:24 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:33848 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751808AbeFBR5V (ORCPT ); Sat, 2 Jun 2018 13:57:21 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id CAFCC607E8; Sat, 2 Jun 2018 17:57:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1527962240; bh=sDtINSpVHeZryBvZ+qAUCSGu55pYJlMM9rCZLho4iS0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=HRVslMRqJH09wuCQL3Na9j8KKokpcrnbCnanbFsBpU+U6zeNNnUo2QuMGG8VBupce s+Fj3ry32ondy+riayfJHPNZ295XkHbdjmldd2HSelRky4BTw5E6keENmvOvZiHrFM LZtCST2bIarbnPoq4mUhP7GL4EdlTLtTEjng5WzA= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 565EF60249; Sat, 2 Jun 2018 17:57:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1527962239; bh=sDtINSpVHeZryBvZ+qAUCSGu55pYJlMM9rCZLho4iS0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Dj9bMWG+avv8cMoPZHcthWYfqlh9f2vWGqzh4nMm9fURgQH54suD6iVFVu46B/2Cb +M+ftljfizdr/sZgW93l9i1Xb/ycp38EKLMk0Vqlf/208SW9vGEP6aT5MRd+DpMre4 Lz7hugPDBNKLl1jZKFYX8xTdZQrtoYVz7vXxrUdk= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 02 Jun 2018 13:57:19 -0400 From: okaya@codeaurora.org To: Pavel Machek Cc: Greg Kroah-Hartman , linux-pci@vger.kernel.org, timur@codeaurora.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Jonathan Corbet , Bjorn Helgaas , Thomas Gleixner , Ingo Molnar , Christoffer Dall , "Paul E. McKenney" , Marc Zyngier , Kai-Heng Feng , Thymo van Beers , Frederic Weisbecker , Konrad Rzeszutek Wilk , David Rientjes , "Rafael J. Wysocki" , Keith Busch , Dongdong Liu , Frederick Lawler , Oza Pawandeep , Gabriele Paoloni , "open list:DOCUMENTATION" , open list Subject: Re: [PATCH] PCI: Add pci=safemode option In-Reply-To: <20180602174307.GB14870@amd> References: <1527650389-31575-1-git-send-email-okaya@codeaurora.org> <20180530043103.GA19734@kroah.com> <6c317ed8-cca3-8862-5f3b-12cf14e4d53b@codeaurora.org> <20180602174307.GB14870@amd> Message-ID: X-Sender: okaya@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-06-02 13:43, Pavel Machek wrote: > Hi! > >> > And you should explain what exactly in PCI is "optional". Who defines >> > this and where is that list and what can go wrong if those options are >> > not enabled? >> >> Bjorn and I discussed the need for such a "safe" mode feature when you >> want to bring up PCI for a platform. You want to turn off everything >> as >> a starter and just stick to bare minimum. >> >> I can add a few words describing them. The goal of this option is to >> keep >> base PCI features with MSI only. Things like PME, AER, ASPM, Extended >> Tags, LTR, Relaxed Ordering, SRIOV are all considered optional. >> safemode >> is certainly not intended for production environments. >> >> I can taint the kernel as a suggestion. > > I don't think tainting is required. even modern platforms should work > in the safe mode. Yeah, concern was getting used to the safe mode and never running the full stack to fix the actual issues like getting away with crappy hardware and firmware. It becomes a support issue for the community. > Pavel