From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53597) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLfZK-0002Ss-Nx for qemu-devel@nongnu.org; Wed, 02 Nov 2011 14:29:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLfZJ-0002Jd-6u for qemu-devel@nongnu.org; Wed, 02 Nov 2011 14:29:46 -0400 Received: from mail-yw0-f45.google.com ([209.85.213.45]:51091) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLfZJ-0002JW-4R for qemu-devel@nongnu.org; Wed, 02 Nov 2011 14:29:45 -0400 Received: by ywb3 with SMTP id 3so491148ywb.4 for ; Wed, 02 Nov 2011 11:29:44 -0700 (PDT) Message-ID: <4EB18C13.2030704@codemonkey.ws> Date: Wed, 02 Nov 2011 13:29:39 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <4639B135-B96A-43A0-B4FA-6DDCBE3FBA92@suse.de> <4EB18172.1020905@adacore.com> <4EB18952.4080403@siemens.com> In-Reply-To: <4EB18952.4080403@siemens.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] GSoC mentor summit QEMU users session List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Peter Maydell , Alexander Graf , Fabien Chouteau , "qemu-devel@nongnu.org Developers" On 11/02/2011 01:17 PM, Jan Kiszka wrote: > On 2011-11-02 18:44, Fabien Chouteau wrote: >> On 31/10/2011 14:12, Peter Maydell wrote: >>> On 29 October 2011 14:52, Alexander Graf wrote: >>>> A lot of people seem to also have code that doesn't make sense >>>> upstream, for example implementing a one-off device that only >>>> really matters for their own devboard which nobody else owns. >>>> For such cases, having a plugin framework would be handy. I >>>> interestingly enough got into the same discussion on LinuxCon >>>> with some QEMU downstreams. >>> >>> If we get the qdev rework done then I think we're probably in >>> a better position to have a plugin framework for devices. (There >>> are some issues about API and ABI stability guarantees, of course.) >>> >> >> Interesting, we have a "plug-in" implementation in our Qemu branch. It > > We have a "plugin" model here as well. It's really simple: the plugin is > loaded dynamically into the QEMU process and can access any global > function and variable. Of course, this breaks regularly. Yes, this is the Right Model. All of the work is in making the interfaces not break regularly. Loading a shared object is easy enough. Regards, Anthony Liguori