From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "alan@linux.intel.com" <alan@linux.intel.com>,
linux-kernel@vger.kernel.org, Len.Brown@intel.com,
Adam Williamson <awilliam@redhat.com>
Subject: Re: [patch] x86: Introduce BOOT_EFI and BOOT_CF9 into the reboot sequence loop
Date: Sat, 01 Mar 2014 06:11:03 +0800 [thread overview]
Message-ID: <53110977.8080907@linux.intel.com> (raw)
In-Reply-To: <5310CBB7.4030407@linux.intel.com>
On 2014/3/1 1:47, H. Peter Anvin wrote:
> On 02/27/2014 10:54 PM, Li, Aubrey wrote:
>> On 2014/2/28 14:44, Matthew Garrett wrote:
>>> On Fri, Feb 28, 2014 at 02:39:56PM +0800, Li, Aubrey wrote:
>>>
>>>> Just let you know, Windows8.1 calls EFI on these boxes for reboot/shutdown.
>>>
>>> Ok, in that case we should add EFI reboot to the list once Matt's 1:1
>>> mapping support has landed. The right place to try it is probably after
>>> the second attempt to perform an ACPI reboot. I'm still not enthusiastic
>>> about adding cf9 by default.
>>>
>>
>> I'll defer to you if no one on the list supports me to add cf9.
>>
>
> I believe we *had* it in the default list for a while, and it caused
> hangs on some systems.
So this can be finalized, add EFI after twice ACPI reboot attempt. I'll
update the bugzilla and the patch.
Thanks,
-Aubrey
>
> -hpa
>
>
next prev parent reply other threads:[~2014-02-28 22:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 4:11 [patch] x86: Introduce BOOT_EFI and BOOT_CF9 into the reboot sequence loop Li, Aubrey
2014-02-28 4:56 ` Matthew Garrett
2014-02-28 5:22 ` Li, Aubrey
2014-02-28 5:56 ` Matthew Garrett
2014-02-28 6:07 ` Li, Aubrey
2014-02-28 6:12 ` Matthew Garrett
2014-02-28 6:20 ` Li, Aubrey
2014-02-28 6:23 ` Matthew Garrett
2014-02-28 6:39 ` Li, Aubrey
2014-02-28 6:44 ` Matthew Garrett
2014-02-28 6:54 ` Li, Aubrey
2014-02-28 17:47 ` H. Peter Anvin
2014-02-28 22:11 ` Li, Aubrey [this message]
2014-02-28 22:16 ` Adam Williamson
2014-03-01 17:10 ` Li, Aubrey
2014-03-01 17:22 ` Matthew Garrett
2014-03-01 17:31 ` Li, Aubrey
2014-03-01 18:19 ` Matthew Garrett
2014-03-01 19:01 ` Matthew Garrett
2014-03-02 0:15 ` Li, Aubrey
2014-03-01 20:06 ` H. Peter Anvin
2014-03-01 20:21 ` Matthew Garrett
2014-03-01 20:26 ` H. Peter Anvin
2014-03-02 0:26 ` Li, Aubrey
2014-03-02 0:33 ` H. Peter Anvin
2014-03-02 1:47 ` Li, Aubrey
2014-03-02 2:07 ` H. Peter Anvin
2014-03-02 2:20 ` Li, Aubrey
2014-03-02 2:23 ` Matthew Garrett
2014-03-02 2:35 ` H. Peter Anvin
2014-03-02 10:39 ` Li, Aubrey
2014-03-02 16:52 ` H. Peter Anvin
2014-03-02 22:13 ` Li, Aubrey
2014-03-02 22:26 ` Matthew Garrett
2014-03-02 22:45 ` Li, Aubrey
2014-03-02 23:11 ` Matthew Garrett
2014-03-02 23:23 ` Li, Aubrey
2014-03-03 0:07 ` Matthew Garrett
2014-03-03 0:18 ` H. Peter Anvin
2014-03-03 1:36 ` Li, Aubrey
2014-03-03 1:47 ` H. Peter Anvin
2014-03-03 1:49 ` Li, Aubrey
2014-03-03 22:11 ` Li, Aubrey
2014-03-02 23:57 ` H. Peter Anvin
2014-03-05 23:39 ` [tip:x86/reboot] x86, reboot: Add EFI and CF9 reboot methods into the default list tip-bot for Li, Aubrey
2014-03-05 23:45 ` [tip:x86/reboot] x86, reboot: Only use CF9_COND automatically, not CF9 tip-bot for H. Peter Anvin
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=53110977.8080907@linux.intel.com \
--to=aubrey.li@linux.intel.com \
--cc=Len.Brown@intel.com \
--cc=alan@linux.intel.com \
--cc=awilliam@redhat.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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