qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	"Zhong, Yang" <yang.zhong@intel.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU and Kconfig
Date: Thu, 8 Nov 2018 14:42:19 +0100	[thread overview]
Message-ID: <95a93d53-f87d-bd96-9363-582c4eae4160@redhat.com> (raw)
In-Reply-To: <20181108130648.GJ12503@habkost.net>

On 08/11/2018 14:06, Eduardo Habkost wrote:
> On Thu, Nov 08, 2018 at 10:55:21AM +0100, Paolo Bonzini wrote:
>> On 07/11/2018 20:30, Thomas Huth wrote:
>>> On 2018-11-07 20:24, Eduardo Habkost wrote:
>>>> On Wed, Nov 07, 2018 at 06:39:54PM +0100, Paolo Bonzini wrote:
>>>>> On 07/11/2018 16:41, Samuel Ortiz wrote:
>>>>>> - The Kconfig parser would be used to generate the equivalent of what we
>>>>>>   currently have under default-configs/
>>>
>>> I think we would still have something like default-configs - but there
>>> would only be the bare minimum config switches in there, the rest would
>>> be pulled in by dependencies.
>>
>> Yes, in theory default-configs would end up empty, except for possibly
>> some commented lines to show the "default y" symbols for the target.
>>
>>> We could then also even have multiple config directories:
>>>
>>> ./configs
>>>  +-------/default-softmmu
>>>  +-------/default-linux-user
>>>  +-------/nemu (or lean-kvm or something similar)
>>>  +...
>>>
>>> ... just my 0.02 €, feel free to ignore that idea ;-)
>>
>> Yup, one can also think of a configure option like "./configure
>> --with-device-config=configs/nemu/" to pick up the alternative
>> configurations.
>>
>>>> Also, I would like to eventually replace many ./configure options
>>>> with options read from a build configuration file.
>>>>
>>>> Distributions often have huge ./configure command lines in their
>>>> QEMU packages, and they could be replaced by simple build
>>>> configuration files.
>>>>
>>>> Having a mode that requires all build options to be specified
>>>> explicitly (instead of silently picking a default) would be
>>>> useful for distributions, too.
>>>
>>> I think we should maybe not mix host configuration (via ./configure) and
>>> the target configuration (via kconfig), should we?
>>
>> Yeah, the configure command line is a different story.  If there are
>> suggestion on how to improve it, great, but let's not conflate it with
>> Kconfig.
> 
> I believe we have many ./configure options that are supposed to
> be target configuration.  e.g.: --enable-slirp, --eanble-kvm,
> --enable-xen, etc.

SLIRP is not a target configuration, it's a backend like most other
configure command line options.  The accelerators are but (except for
TCG of course) they also depend on the host OS and architecture, which
makes them a bit more complicated than default-configs/ symbols.  There
are also things like --enable-vhost-user which affect the creation of
both devices (e.g. vhost-user-scsi-pci) and backends (e.g. the
vhost-user-net backend, which uses a "regular" virtio-net-pci device).

It would surely be possible for configure to call into minikconf to
parse a configuration file and apply dependencies (do we actually have
dependencies across configure options?) or something like that, but
let's not put the cart before the horse...

Paolo

  reply	other threads:[~2018-11-08 13:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180924092120.GA30163@caravaggio>
     [not found] ` <7c2b477e-bdac-c887-2510-82fe04acdcfe@redhat.com>
     [not found]   ` <87b22690-e39c-3b46-dcb4-f6abc3213142@redhat.com>
     [not found]     ` <CAFEAcA8yHb4MdtsJuXcswQp93DN5tSeN9dn8AWWL9se0DKvdcg@mail.gmail.com>
     [not found]       ` <41ceda53-467e-32a1-8fa6-13f0f9c08ad1@redhat.com>
     [not found]         ` <CAFEAcA9oCs+Y1fnY8dOR16n_Hn7PaHziL7K0HZK6=BAd_Gyecg@mail.gmail.com>
     [not found]           ` <e496287e-f8ba-3608-42e1-efb697cfc784@redhat.com>
2018-11-07 15:41             ` [Qemu-devel] QEMU and Kconfig Samuel Ortiz
2018-11-07 17:39               ` Paolo Bonzini
2018-11-07 19:24                 ` Eduardo Habkost
2018-11-07 19:30                   ` Thomas Huth
2018-11-08  9:55                     ` Paolo Bonzini
2018-11-08 10:14                       ` Thomas Huth
2018-11-08 10:53                         ` Philippe Mathieu-Daudé
2018-11-08 12:02                         ` Paolo Bonzini
2018-11-08 13:06                       ` Eduardo Habkost
2018-11-08 13:42                         ` Paolo Bonzini [this message]
2018-11-08 17:14                           ` Eduardo Habkost
2018-11-08 17:58                             ` Paolo Bonzini
2018-11-08 18:42                               ` Eduardo Habkost
2018-11-08 20:28                                 ` Paolo Bonzini
2018-11-08 21:00                                   ` Eduardo Habkost
2018-11-09 10:10                                     ` Paolo Bonzini
2018-11-09 19:16                                       ` Eduardo Habkost
2018-11-14 11:50                                         ` Paolo Bonzini
2018-11-08 11:06                   ` Samuel Ortiz
2018-12-13 11:50                     ` Yang Zhong
2018-12-13 13:27                       ` Paolo Bonzini
     [not found]         ` <20180926141518.GB9073@caravaggio>
     [not found]           ` <3743752b-2670-1d89-2088-1e67122f5dcd@redhat.com>
2018-11-08  8:46             ` Philippe Mathieu-Daudé
2018-11-08  9:56               ` Paolo Bonzini
2018-11-08 12:46                 ` Markus Armbruster

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=95a93d53-f87d-bd96-9363-582c4eae4160@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sameo@linux.intel.com \
    --cc=thuth@redhat.com \
    --cc=yang.zhong@intel.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).