From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] xen: Restrict build to x86 targets
Date: Mon, 29 Nov 2010 13:30:29 +0100 [thread overview]
Message-ID: <4CF39CE5.9090204@siemens.com> (raw)
In-Reply-To: <5C53BA9F-A1B7-4CAB-BFFC-F6111021A292@suse.de>
Am 29.11.2010 13:24, Alexander Graf wrote:
>
> On 28.11.2010, at 16:59, Jan Kiszka wrote:
>
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Xen target bits in qemu are intended for x86. Let the build system
>> reflect this and avoid useless building/linking for other targets.
>
> Not sure I understand the split. Xen is x86 only, yes. But why split it into host and target? Target usually defines the guest. The piece you marked as _HOST are target specific.
At least so far, the HOST part is build once for all targets into the
host backend library. As this step injected CONFIG_XEN into all target
builds, even non-x86 targets built xen_machine_pv and xen_domainbuild.
That's addressed by the patch.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-11-29 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 15:59 [Qemu-devel] [PATCH] xen: Restrict build to x86 targets Jan Kiszka
2010-11-29 12:24 ` Alexander Graf
2010-11-29 12:30 ` Jan Kiszka [this message]
2010-11-29 12:40 ` Alexander Graf
2010-11-29 12:44 ` Jan Kiszka
2010-11-29 14:15 ` Alexander Graf
2010-11-29 14:27 ` Jan Kiszka
2010-11-29 14:32 ` Alexander Graf
2010-12-01 10:21 ` Anthony PERARD
2010-12-01 10:25 ` Alexander Graf
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=4CF39CE5.9090204@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=agraf@suse.de \
--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 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).