From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <jbeulich@novell.com>
Cc: Miguel Boton <mboton.lkml@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: mach_reboot_fixups()
Date: Fri, 7 Mar 2008 09:24:42 +0100 [thread overview]
Message-ID: <20080307082441.GA12150@elte.hu> (raw)
In-Reply-To: <47D103D0.76E4.0078.0@novell.com>
* Jan Beulich <jbeulich@novell.com> wrote:
> Not exactly - when rebooting through EFI or BIOS, the old code didn't
> go through mach_reboot_fixups(), and I think that is the correct
> behavior (albeit, when the EFI path fell back to the triple fault
> mechanism, it should have honored the fixup logic, and I think it is
> more correct that the new code tries the keyboard method first).
> Perhaps the most reasonable way to go is to honor all reboot= settings
> without using the override code first:
> case BOOT_KBD:
> + mach_reboot_fixups(); /* for board specific fixups */
ok, agreed.
> (with the exception that reboot=keyboard will still have the effect of
> honoring the fixups, but I think this is better than further
> complicating the logic).
the fixups are really "emergency exceptions" - for (a very low number
of) broken boards that just cannot reboot via the default BOOT_KBD
method. In that sense it's a small detail how widely we apply the
exceptions - those boards probably wont be rebooted via reboot=bios
[people only use reboot options when they have trouble rebooting].
> In case you want to take this,
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
i modified the patch and added your signoff - thanks,
Ingo
prev parent reply other threads:[~2008-03-07 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 17:02 mach_reboot_fixups() Jan Beulich
2008-03-06 17:43 ` mach_reboot_fixups() Ingo Molnar
2008-03-06 17:49 ` mach_reboot_fixups() Ingo Molnar
2008-03-07 7:58 ` mach_reboot_fixups() Jan Beulich
2008-03-07 8:24 ` Ingo Molnar [this message]
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=20080307082441.GA12150@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mboton.lkml@gmail.com \
--cc=tglx@linutronix.de \
/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.