From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] GSoC mentor summit QEMU users session
Date: Tue, 01 Nov 2011 11:05:45 +0100 [thread overview]
Message-ID: <4EAFC479.1090601@redhat.com> (raw)
In-Reply-To: <CAFEAcA9jh5E5WQH6YwAX1HBKg8W5NB5aR8kmTTz2h6wdRhc0KA@mail.gmail.com>
Hi,
> 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.)
One of the qdev intended benefits is to have pretty much self-contained
device emulation. If doesn't work equally well everythere. For alot of
-- for example -- PCI devices it does work nicely though. Adding a
device is simply a matter of dropping a file into the tree and a line
into the Makefile and you are done. The device is available to be used
via -device. So the cost of maintaining stuff out-of-tree isn't that
big as you almost never have patch conflict issues.
For embedded stuff it is usually a bit trickier as the device
interconnects are hard-coded in the board creation bits and devices
can't be hooked up using -device (or some other generic mechanism which
uses -- say -- device trees) ...
cheers,
Gerd
next prev parent reply other threads:[~2011-11-01 10:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 13:52 [Qemu-devel] GSoC mentor summit QEMU users session Alexander Graf
2011-10-31 13:12 ` Peter Maydell
2011-11-01 0:08 ` Alexander Graf
2011-11-01 1:35 ` Peter Maydell
2011-11-01 4:29 ` Alexander Graf
2011-11-01 10:05 ` Gerd Hoffmann [this message]
2011-11-01 23:11 ` Chris Johns
2011-11-02 17:44 ` Fabien Chouteau
2011-11-02 18:17 ` Jan Kiszka
2011-11-02 18:29 ` Anthony Liguori
2011-11-02 18:34 ` Alexander Graf
2011-11-02 18:46 ` Jan Kiszka
2011-11-02 18:47 ` Alexander Graf
2011-11-02 19:07 ` Peter Maydell
2011-11-02 19:27 ` Alexander Graf
2011-11-02 19:35 ` Anthony Liguori
2011-11-02 20:24 ` Blue Swirl
2011-11-02 20:42 ` Anthony Liguori
2011-11-03 7:34 ` Markus Armbruster
2011-11-03 7:46 ` Markus Armbruster
2011-11-03 8:36 ` Andreas Färber
2011-11-04 15:47 ` Alexander Graf
2011-11-02 18:50 ` Anthony Liguori
2011-11-02 18:52 ` Jan Kiszka
2011-11-02 18:51 ` Anthony Liguori
2011-11-03 7:38 ` Stefan Hajnoczi
2011-11-03 7:44 ` Markus Armbruster
2011-11-01 14:28 ` Andreas Färber
2011-11-01 14:50 ` Anthony Liguori
2011-11-02 17:39 ` Fabien Chouteau
2011-11-03 7:44 ` Stefan Hajnoczi
2011-11-03 9:35 ` Fabien Chouteau
2011-11-04 8:36 ` Stefan Hajnoczi
2011-11-04 9:53 ` Fabien Chouteau
2011-11-04 12:04 ` Stefan Hajnoczi
2011-11-04 14:36 ` Fabien Chouteau
2011-11-04 18:45 ` Lluís Vilanova
2011-11-07 10:16 ` Fabien Chouteau
2011-11-07 11:50 ` Lluís Vilanova
2011-11-07 13:51 ` Fabien Chouteau
2011-11-07 14:17 ` Lluís Vilanova
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=4EAFC479.1090601@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.