From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751209AbeAYS3s (ORCPT <rfc822;w@1wt.eu>);
        Thu, 25 Jan 2018 13:29:48 -0500
Received: from mail-qt0-f194.google.com ([209.85.216.194]:38355 "EHLO
        mail-qt0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750994AbeAYS3q (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 25 Jan 2018 13:29:46 -0500
X-Google-Smtp-Source: AH8x224/USnJJWMChyUhz144npHRVFjjmoAuustpOEModgQwaUZ0+mgnS8TsqptMbe5ziNl6Rop+HQ==
Message-ID: <1516904984.5161.2.camel@redhat.com>
Subject: Re: "irq/matrix: Spread interrupts on allocation" breaks nouveau in
 mainline kernel
From: Lyude Paul <lyude@redhat.com>
Reply-To: lyude@redhat.com
To: Mike Galbraith <efault@gmx.de>,
        "Ghannam, Yazen" <Yazen.Ghannam@amd.com>,
        Thomas Gleixner <tglx@linutronix.de>
Cc: "hpa@zytor.com" <hpa@zytor.com>,
        "keith.busch@intel.com" <keith.busch@intel.com>,
        "mingo@kernel.org" <mingo@kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Borislav Petkov <bp@alien8.de>
Date: Thu, 25 Jan 2018 13:29:44 -0500
In-Reply-To: <1516850941.6785.7.camel@gmx.de>
References: <1516744873.29151.3.camel@redhat.com>
         <1516757219.29151.7.camel@redhat.com>
         <alpine.DEB.2.20.1801241351080.1997@nanos>
         <1516816150.4109.2.camel@redhat.com>
         <DM5PR12MB19161E66F534B7050B8CCBF0F8E20@DM5PR12MB1916.namprd12.prod.outlook.com>
         <1516823810.4109.26.camel@redhat.com> <1516824121.4109.28.camel@redhat.com>
         <1516850941.6785.7.camel@gmx.de>
Organization: Red Hat
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.4 (3.26.4-1.fc27) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Will cc you with some patches in a bit, think I have this problem figured out :)

On Thu, 2018-01-25 at 04:29 +0100, Mike Galbraith wrote:
> On Wed, 2018-01-24 at 15:02 -0500, Lyude Paul wrote:
> > Almost forgot to mention: I came across this patch because reverting it
> > locally on the mainline kernel makes request_irq() behave normally (it
> > doesn't
> > attempt to allocate the same vector twice anymore) and nouveau starts doing
> > suspend/resume correctly again
> 
> Ah, someone already hunted down my resume woes.  Yup, reverting
> $subject fixed up my sole reason to use nouveau (to be able to _resume_
> as well as suspend:).  If anyone needs a lab rat, just holler.
> 
> 	-Mike