From owner-freebsd-virtualization@FreeBSD.ORG  Thu Jan 23 20:34:43 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 95CAC2E3
 for <virtualization@freebsd.org>; Thu, 23 Jan 2014 20:34:43 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6C41717FA
 for <virtualization@freebsd.org>; Thu, 23 Jan 2014 20:34:43 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 61C3BB99B;
 Thu, 23 Jan 2014 15:34:42 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: Neel Natu <neelnatu@gmail.com>
Subject: Re: bhyve and legacy
Date: Thu, 23 Jan 2014 14:54:57 -0500
User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; )
References: <201401221715.42164.jhb@freebsd.org>
 <CAFgRE9FC9zzgkNw8voa7T9dRsuUzUOmBdz6GmgC4bYUbnzXNHg@mail.gmail.com>
In-Reply-To: <CAFgRE9FC9zzgkNw8voa7T9dRsuUzUOmBdz6GmgC4bYUbnzXNHg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201401231454.58012.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Thu, 23 Jan 2014 15:34:42 -0500 (EST)
Cc: "freebsd-virtualization@freebsd.org" <virtualization@freebsd.org>
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 20:34:43 -0000

On Wednesday, January 22, 2014 9:48:20 pm Neel Natu wrote:
> Hi John,
> 
> On Wed, Jan 22, 2014 at 2:15 PM, John Baldwin <jhb@freebsd.org> wrote:
> > Is there any interest in supporting more "legacy" setups via bhyve?  In
> > particular, I'd like to take a whack at improving the PCI INTx support, but
> > that can involve several things such as possibly implementing 8259A support
> > and a PCI interrupt router vs always assuming that we have APICs.  If we do
> 
> I would love to see PCI INTx support so we can do legacy interrupts
> for the virtio device models.
> 
> However, does that require going all the way back to 8259 style
> interrupts? It should work fine with IOAPIC, no?

No, it does not.  It was more a question of what was desired.  The first step
would probably just be to get the IOAPIC case working well and make sure the
_PRT is populated in ACPI and MP Table is correct.  (For example, in typical
systems, ISA IRQs are not used for PCI INTx on an I/O APIC, but interrupt pins
above 15 are used).

-- 
John Baldwin