From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: [PATCH 4/9] raisin: add a component to build qemu_traditional Date: Wed, 15 Apr 2015 17:11:53 +0100 Message-ID: References: <1429110900-8286-4-git-send-email-stefano.stabellini@eu.citrix.com> <552E832A.9020900@citrix.com> <552E8870.6020302@citrix.com> <1429113529.15516.344.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1429113529.15516.344.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: george.dunlap@eu.citrix.com, Andrew Cooper , xen-devel@lists.xensource.com, Ian Jackson , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Wed, 15 Apr 2015, Ian Campbell wrote: > On Wed, 2015-04-15 at 16:49 +0100, Andrew Cooper wrote: > > >> It would be nice if there was a --wtih-system-qemu-trad= option, but > > >> that has been looked upon unfavourably by the maintainers. > > > Thanks for feedback!! > > > I think Raisin needs something like --with-system-qemu-trad=, so if Xen > > > doesn't provide it, we'll have to carry a patch in Raisin to do it. > > > > > > Do you have a link to the discussion or previously rejected patch? > > > > I am not sure that there was ever a patch - it may have been a > > discussion I had with ijc in person. > > Possibly I can't remember myself either. > > > I would be +1 for a --with-system-qemu-trad= option to mirror the > > --with-system-qemu, especially as I am now not the only advocate of one. > > In a pre-raisin world I suppose I thought it didn't make too much sense > to go through that churn if we weren't going to stop _all_ > cloning/downloading from within xen.git. > > Personally I would have considered qemu-trad very much part of the long > tail wrt moving things out of xen.git, but anyway. > > I'd like to see raisin used/supported by osstest before we start > accepting thoe sorts of xen.git patches being suggested here. I think we'll have to carry those patches in Raisin anyway, otherwise how are we supposed to be able to build xen 4.5? I don't think is reasonable to be able to build only 4.6 onward. > (I also think osstest support is a prerequisite for saying it is an > officially support XenProject thing, but that's offtopic in this > context) I spoke with IanJ and he didn't seem too keen on adding raisin support to osstest before raisin could build everything out of tree. That's way I started tackling qemu and qemu-traditional.