summaryrefslogtreecommitdiffstats
path: root/include/asm-xtensa
diff options
context:
space:
mode:
authorJeremy Fitzhardinge <jeremy@xensource.com>2007-07-17 18:37:05 -0700
committerJeremy Fitzhardinge <jeremy@goop.org>2007-07-18 08:47:42 -0700
commite46cdb66c8fc1c8d61cfae0f219ff47ac4b9d531 (patch)
tree7d9cdfef91e69fcfcba762a5a70cd58900308a5b /include/asm-xtensa
parent3b827c1b3aadf3adb4c602d19863f2d24e7cbc18 (diff)
downloadblackbird-op-linux-e46cdb66c8fc1c8d61cfae0f219ff47ac4b9d531.tar.gz
blackbird-op-linux-e46cdb66c8fc1c8d61cfae0f219ff47ac4b9d531.zip
xen: event channels
Xen implements interrupts in terms of event channels. Each guest domain gets 1024 event channels which can be used for a variety of purposes, such as Xen timer events, inter-domain events, inter-processor events (IPI) or for real hardware IRQs. Within the kernel, we map the event channels to IRQs, and implement the whole interrupt handling using a Xen irq_chip. Rather than setting NR_IRQ to 1024 under PARAVIRT in order to accomodate Xen, we create a dynamic mapping between event channels and IRQs. Ideally, Linux will eventually move towards dynamically allocating per-irq structures, and we can use a 1:1 mapping between event channels and irqs. Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com> Signed-off-by: Chris Wright <chrisw@sous-sol.org> Cc: Ingo Molnar <mingo@elte.hu> Cc: Eric W. Biederman <ebiederm@xmission.com>
Diffstat (limited to 'include/asm-xtensa')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud