All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Hoffmann" <jh2000@Root24.eu>
To: <linux-kernel@vger.kernel.org>
Subject: [Patch] panic.c
Date: Sun, 5 Aug 2007 17:28:45 +0200	[thread overview]
Message-ID: <006701c7d775$53137cc0$6800a8c0@jhnotebook> (raw)

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Hello everybody,
(This is the first time i send in a patch, so correct me if I’m doing
something wrong)
This patch causes the cpu to stop instead of using an endless loop (I’m
not sure if this works with the watchdog so please take a review).
The idea behind this is to keep the power usage on panic’d machines
(without auto-reboot) low. Another point is in an Virtual Machine
environment the process of the VM is using 100% of the host-cpu. This
would stuck other programs or VMs. This patch brings the VM to stop and
keeps the cpu usage below 1%.
 
I have tested the patch in an VM, the only change is mdelay(); to
cpu_idle(); it doesn’t need more libs and should have no special
depencies to consider.
The panic-blink doesn’t work further so it might be removed if there is
no better way.
 
Maybe someone has an better idea for this ‘problem’
 
Greetings
Jörg Hoffmann
 

[-- Attachment #2: panic.c.diff --]
[-- Type: application/octet-stream, Size: 260 bytes --]

10a11,15
> 
> /*
>  * Modification History kernel/panic.c
>  * 05/08/07	The Kernel stops the CPU on panic if the reboot= parameter isn't set to keep the cpu/power usage low.	- JÃrg Hoffmann
>  */
22d26
< 
137c141
< 		mdelay(1);
---
> 		cpu_idle();

             reply	other threads:[~2007-08-05 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 15:28 Jörg Hoffmann [this message]
2007-08-05 15:35 ` [Patch] panic.c Jan Engelhardt
2007-08-05 20:14   ` Heiko Carstens

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='006701c7d775$53137cc0$6800a8c0@jhnotebook' \
    --to=jh2000@root24.eu \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.