From owner-freebsd-bugs@freebsd.org  Tue Oct 20 21:53:36 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42DF3A1AE27
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 20 Oct 2015 21:53:36 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3045E6A9
 for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 2015 21:53:36 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9KLraFj086145
 for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 2015 21:53:36 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 203874] MSI/MSI-X interrupts don't work in VMware virtual
 machines
Date: Tue, 20 Oct 2015 21:53:36 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: marius@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-203874-8-WcxYMcq8bq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203874-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-203874-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 21:53:36 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874

Marius Strobl <marius@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marius@FreeBSD.org

--- Comment #2 from Marius Strobl <marius@FreeBSD.org> ---
Removing the ESXi MSI-X quirk altogether simply is way too gross as the
intention is to provide a setup which at least works out of the box, also on
older versions of the the VMM and even if that doesn't yield the optimal
configuration. As you apparently work for VMware, could you please get the
revision ID in the PCI header of 0x079015ad and 0x07a015ad bridges bumped for
the implementations that have MSI-X allocation fixed - if that hasn't already
be done, yet -, so we can distinguish the good from the bad ones in the PCI
code? My logs indicate that at least the bridges reporting revision 0x1 were
affected.

-- 
You are receiving this mail because:
You are the assignee for the bug.