All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Glauber Costa <glommer@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] Set bit 1 in disabled processor's _STA
Date: Mon, 18 May 2009 08:44:54 +0300	[thread overview]
Message-ID: <4A10F5D6.5060700@redhat.com> (raw)
In-Reply-To: <20090518051718.GL3909@redhat.com>

Gleb Natapov wrote:
> On Sun, May 17, 2009 at 11:07:31PM +0300, Avi Kivity wrote:
>   
>> Gleb Natapov wrote:
>>     
>>> Theoretically we can provide different values for different OSes, but
>>> this is just a guess work since there is no any documentation how CPU
>>> hot-plug should work on x86.
>>>   
>>>       
>> ACPI in fact supports this, but I hope we don't have to do that.
>>
>>     
> ACPI way is what I am talking about. Implement _OS object.
>   

/*
 * The story of _OSI(Linux)
 *
 * From pre-history through Linux-2.6.22,
 * Linux responded TRUE upon a BIOS OSI(Linux) query.
 *
 * Unfortunately, reference BIOS writers got wind of this
 * and put OSI(Linux) in their example code, quickly exposing
 * this string as ill-conceived and opening the door to
 * an un-bounded number of BIOS incompatibilities.
 *
 * For example, OSI(Linux) was used on resume to re-POST a
 * video card on one system, because Linux at that time
 * could not do a speedy restore in its native driver.
 * But then upon gaining quick native restore capability,
 * Linux has no way to tell the BIOS to skip the time-consuming
 * POST -- putting Linux at a permanent performance disadvantage.
 * On another system, the BIOS writer used OSI(Linux)
 * to infer native OS support for IPMI!  On other systems,
 * OSI(Linux) simply got in the way of Linux claiming to
 * be compatible with other operating systems, exposing
 * BIOS issues such as skipped device initialization.
 *
 * So "Linux" turned out to be a really poor chose of
 * OSI string, and from Linux-2.6.23 onward we respond FALSE.
 *
 * BIOS writers should NOT query _OSI(Linux) on future systems.
 * Linux will complain on the console when it sees it, and return FALSE.
 * To get Linux to return TRUE for your system  will require
 * a kernel source update to add a DMI entry,
 * or boot with "acpi_osi=Linux"
 */

// Looks like no real content in this message?

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-05-18  5:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 12:14 [PATCH] Set bit 1 in disabled processor's _STA Glauber Costa
2009-05-17  8:23 ` Gleb Natapov
2009-05-17 13:27   ` Glauber Costa
2009-05-17 14:30     ` Gleb Natapov
2009-05-17 15:06       ` Glauber Costa
2009-05-17 15:21         ` Gleb Natapov
2009-05-17 15:47           ` Glauber Costa
2009-05-18  6:58             ` Gleb Natapov
2009-05-17 14:31   ` Glauber Costa
2009-05-17 14:32     ` Gleb Natapov
2009-05-17 15:07       ` Glauber Costa
2009-05-17 15:30         ` Gleb Natapov
2009-05-17 20:07           ` Avi Kivity
2009-05-18  0:47             ` Glauber Costa
2009-05-18  5:17             ` Gleb Natapov
2009-05-18  5:44               ` Avi Kivity [this message]
2009-05-18  5:53                 ` Gleb Natapov
2009-05-18 11:39                   ` Glauber Costa
2009-05-18 11:40                     ` Gleb Natapov
2009-05-18 12:40                       ` Glauber Costa
2009-05-18 12:42                         ` Gleb Natapov
2009-05-18 12:59                           ` Glauber Costa

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=4A10F5D6.5060700@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.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 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.