From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: [PATCH] x86: wrap kexec feature with CONFIG_KEXEC
Date: Wed, 2 Sep 2015 11:00:32 +0100 [thread overview]
Message-ID: <55E6C8C0.7060308@citrix.com> (raw)
In-Reply-To: <55E6B906020000780009ED0C@prv-mh.provo.novell.com>
On 02/09/15 07:53, Jan Beulich wrote:
>>>> On 01.09.15 at 19:55, <jonathan.creekmore@gmail.com> wrote:
>> "Jan Beulich" <JBeulich@suse.com> writes:
>>
>>>>>> On 01.09.15 at 16:29, <jonathan.creekmore@gmail.com> wrote:
>>> Which is both appreciated and understandable. I suppose you
>>> agree though that if you were to follow the model used for the
>>> kexec part, things would quickly become unwieldy. Hence I would
>>> strongly suggest considering to introduce Linux'es or a
>>> Linux-like configure mechanism before continuing to make code
>>> conditionally compilable.
>> Oh, I definitely agree.
>>
>> What exactly are you looking for? Are you looking for just a KConfig
>> type of mechanism, or a full KBuild implementation. In a previous life,
>> I ported both to an embedded RTOS build. I think it might be simpler to
>> just start with a KConfig mechanism, though. If you want, I can take a
>> swing at starting down that path.
> Just Kconfig (I don't see any connection here to the need of a
> clone of the Kbuild mechanism). But give it a little time for other
> maintainers to voice an opinion (perhaps worthwhile spelling out
> the intention in a separate mail thread).
For something like this, just Kconfig. That will be a good improvement
on its own.
There are orthogonal reasons for looking to improve the build system
itself (In particular, being able to do out-of-tree builds), but lets
not merge the issues together.
~Andrew
prev parent reply other threads:[~2015-09-02 10:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 14:47 [PATCH] x86: wrap kexec feature with CONFIG_KEXEC Jonathan Creekmore
2015-08-27 15:22 ` Jan Beulich
2015-08-27 15:22 ` Andrew Cooper
2015-08-27 15:34 ` Jan Beulich
2015-08-27 15:39 ` Andrew Cooper
2015-08-27 15:27 ` David Vrabel
2015-08-27 15:35 ` Jan Beulich
2015-08-27 15:44 ` Jonathan Creekmore
2015-09-01 10:36 ` Ian Campbell
2015-09-01 10:44 ` Andrew Cooper
2015-09-01 10:54 ` Jan Beulich
2015-09-01 10:59 ` Andrew Cooper
2015-09-01 14:29 ` Jonathan Creekmore
2015-09-01 15:00 ` Jan Beulich
2015-09-01 17:55 ` Jonathan Creekmore
2015-09-02 6:53 ` Jan Beulich
2015-09-02 10:00 ` Andrew Cooper [this message]
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=55E6C8C0.7060308@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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.