From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: "Shi, FengX" <fengx.shi@intel.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"matjaz.hegedic@gmail.com" <matjaz.hegedic@gmail.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"Li, Fei" <fei.li@intel.com>,
"xlpang@redhat.com" <xlpang@redhat.com>,
"Gortmaker, Paul (Wind River)" <paul.gortmaker@windriver.com>,
"alex.hung@canonical.com" <alex.hung@canonical.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] reboot: extend delay from 50us to 50ms for CF9 reboot
Date: Thu, 1 Jun 2017 13:59:40 +0100 [thread overview]
Message-ID: <20170601135940.71e1d212@alans-desktop> (raw)
In-Reply-To: <5111FC7902668B47AB76E3967882E2F26AD54985@SHSMSX101.ccr.corp.intel.com>
On Thu, 1 Jun 2017 02:52:32 +0000
"Shi, FengX" <fengx.shi@intel.com> wrote:
> On some emulator system, 50us is not enough to reboot the system
> when write reboot_code to cf9. System will halt there by int3.
Then your emulator is not emulating 8) and you really need to get whoever
is responsible to fix it. If it's some kind of Intel internal emulator
then I don't see why a hack for it belongs upstream either.
You can also use existing boot options to force an EFI, ACPI or BIOS
reboot with a standard kernel so you can deal with your emulator in your
emulator firmware just fine.
> Here extend the delay time from 50us to 50ms.
> Such extension will improve the robustness of reboot,
> without impact to the time of system reboot, which is already triggered by outb.
On a system where a PCI reboot fails you add 50ms before the triple fault
kicks in, so that statement is not true.
Alan
prev parent reply other threads:[~2017-06-01 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 2:52 Shi, FengX
2017-06-01 12:59 ` Alan Cox [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=20170601135940.71e1d212@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=alex.hung@canonical.com \
--cc=fei.li@intel.com \
--cc=fengx.shi@intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matjaz.hegedic@gmail.com \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xlpang@redhat.com \
/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
all inboxes | Powered by JetHome®