public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Please pull x86 tree
Date: Sat, 21 Oct 2006 18:44:06 +0200	[thread overview]
Message-ID: <200610211844.07051.ak@suse.de> (raw)


Linus, please pull from

  git://one.firstfloor.org/home/andi/git/linux-2.6 for-linus

These are all accumulated bug fixes for x86-64 and i386 and should
be all pretty safe.

The only thing that isn't a clear bug fix is the dwarf2 unwinder
speedup -- i'm including that on popular demand because it fixes
a serious performance regression with lockdep.

There are also some reverts included where it turned out that
the change wasn't that great an idea.

Andi Kleen:
      i386: Update defconfig
      x86: Use -maccumulate-outgoing-args
      x86-64: Revert interrupt backlink changes
      i386: Disable nmi watchdog on all ThinkPads
      x86: Revert new unwind kernel stack termination
      x86-64: Revert timer routing behaviour back to 2.6.16 state

Andrew Morton:
      i386: fix .cfi_signal_frame copy-n-paste error

bibo,mao:
      x86-64: x86_64 add NX mask for PTE entry

Corey Minyard:
      x86-64: Fix for arch/x86_64/pci/Makefile CFLAGS

Eric W. Biederman:
      x86-64: Use irq_domain in ioapic_retrigger_irq
      x86-64: Put more than one cpu in TARGET_CPUS

Jan Beulich:
      x86-64: Speed up dwarf2 unwinder
      x86-64: Fix ENOSYS in system call tracing

Jeremy Fitzhardinge:
      i386: Fix fake return address

keith mannthey:
      x86-64: x86_64 hot-add memory srat.c fix

Vivek Goyal:
      x86-64: fix page align in e820 allocator
      x86-64: Overlapping program headers in physical addr space fix

Yinghai Lu:
      x86-64: typo in __assign_irq_vector when updating pos for vector and offset

 Makefile                          |    1 
 arch/i386/Makefile                |    8 +
 arch/i386/defconfig               |   30 ++-
 arch/i386/kernel/head.S           |    2 
 arch/i386/kernel/nmi.c            |   10 +
 arch/i386/kernel/process.c        |    6 -
 arch/x86_64/Makefile              |    4 
 arch/x86_64/kernel/e820.c         |   14 +-
 arch/x86_64/kernel/early-quirks.c |    9 +
 arch/x86_64/kernel/entry.S        |   10 -
 arch/x86_64/kernel/genapic_flat.c |    2 
 arch/x86_64/kernel/io_apic.c      |   15 +-
 arch/x86_64/kernel/vmlinux.lds.S  |    3 
 arch/x86_64/mm/srat.c             |    4 
 arch/x86_64/pci/Makefile          |    2 
 drivers/firmware/dmi_scan.c       |   20 ++
 include/asm-generic/vmlinux.lds.h |   16 ++
 include/asm-x86_64/pgtable.h      |    1 
 include/asm-x86_64/proto.h        |    2 
 include/linux/dmi.h               |    2 
 include/linux/unwind.h            |    2 
 init/main.c                       |    1 
 kernel/unwind.c                   |  318 ++++++++++++++++++++++++++++++++-----
 23 files changed, 385 insertions(+), 97 deletions(-)

             reply	other threads:[~2006-10-21 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21 16:44 Andi Kleen [this message]
2006-10-21 17:51 ` [discuss] Please pull x86 tree Muli Ben-Yehuda
2006-10-21 18:14   ` Andi Kleen
2006-10-21 19:41     ` Muli Ben-Yehuda
2006-10-21 19:56 ` 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=200610211844.07051.ak@suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox