From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34071) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SEkn5-0002vZ-5u for qemu-devel@nongnu.org; Mon, 02 Apr 2012 13:11:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SEkn3-0002bg-II for qemu-devel@nongnu.org; Mon, 02 Apr 2012 13:11:38 -0400 Received: from smtp.ctxuk.citrix.com ([62.200.22.115]:54634 helo=SMTP.EU.CITRIX.COM) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SEkn3-0002bM-C0 for qemu-devel@nongnu.org; Mon, 02 Apr 2012 13:11:37 -0400 From: Ian Jackson MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-ID: <20345.56773.8058.87028@mariner.uk.xensource.com> Date: Mon, 2 Apr 2012 18:11:33 +0100 In-Reply-To: References: Subject: Re: [Qemu-devel] [Xen-devel] [XEN][RFC PATCH 14/15] xl-parsing: Parse the new option device_models List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Julien Grall Cc: julian.pidancet@citrix.com, xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Stefano.Stabellini@eu.citrix.com Julien Grall writes ("[Xen-devel] [XEN][RFC PATCH 14/15] xl-parsing: Parse the new option device_models"): > For the support of multiple ioreq server, we add a new option "device_models". > It's an array of device model, for each device model, we need to specify > which pci, IO range (MMIO, PIO) will be allow. I don't think this is really a suitable interface. The PCI space in the guest is controlled by the device models(s) and the user should surely specify which devices should be provided by which dms, in terms of devices not in terms of PCI space. Ian. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [Xen-devel] [XEN][RFC PATCH 14/15] xl-parsing: Parse the new option device_models Date: Mon, 2 Apr 2012 18:11:33 +0100 Message-ID: <20345.56773.8058.87028@mariner.uk.xensource.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Julien Grall Cc: julian.pidancet@citrix.com, xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Stefano.Stabellini@eu.citrix.com List-Id: xen-devel@lists.xenproject.org Julien Grall writes ("[Xen-devel] [XEN][RFC PATCH 14/15] xl-parsing: Parse the new option device_models"): > For the support of multiple ioreq server, we add a new option "device_models". > It's an array of device model, for each device model, we need to specify > which pci, IO range (MMIO, PIO) will be allow. I don't think this is really a suitable interface. The PCI space in the guest is controlled by the device models(s) and the user should surely specify which devices should be provided by which dms, in terms of devices not in terms of PCI space. Ian.