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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 F0E77C43215 for ; Fri, 22 Nov 2019 11:31:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C7E8720674 for ; Fri, 22 Nov 2019 11:31:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="fsH5f2ml" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727442AbfKVLbJ (ORCPT ); Fri, 22 Nov 2019 06:31:09 -0500 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:24776 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726417AbfKVLbJ (ORCPT ); Fri, 22 Nov 2019 06:31:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574422268; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Fk7+9wRBOnitbINGrkgws0BRV6i2F3wIBf4jxMH1Ew8=; b=fsH5f2mlfPAEsZrfN92O2qufAmmWqZPv82uAkQHc7QotC5gTc2NAX96ORApkovgPZSCKxN FV+z2HlPGvixyPFe3lSlM+BRoLvTbh0OC/ACaa6Swo+mHHZ11zvQTGNANRjHfXvf6LBnMn bJFO9CP7TWdvqpgATrYV/U5/m+rZ/zQ= Received: from mail-qv1-f70.google.com (mail-qv1-f70.google.com [209.85.219.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-392-41iS0reXNyqy8iO4S3eOxw-1; Fri, 22 Nov 2019 06:31:04 -0500 Received: by mail-qv1-f70.google.com with SMTP id w2so4460689qvz.10 for ; Fri, 22 Nov 2019 03:31:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Aur9rsWegbHLh3oY6ky2CGYiseXs+N84XUMnQYfdl6g=; b=DNMok9Y9GzptZDn9xOJm/SzHBesJFq7csiYjdbQ4DoTng99FV6r/xc3YaH7mokkQ0o 0zeYxXIvauT7dcDfLUFEveHGldpH9xUZzHRrSxT+wkQq69b82FkU97yIoDPaq1hXtYkG mLgvL2/6gII3sSWPM0jposrTWoWkb620aaVdJnKqUNH9eaen5Hx+r6pG8l126WWqvAmn dFIxufc1gdukJ5RLqiytLAXIJ3qtX4EpKtdkx03kKvex7zptOwBoTmW3BsexLw6/Szvi CchFaKi7QCQ8nhdy3ICMsMe6mWWcmIEiDV/9feSjrdZmrRLmN0PVYhFW72QjZuc3P4uv 6JPQ== X-Gm-Message-State: APjAAAXTlHAIDBiWahNzjW6aB/6QKVdolHVdjMy3LxnjhxswUgygF7fH R5mizs5ewFAXklFxIqFlbdAkoRkc8+X/KhGcsMInZ8P1V/KcYneXGii5dM+BAntUlEmw69ZRW3a Goo4/o1IlqZ0/GVmEOAXIc66Rdvod/NSsr/M= X-Received: by 2002:ac8:5557:: with SMTP id o23mr13894106qtr.378.1574422264296; Fri, 22 Nov 2019 03:31:04 -0800 (PST) X-Google-Smtp-Source: APXvYqz4tUnanEcz7OF5qm09oSIPeTrgesqROQcAYMdb3VQX3IrvgvC0XjOQgTAq+ByslNwLSUis/BX58JFkAfiwgdw= X-Received: by 2002:ac8:5557:: with SMTP id o23mr13894072qtr.378.1574422264060; Fri, 22 Nov 2019 03:31:04 -0800 (PST) MIME-Version: 1.0 References: <20191120155301.GL11621@lahna.fi.intel.com> <20191121112821.GU11621@lahna.fi.intel.com> <20191121114610.GW11621@lahna.fi.intel.com> <20191121125236.GX11621@lahna.fi.intel.com> <20191121194942.GY11621@lahna.fi.intel.com> In-Reply-To: From: Karol Herbst Date: Fri, 22 Nov 2019 12:30:52 +0100 Message-ID: Subject: Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges To: "Rafael J. Wysocki" Cc: Mika Westerberg , Bjorn Helgaas , LKML , Lyude Paul , "Rafael J . Wysocki" , Linux PCI , Linux PM , dri-devel , nouveau , Dave Airlie , Mario Limonciello X-MC-Unique: 41iS0reXNyqy8iO4S3eOxw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Fri, Nov 22, 2019 at 10:07 AM Rafael J. Wysocki wrot= e: > > On Fri, Nov 22, 2019 at 1:13 AM Karol Herbst wrote: > > > > so while trying to test with d3cold disabled, I noticed that I run > > into the exact same error. > > Does this mean that you disabled d3cold on the GPU via sysfs (the > "d3cold_allowed" attribute was 0) and the original problem still > occurred in that configuration? > yes. In my previous testing I was poking into the PCI registers of the bridge controller and the GPU directly and that never caused any issues as long as I limited it to putting the devices into D3hot. > > And I verified that the > > \_SB.PCI0.PEG0.PG00._STA returns 1, which indicates it should still be > > turned on. > > I don't really understand this comment, so can you explain it a bit to > me, please? > that's the ACPI method to fetch the "status" of the power resource, it should return 0 when the device was powered off (the GPU) and 1 otherwise.