From: Glauber Costa <glommer@redhat.com>
To: Gleb Natapov <gleb@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 12:06:22 -0300 [thread overview]
Message-ID: <20090517150622.GN27295@poweredge.glommer> (raw)
In-Reply-To: <20090517143006.GJ3909@redhat.com>
On Sun, May 17, 2009 at 05:30:06PM +0300, Gleb Natapov wrote:
> On Sun, May 17, 2009 at 10:27:41AM -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).
> > Yes, that is what happens. But then, by checking "show hidden devices",
> > the disabled processor appears, but are listed as malfunctioning.
> >
> > Because of this, SVVP tests break without this patch.
> >
> What kind of error?
Message 4/15/2009 4:07:04.635 AM Checking Intel Processor
Error 4/15/2009 4:07:04.635 AM ERROR: Device (QEMU Virtual CPU version 0.9.1)
is not currently enabled, or has some problem
File: Line: 0
Error Type: BOOL
Error Code: 0x1
Error Text: Error 0x00000001
Alternatively, if you go to the device manager, and "Show hidden processors",
you'll see the processors appear, but marked with a "!". Clicking into details,
there is a message saying that the device is malfunctioning.
>
> > > This patch breaks resume from hibernate on windows 2008/vista.
> > Oh god... do you have any idea why?
> >
> > which bits should we set for everything to work?
> Bit 1 should not be set :) What I think is happening windows finds more
> CPUs on resume then it had before hibernate.
It does not make sense to me at first. resume should not be a much different
use case than plain boot. If it does the right thing on bootup, why would it
mess up in case of resume?
next prev parent reply other threads:[~2009-05-17 15:01 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 [this message]
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
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=20090517150622.GN27295@poweredge.glommer \
--to=glommer@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@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