public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH] Set bit 1 in disabled processor's _STA
Date: Sun, 17 May 2009 18:30:22 +0300	[thread overview]
Message-ID: <20090517153022.GB21386@redhat.com> (raw)
In-Reply-To: <20090517150727.GO27295@poweredge.glommer>

On Sun, May 17, 2009 at 12:07:27PM -0300, Glauber Costa wrote:
> On Sun, May 17, 2009 at 05:32:35PM +0300, Gleb Natapov wrote:
> > On Sun, May 17, 2009 at 11:31:07AM -0300, Glauber Costa wrote:
> > > On Sun, May 17, 2009 at 11:23:47AM +0300, Gleb Natapov wrote:
> > > > On Fri, May 15, 2009 at 08:14:43AM -0400, Glauber Costa wrote:
> > > > > This patch sets bits 1 in disabled processor's _STA.
> > > > > According to the ACPI spec, this bit means:
> > > > >  "Set if the device is enabled and decoding its resources."
> > > > > 
> > > > > Without it, Windows 2008 device manager shows the processors
> > > > > as malfunctioning hardware.
> > > > > 
> > > > If you uncheck "show hidden devices" option in View menu of the
> > > > device manager you should see only enabled CPUs (bit 2 of _STA).
> > > > This patch breaks resume from hibernate on windows 2008/vista.
> > > 
> > > The last change on that piece of code was made by you under the comment:
> > > 
> > >      1) Disabled processor's _STA method should return 0 (this fixes Vista's
> > >         BSOD on resuming after hibernate problem)
> > > 
> > > However, you did not changed it to 0, but to 9 instead. What did you meant?
> > > 
> > I wrote commit message before changing it to 9 :( I don't remember why I
> > changed it to 9, but I think it was because of Linux CPU hot-plug.
> > 
> > > It appears that windows won't accept bit 0 without bit 1 being set.
> > > 
> > > However, it works fine in my use case if _STA returns 0 or 8. The only real
> > > problem is, as I said, setting bit 0 but not bit 1. Does any among 0 or 8
> > > works for your hibernate use case?
> > Can you check Linux cpu hot-plug please.
> Yeah, unfortunately neither work for linux cpu hotplug. Anything without bit 0 set
> won't work. So valid values appear to be 0x1, 0x3, 0x9, 0xB.
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.

--
			Gleb.

  reply	other threads:[~2009-05-17 15:30 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 [this message]
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
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=20090517153022.GB21386@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox