From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: bk pull on ia64 linux tree
Date: Tue, 25 Jan 2005 23:03:03 +0000 [thread overview]
Message-ID: <200501252303.j0PN33A19074@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.11
This will update the files shown below ... the apparently huge change
to ptrace.c is mostly code reformatting to fit in 80 columns.
Thanks!
-Tony
arch/ia64/ia32/ia32_signal.c | 20 -
arch/ia64/ia32/sys_ia32.c | 33 --
arch/ia64/kernel/entry.S | 18 -
arch/ia64/kernel/perfmon.c | 17 -
arch/ia64/kernel/ptrace.c | 687 +++++++++++++++++++++++++------------------
arch/ia64/kernel/signal.c | 9
arch/ia64/kernel/sys_ia64.c | 7
arch/ia64/kernel/traps.c | 76 ++--
arch/ia64/pci/pci.c | 2
include/asm-ia64/unistd.h | 14
10 files changed, 490 insertions(+), 393 deletions(-)
through these ChangeSets:
<tony.luck@intel.com> (05/01/25 1.2031)
[IA64] entry.S: .align in .text sections is broken, use TEXT_ALIGN()
A few reports of illegal instruction panics while trying to boot
were tracked to this. Fix by David Mosberger.
Signed-off-by: Tony Luck <tony.luck@intel.com>
<tony.luck@intel.com> (05/01/25 1.2030)
[IA64] pci_sal_read seg limit is 65535, not 255
Spotted by Andreas Schwab, fix from Matthew Wilcox
and David Mosberger.
Signed-off-by: Tony Luck <tony.luck@intel.com>
<davidm@hpl.hp.com> (05/01/25 1.2029)
[IA64] fix ptrace debug-register handling bug
I noticed that the PTRACE_POKEUSR code incorrectly clears bits 56-58
of _all_ debug registers. The intention was to only clear it for
odd-numbered registers, to ensure that user-level can only set
user-level data/instruction-breakpoints. Patch below fixes this problem.
The patch also replaces explicit clearing of the single-step and
taken-branch PSR bits with a call to ptrace_disable() for PTRACE_KILL.
Signed-off-by: David Mosberger-Tang <davidm@hpl.hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<davidm@hpl.hp.com> (05/01/25 1.2028)
[IA64] clean up pt_regs accesses
This patch replaces the idiom:
func (args..., long stack) {
struct pt_regs *regs = (struct pt_regs *) &stack;
with the more commonly used:
func (args..., struct pt_regs regs) {
The latter didn't used to work with the very earliest kernels and
compilers (anybody remember egcs?) but gcc-3.3 and probably even
gcc-2.96 don't have a problem with it anymore.
The change also makes sparse happier, since it doesn't like it when
you access memory past the end of the declared size of that variable.
Signed-off-by: David Mosberger-Tang <davidm@hpl.hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<tony.luck@intel.com> (05/01/25 1.2027)
[IA64] ptrace.c: Format to make it fit in 80 cols.
David thinks this might make Jesse and Willy happy (or
at least happier). If they can cope with line breaks
before a binary operator, rather than after, then maybe
it will :-)
Signed-off-by: David Mosberger-Tang <davidm@hpl.hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
<kenneth.w.chen@intel.com> (05/01/25 1.2026)
[IA64] Ensure that r9 can't be a NaT on return from sys_pipe()
This version doesn't cost us any extra cycles.
Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
Signed-off-by: Rohit Seth <rohit.seth@intel.com>
Acked-by: David Mosberger <davidm@hpl.hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
next prev parent reply other threads:[~2005-01-25 23:03 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
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 [this message]
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=200501252303.j0PN33A19074@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