From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.2] pc: acpi: mark all possible CPUs as enabled in SRAT
Date: Fri, 21 Nov 2014 13:38:26 +0100 [thread overview]
Message-ID: <20141121133826.0887182e@nial.usersys.redhat.com> (raw)
In-Reply-To: <1415636450-18674-1-git-send-email-imammedo@redhat.com>
On Mon, 10 Nov 2014 16:20:50 +0000
Igor Mammedov <imammedo@redhat.com> wrote:
> If QEMU is started with -numa ... Windows only notices that
> CPU has been hot-added but it will not online such CPUs.
>
> It's caused by the fact that possible CPUs are flagged as
> not enabled in SRAT and Windows honoring that information
> doesn't use corresponding CPU.
>
> ACPI 5.0 Spec regarding to flag says:
> "
> Table 5-47 Local APIC Flags
> ...
> Enabled: if zero, this processor is unusable, and the operating system
> support will not attempt to use it.
> "
>
> Fix QEMU to adhere to spec and mark possible CPUs as enabled
> in SRAT.
>
> With that Windows onlines hot-added CPUs as expected.
>
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
ping
> ---
> hw/i386/acpi-build.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> index 4003b6b..06499da 100644
> --- a/hw/i386/acpi-build.c
> +++ b/hw/i386/acpi-build.c
> @@ -1269,8 +1269,7 @@ acpi_build_srat_memory(AcpiSratMemoryAffinity *numamem, uint64_t base,
> }
>
> static void
> -build_srat(GArray *table_data, GArray *linker,
> - AcpiCpuInfo *cpu, PcGuestInfo *guest_info)
> +build_srat(GArray *table_data, GArray *linker, PcGuestInfo *guest_info)
> {
> AcpiSystemResourceAffinityTable *srat;
> AcpiSratProcessorAffinity *core;
> @@ -1300,11 +1299,7 @@ build_srat(GArray *table_data, GArray *linker,
> core->proximity_lo = curnode;
> memset(core->proximity_hi, 0, 3);
> core->local_sapic_eid = 0;
> - if (test_bit(i, cpu->found_cpus)) {
> - core->flags = cpu_to_le32(1);
> - } else {
> - core->flags = cpu_to_le32(0);
> - }
> + core->flags = cpu_to_le32(1);
> }
>
>
> @@ -1622,7 +1617,7 @@ void acpi_build(PcGuestInfo *guest_info, AcpiBuildTables *tables)
> }
> if (guest_info->numa_nodes) {
> acpi_add_table(table_offsets, tables->table_data);
> - build_srat(tables->table_data, tables->linker, &cpu, guest_info);
> + build_srat(tables->table_data, tables->linker, guest_info);
> }
> if (acpi_get_mcfg(&mcfg)) {
> acpi_add_table(table_offsets, tables->table_data);
prev parent reply other threads:[~2014-11-21 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 16:20 [Qemu-devel] [PATCH for-2.2] pc: acpi: mark all possible CPUs as enabled in SRAT Igor Mammedov
2014-11-10 17:40 ` Paolo Bonzini
2014-11-10 17:48 ` Igor Mammedov
2014-11-10 17:56 ` Paolo Bonzini
2014-11-10 18:17 ` Michael S. Tsirkin
2014-11-10 18:26 ` Paolo Bonzini
2014-11-10 18:34 ` Michael S. Tsirkin
2014-11-10 18:38 ` Paolo Bonzini
2014-11-11 8:35 ` Igor Mammedov
2014-11-11 11:08 ` Paolo Bonzini
2014-11-11 14:29 ` Igor Mammedov
2014-11-21 12:38 ` Igor Mammedov [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=20141121133826.0887182e@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).