qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Alexander Graf <agraf@suse.de>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Xen-devel] Re: [PATCH 1/4] xen: Clean up build system
Date: Tue, 21 Jun 2011 15:16:12 +0200	[thread overview]
Message-ID: <4E00999C.9080608@siemens.com> (raw)
In-Reply-To: <19968.38432.700616.100291@mariner.uk.xensource.com>

On 2011-06-21 15:01, Ian Jackson wrote:
> Alexander Graf writes ("[Xen-devel] Re: [PATCH 1/4] xen: Clean up build system"):
>> On 21.06.2011, at 08:26, Jan Kiszka wrote:
>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> Introduce CONFIG_XEN_BACKEND so that this new config solely controls the
>>> target-independent backend build and CONFIG_XEN can focus on per-target
>>> building.
>>
>> What's the incentive here? I very much doubt we'll ever want to
>> support xen on !x86. In fact, the better solution would probably be
>> to just move every build component to x86 specific code.
> 
> In the past Xen has supported ppc too and there is a half-congealed
> arm port.  It's not a good assumption that Xen is x86-specific.

We aren't setting x86 dependency into stone here, we are just trying to
keep support for what is there today clean and simple. The build system
can become more advanced again once there is support for modern ARM or
PowerPC. But until other Xen archs materialize into a usable form, it's
futile to design for their past or possible future requirements. KVM is
also no longer considering IA64 when cleaning up.

Jan

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

  reply	other threads:[~2011-06-21 13:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21  6:26 [Qemu-devel] [PATCH 0/4] Xen cleanups Jan Kiszka
2011-06-21  6:26 ` [Qemu-devel] [PATCH 1/4] xen: Clean up build system Jan Kiszka
2011-06-21  7:21   ` Alexander Graf
2011-06-21  7:23     ` Jan Kiszka
2011-06-21  7:26       ` Alexander Graf
2011-06-21  7:27         ` Jan Kiszka
2011-06-21  7:46           ` Alexander Graf
2011-06-21  7:57             ` Jan Kiszka
2011-06-21  8:15               ` Alexander Graf
2011-06-21 13:01     ` [Qemu-devel] [Xen-devel] " Ian Jackson
2011-06-21 13:16       ` Jan Kiszka [this message]
2011-06-21 13:18       ` Alexander Graf
2011-06-21 13:48         ` Stefano Stabellini
2011-06-21  6:26 ` [Qemu-devel] [PATCH 2/4] xen: Uninline xen_unmap_block Jan Kiszka
2011-06-21  7:22   ` Alexander Graf
2011-06-21 13:49     ` Stefano Stabellini
2011-06-21  6:26 ` [Qemu-devel] [PATCH 3/4] xen: Clean up map cache API naming Jan Kiszka
2011-06-21  7:23   ` Alexander Graf
2011-06-21 13:49     ` Stefano Stabellini
2011-06-21  6:26 ` [Qemu-devel] [PATCH 4/4] xen: Fold CONFIG_XEN_MAPCACHE into CONFIG_XEN Jan Kiszka
2011-06-21  7:31   ` Alexander Graf
2011-06-21 13:50     ` Stefano Stabellini
2011-06-21 13:49 ` [Qemu-devel] [PATCH 0/4] Xen cleanups Stefano Stabellini
2011-06-21 14:00 ` 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=4E00999C.9080608@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=agraf@suse.de \
    --cc=anthony.perard@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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).