public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Len Brown <lenb@kernel.org>, Matthew Garrett <mjg@redhat.com>,
	Ingo Molnar <mingo@elte.hu>, Avi Kivity <avi@redhat.com>,
	linux-acpi@vger.kernel.org, Len Brown <len.brown@intel.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Attempt rebooting via port CF9 if it seems to be available
Date: Wed, 12 Nov 2008 21:49:10 +0300	[thread overview]
Message-ID: <200811122149.11947.arvidjaar@mail.ru> (raw)
In-Reply-To: <491A225F.4090407@zytor.com>

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

On Wednesday 12 November 2008, H. Peter Anvin wrote:
> Looking at doing the port CF9 fallback, I stumbled onto something fishy.
> 
> I wonder if anyone here happens to have any idea why we turn off
> caching in machine_real_restart()?  Jumping to the BIOS is *not* a
> reset; we jump to the decompressed BIOS on low memory which is usually
> shadowed, not to the BIOS entry point.  In that way, it's more of an
> INIT than a reset, and disabling caching seems broken.
> 
> Either way, here is a preliminary patch to do the CF9 if safe, and then
> falling back to keyboard reboot.  I'm a bit concerned about how to test
> it, of course; this stuff is sensitive and just about impossible to test
> except on millions of machines at once...
> 
> If you have any machines (especially problematic ones) and find that
> this patch either helps or hurts or do nothing, please do let me know so
> I have any idea of the extent of coverage.
> 

Works here both with default and reboot=p.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2008-11-12 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <007e7d616a5d1c2e16ad627d03f8b97799445e71.1226032943.git.len.brown@intel.com>
     [not found] ` <200811080930.21462.arvidjaar@mail.ru>
     [not found]   ` <alpine.LFD.2.00.0811080208590.3092@localhost.localdomain>
     [not found]     ` <200811081050.25477.arvidjaar@mail.ru>
     [not found]       ` <20081108115956.GE8354@elte.hu>
     [not found]         ` <4916B38B.7050905@redhat.com>
     [not found]           ` <4916B4DB.90602@zytor.com>
     [not found]             ` <20081110083938.GD22392@elte.hu>
     [not found]               ` <20081110115732.GA30181@srcf.ucam.org>
     [not found]                 ` <20081110125630.GC28643@elte.hu>
     [not found]                   ` <20081110130029.GC30894@srcf.ucam.org>
     [not found]                     ` <alpine.LFD.2.00.0811111802440.4480@localhost.localdomain>
2008-11-12  0:25                       ` Attempt rebooting via port CF9 if it seems to be available H. Peter Anvin
2008-11-12 18:49                         ` Andrey Borzenkov [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=200811122149.11947.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=hpa@zytor.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mjg@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