From owner-freebsd-xen@FreeBSD.ORG Thu Aug 29 19:39:21 2013 Return-Path: Delivered-To: xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 492B9777; Thu, 29 Aug 2013 19:39:21 +0000 (UTC) (envelope-from gibbs@FreeBSD.org) Received: from aslan.scsiguy.com (www.scsiguy.com [70.89.174.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0770D23AF; Thu, 29 Aug 2013 19:39:20 +0000 (UTC) Received: from [192.168.6.133] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) (authenticated bits=0) by aslan.scsiguy.com (8.14.7/8.14.5) with ESMTP id r7TJdJsT084636 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 29 Aug 2013 19:39:20 GMT (envelope-from gibbs@FreeBSD.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: [CFR] Event channel Interrupts and unified Xen interrupt infrastructure. From: "Justin T. Gibbs" In-Reply-To: <521FA2BC.2060707@freebsd.org> Date: Thu, 29 Aug 2013 13:39:14 -0600 Content-Transfer-Encoding: 7bit Message-Id: <32A063DA-DAD2-407E-A0EC-FA5733C29C4C@FreeBSD.org> References: <7D29BB74-2341-4164-B2B8-85A4CAB3A6CE@FreeBSD.org> <521FA2BC.2060707@freebsd.org> To: Colin Percival X-Mailer: Apple Mail (2.1508) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (aslan.scsiguy.com [70.89.174.89]); Thu, 29 Aug 2013 19:39:20 +0000 (UTC) Cc: xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2013 19:39:21 -0000 On Aug 29, 2013, at 1:36 PM, Colin Percival wrote: > In sys/x86/xen/hvm.c: > +/** > + * If non-zero, the hypervisor has been configured to use a direct > + * IDT event callback to the > + */ > > This comment seems to be missing part of its Fixed. -- Justin