Received: by 10.223.176.46 with SMTP id f43csp2500683wra; Thu, 25 Jan 2018 10:47:58 -0800 (PST) X-Google-Smtp-Source: AH8x2265Vewxf+ZK8apw70XK5mI6rO9sxg0tcrzW+VDTAS9SUAwVdShfNC3L/EummtdjMpOpSJ/N X-Received: by 10.98.79.12 with SMTP id d12mr17056950pfb.186.1516906078621; Thu, 25 Jan 2018 10:47:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516906078; cv=none; d=google.com; s=arc-20160816; b=jiMQ8PPaU7S8Ki1z8uGvzvwlJkQguqrg/GMpb/FJD0l3K3VMVDUnR0jGaQjWxUec5a 4APAW3aop6weOV3ANH6qRzvntL7Z2oP8vteNQ0MNHLOk1q6XscxcXMN1t6R40zjKREmI hKBuYbuUwx1XTSbWERYLfgx7ZDDnUVijks+DuLZAJZyYMRAYhkZej3SP/8RbQFqJMOim kAOxXWrJ4KqU8KQnSsI3P2qkAoJZ4xOEXdDtsKY1H76raOvqAuTr9WOzvhBBT/39OfYo z2SdrFmJnSsC1ohQHGK9HYp3Xf7ljzJdH3rlW9Zt1Y4MSIJSKdxXTBxOxhI2zZdPp93a Ogug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=THnYDV/4XLbGsW2+ac1e1ATYCit94PIx/Uq9+AeYwUY=; b=tUh8o50TZ1e1ON3lVpFCVj3N6HPBZrJCvCPNKRGwyJqAXumEMeUp1H7g8wP6kOpl9X U+zd079f1OiZC0L6EnONQBl96vI9/Jq6rurihhnShSdQlUH0PW3nUYJFRO9VjdeYDaBb QkwUZRsqdjPpMR70VAzZlXIthxBcFpD8oorfAlw3XCYZumQTJmUDpW7NlEZWy/K8FQVI QbVBBjDXu7Hx73qiiaZKf6EusYOVeTyrGk6djJEYZ2w9avgWye2WG8MoXh0Lh7wmV+L5 vwTZ7p0tPkEWgS5IaNuNDt/xiEeCGuB+4yk3ecNy8Re29j9/g4N+69H/AAui48AWx5WE kTRg== ARC-Authentication-Results: i=1; mx.google.com; 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 205si4972994pfw.227.2018.01.25.10.47.44; Thu, 25 Jan 2018 10:47:58 -0800 (PST) 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; 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 S1751200AbeAYSrS (ORCPT + 99 others); Thu, 25 Jan 2018 13:47:18 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:35895 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750994AbeAYSrR (ORCPT ); Thu, 25 Jan 2018 13:47:17 -0500 Received: from p4fea5f09.dip0.t-ipconnect.de ([79.234.95.9] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1eemVW-0005bS-JG; Thu, 25 Jan 2018 19:44:18 +0100 Date: Thu, 25 Jan 2018 19:46:57 +0100 (CET) From: Thomas Gleixner To: Lyude Paul cc: "Ghannam, Yazen" , "hpa@zytor.com" , "keith.busch@intel.com" , "mingo@kernel.org" , "linux-kernel@vger.kernel.org" , Borislav Petkov Subject: Re: "irq/matrix: Spread interrupts on allocation" breaks nouveau in mainline kernel In-Reply-To: <1516904638.5161.1.camel@redhat.com> Message-ID: References: <1516744873.29151.3.camel@redhat.com> <1516757219.29151.7.camel@redhat.com> <1516816150.4109.2.camel@redhat.com> <1516823810.4109.26.camel@redhat.com> <1516904638.5161.1.camel@redhat.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 25 Jan 2018, Lyude Paul wrote: > I think you are right, apologies. Glad to know this isn't a regression in the > IRQ handling code :). It looks like our nouveau problems are probably coming > from the fact that we don't just leave IRQs setup through suspend/resume which > as far as I can tell, is probably not the correct thing to do. If you tear down the interrupt, then you have to make sure that it's completely masked and disabled on the device side (including MSI). Thanks, tglx