All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@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>
Subject: Re: Question about evtchn_callback reentry
Date: Mon, 18 Dec 2006 13:42:19 +0000	[thread overview]
Message-ID: <C1AC4B3B.6401%keir@xensource.com> (raw)
In-Reply-To: <C1AC2AE2.63DC%keir@xensource.com>

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

  reply	other threads:[~2006-12-18 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  9:53 Question about evtchn_callback reentry Xu, Anthony
2006-12-18 11:24 ` Keir Fraser
2006-12-18 13:42   ` Keir Fraser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-20 10:08 Xu, Anthony
2006-12-20 10:31 ` Keir Fraser
2006-12-20  3:03 [Xen-devel] " Xu, Anthony
2006-12-20  8:31 ` Keir Fraser
2006-12-18  5:28 [Xen-devel] " Xu, Anthony
2006-12-18  9:31 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C1AC4B3B.6401%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=anthony.xu@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.