From: Andreas Herrmann <andreas.herrmann3@amd.com>
To: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <borislav.petkov@amd.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] x86: urgent fixes for AMD Magny-Cours support
Date: Thu, 3 Sep 2009 09:38:18 +0200 [thread overview]
Message-ID: <20090903073818.GE7216@alberich.amd.com> (raw)
Hi,
so finally I've created a basic set of patches to fix Linux for AMD
Magny-Cours CPU. Basic means no new sysfs attributes, no new cpumasks
etc. Most of it is AMD specific code. Only patch 4 modifies a more
generic x86 function.
I kindly ask to apply these patches for .31 -- even so late in the
game. It should not introduce regressions but allows to run .31 on
Magny-Cours without hiccups.
If it is really too late for .31 it should be scheduled for .32 and I'll try
to bring it into stable-31.
Thanks!
Andreas
--
Operating | Advanced Micro Devices GmbH
System | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
Research | Geschäftsführer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
(OSRC) | Registergericht München, HRB Nr. 43632
next reply other threads:[~2009-09-03 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 7:38 Andreas Herrmann [this message]
2009-09-03 7:40 ` [PATCH 1/4] x86: Fix CPU llc_shared_map information for AMD Magny-Cours Andreas Herrmann
2009-09-03 7:41 ` [PATCH 2/4] x86, cacheinfo: Fixup L3 cache information for AMD multi-node processors Andreas Herrmann
2009-09-03 7:42 ` [PATCH 3/4] x86, mcheck: Use correct cpumask for shared bank4 Andreas Herrmann
2009-09-03 7:44 ` [PATCH 4/4] x86, sched: Workaround broken sched domain creation for AMD Magny-Cours Andreas Herrmann
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=20090903073818.GE7216@alberich.amd.com \
--to=andreas.herrmann3@amd.com \
--cc=borislav.petkov@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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