From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org,
Anthony Liguori <anthony@codemonkey.ws>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for 1.4 0/4] Simplify Makefile.objs some more
Date: Sun, 20 Jan 2013 00:22:19 +0100 [thread overview]
Message-ID: <50FB2AAB.2060805@suse.de> (raw)
In-Reply-To: <50FB18D8.7010805@redhat.com>
Am 19.01.2013 23:06, schrieb Paolo Bonzini:
> Il 19/01/2013 19:11, Andreas Färber ha scritto:
>>>> The patches are mostly mechanical substitutions, and there is no
>>>> user-visible change---neither in total build time, nor in the files that
>>>> are linked into the executables.
>> Without having tested this yet I want to remind that it is necessary for
>> qom/cpu.c to be built twice
>
> Hmm, it's not anymore actually (since libuser was removed). It hasn't
> been built twice for a month and apparently nothing broke.
I surely didn't ack that. Have you actually tested linux-user to verify
it works? It might lead to unexpected CPUState field accesses.
>> , to not run into similar issues like
>> util/oslib-posix.c.
>
> The only dependency is
>
> #if !defined(CONFIG_USER_ONLY)
> int kvm_fd;
> bool kvm_vcpu_dirty;
> #endif
> struct KVMState *kvm_state;
> struct kvm_run *kvm_run;
>
> Plenty of other fields are meaningless for !CONFIG_USER_ONLY but are
> unconditionally present in struct CPUState. Given this inconsistency,
> why is it still useful to build it twice?
You are judging based on master. I have some more code movements queued
(qom-cpu-8) and I believe it was Anthony who insisted on suppressing
those unneeded user-only fields even if they were unconditional in
CPU_COMMON before.
qom/cpu.c is not intended to remain so small forever - any cpu_* code
that does not depend on CPUArchState can find a new home there.
cpu_interrupt() is being moved to qom/cpu.h and cpu_reset_interrupt() to
qom/cpu.c for instance. And I'm working on refactoring CPU VMState, that
either requires #ifdef'ery or lots of new stubs beyond what Eduardo added.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-01-19 23:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 10:06 [Qemu-devel] [PATCH for 1.4 0/4] Simplify Makefile.objs some more Paolo Bonzini
2013-01-19 10:06 ` [Qemu-devel] [PATCH 1/4] build: move around libcacard-y definition Paolo Bonzini
2013-01-19 18:05 ` Andreas Färber
2013-01-19 22:01 ` Paolo Bonzini
2013-01-19 23:26 ` Andreas Färber
2013-01-19 10:06 ` [Qemu-devel] [PATCH 2/4] build: use -$(CONFIG_SECCOMP) instead of ifeq Paolo Bonzini
2013-01-19 18:06 ` Andreas Färber
2013-01-19 10:06 ` [Qemu-devel] [PATCH 3/4] build: remove universal-obj-y Paolo Bonzini
2013-01-19 10:06 ` [Qemu-devel] [PATCH 4/4] build: remove extra-obj-y Paolo Bonzini
2013-01-19 18:11 ` [Qemu-devel] [PATCH for 1.4 0/4] Simplify Makefile.objs some more Andreas Färber
2013-01-19 22:06 ` Paolo Bonzini
2013-01-19 22:07 ` Paolo Bonzini
2013-01-19 23:22 ` Andreas Färber [this message]
2013-01-20 9:06 ` 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=50FB2AAB.2060805@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--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 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.