From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: bk pull on ia64 linux tree
Date: Thu, 16 Sep 2004 22:39:11 +0000 [thread overview]
Message-ID: <200409162239.i8GMdBM01917@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/Kconfig | 6
arch/ia64/kernel/minstate.h | 6
arch/ia64/sn/kernel/sn2/Makefile | 2
arch/ia64/sn/kernel/sn2/prominfo_proc.c | 2
arch/ia64/sn/kernel/sn2/sn_hwperf.c | 652 ++++++++++++++++++++++++++++++++
arch/ia64/sn/kernel/sn2/sn_proc_fs.c | 7
include/asm-ia64/mca_asm.h | 3
include/asm-ia64/sn/sn2/sn_hwperf.h | 218 ++++++++++
include/asm-ia64/sn/sn_sal.h | 18
9 files changed, 905 insertions(+), 9 deletions(-)
through these ChangeSets:
<markgw@sgi.com> (04/09/16 1.1867.3.7)
[IA64] SGI Altix hardware performance monitoring API
The SGI Altix PROM supports a SAL call for performance monitoring and for
exporting NUMA topology. We need this in community kernels for diagnostic
and performance tools to use, especially on very large machines.
This patch registers a dynamic misc device "sn_hwperf" that supports an
ioctl interface for reading/writing memory mapped registers on Altix
nodes and routers via the new SAL call. It also creates a read-only
procfs file "/proc/sgi_sn/sn_topology" to export NUMA topology and Altix
hardware inventory.
> What tools are using this?
Performance Co-Pilot http://oss.sgi.com/projects/pcp in particular,
pmshub, shubstats and linkstat. Numerous other users include anything
that needs knowledge of numa topology/interconnect in order to perform
well, e.g. mpt. BTW I have not exported any API functions .. at this
point I don't think we need any modules to call the API.
Signed-off-by: Mark Goodwin <markgw@sgi.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<jbarnes@sgi.com> (04/09/16 1.1867.3.6)
[IA64] Kconfig: Add help text for IA64_SGI_SN2 config option.
Mark Goodwin suggested that we document our platform a bit. This patch adds
help text for the sn2 specific kernel option.
Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<kaos@sgi.com> (04/09/16 1.1867.3.5)
[IA64] ar.k[56] have virtual addresses already, don't convert
r.k[56] used to contain physical addresses but now contain virtual
addresses. There are code remnants which still believe that they are
physical and "convert" ar.k[56] to virtual. This breaks when current
is not in region 7 (e.g. the idle task on cpu 0).
Signed-off-by: Keith Owens <kaos@sgi.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<jbarnes@sgi.com> (04/09/15 1.1867.3.4)
[IA64-SGI]: fix `qw' might be used uninitialized warning
The compiler has no way of knowing whether nentries will be greater than 0, so
it was generating a warning that qw might be used uninitialized. Fix it by
explicitly setting it to 0. Cc'ing Brian in case he has an internal version
he'd like to keep in sync.
Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<tony.luck@intel.com> (04/09/15 1.1803.151.8)
[IA64] make INIT dump work again
current can be in region 5, use 'tpa' to convert to physical
Signed-off-by: Tony Luck <tony.luck@intel.com>
next prev parent reply other threads:[~2004-09-16 22:39 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 [this message]
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
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=200409162239.i8GMdBM01917@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