Re: s390 user_enable_single_step() (Was: odd utrace testing results on s390x)

2010-01-06 Thread Heiko Carstens
On Tue, Jan 05, 2010 at 08:58:18PM +0100, Oleg Nesterov wrote:
 I decided to re-test this all with vanilla 2.6.33-rc2. It is really
 amazing how long it takes to recompile/install the kernel!

Then either you have a lot of steal time or an old machine (pre z10)?
You could also try to define more cpus if you have a virtual machine:
#cp define cpu from-to
...that is if your admin gave you permissions to do that.

 I spent
 the rest of this day fighting with this rhts machine. Result - it
 doesn't boot:
 
   00: zIPL v1.8.2-5.el6 interactive boot menu
   00:
   00:  0. default (2.6.33-rc2)
   00:
   00:  1. 2.6.33-rc2
   00:  2. 2.6.32.2-14.s390x.el6.s390x
   00:  3. 2.6.32.2-14.el6.s390x
   00:  4. linux
   00:
   00: Note: VM users please use '#cp vi vmsg input'
   00:
   00: Please choose (default will boot in 15 seconds):
   00: Booting default (2.6.33-rc2)...
Ý0011c4fc¨ sysc_return+0x0/0x8
Ý003cc0c6¨ selinux_sb_copy_data+0x17e/0x238
   (Ý003cbf94¨ selinux_sb_copy_data+0x4c/0x238)
Ý003b62a6¨ security_sb_copy_data+0x4e/0x60
Ý00280338¨ vfs_kern_mount+0x19c/0x1f4
Ý002803de¨ kern_mount_data+0x4e/0x5c
Ý00ae1908¨ devtmpfs_init+0x60/0xbc
Ý00ae1818¨ driver_init+0x28/0x6c
Ý00abe582¨ kernel_init+0x32a/0x3d8
Ý0010b8c2¨ kernel_thread_starter+0x6/0xc
Ý0010b8bc¨ kernel_thread_starter+0x0/0xc
   INFO: lockdep is turned off.
   00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000  
 00114BD4
 
 Cai, any chance you can help? Using /usr/bin/console I can't choose another
 kernel at the 00: Please choose (default will boot in 15 seconds): stage,
 how can I do this???

You did enter something like
#cp vi vmsg 2
and not just '2'?



Re: s390: stepping PT_PTRACED (Was: utrace failed to compile for s390x)

2009-12-09 Thread Heiko Carstens
On Wed, Dec 09, 2009 at 08:54:28PM +0100, Oleg Nesterov wrote:
 (add cc's)
 
 On 12/03, Roland McGrath wrote:
 
   Not sure what should we do right now, s390 needs more attention.
   Also, it uses PT_PTRACED bit, I am afraid this is not what we wan
   with utrace.
 
  This looks simple.  Its one use can just be
  tracehook_consider_fatal_signal(SIGTRAP) instead.  I expect you can just
  send that change to the s390 maintainers and they will take it.
 
 Done.
 
 But... I tried to understand these check and failed. Why do we need them?
 They look unneeded to me, but of course I know nothing about s390.

Could be. I tried to figure out when and why this was added. But looks
like this is 10 year old code.