From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 2/3] Fix CPU hotplug
Date: Wed, 04 Feb 2009 14:45:12 +0200 [thread overview]
Message-ID: <49898DD8.1020609@redhat.com> (raw)
In-Reply-To: <20090204095810.6892.59110.stgit@dhcp-1-237.tlv.redhat.com>
Gleb Natapov wrote:
> 1) Disabled processor's _STA method should return 0 (this fixes Vista's
> BSOD on resuming after hibernate problem)
> 2) Disabled processor's _MAT method should return disabled MADT entry
> instead of 0
> 3) Extend bitmask of hot pluggable CPUs to be 16 bit long
> 4) Generate interrupt only if corespondent EN bit is set
>
Looks like a good idea, but it is really necessary? The guest should be
able to deal with null notifies.
(I'd like to apply this, just want to understand).
> 5) Use reserved STS bits from PIIX4 chipset to avoid clash in the
> future.
>
Please split into separate patches.
> @@ -739,9 +741,29 @@ DefinitionBlock (
>
> Return(0x01)
> }
> +
> Method(_L02) {
> + Store(Zero, Local3)
> + Store(\_PR.PRU, Local2)
> + Xor(Local2, \_PR.PRD, Local0)
> + Store(Local2, \_PR.PRD)
> + Store(\_PR.PRD, Local1)
> + While (LNotEqual (Local0, Zero)) {
> + Store(ShiftLeft(1, Local3), Local1)
> + If (And(Local0, Local1)) {
> + Store(And(Local0, Not(Local1)), Local0)
> + If (And(Local2, Local1)) {
> + Store(1, Local4)
> + } Else {
> + Store(3, Local4)
> + }
> + \_PR.NTFY(Local3, Local4)
> + }
> + Increment(Local3)
> + }
> Return(0x01)
> }
>
Please document this.
> --- a/qemu/hw/acpi.c
> +++ b/qemu/hw/acpi.c
> @@ -578,8 +578,8 @@ void qemu_system_powerdown(void)
> struct gpe_regs {
> uint16_t sts; /* status */
> uint16_t en; /* enabled */
> - uint8_t up;
> - uint8_t down;
> + uint16_t cpus_sts;
> + uint16_t bios_cpus_sts;
> };
>
We'll need to scale this soon.
>
> struct pci_status {
> @@ -603,10 +603,12 @@ static uint32_t gpe_readb(void *opaque, uint32_t addr)
> struct gpe_regs *g = opaque;
> switch (addr) {
> case PROC_BASE:
> - val = g->up;
> - break;
> case PROC_BASE + 1:
> - val = g->down;
> + val = gpe_read_val(g->cpus_sts, addr);
> + break;
> + case PROC_BASE + 2:
> + case PROC_BASE + 3:
> + val = gpe_read_val(g->bios_cpus_sts, addr);
> break;
>
Why can't the bios maintain bios_cpu_sts in RAM?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-02-04 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 9:58 [PATCH 1/3] Fix GPE registers read/write handling Gleb Natapov
2009-02-04 9:58 ` [PATCH 2/3] Fix CPU hotplug Gleb Natapov
2009-02-04 12:45 ` Avi Kivity [this message]
2009-02-04 13:03 ` Gleb Natapov
2009-02-04 13:24 ` Avi Kivity
2009-02-04 13:31 ` Gleb Natapov
2009-02-04 13:35 ` Avi Kivity
2009-02-04 13:36 ` Gleb Natapov
2009-02-04 9:58 ` [PATCH 3/3] PCI hotplug fixes Gleb Natapov
2009-02-04 12:29 ` [PATCH 1/3] Fix GPE registers read/write handling Avi Kivity
2009-02-04 12:39 ` Gleb Natapov
2009-02-04 12:46 ` Avi Kivity
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=49898DD8.1020609@redhat.com \
--to=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