From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [Patch] continue_hypercall_on_cpu rework using tasklets Date: Tue, 13 Apr 2010 15:49:52 +0200 Message-ID: <4BC47680.60700@ts.fujitsu.com> References: <4BC46F58.3030805@ts.fujitsu.com> <4BC4908B020000780003A008@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BC4908B020000780003A008@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Jan Beulich wrote: >>>> Juergen Gross 13.04.10 15:19 >>> >> cpupools are using continue_hypercall_on_cpu, but this function is defined for >> x86 only, not for ia64. I see 2 possible solutions: >> >> 1. make continue_hypercall_on_cpu available on ia64, too >> 2. make cpupools a pure x86 feature > > Is there anything meaningful in the new code that's really x86-specific > (i.e. can't the whole code chunk be moved to xen/common/)? My main concern is the difference in the handling of schedule_tail. I just can't tell how to change the ia64 variant to make it work correctly. The other x86-specific part is the setting of the return register, but this is rather easy doable by using an architecture specific macro. Juergen -- Juergen Gross Principal Developer Operating Systems TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com Domagkstr. 28 Internet: ts.fujitsu.com D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html