From owner-freebsd-bugs@freebsd.org  Tue Oct 20 22:28:44 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 CF89BA1A617
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 20 Oct 2015 22:28:44 +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 BD00AC26
 for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 2015 22:28:44 +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 t9KMSi9C072118
 for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 2015 22:28:44 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 22:28:45 +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: bhavesh@vmware.com
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: 
Message-ID: <bug-203874-8-YKEKlLhG2H@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 22:28:44 -0000

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

--- Comment #3 from bhavesh@vmware.com ---
(In reply to Marius Strobl from comment #2)

I tried to search for the history behind why this quirk was introduced for
VMware virtual machines in the first place, as we've never shipped a version of
ESXi where the implementation of MSI or MSI-X was broken, like the comment
suggests it was in ESXi 5.1 and before.

So there have been no bumps to the PCI revision IDs of these devices that can
identify when it was broken v/s fixed as from our POV it was never broken.

Can you point me to some bug report or mailing list archive or something that
details what was supposedly broken w.r.t. "MSI-X allocation on ESXi?"

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