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=-1.1 required=3.0 tests=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 0F24BCA9EB5 for ; Mon, 21 Oct 2019 08:55:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D59A720873 for ; Mon, 21 Oct 2019 08:55:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1571648102; bh=P/ILjmf9K7qy+5ndurAox0KwdPha8scfK03vxEE4NRY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=aA62uWNHkYX9E6T7YhVv/Gc92cks5H2JyWY/LtLkLdjsN4Q8jk6jf8LT9td3utyVt VQJOVGjr7oC0Gqyr0xyLC9Aww6RC+QdG51Zuhi4GVuCGJd0BJdUkCnEbE127AEPVDe nvyOgr+DZoPOYJ+9FNe7fmNruPlaRLe2p5BGco74= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726227AbfJUIzC (ORCPT ); Mon, 21 Oct 2019 04:55:02 -0400 Received: from mail-oi1-f195.google.com ([209.85.167.195]:42827 "EHLO mail-oi1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726648AbfJUIzC (ORCPT ); Mon, 21 Oct 2019 04:55:02 -0400 Received: by mail-oi1-f195.google.com with SMTP id i185so10356888oif.9; Mon, 21 Oct 2019 01:55:00 -0700 (PDT) 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=P/ILjmf9K7qy+5ndurAox0KwdPha8scfK03vxEE4NRY=; b=qcIdAx+pCT2mvNclo7bSkh3t1yfqyHeWFKZL+trru+D74F9qqvwzrzfgbFrhCLelCH sy+cOMGn0SDsiQrJNBwtMjKsLUwa3qxNehbuA0tNAG8ev326bQ7meCnRF8TgmUkq/phr SmzxuclRSKqNS3byHFotU9M8cOIyIogL5+pU952zYSBr3vFLHg0Xg2rjver8K6Z7YY7B 6x2zvJ5RSxf66rUNDUzzKm7A0J1/HLTdE914hFIZhLGI9pV2IrK5kTGHtsFiEeT1Ocyw aHKGWLcCXZFPAm/GXKTBmM6pllNN/2y9+VRrxqFdLLbLWpcfmoxNip/Ub3KwrvDVn6GV ovvw== X-Gm-Message-State: APjAAAWxsjiwYzVkxkyvT47sWH1hukgyP2V6IhebSCsMi5+kdI4nOQK9 zKVxXUlSbQGet8wmx3umU4AJ462++Y6jAXPhTv4= X-Google-Smtp-Source: APXvYqxjzY5Z9AlzOzvJ1XuK2u9xTXSln0v5M1CtCTChjomBuQeW7TgO9aX3S6FSb4eoCSqoL9ysnO+NpbIvsAV6Oss= X-Received: by 2002:aca:5885:: with SMTP id m127mr18881140oib.110.1571648099816; Mon, 21 Oct 2019 01:54:59 -0700 (PDT) MIME-Version: 1.0 References: <20190814213118.28473-1-kherbst@redhat.com> <2215840.qs0dBhReda@kreacher> <5228680.jBuKzensJx@kreacher> In-Reply-To: From: "Rafael J. Wysocki" Date: Mon, 21 Oct 2019 10:54:48 +0200 Message-ID: Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output" To: Karol Herbst Cc: "Rafael J. Wysocki" , Alex Hung , "Rafael J. Wysocki" , Dave Airlie , LKML , Linux ACPI , dri-devel , nouveau , Mario Limonciello , Ben Skeggs , Dave Airlie Content-Type: text/plain; charset="UTF-8" Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Mon, Oct 21, 2019 at 10:48 AM Karol Herbst wrote: > > fyi: I decided to go for a different workaround to fix the runpm > issues observed with nvidia gpus with nouveau in the "pci: prevent > putting nvidia GPUs into lower device states on certain intel bridges" > thread OK, I've seen that. > that's on the pci and pm mailing list. Maybe it makes sense to wait > for that to land before actually removing the ACPI workarounds here? Sounds reasonable. > The workaround I had in this series didn't seem to be reliable enough, > so I ditched that approached. OK, please let me know when the _OSI string in question can be dropped. > On Mon, Oct 21, 2019 at 10:14 AM Rafael J. Wysocki wrote: > > > > On Mon, Oct 21, 2019 at 4:14 AM Alex Hung wrote: > > > > > > We have done some tests on three of Intel + nVidia configuration > > > systems with OEM _OSI strings removed - while some bugs are still > > > observed, ex. one out of three has suspend/resume issues, no system > > > crashes were observed - the biggest issue that worries us. > > > > > > The positive results give us confident to ack the removal of the OEM > > > _OSI strings. While our tests were not able to cover all possible I+N > > > systems, we are sure we can fix issues along the way. If there aren't > > > systems that cannot be fixed without these OEM _OSI strings, these > > > strings should probably enable with DMI quirks (possible future > > > patches) so they won't affect others. > > > > > > Acked-by: Alex Hung > > > > OK, thanks! > > > > I can queue this up or if it's better to route it through the DRM > > tree, please do that (and let me know).