From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:58720) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SYzD2-00058o-6J for qemu-devel@nongnu.org; Mon, 28 May 2012 08:38:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SYzCu-00021E-9e for qemu-devel@nongnu.org; Mon, 28 May 2012 08:38:03 -0400 Received: from mail-lb0-f173.google.com ([209.85.217.173]:56117) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SYzCt-00020O-Vo for qemu-devel@nongnu.org; Mon, 28 May 2012 08:37:56 -0400 Received: by lbok6 with SMTP id k6so2335071lbo.4 for ; Mon, 28 May 2012 05:37:53 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4FBDA889.4000907@samsung.com> References: <4FABA585.8050400@samsung.com> <4FBDA889.4000907@samsung.com> Date: Mon, 28 May 2012 13:37:53 +0100 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] Virtio-pci issue List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Evgeny Voevodin Cc: Peter Maydell , Kyungmin Park , Dmitry Solodkiy , qemu-devel@nongnu.org, Anthony Liguori On Thu, May 24, 2012 at 4:18 AM, Evgeny Voevodin wrote: > And also there is another problem that I've faced with. It is the ability to > plug as many pci back-ends as board wants. > I mean that if for each back-end board should create a transport, then user > have to know maximum number of transport instances > created by board. In the case of mmio transport I think that it's a correct > behaviour, but for pci transport seems not. Not sure I understand the problem. Can you rephrase it? Stefan