From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Airlie <airlied@linux.ie>
Subject: [GIT PULL] xen.git 2.6.30: xen dom0 apic changes
Date: Tue, 24 Mar 2009 10:42:02 -0700 [thread overview]
Message-ID: <49C91B6A.1090504@goop.org> (raw)
In-Reply-To: <49C915A3.3020809@goop.org>
The following changes since commit 6b36d6251e178636a3c032611948a5c7af44582e:
Jeremy Fitzhardinge (1):
x86: don't need "changed" parameter for set_io_bitmap()
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git push2/xen/dom0/apic
Gerd Hoffmann (2):
xen: set pirq name to something useful.
xen: fix legacy irq setup, make ioapic-less machines work.
Ian Campbell (1):
xen: pre-initialize legacy irqs early
Jeremy Fitzhardinge (13):
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
xen: don't setup acpi interrupt unless there is one
xen: use acpi_get_override_irq() to get triggering for legacy irqs
xen: initialize irq 0 too
xen: dynamically allocate irq & event structures
xen: disable MSI
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/apic/io_apic.c | 37 +++++-
arch/x86/xen/Kconfig | 11 ++
arch/x86/xen/Makefile | 3 +-
arch/x86/xen/apic.c | 60 +++++++++
arch/x86/xen/enlighten.c | 2 +
arch/x86/xen/mmu.c | 10 ++
arch/x86/xen/pci.c | 86 +++++++++++++
arch/x86/xen/xen-ops.h | 6 +
drivers/pci/pci.h | 2 -
drivers/xen/events.c | 273 ++++++++++++++++++++++++++++++++++++++--
include/linux/pci.h | 6 +
include/xen/events.h | 22 ++++
15 files changed, 541 insertions(+), 15 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
next prev parent reply other threads:[~2009-03-24 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 17:17 2.6.30 Xen merge plan (what's in xen.git) Jeremy Fitzhardinge
2009-03-24 17:36 ` [GIT PULL] xen.git 2.6.30: push2/x86/paravirt: preemption in lazy mmu updates Jeremy Fitzhardinge
2009-03-24 17:37 ` [GIT PULL] xen.git 2.6.30: core Xen updates Jeremy Fitzhardinge
2009-03-24 17:39 ` [GIT PULL] xen.git 2.6.30: usermode control interfaces Jeremy Fitzhardinge
2009-03-24 17:40 ` [GIT PULL] xen.git 2.6.30: xen dom0 core support Jeremy Fitzhardinge
2009-03-24 17:42 ` Jeremy Fitzhardinge [this message]
2009-03-24 17:43 ` [GIT PULL] xen.git 2.6.30: xen dom0 PCI device support Jeremy Fitzhardinge
2009-03-24 17:48 ` 2.6.30 Xen merge plan (what's in xen.git) Ingo Molnar
2009-03-24 18:08 ` Jeremy Fitzhardinge
2009-03-24 23:05 ` H. Peter Anvin
2009-03-24 23:28 ` H. Peter Anvin
2009-03-25 5:49 ` Jeremy Fitzhardinge
2009-03-29 15:58 ` 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=49C91B6A.1090504@goop.org \
--to=jeremy@goop.org \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox