1. 09 8月, 2005 1 次提交
  2. 27 7月, 2005 1 次提交
  3. 12 7月, 2005 1 次提交
  4. 28 6月, 2005 1 次提交
    • R
      [PATCH] Return probe redesign: ia64 specific implementation · 9508dbfe
      Rusty Lynch 提交于
      The following patch implements function return probes for ia64 using
      the revised design.  With this new design we no longer need to do some
      of the odd hacks previous required on the last ia64 return probe port
      that I sent out for comments.
      
      Note that this new implementation still does not resolve the problem noted
      by Keith Owens where backtrace data is lost after a return probe is hit.
      
      Changes include:
       * Addition of kretprobe_trampoline to act as a dummy function for instrumented
         functions to return to, and for the return probe infrastructure to place
         a kprobe on on, gaining control so that the return probe handler
         can be called, and so that the instruction pointer can be moved back
         to the original return address.
       * Addition of arch_init(), allowing a kprobe to be registered on
         kretprobe_trampoline
       * Addition of trampoline_probe_handler() which is used as the pre_handler
         for the kprobe inserted on kretprobe_implementation.  This is the function
         that handles the details for calling the return probe handler function
         and returning control back at the original return address
       * Addition of arch_prepare_kretprobe() which is setup as the pre_handler
         for a kprobe registered at the beginning of the target function by
         kernel/kprobes.c so that a return probe instance can be setup when
         a caller enters the target function.  (A return probe instance contains
         all the needed information for trampoline_probe_handler to do it's job.)
       * Hooks added to the exit path of a task so that we can cleanup any left-over
         return probe instances (i.e. if a task dies while inside a targeted function
         then the return probe instance was reserved at the beginning of the function
         but the function never returns so we need to mark the instance as unused.)
      Signed-off-by: NRusty Lynch <rusty.lynch@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9508dbfe
  5. 04 5月, 2005 3 次提交
    • T
      [IA64] Fix two warnings introduced by perfmon patches. · a71f62ed
      Tony Luck 提交于
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      a71f62ed
    • S
      [IA64] perfmon & PAL_HALT again · 8df5a500
      Stephane Eranian 提交于
      The pmu_active test is based on the values of PSR.up. THIS IS THE PROBLEM as
      it does not take into account the lazy restore logic which is as follow (simplified):
      
      context switch out:
      	save PMDs
      	clear psr.up
      	release ownership
      
      context switch in:
      	if (ctx->last_cpu == smp_processor_id() && ctx->cpu_activation == cpu_activation) {
      		set psr.up
      		return
      	}
      	restore PMD
      	restore PMC
      	ctx->last_cpu   = smp_processor_id();
      	ctx->activation = ++cpu_activation;
      	set psr.up
      
      The key here is that on context switch out, we clear psr.up and on context switch in
      we check if nobody else used the PMU on that processor since last time we came. In
      that case, we assume the PMD/PMC are ours and we simply reactivate.
      
      The Caliper problem is that between the moment we context switch out and the moment we
      come back, nobody effectively used the PMU BUT the processor went idle. Normally this
      would have no incidence but PAL_HALT does alter the PMU registers.  In default_idle(),
      the test on psr.up is not strong enough to cover this case and we go into PAL which
      trashed the PMU resgisters. When we come back we falsely assume that this is our state
      yet it is corrupted. Very nasty indeed.
      
      To avoid the problem it is necessary to forbid going to PAL_HALT as soon as perfmon
      installs some valid state in the PMU registers. This happens with an application
      attaches a context to a thread or CPU. It is not enough to check the psr/dcr bits.
      Hence I propose the attached patch. It adds a callback in process.c to modify the
      condition to enter PAL on idle. Basically, now it is conditional to pal_halt=1 AND
      perfmon saying it is okay.
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      8df5a500
    • Z
      [IA64] reduce cacheline bouncing in cpu_idle_wait · 7d5f9c0f
      Zwane Mwaikambo 提交于
      Andi noted that during normal runtime cpu_idle_map is bounced around a lot,
      and occassionally at a higher frequency than the timer interrupt wakeup
      which we normally exit pm_idle from.  So switch to a percpu variable.
      
      I didn't move things to the slow path because it would involve adding
      scheduler code to wakeup the idle thread on the cpus we're waiting for.
      Signed-off-by: NZwane Mwaikambo <zwane@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      7d5f9c0f
  6. 23 4月, 2005 1 次提交
    • A
      [IA64] cpu hotplug: return offlined cpus to SAL · b8d8b883
      Ashok Raj 提交于
      This patch is required to support cpu removal for IPF systems. Existing code
      just fakes the real offline by keeping it run the idle thread, and polling
      for the bit to re-appear in the cpu_state to get out of the idle loop.
      
      For the cpu-offline to work correctly, we need to pass control of this CPU 
      back to SAL so it can continue in the boot-rendez mode. This gives the
      SAL control to not pick this cpu as the monarch processor for global MCA
      events, and addition does not wait for this cpu to checkin with SAL
      for global MCA events as well. The handoff is implemented as documented in 
      SAL specification section 3.2.5.1 "OS_BOOT_RENDEZ to SAL return State"
      Signed-off-by: NAshok Raj <ashok.raj@intel.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      b8d8b883
  7. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4