LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: What was in the x86 merge for .20
Date: Fri, 8 Dec 2006 04:01:25 +0100	[thread overview]
Message-ID: <200612080401.25746.ak@suse.de> (raw)


[The merge already made it to Linus' tree. Sorry for sending this message
late]

Most of this is for both i386 and x86-64, unless when noted

These are just some high lights. As usual there are more
smaller optimizations, cleanups etc

- paravirt support for i386: the basic hooks for replacing all 
non virtualizable instructions on x86 are in. This currently
only runs on native hardware, but will allow to link in
modules  for paravirtualized Xen/Vmware/lhype.
There are some limitations like no SMP support yet. 
- Support for a Processor Data Area (PDA) on i386. This makes
the code more similar to x86-64 and will allow some other
optimizations in the future. 
- Relocatable kernel support for i386. This allows to load 
a single kernel binary on multiple addresses. This is useful
to use kdump kernels without having to maintain separate
binaries.
- Sleazy FPU feature also supported now on i386 -- this will
give a small improvement to FPU intensive programs because
they have to do  less lazy FPU exceptions.
- When a spinlock lockup occurs print backtraces of all CPUs. This 
makes debugging deadlocks easier
- x86-64 now also spins on spinlocks with interrupts enabled when
possible.
- Various dwarf2 unwinder improvements.
In particular better debugging support for figuring out what's wrong
and the unwinder should be less likely to crash now when it finds
invalid unwinding data.
- Use more efficient cache flushing when cache attributes are changed
- Allow compiling kernel for core2.  To be really useful this
will require gcc support to compile for core2 which isn't ready yet.
- Various fixes to the MTRR code
- Some preparatory infrastructure for perfmon
- Improve TSC setup heuristics on Core2 and AMD K8
- Don't try to synchronize TSCs on boot anymore. Instead just
checks if they are synchronized or not and disable TSC use
when unsynchronized. 
- More fixes to the idle notifier
- Various other bug fixes and cleanups

-Andi 

             reply	other threads:[~2006-12-08  2:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08  3:01 Andi Kleen [this message]
2006-12-08 10:08 ` Andrew Morton
2006-12-08 10:44   ` Ingo Molnar
2006-12-08 16:41   ` Siddha, Suresh B
2006-12-08 17:10     ` Andi Kleen
2006-12-08 18:00       ` Siddha, Suresh B
2006-12-08 20:15         ` [discuss] " Andi Kleen
2006-12-09  8:41         ` Andrew Morton
2006-12-09 18:51           ` Andi Kleen
2006-12-08 17:12   ` Andi Kleen
2006-12-08 12:04 ` Arkadiusz Miskiewicz
2006-12-08 12:51   ` Muli Ben-Yehuda
2006-12-08 13:03     ` Arkadiusz Miskiewicz
2006-12-08 16:34       ` Muli Ben-Yehuda
2006-12-08 18:04       ` Andi Kleen
2006-12-08 18:10         ` Arkadiusz Miskiewicz
2006-12-08 20:07           ` Andi Kleen
2006-12-08 20:36             ` Jeremy Fitzhardinge
2006-12-08 20:35   ` Jeremy Fitzhardinge
2006-12-08 21:06     ` proxy_pda was " Andi Kleen
2006-12-08 21:09       ` Jeremy Fitzhardinge
2006-12-08 21:22         ` Andi Kleen
2006-12-08 21:34           ` Jeremy Fitzhardinge
2006-12-08 22:04           ` Arkadiusz Miskiewicz

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=200612080401.25746.ak@suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: What was in the x86 merge for .20' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).