All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Yinghai Lu <yinghai@kernel.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: [PATCH 0/9] *** SUBJECT HERE ***
Date: Fri, 13 Feb 2009 17:11:58 -0800	[thread overview]
Message-ID: <cover.1234573847.git.jeremy.fitzhardinge@citrix.com> (raw)
In-Reply-To: <cover.1234573847.git.jeremy.fitzhardinge@citrix.com>

From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

*** BLURB HERE ***

Ian Campbell (1):
  xen: pre-initialize legacy irqs early

Jeremy Fitzhardinge (8):
  xen/dom0: handle acpi lapic parsing in Xen dom0
  xen: hook io_apic read/write operations
  xen: create dummy ioapic mapping
  xen: implement pirq type event channels
  x86/io_apic: add get_nr_irqs_gsi()
  xen/apic: identity map gsi->irqs
  xen: direct irq registration to pirq event channels
  xen: bind pirq to vector and event channel

 arch/x86/include/asm/io_apic.h |    7 +
 arch/x86/include/asm/xen/pci.h |   13 ++
 arch/x86/kernel/acpi/boot.c    |   18 +++-
 arch/x86/kernel/io_apic.c      |   37 +++++-
 arch/x86/xen/Kconfig           |   11 ++
 arch/x86/xen/Makefile          |    4 +-
 arch/x86/xen/apic.c            |   57 +++++++++
 arch/x86/xen/enlighten.c       |    2 +
 arch/x86/xen/mmu.c             |   10 ++
 arch/x86/xen/pci.c             |   81 +++++++++++++
 arch/x86/xen/xen-ops.h         |    6 +
 drivers/xen/events.c           |  260 +++++++++++++++++++++++++++++++++++++++-
 include/xen/events.h           |   22 ++++
 13 files changed, 520 insertions(+), 8 deletions(-)
 create mode 100644 arch/x86/include/asm/xen/pci.h
 create mode 100644 arch/x86/xen/apic.c
 create mode 100644 arch/x86/xen/pci.c


       reply	other threads:[~2009-02-14  1:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14  1:11 Jeremy Fitzhardinge [this message]
2009-02-14  1:11 ` [PATCH 1/9] xen/dom0: handle acpi lapic parsing in Xen dom0 Jeremy Fitzhardinge
2009-02-14  1:12 ` [PATCH 2/9] xen: hook io_apic read/write operations Jeremy Fitzhardinge
2009-02-14  2:10   ` Yinghai Lu
2009-02-14  5:32     ` Jeremy Fitzhardinge
2009-02-14  9:12       ` [Xen-devel] " venkatesh k
2009-02-14  1:12 ` [PATCH 3/9] xen: create dummy ioapic mapping Jeremy Fitzhardinge
2009-02-14  1:12 ` [PATCH 4/9] xen: implement pirq type event channels Jeremy Fitzhardinge
2009-02-14  1:12 ` [PATCH 5/9] x86/io_apic: add get_nr_irqs_gsi() Jeremy Fitzhardinge
2009-02-14  1:12 ` [PATCH 6/9] xen/apic: identity map gsi->irqs Jeremy Fitzhardinge
2009-02-14  1:12 ` [PATCH 7/9] xen: direct irq registration to pirq event channels Jeremy Fitzhardinge
2009-02-14  1:12 ` [PATCH 8/9] xen: bind pirq to vector and event channel Jeremy Fitzhardinge
2009-02-14  1:12 ` [PATCH 9/9] xen: pre-initialize legacy irqs early Jeremy Fitzhardinge
  -- strict thread matches above, loose matches on Subject: below --
2009-02-18 22:30 [PATCH 0/9] *** SUBJECT HERE *** Jeremy Fitzhardinge

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=cover.1234573847.git.jeremy.fitzhardinge@citrix.com \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=yinghai@kernel.org \
    /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.