From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754937AbbCBTLH (ORCPT ); Mon, 2 Mar 2015 14:11:07 -0500 Received: from vserver.eikelenboom.it ([84.200.39.61]:53800 "EHLO smtp.eikelenboom.it" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754166AbbCBTLF (ORCPT ); Mon, 2 Mar 2015 14:11:05 -0500 Date: Mon, 2 Mar 2015 20:11:00 +0100 From: Sander Eikelenboom Organization: Eikelenboom IT services X-Priority: 3 (Normal) Message-ID: <583821471.20150302201100@eikelenboom.it> To: Alexander Gordeev CC: Tejun Heo , Stefan Bader , Subject: Re: 3.19: device name associates with IRQ's for ahci controllers operating with a single IRQ changed from "ahci?" to "" In-Reply-To: <20150302185809.GA23808@agordeev.usersys.redhat.com> References: <534449189.20150209205457@eikelenboom.it> <54D9B9FA.9030900@canonical.com> <20150210145120.GI3220@htj.duckdns.org> <20150216172841.GA23072@agordeev.usersys.redhat.com> <20150302172108.GN17694@htj.duckdns.org> <20150302185809.GA23808@agordeev.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Monday, March 2, 2015, 7:58:10 PM, you wrote: > On Mon, Mar 02, 2015 at 12:21:08PM -0500, Tejun Heo wrote: >> Hello, >> >> On Mon, Feb 16, 2015 at 05:28:42PM +0000, Alexander Gordeev wrote: >> > The problem dates back to commit 4f37b50 ("libata: Use dev_name() for >> > request_irq() to distinguish devices"). If the commit is considered valid >> > then still might be legitimate as well. Not sure what is the best >> > approach here. >> >> What does indicate? Does it successfully identify the device in >> question? > I suppose, PCI bus-device-function. > Yes, it does. But at least it should be the same for single irq and not single irq, which at present doesn't seem to be the case. Apart from that you could also combine the devicetype with the BDF, like xen-pciback does that looks like this in /proc/interrupts: 22: 226798 0 0 0 0 0 xen-pirq-ioapic-level xen-pciback[0000:03:06.0] -- Sander >> Thanks. >> >> -- >> tejun