From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755901AbcANVRE (ORCPT ); Thu, 14 Jan 2016 16:17:04 -0500 Received: from www.linutronix.de ([62.245.132.108]:59446 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755755AbcANVRB (ORCPT ); Thu, 14 Jan 2016 16:17:01 -0500 Date: Thu, 14 Jan 2016 22:15:59 +0100 (CET) From: Thomas Gleixner To: Jason Taylor cc: "linux-kernel@vger.kernel.org" , x86@kernel.org, Jiang Liu Subject: Re: VMware PCI passthrough regression In-Reply-To: <4113b621e0f94c26b28ed1f80979287f@WB-SVT-EXBE03.simplivity.com> Message-ID: References: <4113b621e0f94c26b28ed1f80979287f@WB-SVT-EXBE03.simplivity.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jason, On Thu, 14 Jan 2016, Jason Taylor wrote: > I've run into a regression using PCI passthrough with the 4.4 > kernel. Actually that is a 4.2 kernel according to the dmesg in the bug tracker. > Attempting to passthrough an LSI card with ESXi version 6. Seeing > timeouts and oops in the log and the disks do not show up. The timeouts are probably related to missing irq delivery, so it might be related to the big overhaul of the x86 irq subsystem. The oops is a genuine driver bug probably unearthed by the irq issue. That should be reported seperately to the megasas folks. > I performed a bisect which tracked down the issue to the commit below. > > More details are available in a bug report I filed with Ubuntu: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528849 > > commit 52f518a3a7c2f80551a38d38be28bc9f335e713c > x86/MSI: Use hierarchical irqdomains to manage MSI interrupts I have no idea how that breaks the vmware passthrough. Can you please verify - whether that kernel works on the real hardware with that LSI card - whether that kernel works in a KVM guest with that card passed through If one of those things break, we can certainly help to analyse that. If not, then you need to talk to vmware. Thanks, tglx