discuss  

Messages by Thread

• [Discuss] [PATCH 0/6] Fix run-time memory leaks and unify process/* clear functions names Sergey Senozhatsky
  • [Discuss] [PATCH 1/6] process/device: Introduce clear_proc_devices() Sergey Senozhatsky
  • [Discuss] [PATCH 2/6] process/timer: Rework clear_timers() to free allocated memory Sergey Senozhatsky
  • [Discuss] [PATCH 3/6] process/work: Rework clear_work() (former delete_all_work()) to free allocated memory. Sergey Senozhatsky
  • [Discuss] [PATCH 4/6] process/process: Introduce clear_processes() function to free allocated memory Sergey Senozhatsky
  • [Discuss] [PATCH 5/6] process/interrupt: Introduce clear_interrupts() function to free allocated memory Sergey Senozhatsky
  • [Discuss] [PATCH 6/6] process/do_process: Use introduced clear_* methods Sergey Senozhatsky
• [Discuss] [PATCH 2/2] lib: style: Pass const references of std::string Sergey Senozhatsky
• [Discuss] (no subject) Sergey Senozhatsky
• [Discuss] [PATCH 1/2] display: style: Pass const references of std::string Sergey Senozhatsky
• [Discuss] [PATCH] Use callback in detect_power_meters() to read /proc/* directory Sergey Senozhatsky
• [Discuss] [PATCH] powertop v1.13 default time Tim
• [Discuss] [PATCH] tuning: don't call wclear/werase on each cursor move Sergey Senozhatsky
  • Re: [Discuss] [PATCH] tuning: don't call wclear/werase on each cursor move Kristen Carlson Accardi
• [Discuss] [PATCH] remove "/sys/class/net/" traverse code duplicate Sergey Senozhatsky
  • Re: [Discuss] [PATCH] remove "/sys/class/net/" traverse code duplicate Kristen Carlson Accardi
• [Discuss] [PATCH] Kill unused `unsigned int i, j' variables in cpudevice::power_usage() Sergey Senozhatsky
• [Discuss] [PATCH] style: Catch exceptions as a reference in ahci::start/end_measurement Sergey Senozhatsky
  • Re: [Discuss] [PATCH] style: Catch exceptions as a reference in ahci::start/end_measurement Kristen Carlson Accardi
  • Re: [Discuss] [PATCH] style: Catch exceptions as a reference in ahci::start/end_measurement Kristen Carlson Accardi
• [Discuss] [PATCH] style: Catch exceptions as a reference in alsa::start/end_measurement Sergey Senozhatsky
• [Discuss] [PATCH] perf_bundle: replace event_names std::vector<char *> with std::map<int, char*> Sergey Senozhatsky
  • Re: [Discuss] [PATCH] perf_bundle: replace event_names std::vector<char *> with std::map<int, char*> Sergey Senozhatsky
• [Discuss] [PATCH] cleanup: kill `linebuf' variable in html_display_cpu_cstates() Sergey Senozhatsky
• [Discuss] [PATCH] cleanup: kill `linebuf' variable in html_display_cpu_pstates() Sergey Senozhatsky
• [Discuss] [PATCH] cleanup: avoid total_pstat_time() call in reset_pstate_data() Sergey Senozhatsky
• [Discuss] [PATCH] cleanup: remove unused `*irqe' in handle_trace_point() Sergey Senozhatsky
• [Discuss] about menu governor menu_select function question？？ wkq5325
• Re: [Discuss] [ANNOUNCE] cpupowerutils - cpufrequtils extended with quite some features Thomas Renninger
• [Discuss] high ticks from i915@pci Karthik Paithankar
  • Re: [Discuss] high ticks from i915@pci Arjan van de Ven
  • Re: [Discuss] high ticks from i915@pci Karthik Paithankar
  • Re: [Discuss] high ticks from i915@pci Sarah Sharp
  • Re: [Discuss] high ticks from i915@pci Karthik Paithankar
  • Re: [Discuss] high ticks from i915@pci Karthik Paithankar
• [Discuss] Why C0 CPUIDLE CORE POLL IDLE ？？ wkq5325
• [Discuss] [announce] Intel BIOS Implementation Test Suite (BITS) Burt Triplett
• [Discuss] patches status update Sergey Senozhatsky
• [Discuss] Powertop-2.0 Kernel config options Arne Klein
  • Re: [Discuss] Powertop-2.0 Kernel config options Keean Schupke
  • Re: [Discuss] Powertop-2.0 Kernel config options Arne Klein
• Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Arjan van de Ven
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Debayan Banerjee
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Debayan Banerjee
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Arjan van de Ven
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Debayan Banerjee
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Arjan van de Ven
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Debayan Banerjee
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Debayan Banerjee
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Tiago Marques
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Debayan Banerjee
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Tiago Marques
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Debayan Banerjee
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Tiago Marques
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Debayan Banerjee
  • Re: [Discuss] Why am I stuck at C0 polling 99% of the time? Tiago Marques
• [Discuss] Powertop-2.0 background Keean Schupke
  • Re: [Discuss] Powertop-2.0 background Auke Kok
  • Re: [Discuss] Powertop-2.0 background Keean Schupke
  • Re: [Discuss] Powertop-2.0 background Tim Barnett
  • Re: [Discuss] Powertop-2.0 background Keean Schupke
  • Re: [Discuss] Powertop-2.0 background Tim Barnett
  • Re: [Discuss] Powertop-2.0 background Jacob Lerenius 73100
• [Discuss] Powertop-2.0 Kernel config options Keean Schupke
  • Re: [Discuss] Powertop-2.0 Kernel config options Sergey Senozhatsky
  • Re: [Discuss] Powertop-2.0 Kernel config options Sergey Senozhatsky
  • Re: [Discuss] Powertop-2.0 Kernel config options Sergey Senozhatsky
  • Re: [Discuss] Powertop-2.0 Kernel config options Keean Schupke
• [Discuss] [PATCH] introduce support for new trace API: cpu_frequency, cpu_idle Sergey Senozhatsky
• [Discuss] multi-core ondemand? wkq5325
  • Re: [Discuss] multi-core ondemand? Arjan van de Ven
  • Re: [Discuss] multi-core ondemand? wkq5325
• [Discuss] mclinux.pdf not found? Sundar
  • Re: [Discuss] mclinux.pdf not found? wkq5325
  • Re: [Discuss] mclinux.pdf not found? Sundar
  • Re: [Discuss] mclinux.pdf not found? wkq5325
• Re: [Discuss] [PATCH 0/3] destroy_tabs: free allocated tabs Arjan van de Ven
  • Re: [Discuss] [PATCH 0/3] destroy_tabs: free allocated tabs Arjan van de Ven
• [Discuss] [PATCH 5/5] tuning: use equals to compare doubles Sergey Senozhatsky
• [Discuss] [PATCH 4/5] devices: use equals to compare doubles Sergey Senozhatsky
• [Discuss] [PATCH 3/5] measurement: use equals to compare doubles Sergey Senozhatsky
  • Re: [Discuss] [PATCH 3/5] measurement: use equals to compare doubles Arjan van de Ven
  • Re: [Discuss] [PATCH 3/5] measurement: use equals to compare doubles Sergey Senozhatsky
  • [Discuss] [PATCH] introduce on-demand tunables list refresh Sergey Senozhatsky
• [Discuss] [PATCH 2/5] process: use equals to compare doubles Sergey Senozhatsky
• [Discuss] [PATCH 1/5] devices: use equals to compare doubles Sergey Senozhatsky
• [Discuss] floating point comparison Sergey Senozhatsky
  • Re: [Discuss] floating point comparison Arjan van de Ven
  • Re: [Discuss] floating point comparison Sergey Senozhatsky
  • [Discuss] [PATCH] floating point comparison Sergey Senozhatsky
  • Re: [Discuss] [PATCH] floating point comparison Arjan van de Ven
  • Re: [Discuss] [PATCH] floating point comparison Sergey Senozhatsky
  • [Discuss] [PATCH] fix `equals' prototype Sergey Senozhatsky
• [Discuss] Announcing the beta release of PowerTOP 2.0 Arjan van de Ven
• [Discuss] [PATCH] fix `conditional jump or move depends on uninitialised value(s)' Sergey Senozhatsky
• [Discuss] /dev/cpu_dma_latency for each process? wkq5325
• [Discuss] [PATCH] init last_waker in power_consumer constructor Sergey Senozhatsky
  • Re: [Discuss] [PATCH] init last_waker in power_consumer constructor Arjan van de Ven
  • Re: [Discuss] [PATCH] init last_waker in power_consumer constructor Sergey Senozhatsky
• [Discuss] [PATCH] init end_level in backlight constructor Sergey Senozhatsky
• [Discuss] The first alpha release for PowerTOP 2.0 Woodruff, Richard
• [Discuss] ACPI on Toshiba Satellite A30-303 Corne van Tonder
• [Discuss] The second alpha of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] The second alpha of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] The second alpha of PowerTOP 2.0 Sergey Senozhatsky
  • Re: [Discuss] The second alpha of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] The second alpha of PowerTOP 2.0 Sergey Senozhatsky
  • Re: [Discuss] The second alpha of PowerTOP 2.0 wkq5325
  • Re: [Discuss] The second alpha of PowerTOP 2.0 Arjan van de Ven
• Re: [Discuss] cpu/*: non-throwing operator new (2) Arjan van de Ven
  • Re: [Discuss] cpu/*: non-throwing operator new (2) Sergey Senozhatsky
  • Re: [Discuss] cpu/*: non-throwing operator new (2) Arjan van de Ven
  • Re: [Discuss] cpu/*: non-throwing operator new (2) Arjan van de Ven
• [Discuss] cpu/* non-throwing new operator Sergey Senozhatsky
• [Discuss] [PATCH] reset_display on intel get_msr error Sergey Senozhatsky
• [Discuss] tick_nohz_get_sleep_length() future sleep time or current sleep? wkq5325
  • Re: [Discuss] tick_nohz_get_sleep_length() future sleep time or current sleep? Arjan van de Ven
  • Re: [Discuss] tick_nohz_get_sleep_length() future sleep time or current sleep? wkq5325
• [Discuss] [PATCH] reset terminal state (resend) Sergey Senozhatsky
  • Re: [Discuss] [PATCH] reset terminal state (resend) Arjan van de Ven
  • Re: [Discuss] [PATCH] reset terminal state (resend) Arjan van de Ven
• [Discuss] Announcing the first alpha release of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Michael Riepe
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Michael Riepe
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Michael Riepe
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Michael Riepe
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Michael Riepe
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Alexander Monakov
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 wkq5325
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Arjan van de Ven
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 wkq5325
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 wkq5325
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 Sergey Senozhatsky
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 wkq5325
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 wkq5325
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 wkq5325
  • Re: [Discuss] Announcing the first alpha release of PowerTOP 2.0 wkq5325
• [Discuss] powertop show multi frequency? wkq5325
  • Re: [Discuss] powertop show multi frequency? Arjan van de Ven
• [Discuss] List with idle-power-consumption of CPU's Paul van der Vlis
  • Re: [Discuss] List with idle-power-consumption of CPU's Auke Kok
  • Re: [Discuss] List with idle-power-consumption of CPU's Paul van der Vlis
  • Re: [Discuss] List with idle-power-consumption of CPU's Auke Kok
  • Re: [Discuss] List with idle-power-consumption of CPU's Stephen Dawson-Haggerty
  • Re: [Discuss] List with idle-power-consumption of CPU's Stephen Dawson-Haggerty
• [Discuss] is Lesswatts only about Intel? Paul van der Vlis
• Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Jean Pihet
  • [Discuss] [PATCH] tracing, perf: add more power related events Jean Pihet
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Jean Pihet
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Jean Pihet
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Jean Pihet
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Jean Pihet
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Jean Pihet
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Arjan van de Ven
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Jean Pihet
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Arjan van de Ven
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
  • Re: [Discuss] [PATCH] tracing, perf: add more power related events Thomas Renninger
• Re: [Discuss] Improving High-Load Performance with the Ondemand Governor [PATCH ATTACHED] Thomas Renninger
• [Discuss] Does scheduler tunables support NUMA? 吴名
  • Re: [Discuss] Does scheduler tunables support NUMA? Suresh Siddha
• Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Thomas Renninger
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Arjan van de Ven
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Arjan van de Ven
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Tiago Marques
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Tiago Marques
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Thomas Renninger
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Tiago Marques
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Len Brown
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Tiago Marques
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Tiago Marques
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Thomas Renninger
  • Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Tiago Marques
• [Discuss] BLTK error in MAKE lakshmanan manan
  • Re: [Discuss] BLTK error in MAKE Shi, Alex
  • Re: [Discuss] BLTK error in MAKE Shi, Alex
• [Discuss] PowerTop: Segmentation fault in dump mode? Cui, Dexuan
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Yang, Chengwei
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Cui, Dexuan
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Auke Kok
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Cui, Dexuan
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Auke Kok
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Cui, Dexuan
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Auke Kok
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Cui, Dexuan
  • Re: [Discuss] PowerTop: Segmentation fault in dump mode? Auke Kok

• Earlier messages
• Later messages