From owner-freebsd-virtualization@freebsd.org  Thu Aug  9 16:24:12 2018
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2766F106BD46
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Thu,  9 Aug 2018 16:24:12 +0000 (UTC) (envelope-from jhb@FreeBSD.org)
Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D30507C658
 for <freebsd-virtualization@freebsd.org>; Thu,  9 Aug 2018 16:24:11 +0000 (UTC)
 (envelope-from jhb@FreeBSD.org)
Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx
 [66.234.199.215])
 by mail.baldwin.cx (Postfix) with ESMTPSA id 18D6310B429;
 Thu,  9 Aug 2018 12:24:11 -0400 (EDT)
Subject: Re: Passthrough not working with OpenBSD nor NetBSD
To: Farid Joubbi <djfarid@gmail.com>
References: <CAEN4iua-8W8JjU9DNBiP-dcuBiMZRp+yCRy0ekeAF9LXc4hQ9Q@mail.gmail.com>
 <f16bd6d1-6566-6a61-4bca-1333bbdf91e8@FreeBSD.org>
 <CAEN4iub014PXgjf18VH5xgjTxVeHcmAtRaK2joWgR4=_E-oX5w@mail.gmail.com>
Cc: freebsd-virtualization@freebsd.org
From: John Baldwin <jhb@FreeBSD.org>
Message-ID: <a91706b0-0fc3-22ee-2f56-29a10c923500@FreeBSD.org>
Date: Thu, 9 Aug 2018 09:24:10 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAEN4iub014PXgjf18VH5xgjTxVeHcmAtRaK2joWgR4=_E-oX5w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (mail.baldwin.cx); Thu, 09 Aug 2018 12:24:11 -0400 (EDT)
X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx
X-Virus-Status: Clean
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2018 16:24:12 -0000

On 8/8/18 11:08 AM, Farid Joubbi wrote:
> That's what I also thought, but it's not anything I can force it to do, is it? Isn't it supposed to detect the MSI interrupt compatibility automatically?

Apparently Open/Net always try to setup INTx before trying MSI even if they
won't use INTx per the commit log in revision 280725.  We could perhaps try
to provide a "fake" INTx interrupt that doesn't work, but I'll have to think
about how to implement that. 

-- 
John Baldwin