From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: bk pull on ia64 linux tree
Date: Thu, 30 Sep 2004 16:43:27 +0000 [thread overview]
Message-ID: <200409301643.i8UGhRu27470@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401121658240.14305@evo.osdl.org>
Hi Linus,
please do a
bk pull http://lia64.bkbits.net/linux-ia64-release-2.6.9
This will update the files shown below.
Thanks!
-Tony
arch/ia64/configs/bigsur_defconfig | 1132 ++++++++++++++++++++++++++++++++
arch/ia64/kernel/acpi.c | 3
arch/ia64/kernel/perfmon.c | 6
arch/ia64/sn/kernel/sn2/prominfo_proc.c | 305 +++-----
include/asm-ia64/sn/sn_sal.h | 36 -
5 files changed, 1311 insertions(+), 171 deletions(-)
through these ChangeSets:
<eranian@hpl.hp.com> (04/09/30 1.1960)
[IA64] minor fix to perfmon
change the return value of PFM_CREATE_CONTEXT from
EAGAIN to ENOMEM when the sampling buffer size is
larger than the RLIMIT_MEMLOCK limit of the task.
signed-off-by: Stephane Eranian <eranian@hpl.hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<eranian@hpl.hp.com> (04/09/30 1.1959)
[IA64] perfmon2 fix for TASK_TRACED
fix a problem in pfm_check_task_state() and pfm_task_incompatible()
which was caused by the introduction of the new TASK_TRACED state.
Tool would fail to attach to a process,i.e., PFM_LOAD_CONTEXT would
fail. With the fix perfmon now accepts to operate on tasks which are
in either TASK_STOPPED or TASK_TRACED state. The problem was tracked
down by Alex Williamson from HP who also submitted the patch.
signed-off-by: Stephane Eranian <eranian@hpl.hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<tony.luck@intel.com> (04/09/29 1.1958)
[IA64] SMP systems may not have SRAT, still need to mark node0 online.
This only causes a problem in the -mm tree now, but Zou Nan hai and
Shaohua Li sent me this fix so that SMP systems compiled with the
generic kernel (which turns on NUMA and CPUSETS in -mm) won't hit
a BUG_ON in kernel/cpuset.c guarantee_online_mems() which is called
from acpi_early_init()
Signed-off-by: Tony Luck <tony.luck@intel.com>
<jbarnes@sgi.com> (04/09/29 1.1957)
[IA64] defconfig for Intel bigsur
Here's a defconfig that comes up on my box and has a reasonable set of modules
enabled.
Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<jbarnes@sgi.com> (04/09/29 1.1956)
[IA64-SGI] sn2: serialize access to PROM chips
If we read and write the PROM chips at the same time, as might happen at boot
when salinfo extracts MCA records and a user is checking the PROM revision
in /proc/sgi_prominfo, an MCA might occur, since the PROM chips can't be
accessed that way. This patch fixes the problem for systems with new PROMs
(>= 3.50) by using the SAL to do PROM reads.
Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
next prev parent reply other threads:[~2004-09-30 16:43 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 0:59 bk pull on ia64 linux tree Linus Torvalds
2004-01-13 1:17 ` David Mosberger
2004-01-13 1:36 ` David Mosberger
2004-01-13 16:08 ` Jesse Barnes
2004-01-27 1:37 ` David Mosberger
2004-01-27 10:23 ` Jes Sorensen
2004-01-27 14:49 ` Martin Hicks
2004-01-27 16:22 ` David Mosberger
2004-01-27 21:57 ` David Mosberger
2004-02-11 5:19 ` David Mosberger
2004-02-12 1:05 ` Keith Owens
2004-02-12 1:31 ` David Mosberger
2004-02-13 22:44 ` Andrew Morton
2004-02-13 22:46 ` David Mosberger
2004-02-23 19:12 ` David Mosberger
2004-03-12 5:37 ` David Mosberger
2004-03-17 19:14 ` David Mosberger
2004-03-25 20:30 ` David Mosberger
2004-04-09 16:05 ` David Mosberger
2004-04-23 6:48 ` David Mosberger
2004-04-29 22:21 ` David Mosberger
2004-04-30 17:49 ` David Mosberger
2004-05-03 22:58 ` David Mosberger
2004-05-11 7:02 ` David Mosberger
2004-05-11 7:06 ` Christoph Hellwig
2004-05-11 18:39 ` Jesse Barnes
2004-05-21 21:45 ` David Mosberger
2004-06-05 5:57 ` David Mosberger
2004-06-19 6:58 ` David Mosberger
2004-06-30 0:04 ` David Mosberger
2004-06-30 0:44 ` Peter Chubb
2004-06-30 0:52 ` David Mosberger
2004-06-30 16:23 ` Jesse Barnes
2004-07-06 18:46 ` David Mosberger
2004-07-27 7:19 ` David Mosberger
2004-07-30 21:17 ` Luck, Tony
2004-08-04 22:05 ` Luck, Tony
2004-08-09 18:09 ` Luck, Tony
2004-08-23 21:23 ` tony.luck
2004-09-03 6:05 ` tony.luck
2004-09-09 5:51 ` Luck, Tony
2004-09-13 19:46 ` Luck, Tony
2004-09-16 22:39 ` Luck, Tony
2004-09-21 20:09 ` Luck, Tony
2004-09-22 23:14 ` Luck, Tony
2004-09-23 23:23 ` Luck, Tony
2004-09-28 18:34 ` Luck, Tony
2004-09-30 16:43 ` Luck, Tony [this message]
2004-10-01 16:42 ` Luck, Tony
2004-10-07 22:56 ` Luck, Tony
2004-10-20 0:15 ` Luck, Tony
2004-10-21 0:17 ` Luck, Tony
2004-10-27 3:58 ` Luck, Tony
2004-11-04 0:22 ` Luck, Tony
2004-11-12 17:42 ` Luck, Tony
2005-01-19 18:52 ` Luck, Tony
2005-01-23 3:05 ` Luck, Tony
2005-01-24 16:53 ` Jesse Barnes
2005-01-25 6:30 ` Luck, Tony
2005-01-25 23:03 ` Luck, Tony
2005-03-18 23:30 ` Luck, Tony
-- strict thread matches above, loose matches on Subject: below --
2003-07-28 20:39 David Mosberger
2003-08-16 1:20 ` David Mosberger
2003-09-09 6:43 ` David Mosberger
2003-10-16 22:27 ` David Mosberger
2003-10-17 3:36 ` David Mosberger
2003-10-25 6:44 ` David Mosberger
2003-11-11 0:55 ` David Mosberger
2003-11-11 2:38 ` David Mosberger
2003-11-12 7:18 ` David Mosberger
2003-11-21 22:12 ` David Mosberger
2003-11-26 7:55 ` David Mosberger
2003-12-21 8:05 ` David Mosberger
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=200409301643.i8UGhRu27470@unix-os.sc.intel.com \
--to=tony.luck@intel.com \
--cc=linux-ia64@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox