From owner-freebsd-xen@FreeBSD.ORG Mon Jan 6 09:35:38 2014 Return-Path: Delivered-To: freebsd-xen@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 48C0F840; Mon, 6 Jan 2014 09:35:38 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CBA4F171D; Mon, 6 Jan 2014 09:35:36 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.95,611,1384300800"; d="scan'208";a="87820970" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 06 Jan 2014 09:35:23 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Mon, 6 Jan 2014 04:35:27 -0500 Message-ID: <52CA78DE.9060502@citrix.com> Date: Mon, 6 Jan 2014 10:35:26 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Julien Grall , , , , , , , Subject: Re: [Xen-devel] [PATCH v9 15/19] xen: create a Xen nexus to use in PV/PVH References: <1388677433-49525-1-git-send-email-roger.pau@citrix.com> <1388677433-49525-16-git-send-email-roger.pau@citrix.com> <52C9D4CA.6070403@linaro.org> In-Reply-To: <52C9D4CA.6070403@linaro.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 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: Mon, 06 Jan 2014 09:35:38 -0000 On 05/01/14 22:55, Julien Grall wrote: > > > On 01/02/2014 03:43 PM, Roger Pau Monne wrote: >> Introduce a Xen specific nexus that is going to be in charge for >> attaching Xen specific devices. > > Now that we have a xenpv bus, do we really need a specific nexus for Xen? > We should be able to use the identify callback of xenpv to create the bus. > > The other part of this patch can be merged in the patch #14 "Introduce > xenpv bus and a dummy pvcpu device". On x86 at least we need the Xen specific nexus, or we will fall back to use the legacy nexus which is not what we really want.