All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:27:53 +0100	[thread overview]
Message-ID: <4CF3B869.4080001@siemens.com> (raw)
In-Reply-To: <8C89D18A-502C-4458-83DE-7B393546547D@suse.de>

Am 29.11.2010 15:15, Alexander Graf wrote:
> 
> On 29.11.2010, at 13:44, Jan Kiszka wrote:
> 
>> Am 29.11.2010 13:40, Alexander Graf wrote:
>>>
>>> On 29.11.2010, at 13:30, Jan Kiszka wrote:
>>>
>>>> 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.
>>>
>>> I still don't understand the need for that split.
>>
>> Enable Xen and build some non-x86 targets, then you see the need.
>>
>>> The device drivers should be built only once, as do the xen_machine_pv parts. Both are useless on non-x86. CONFIG_XEN should simply always be a target specific option.
>>
>> Maybe the split-up between the "generic" host-side interfaces and
>> xen_machine_pv/xen_domainbuild is the problem. You know the dependencies
>> better than me, maybe you find a better fix.
> 
> Should be enough to just replace obj-$(CONFIG_XEN) by obj-i386-$(CONFIG_XEN).

Indeed (as long as qemu's xen remains x86-only).

> Unless it's very urgent, please wait with this patch until qemu-dm and xenner are in. It's pretty suboptimal to have 3 patches flying around that hit the exact same code spot :).

It isn't urgent. If patches series refactor the stuff and fix the
dependency, I'm happy to wait for them.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-11-29 14:28 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
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 [this message]
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=4CF3B869.4080001@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 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.