All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Yang Zhong <yang.zhong@intel.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU and Kconfig
Date: Thu, 13 Dec 2018 14:27:39 +0100	[thread overview]
Message-ID: <f550da1d-1f1b-e36d-55a0-d67a33550b0e@redhat.com> (raw)
In-Reply-To: <20181213115023.GA15355@yangzhon-Virtual>

On 13/12/18 12:50, Yang Zhong wrote:
> Hello Paolo and all,
> 
> The Kconfig has been completed the porting from your repo and
> now i can sucessfully build x86_64-softmmu binary. But there
> are still some issues:
>    1) Only support x86_64 platform.
>       Other platform, especially for ARM platforms, it's hard for me to define 
>       detailed boards like pc or q35 in x86.

No problem, Philippe can look at least at ARM and MIPS.

>    2) Only support "defconfig". 
>       "randconfig" build has some issues, which are mostly related with CONFIG* in Kconfig.host, 
>       some CONFIG* has different setting value in config-host.mak and %/config-device.mak. like
>       CONFIG_OPENGL=y in %/config-device.mak and CONFIG_OPENGL=n in config-host.mak, which result
>       in build failure.

This is probably a bug or missing features in minikconf; values from
config-host.mak and config-target.mak should not be included in
config-devices.mak.

> The current configure and build command are almost same with before and if we want to disable or enable
> some features, like "tcg", we still need add "--enable/--disable-tcg" in configure command line. If we want
> to disable one emulation device, we can disable this in related Kconfig file in hw/ directory.

Yes, this is expected.

> There are still some left issues
>    a) How to replace the CONFIG* in configure, Some CONFIG* need some logic to generate, 
>       those are hard to input this CONFIG* in Kconfig.host or Kconfig* file.
> 
>    b) The CONFIG* in %/config-target.mak file, this is still related with configure. 
>         
>    c) If a) and b) can be fixed, randconfig is not critical issue.
> 
> I will send RFC patches to QEMU community and please all give some comments. many thanks!

Great, this way people can experiment it and we can finalize the design
before continuing the work.

Thanks,

Paolo

  reply	other threads:[~2018-12-13 13:27 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
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 [this message]
     [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=f550da1d-1f1b-e36d-55a0-d67a33550b0e@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 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.