qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, "Thomas Huth" <thuth@redhat.com>
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
	qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2] hw/*/Makefile.objs: Move many .o files to common-objs
Date: Thu, 30 Jan 2020 17:33:28 +0100	[thread overview]
Message-ID: <8077a146-f190-a584-9700-e2931a2a3beb@redhat.com> (raw)
In-Reply-To: <871rrh9fkc.fsf@linaro.org>

On 30/01/20 15:36, Alex Bennée wrote:
> 
>> We have many files that apparently do not depend on the target CPU
>> configuration, i.e. which can be put into common-obj-y instead of
>> obj-y.
> While common-obj-y is still shared by linux-user this will also add
> slightly to user-only build times.

It won't, all the directories that Thomas is touching are under ifeq
($(CONFIG_SOFTMMU), y)...endif in hw/Makefile.objs.

> I'd like to see some separation of:
> 
>  common-user-obj
>  common-sys-obj

That actually is done in the Meson conversion, where they are called
respectively user_ss and softmmu_ss ("ss" stands for sourceset).  They
are added like so to common_ss:

common_ss.add_all(when: 'CONFIG_SOFTMMU', if_true: softmmu_ss)
common_ss.add_all(when: 'CONFIG_USER_ONLY', if_true: user_ss)

> and I guess the stuff already common to everything is already in
> libqemuutil.a

In my meson-poc branch, the only files that are added directly to
common_ss rather than softmmu_ss or user_ss are the files in hw/core and
the disassemblers.

Paolo



      reply	other threads:[~2020-01-30 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 13:38 [PATCH v2] hw/*/Makefile.objs: Move many .o files to common-objs Thomas Huth
2020-01-30 14:36 ` Alex Bennée
2020-01-30 16:33   ` Paolo Bonzini [this message]

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=8077a146-f190-a584-9700-e2931a2a3beb@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).