From: "H. Peter Anvin" <hpa@zytor.com>
To: Michael D Labriola <mlabriol@gdeb.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kushal Koolwal <kushalkoolwal@gmail.com>,
linux-kernel@vger.kernel.org, michael.d.labriola@gmail.com,
Ingo Molnar <mingo@elte.hu>,
Matthew Garrett <mjg59@srcf.ucam.org>,
support@versalogic.com, Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org
Subject: Re: [PATCH] x86, reboot: skip DMI checks if reboot set by user
Date: Thu, 19 Jan 2012 11:17:54 -0800 [thread overview]
Message-ID: <4F186C62.6000606@zytor.com> (raw)
In-Reply-To: <OFE1B368BB.B6249713-ON8525798A.00692513-8525798A.0069B44E@gdeb.com>
On 01/19/2012 11:14 AM, Michael D Labriola wrote:
>>
>> Yes, and such a patch would be appreciated.
>>
>> The reason it is as it is dates back to before the 32-64 bit
>> unification, as far as I know.
>>
>> (BIOS reboot is currently not supported on 64 bits, mainly.)
>
> Well, that does complicate it a bit. I'll gin something up and see what
> you think. I guess it will involve having an #ifdef CONFIG_X86_32 block
> inside a single dmi_table structure for the BIOS quirks.
>
> Actually, set_kbd_reboot is inside the current X86_32 only block, along
> with the one DMI callback that uses it. Is this correct?
>
Probably not, although I suspect most of the users of that are 32-bit
only systems.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-01-19 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 15:16 [PATCH] x86, reboot: skip DMI checks if reboot set by user Michael D Labriola
2012-01-17 19:58 ` Alan Cox
2012-01-19 15:32 ` Michael D Labriola
2012-01-19 15:45 ` Alan Cox
2012-01-19 15:48 ` Michael D Labriola
[not found] ` <OF8642E997.5ED041E1-ON8525798A.0056983A-8525798A.0056E05B@LocalDomain>
2012-01-19 17:46 ` Michael D Labriola
2012-01-19 17:52 ` H. Peter Anvin
2012-01-19 19:14 ` Michael D Labriola
2012-01-19 19:17 ` H. Peter Anvin [this message]
2012-01-19 19:34 ` Michael D Labriola
2012-01-19 19:41 ` Ingo Molnar
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=4F186C62.6000606@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kushalkoolwal@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.d.labriola@gmail.com \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=mlabriol@gdeb.com \
--cc=support@versalogic.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox