From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: IRQs, move_in_progress, -EBUSY &c Date: Wed, 11 Aug 2010 16:04:40 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: George Dunlap , "xen-devel@lists.xensource.com" , Jeremy Fitzhardinge , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 11/08/2010 15:56, "George Dunlap" wrote: > However, it seems that moving IRQs is not handled properly. Either > the pvops kernel should retry if it gets an -EBUSY, or the hypercall > should not fail, but wait until it can return success. Move_in_progress is a private hypervisor implementation detail. We shouldn't make it visible to the guest via EBUSY. Worst case we should be turning the retry into a hypercall continuation. Even better if we don't need to make the IRQ bind request wait at all... Not sure why that needs to happen at all. -- Keir > I discovered all this by adding debug statements to the IRQ path; the > patch is attached, if anyone else wants to use it. > > -George