From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhenzhong Duan Subject: Re: [PATCH] xen: reuse the same pirq allocated when driver load first time Date: Mon, 13 May 2013 15:44:36 +0800 Message-ID: <519099E4.1070709@oracle.com> References: <518A0A50.1020705@oracle.com> <20130510185339.GD2562@phenom.dumpdata.com> Reply-To: zhenzhong.duan@oracle.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130510185339.GD2562@phenom.dumpdata.com> Sender: linux-kernel-owner@vger.kernel.org To: Konrad Rzeszutek Wilk Cc: Stefano Stabellini , xen-devel@lists.xensource.com, "linux-kernel@vger.kernel.org" , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Yuval Shaia , Feng Jin , Chien Yen List-Id: xen-devel@lists.xenproject.org On 2013-05-11 02:53, Konrad Rzeszutek Wilk wrote: > On Wed, May 08, 2013 at 04:18:24PM +0800, Zhenzhong Duan wrote: >> When driver load and unload in a loop, pirq will exhaust finally. >> Try to use the same pirq which was already mapped and binded at first time > So what happens if I unload and reload two drivers in random order? Same result. In fact, not only pirq exhuast issue, also driver can't be reloaded successfully everytime. When trying to load driver which need to setup msix (ex. mlx4_core) it once succeed and once failed (3rd time succeed, 4th failed etc). zduan