From: "Gémes Géza" <geza.gemes@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>, George Dunlap <george.dunlap@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: raisin and minios stubdom
Date: Fri, 7 Apr 2017 20:29:45 +0200 [thread overview]
Message-ID: <941ed525-bbf3-9b6e-94a0-935480d45d25@gmail.com> (raw)
In-Reply-To: <20170403120121.sk4q6cqbogvjnaii@citrix.com>
2017-04-03 14:01 keltezéssel, Wei Liu írta:
> On Mon, Apr 03, 2017 at 12:17:08PM +0100, George Dunlap wrote:
>> On Mon, Mar 27, 2017 at 8:28 PM, Gémes Géza <geza.gemes@gmail.com> wrote:
>>> Hi,
>>>
>>> Currently the xen build system has optional support for building a minios
>>> (+needed libraries and tools) based stubdom.
>>>
>>> What is your opinion about moving support for building this into raisin and
>>> once that is stable drop support in the xen build system?
>> This was actually the original purpose of raisin: to allow a framework
>> for simply building all related components of a Xen system without
>> requiring *everything* to be built in-tree with make. The thing that
>> triggered Stefano to write raisin was the availability of grub-xen
>> (building grub upstream as a PV target) -- there was resistance to
>> putting Yet Another Thing in the tree.
>>
>> But the fact is it hasn't gotten much up-take with developers, and I
>> think you're the first user to give significant feedback on it. As
>> you can see, many people prefer to have everything built under one
>> umbrella.
>>
>> Logically it makes sense to *either* do things one way (make
>> everything under xen.git) or the other way (make only xen and tools
>> under xen.git, and use a tool like raisin to build everything else).
>> But as a community we haven't been able to agree on either one, and so
>> the status quo -- most things built under xen.git but nothing *new* --
>> continues.
>>
>> In the meantime, there's no reason not to do both. A normal "make" in
>> xen.git will build you a qemu, qemu-traditional, seabios, &c; raisin
>> disables that and builds everything separately. The plan was always
>> to do the same thing for minios; nobodys had time to work on it yet.
>>
> You would be surprised by the patches I had written in the past year.
> ;-)
>
> Gémes, please check out
>
> git://xenbits.xen.org/people/liuw/xen.git wip.split-stubdom-v2
> git://xenbits.xen.org/people/liuw/stubdom.git wip.split-stubdom-v2
>
> They were a bit old, but if you want to start working on that, feel free
> to take what you need.
>
> Wei.
Hi Wei,
Thank you! I'll definitely start by looking at those. Sorry for being
slow in answering, unfortunately I'm quite busy nowadays with my job,
which is unfortunately not Xen related.
Cheers.
Geza
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-04-07 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 19:28 raisin and minios stubdom Gémes Géza
2017-03-27 19:38 ` Konrad Rzeszutek Wilk
2017-03-30 17:42 ` Gémes Géza
2017-03-31 14:05 ` Konrad Rzeszutek Wilk
2017-03-31 14:15 ` Juergen Gross
2017-04-01 6:19 ` Géza Gémes
2017-04-01 18:00 ` Gémes Géza
2017-04-03 5:20 ` Juergen Gross
2017-04-07 18:54 ` Géza Gémes
2017-04-10 5:05 ` Juergen Gross
2017-04-19 23:33 ` Stefano Stabellini
2017-04-03 11:17 ` George Dunlap
2017-04-03 12:01 ` Wei Liu
2017-04-07 18:29 ` Gémes Géza [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=941ed525-bbf3-9b6e-94a0-935480d45d25@gmail.com \
--to=geza.gemes@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).