linux-kernel - [GIT PULL] x86/xen: Use xen-specific path for interrupt delivery

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <498CD755.5030301@goop.org>
Date:	Fri, 06 Feb 2009 16:35:33 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	the arch/x86 maintainers <x86@...nel.org>,
	Xen-devel <xen-devel@...ts.xensource.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] x86/xen: Use xen-specific path for interrupt delivery

Rather than mapping event channels to vectors and then using the 
vector->irq mapping for interrupt delivery, just cut out the middleman 
and directly map event channels to irqs.  This allows for some more 
cleanups in the event handling code.

The following changes since commit 637f52a7cc5b3ae22354b7e45397375a17d626af:
  Jeremy Fitzhardinge (1):
        x86: unify do_IRQ()

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git jsgf/xen/irq

Jeremy Fitzhardinge (5):
      xen: set irq_chip disable
      xen: use our own eventchannel->irq path
      xen: pack all irq-related info together
      xen: remove irq bindcount
      xen: make sure that softirqs get handled at the end of event processing

 arch/x86/include/asm/xen/events.h |    6 -
 arch/x86/xen/irq.c                |   17 +---
 drivers/xen/events.c              |  224 +++++++++++++++++++++++++------------
 3 files changed, 155 insertions(+), 92 deletions(-)


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/