From: Paolo Bonzini <pbonzini@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: peter.maydell@linaro.org, thuth@redhat.com,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Kconfig: add documentation
Date: Tue, 12 Feb 2019 12:27:46 +0100 [thread overview]
Message-ID: <36b82cce-a2e3-1c33-d8dd-c427274c8881@redhat.com> (raw)
In-Reply-To: <20190211181707.05e8596a.cohuck@redhat.com>
On 11/02/19 18:17, Cornelia Huck wrote:
>> +
>> +This domain-specific language is based on the Kconfig language that originated in the
>> +Linux kernel, though it was heavily simplified and the handling of dependencies is
>> +stricter in QEMU.
>> +
>> +Unlike Linux, there is no user interface to edit the configuration, which is instead
>> +specified in per-target files under the ``default-configs/`` directory of the
>> +QEMU source tree. This is because, unlike Linux, configuration and dependencies can be
>> +treated as a black box when building QEMU; the default configuration that QEMU
>> +ships with should be okay in almost all cases.
> So this is only about devices and friends, and not about cpu features
> etc.?
>
For now it is... Ideas are welcome on extensions to the mechanism; for
now it is only about what default-configs/ has always covered, just
better. :)
Paolo
next prev parent reply other threads:[~2019-02-12 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 16:38 [Qemu-devel] [PATCH] Kconfig: add documentation Paolo Bonzini
2019-02-11 17:17 ` Cornelia Huck
2019-02-12 11:27 ` Paolo Bonzini [this message]
2019-02-12 4:11 ` Stefan Hajnoczi
2019-02-12 9:08 ` Markus Armbruster
2019-02-12 10:59 ` Paolo Bonzini
2019-02-13 7:45 ` Markus Armbruster
2019-02-13 15:40 ` Paolo Bonzini
2019-02-12 9:13 ` Thomas Huth
2019-02-12 11:00 ` Paolo Bonzini
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=36b82cce-a2e3-1c33-d8dd-c427274c8881@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=cohuck@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).