qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Interest in hardware plugin functionality
Date: Tue, 10 Jan 2006 12:36:42 -0600	[thread overview]
Message-ID: <43C3FEBA.4060801@us.ibm.com> (raw)
In-Reply-To: <16af12af0601091738t2fbe336td1f7cfc19b832606@mail.gmail.com>

Can you post the patch somewhere?

I've looked into this myself in the past and some devices are more 
easily abstracted than others because of some strange dependencies.  I'm 
curious to see what devices you've turned into plugins and how you've 
solved these problems (I assume that you would make all the current 
devices plugins and not just allow for custom device plugins).

Regards,

Anthony Liguori

Andre Pech wrote:

> Hi,
>
> I have been using qemu to simulate various types of custom hardware 
> for testing purposes. Rather than having to recompile qemu every time 
> I change a hardware simulation, I instead patched qemu to support 
> dynamically loading hardware plugin files at run time. The basic idea 
> is that you can specify .so files to load on the command line when you 
> boot qemu. These files will be dlopened by qemu at run time, and will 
> register themselves as hardware to the appropriate hardware controller 
> (ie a PCI device hardware plugin registers itself with the PCI bus).
>
> I was hoping to get people's reactions to / interest in this sort of 
> feature. Currently I have patched qemu to work for my own purposes, 
> which required having to hack around some issues I ran into. These 
> hacks do not require major changes in how qemu works, but are rather 
> structural changes. For example, the qemu header file naming structure 
> does not lend itself to being installed to somewhere like 
> /usr/include/qemu, and would need some changing. This includes 
> changing 'include "config.h"' to include 'include "qemu/config.h"' due 
> to the common use of config.h by other packages, as well as working 
> through the issues of how to structure things for building qemu 
> hardware plugins against multiple architecture types.
>
> I am more than willing to put all the effort into turning this into a 
> nice patch, if there is a maintainer interested in helping me shepherd 
> this into the mainline.
>
> Thanks,
> Andre Pech
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Qemu-devel mailing list
>Qemu-devel@nongnu.org
>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>  
>

  parent reply	other threads:[~2006-01-10 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10  1:38 [Qemu-devel] Interest in hardware plugin functionality Andre Pech
2006-01-10  6:21 ` Michael Renzmann
2006-01-10 12:01 ` Lennert Buytenhek
2006-01-10 17:41   ` Andre Pech
2006-01-10 18:01   ` Jan Marten Simons
2006-01-10 18:36 ` Anthony Liguori [this message]
2006-01-11  0:14   ` Andre Pech

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43C3FEBA.4060801@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).