qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andre Pech <andre.pech@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Interest in hardware plugin functionality
Date: Tue, 10 Jan 2006 09:41:48 -0800	[thread overview]
Message-ID: <16af12af0601100941l559fd286t9970b8926651d220@mail.gmail.com> (raw)
In-Reply-To: <20060110120109.GA17360@xi.wantstofly.org>

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

This functionality is not strictly for hotplugging. Maybe my use of the term
hardware plugin was misleading. The patch adds the ability to pass a .so
file compiled against qemu's header files to qemu on the command line. This
.so file is dlopened and registers itself as hardware appropriately, all
before the operating system actually boots.
I could envision adding the ability to have a qemu monitor command to
similarly open such a file in order to hotplug a hardware device, but
obviously this would be limited to the hardware types that the operating
system supports hotplugging for.
Andre

On 1/10/06, Lennert Buytenhek <buytenh@wantstofly.org> wrote:
>
> On Mon, Jan 09, 2006 at 05:38:58PM -0800, Andre Pech wrote:
>
> > 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 think the biggest problem would be that a lot of operating systems
> don't support hotplug PCI.
>
>
> --L
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

[-- Attachment #2: Type: text/html, Size: 2046 bytes --]

  reply	other threads:[~2006-01-10 17:43 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 [this message]
2006-01-10 18:01   ` Jan Marten Simons
2006-01-10 18:36 ` Anthony Liguori
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=16af12af0601100941l559fd286t9970b8926651d220@mail.gmail.com \
    --to=andre.pech@gmail.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).