From mboxrd@z Thu Jan 1 00:00:00 1970 From: "KUWAMURA Shin'ya" Subject: Re: removal of ia64 port Date: Fri, 23 Mar 2012 15:52:49 +0900 (JST) Message-ID: <20120323.155249.425911897.kuwa__2795.84319000623$1332485740$gmane$org@jp.fujitsu.com> References: <4F69A3340200007800079D1B@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F69A3340200007800079D1B@nat28.tlf.novell.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: JBeulich@suse.com Cc: xen-ia64-devel@lists.xen.org, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Hi Jan, Thank you for your work on ia64. I am sorry that ia64 remains broken for a long time. >>>>> On Wed, 21 Mar 2012 08:45:24 +0000 >>>>> JBeulich@suse.com("Jan Beulich") said: > > Given that the ia64 port hasn't really been maintained for the last couple > of years (I am apparently the only one to try to keep it building at least, > but I suspect that it has been non-functional for quite a while), I'd like to > propose to remove the port. After quite some time of trying to get an > opinion from Intel on this, I was now notified of their agreement to this > move. > From my pov, the only thing to discuss here is whether this should > happen right away, or after 4.2 went out (then with a formal removal > proposal in that release - the port's state isn't being reflected correctly > anyway in ./MAINTAINERS afaict). I hope that ia64 code remains in xen-unstable for the time being. I am inspecting the problem of hypervisor now. Current ia64 status is: - xen-4.0-testing: work It still work on ia64 with small fixes. I will send patches later. - xen-4.1-testing: probably work with xend - libxl does not work on ia64. - xen-unstable: not work - The hypervisor cannot boot. - It worked on ia64 in October, 2010. Best regards, -- KUWAMURA Shin'ya