Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp761206ybi; Thu, 30 May 2019 06:23:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqwSj8uCwhTgghuq6gVjZTgx4AJ5Gc3I4BM3ED0nZSEzdCFEMY7e+ZlB9F1Z0bx0v+STA8Ya X-Received: by 2002:a17:90a:1b4f:: with SMTP id q73mr3481461pjq.75.1559222609636; Thu, 30 May 2019 06:23:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559222609; cv=none; d=google.com; s=arc-20160816; b=fvwlostuSOUBmxD6HnxG4T6z10UfpVNCZpKZgPQqctQybGWKy6YdPRwvwVsdgOgpdH FdXmKJBktt4n20zM79QJfYps7He40uGeqx1ZLYePX4YwFlImPSuM9f0ZwR4DEsfYGxYM 1p+4dvt98zByPBaZgmUH8bb1wIz5Hvf2YwF/pP2JVcipQbkL/pR1PdtN2FOmQ3ZwMP4C ZBABZhRELIyzYtQG8uLxDdDk/NhmLVipxKwAQxmrEDLilcx5dTnbYBIeKdYSN86Pu6yJ eVpjePywcYKhByBdpXPqv0qjk3PZ6fjRtYLEjrF3V0AUAsvTGyLFF2f9GuKTaDjRjigh 2lUQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=ALwO3Lj214j0KF2V1L1NJ0QXibCmMOJG4w5jvfdZj3I=; b=XuNoSbYVRwIOgJ2811blyeUcZ7Ow5EdByOfWmrs8f/XLBz8u+T0kghRLZif8Qj+Bd8 +DiEE3FX8xcov8XouKPhCVmy8DdRq7+87CMePyoyjB9E5PZbmdDz3ZX+S7VH3dr8TnRY 609vYmqebR/XS+iP35gcvSwUk3N4oLsFq/8YMhWDhPvymkN+YUOx68pQOZCh7xvaCu1h 5mNoM19PnfQRjERH8v6MvpRaxRavLlU/5WH9fBZKsgT6cRpwzM/+zuhhJ1oLwlySrMjW kLrAutY9R5MowqHW/QlQPAFTlzYoi7qefP0rZ3KLqDzi/bA8LvImJBQ+0Ex31jOATeCr xkYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=jv6lKTJp; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n36si2863805pjb.17.2019.05.30.06.23.10; Thu, 30 May 2019 06:23:29 -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=@kernel.org header.s=default header.b=jv6lKTJp; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726899AbfE3NUW (ORCPT + 99 others); Thu, 30 May 2019 09:20:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:44032 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726253AbfE3NUR (ORCPT ); Thu, 30 May 2019 09:20:17 -0400 Received: from localhost (173-25-83-245.client.mchsi.com [173.25.83.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 295362596C; Thu, 30 May 2019 13:20:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559222416; bh=WWUvePG/F5W9jMrKSPbf0krNclZJzDEIlb3GAxBTdPw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jv6lKTJpSAmsvbT9Oc+pbk9Pt+iz2dQ6CvIDOQrDijLggnudc1qnTgggJ8e2jc6Mo wrtl8xLxSaK9pbN0w/QXHk779vZzPu+F9/YAjdKVH5/wOZraWPKeQIFjwCBEBggF1X NrnY+sX+UwXZbkACNs8yTw5tRfrF2r1BC0jdczJc= Date: Thu, 30 May 2019 08:20:15 -0500 From: Bjorn Helgaas To: sathyanarayanan kuppuswamy Cc: "Raj, Ashok" , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, keith.busch@intel.com Subject: Re: [PATCH v2 1/5] PCI/ATS: Add PRI support for PCIe VF devices Message-ID: <20190530132015.GL28250@google.com> References: <20190529225714.GE28250@google.com> <20190529230426.GB5108@araj-mobl1.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 29, 2019 at 04:24:05PM -0700, sathyanarayanan kuppuswamy wrote: > But, regarding VF spec compliance checks, Is there any issue in having them > in enable code ? Perhaps I can change dev_err to dev_warn and not return > error if it found implementation errors. I found it useful to have them > because it helped me in finding some faulty devices during my testing. Let > me know your comments. If you need quirks to make these non-compliant devices usable, we should check for compliance. If not, my personal opinion is that we shouldn't touch things we don't need. Bjorn