From: Alexander Graf <agraf@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Fabien Chouteau <chouteau@adacore.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] GSoC mentor summit QEMU users session
Date: Wed, 02 Nov 2011 20:27:10 +0100 [thread overview]
Message-ID: <4EB1998E.1000502@suse.de> (raw)
In-Reply-To: <CAFEAcA9VBdjLDNWxiyRJw2zBK0cP=rGkoLQSg4iiDgeWVzNu+g@mail.gmail.com>
Peter Maydell wrote:
> On 2 November 2011 18:47, Alexander Graf <agraf@suse.de> wrote:
>
>> Jan Kiszka wrote:
>>
>>> We should also be able to establish an EXPORT_SYMBOL concept, ie. only
>>> export those functions that are supposed to be part of a component API.
>>> Will be some work initially, but should be off long term, both to QEMU
>>> in maintaining stable APIs and to external components in using the
>>> proper ones.
>>>
>
>
>> Yes. IOW, let's go down the same road as Linux. It works well for them,
>> why not for us?
>>
>
> I'd rather see us have a decent usable API for implementing devices
> *inside* the QEMU source tree before we start thinking about having
> one for devices outside the tree...
>
Right. That's exactly what Linux does. On Linux, you have EXPORT_SYMBOL
and EXPORT_SYMBOL_GPL. The former is considered reasonably stable. The
latter can change even in minor revisions.
So the obvious thing to do would be to export everything, but mark it
unstable and then mark things stable as we go in and actually consider
them stable. And only consider them stable for a limited time.
Alex
next prev parent reply other threads:[~2011-11-02 19:27 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
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 [this message]
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=4EB1998E.1000502@suse.de \
--to=agraf@suse.de \
--cc=chouteau@adacore.com \
--cc=jan.kiszka@siemens.com \
--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 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).