From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=37144 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PogZb-0003br-7b for qemu-devel@nongnu.org; Sun, 13 Feb 2011 13:21:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PogZZ-0001E4-R1 for qemu-devel@nongnu.org; Sun, 13 Feb 2011 13:21:26 -0500 Received: from gate.crashing.org ([63.228.1.57]:46733) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PogZZ-0001Dz-DH for qemu-devel@nongnu.org; Sun, 13 Feb 2011 13:21:25 -0500 Subject: Re: [Qemu-devel] Re: [PATCH 15/15] Implement the bus structure for PAPR virtual IO From: Benjamin Herrenschmidt In-Reply-To: <4D580C5F.2060506@codemonkey.ws> References: <1297522467-5975-1-git-send-email-david@gibson.dropbear.id.au> <1297522467-5975-16-git-send-email-david@gibson.dropbear.id.au> <1BA55C28-0AAF-46A5-A14F-04B0B61419DB@suse.de> <1297544424.14982.628.camel@pasglop> <1297552503.14982.637.camel@pasglop> <20110213111450.GD18294@yookeroo> <28596383-B15A-4932-A03C-8C45F5D777D1@suse.de> <1297613854.14982.656.camel@pasglop> <4D580C5F.2060506@codemonkey.ws> Content-Type: text/plain; charset="UTF-8" Date: Sun, 13 Feb 2011 12:21:16 -0600 Message-ID: <1297621276.14982.661.camel@pasglop> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Alexander Graf , "qemu-devel@nongnu.org List" , Blue Swirl , Mackerras , anton@samba.org, Paul@gnu.org, David Gibson On Sun, 2011-02-13 at 10:52 -0600, Anthony Liguori wrote: > > A virtual bus is just an interface. If all virtual devices that > interact via hcalls would all reside on the same virtual bus, then > having hypercalls registered through that interface makes sense > because > you can associate hypercalls with particular devices. This means > that > you can automatically deregister on device removal and things like > that. I see. Well, VIO related h-calls are only part of the picture here, I think we can live with having explicit de-registration if needed ;-) Besides the h-call is still implemented even if no device -instance- is currently plugged into the partition anyways. It just returns a (well defined per-hcall) error code if the instance handle passed to it is bogus. > But I don't think this will work out well. I think treating the > hypercalls as a simple dispatch table just like ioport would make > sense. Yup. Cheers, Ben.