From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: Question about evtchn_callback reentry
Date: Mon, 18 Dec 2006 13:42:19 +0000
Message-ID: <C1AC4B3B.6401%keir@xensource.com>
References: <C1AC2AE2.63DC%keir@xensource.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C1AC2AE2.63DC%keir@xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir@xensource.com>, "Xu, Anthony" <anthony.xu@intel.com>
Cc: xen-devel@lists.xensource.com, xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 18/12/06 11:24, "Keir Fraser" <keir@xensource.com> wrote:

>> If evtchn_callback reentry is allowed.
>> There are 1024 event channels.
>> In theory, dom0 kernal stack may be overflowed.
>> Is there any mechanism to prevent this?
> 
> When running natively there are over 200 vectors available for allocation to
> interrupt sources. In theory the kernel stack may be overflowed, and there
> is no mechanism in Linux to prevent this.

Okay, so I remember now that of course the APIC divides these into 16
priority levels so that does rather restrict the maximum nesting. I'll be
happy to consider adding prioritisation (or just complete disallow of
nesting) for 3.0.5. But I think you should also work to understand the root
cause of the performance drop on ia64.

 -- Keir