From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] make: automatically include dependencies in recursive subdir rules (v2)
Date: Mon, 18 Jun 2012 07:47:02 -0500 [thread overview]
Message-ID: <4FDF2346.9060504@us.ibm.com> (raw)
In-Reply-To: <4FDEF152.2070303@siemens.com>
On 06/18/2012 04:13 AM, Jan Kiszka wrote:
> On 2012-06-18 02:32, Andreas Färber wrote:
>> Am 18.06.2012 02:01, schrieb Anthony Liguori:
>> This will work technically but I still feel this is wrong semantically.
>> The pre-Paolo and current way is picking specific files from the hw/kvm/
>> directory. Your change above implies that in hw/kvm/ only x86 files can
>> live, which I dislike. As suggested before, I would prefer if x86-only
>> files were moved to an x86-specific location - the place for that
>> existing since Paolo's refactoring would be hw/i386/. CC'ing Jan. That
>> would match Paolo's reply in the unicore32 thread on future file
>> placement. Alternatives would be hw/i386/kvm/ or hw/kvm/i386/; we're
>> talking about a handful of files only though, so I don't think they
>> require a new subdirectory.
>
> Some per-arch separation is required, at least in the build process.
> We'll see power and arm stubs for in-kernel devices soon.
i8259.o i8254.o ioapic.o don't need to be arch specific
apic.o ought to be renamed to lapic.o and moved to target-i386/kvm/
I think clock.o also more than likely belongs in target-i386/kvm/. It would
have to be implemented as part of the CPU core if it ever existed IRL.
In general, if is logically part of a CPU core, it ought to be in
target-$(ARCH). Otherwise, it shouldn't be built as a target specific object.
Regards,
Anthony Liguori
> Jan
>
next prev parent reply other threads:[~2012-06-18 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 0:01 [Qemu-devel] [PATCH] make: automatically include dependencies in recursive subdir rules (v2) Anthony Liguori
2012-06-18 0:32 ` Andreas Färber
2012-06-18 9:13 ` Jan Kiszka
2012-06-18 9:31 ` Peter Maydell
2012-06-18 10:42 ` Andreas Färber
2012-06-18 10:56 ` Peter Maydell
2012-06-18 11:35 ` Andreas Färber
2012-06-18 11:45 ` Peter Maydell
2012-06-18 12:47 ` Anthony Liguori [this message]
2012-06-18 13:08 ` Jan Kiszka
2012-06-20 13:06 ` Anthony Liguori
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=4FDF2346.9060504@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=afaerber@suse.de \
--cc=jan.kiszka@siemens.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.