1. 05 10月, 2010 3 次提交
  2. 18 8月, 2010 1 次提交
    • D
      Make do_execve() take a const filename pointer · d7627467
      David Howells 提交于
      Make do_execve() take a const filename pointer so that kernel_execve() compiles
      correctly on ARM:
      
      arch/arm/kernel/sys_arm.c:88: warning: passing argument 1 of 'do_execve' discards qualifiers from pointer target type
      
      This also requires the argv and envp arguments to be consted twice, once for
      the pointer array and once for the strings the array points to.  This is
      because do_execve() passes a pointer to the filename (now const) to
      copy_strings_kernel().  A simpler alternative would be to cast the filename
      pointer in do_execve() when it's passed to copy_strings_kernel().
      
      do_execve() may not change any of the strings it is passed as part of the argv
      or envp lists as they are some of them in .rodata, so marking these strings as
      const should be fine.
      
      Further kernel_execve() and sys_execve() need to be changed to match.
      
      This has been test built on x86_64, frv, arm and mips.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Tested-by: NRalf Baechle <ralf@linux-mips.org>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      d7627467
  3. 14 8月, 2010 1 次提交
  4. 05 8月, 2010 17 次提交
  5. 27 7月, 2010 3 次提交
  6. 06 7月, 2010 11 次提交
  7. 22 5月, 2010 2 次提交
    • K
      MIPS: nofpu and nodsp only affect CPU0 · 0103d23f
      Kevin Cernekee 提交于
      The "nofpu" and "nodsp" kernel command line options currently do not
      affect CPUs that are brought online later in the boot process or
      hotplugged at runtime.  It is desirable to apply the nofpu/nodsp options
      to all CPUs in the system, so that surprising results are not seen when
      a process migrates from one CPU to another.
      
      [Ralf: Moved definitions of mips_fpu_disabled, fpu_disable,
      mips_dsp_disabled and dsp_disable from setup.c to cpu-probe.c to allow
      making mips_fpu_disabled and mips_dsp_disabled static.]
      Signed-off-by: NKevin Cernekee <cernekee@gmail.com>
      Cc: linux-mips@linux-mips.org
      Cc: linux-kernel@vger.kernel.org
      Patchwork: http://patchwork.linux-mips.org/patch/1169/Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      0103d23f
    • J
      MIPS: Use set_cpus_allowed_ptr · ed1bbdef
      Julia Lawall 提交于
      From: Julia Lawall <julia@diku.dk>
      
      Use set_cpus_allowed_ptr rather than set_cpus_allowed.
      
      The semantic patch that makes this change is as follows:
      (http://coccinelle.lip6.fr/)
      
      // <smpl>
      @@
      expression E1,E2;
      @@
      
      - set_cpus_allowed(E1, cpumask_of_cpu(E2))
      + set_cpus_allowed_ptr(E1, cpumask_of(E2))
      
      @@
      expression E;
      identifier I;
      @@
      
      - set_cpus_allowed(E, I)
      + set_cpus_allowed_ptr(E, &I)
      // </smpl>
      Signed-off-by: NJulia Lawall <julia@diku.dk>
      To: peterz@infradead.org
      To: mingo@elte.hu
      To: tglx@linutronix.de
      To: oleg@redhat.com
      To: linux-mips@linux-mips.org
      To: linux-kernel@vger.kernel.org
      To: kernel-janitors@vger.kernel.org
      Patchwork: http://patchwork.linux-mips.org/patch/1087/Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      ed1bbdef
  8. 21 5月, 2010 2 次提交
    • J
      mips,kgdb: kdb low level trap catch and stack trace · 5dd11d5d
      Jason Wessel 提交于
      The only way the debugger can handle a trap in inside rcu_lock,
      notify_die, or atomic_notifier_call_chain without a recursive fault is
      to have a low level "first opportunity handler" do_trap_or_bp() handler.
      
      Generally this will be something the vast majority of folks will not
      need, but for those who need it, it is added as a kernel .config
      option called KGDB_LOW_LEVEL_TRAP.
      
      Also added was a die notification for oops such that kdb can catch an
      oops for analysis.
      
      There appeared to be no obvious way to pass the struct pt_regs from
      the original exception back to the stack back tracer, so a special
      case was added to show_stack() for when kdb is active because you
      generally desire to generally look at the back trace of the original
      exception.
      Signed-off-by: NJason Wessel <jason.wessel@windriver.com>
      Acked-by: NRalf Baechle <ralf@linux-mips.org>
      5dd11d5d
    • J
      kgdb: core changes to support kdb · dcc78711
      Jason Wessel 提交于
      These are the minimum changes to the kgdb core in order to enable an
      API to connect a new front end (kdb) to the debug core.
      
      This patch introduces the dbg_kdb_mode variable controls where the
      user level I/O is routed.  It will be routed to the gdbstub (kgdb) or
      to the kdb front end which is a simple shell available over the kgdboc
      connection.
      
      You can switch back and forth between kdb or the gdb stub mode of
      operation dynamically.  From gdb stub mode you can blindly type
      "$3#33", or from the kdb mode you can enter "kgdb" to switch to the
      gdb stub.
      
      The logic in the debug core depends on kdb to look for the typical gdb
      connection sequences and return immediately with KGDB_PASS_EVENT if a
      gdb serial command sequence is detected.  That should allow a
      reasonably seamless transition between kdb -> gdb without leaving the
      kernel exception state.  The two gdb serial queries that kdb is
      responsible for detecting are the "?" and "qSupported" packets.
      
      CC: Ingo Molnar <mingo@elte.hu>
      Signed-off-by: NJason Wessel <jason.wessel@windriver.com>
      Acked-by: NMartin Hicks <mort@sgi.com>
      dcc78711