qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] possible_cpus: add CPUArchId::type field
Date: Wed, 10 Jan 2018 14:45:17 -0200	[thread overview]
Message-ID: <20180110164517.GT6646@localhost.localdomain> (raw)
In-Reply-To: <1515597770-268979-1-git-send-email-imammedo@redhat.com>

On Wed, Jan 10, 2018 at 04:22:50PM +0100, Igor Mammedov wrote:
> Remove dependency of possible_cpus on 1st CPU instance,
> which decouples configuration data from CPU instances that
> are created using that data.
> 
> Also later it would be used for enabling early cpu to numa node
> configuration at runtime qmp_query_hotpluggable_cpus() should
> provide a list of available cpu slots at early stage,
> before machine_init() is called and the 1st cpu is created,
> so that mgmt might be able to call it and use output to set
> numa mapping.
> 
> Use MachineClass::possible_cpu_arch_ids() callback to set
> cpu type info, along with the rest of possible cpu properties,
> to let machine define which cpu type* will be used.
> 
> * for SPAPR it will be a spapr core type and for ARM/s390x/x86
>   a respective descendant of CPUClass.
> 
> Move parse_numa_opts() in vl.c after cpu_model is parsed into
> cpu_type so that possible_cpu_arch_ids() would know which
> cpu_type to use during layout initialization.
> 
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

Queued to machine-next, thanks.

-- 
Eduardo

      reply	other threads:[~2018-01-10 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 15:22 [Qemu-devel] [PATCH v3] possible_cpus: add CPUArchId::type field Igor Mammedov
2018-01-10 16:45 ` Eduardo Habkost [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=20180110164517.GT6646@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=imammedo@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).