From patchwork Tue Aug 16 03:07:41 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dou Liyang X-Patchwork-Id: 659469 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from lists.gnu.org (lists.gnu.org [IPv6:2001:4830:134:3::11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3sCy504Kmlz9t1v for ; Tue, 16 Aug 2016 13:09:23 +1000 (AEST) Received: from localhost ([::1]:39794 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bZUki-0002LP-K5 for incoming@patchwork.ozlabs.org; Mon, 15 Aug 2016 23:09:20 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57249) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bZUk3-00023m-Nc for qemu-devel@nongnu.org; Mon, 15 Aug 2016 23:08:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bZUjz-0007vi-HN for qemu-devel@nongnu.org; Mon, 15 Aug 2016 23:08:38 -0400 Received: from [59.151.112.132] (port=49829 helo=heian.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bZUjy-0007vB-C5 for qemu-devel@nongnu.org; Mon, 15 Aug 2016 23:08:35 -0400 X-IronPort-AV: E=Sophos;i="5.22,518,1449504000"; d="scan'208";a="9955776" Received: from unknown (HELO cn.fujitsu.com) ([10.167.33.5]) by heian.cn.fujitsu.com with ESMTP; 16 Aug 2016 11:08:30 +0800 Received: from G08CNEXCHPEKD03.g08.fujitsu.local (unknown [10.167.33.85]) by cn.fujitsu.com (Postfix) with ESMTP id C56CF42BC503; Tue, 16 Aug 2016 11:08:28 +0800 (CST) Received: from localhost.localdomain.localdomain (10.167.226.106) by G08CNEXCHPEKD03.g08.fujitsu.local (10.167.33.89) with Microsoft SMTP Server (TLS) id 14.3.279.2; Tue, 16 Aug 2016 11:08:26 +0800 From: Dou Liyang To: Date: Tue, 16 Aug 2016 11:07:41 +0800 Message-ID: <1471316861-5248-1-git-send-email-douly.fnst@cn.fujitsu.com> X-Mailer: git-send-email 2.5.5 MIME-Version: 1.0 X-Originating-IP: [10.167.226.106] X-yoursite-MailScanner-ID: C56CF42BC503.A2938 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: douly.fnst@cn.fujitsu.com X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 59.151.112.132 Subject: [Qemu-devel] [PATCH v4] docs: add cpu-hotplug.txt X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Dou Liyang , drjones@redhat.com, ehabkost@redhat.com, armbru@redhat.com, bharata@linux.vnet.ibm.com, imammedo@redhat.com, david@gibson.dropbear.id.au Errors-To: qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org Sender: "Qemu-devel" This document describes how to use cpu hotplug in QEMU. Signed-off-by: Andrew Jones Signed-off-by: Dou Liyang --- Change log v3 -> v4 From David's advice 1. add spapr examples 2. Fix some comment From drew's advice 1. Fix some syntax Change log v2 -> v3: From drew's advice: 1. modify the examples. 2. Fix some syntax. Change log v1 -> v2: From Fam's advice: 1. Fix some comment. Change log v1: From Igor's advice: 1. Remove any mentioning of apic-id from the document. 2. Remove the "device_del qom_path" from the CPU hot-unplug. 3. Fix some comment. docs/cpu-hotplug.txt | 132 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 132 insertions(+) create mode 100644 docs/cpu-hotplug.txt diff --git a/docs/cpu-hotplug.txt b/docs/cpu-hotplug.txt new file mode 100644 index 0000000..0c1bfe9 --- /dev/null +++ b/docs/cpu-hotplug.txt @@ -0,0 +1,132 @@ +QEMU CPU hotplug +================ + +This document explains how to use the CPU hotplug feature in QEMU, +which regards the CPU as a device, using -device/device_add and +device_del. + +QEMU support was merged for 2.7. + +Guest support is required for CPU hotplug to work. + +CPU hot-plug +------------ + +In order to be able to hotplug CPUs, QEMU has to be told the maximum +number of CPUs which the guest can have. This is done at startup time +by means of the -smp command-line option, which has the following +format: + + -smp [cpus=]n[,maxcpus=cpus][,cores=cores][,threads=threads] + [,sockets=sockets] + +Where, + + - "cpus" sets the number of CPUs to 'n' [default=1]. + - "maxcpus" sets the maximum number of CPUs, including offline VCPUs + for hotplug. + - "sockets" sets the number of discrete sockets in the system. + - "cores" sets the number of CPU cores on one socket. + - "threads" sets the number of threads on one CPU core. + +For example, the following command-line: + + qemu [...] -smp 3,maxcpus=8,sockets=2,cores=2,threads=2 + +creates a guest with 3 VCPUs and supports up to 8 VCPUs. The CPU +topology is sockets (2) * cores (2) * threads (2) and can't be +greater than maxcpus. When the guest finishes loading, the guest +will see 3 VCPUs. More on this below. + +Query available CPU objects +--------------------------- + +To add a VCPUs, it must be identified by socket-id, core-id, and/or +thread-id parameters. + +Before adding the VCPUs, we should know those topology parameters, +so that we can find the available location (socket,core,thread) for +a new VCPU. + +Using the corresponding HMP command "info hotpluggable-cpus" to obtain +them. + +For example, the following command-line: + + (qemu) info hotpluggable-cpus + +lists the hotpluggable CPUs including "CPUInstance Properties" for +hotplugging. Such as this: + + ... + type: "qemu64-x86_64-cpu" + vcpus_count: "1" + CPUInstance Properties: + socket-id: "0" + core-id: "1" + thread-id: "0" + ... + +Or + + ... + type: "POWER7_v2.3-spapr-cpu-core" + vcpus_count: "1" + CPUInstance Properties: + core-id: "2" + ... + +Different platforms may have different "CPUInstance Properties". + +Hotplug CPUs +------------ + +A monitor command can be used to hotplug CPUs: + + - "device_add": creates a CPU device and inserts it into the + specific location. + +For example, the following command adds a VCPU, which has the id cpu1, +to a specific location in the topology (socket=0,core=1,thread=1): + + (qemu) device_add qemu64-x86_64-cpu,id=cpu1,socket-id=0,core-id=1,thread-id=1 + +Where, + + - "qemu64-x86_64-cpu" is the CPU model. + - "id" is the unique identifier in the device set. + - "socket-id/core-id/thread-id" represent the designated location, + which is obtained form the above possible list of CPUs. + +It's also possible to start a guest with a cpu cold-plugged into a +specific location (socket,core,thread). + +In the following command line example, a guest which has 3 VCPUs is +created: + + qemu [...] -smp 1,maxcpus=8,sockets=2,cores=2,threads=2 \ + -device qemu64-x86_64-cpu,id=cpu1,socket-id=1, \ + core-id=1,thread-id=0 \ + -device qemu64-x86_64-cpu,id=cpu2,socket-id=1, \ + core-id=1,thread-id=1 \ + +Two VCPUs are cold-plugged by "-device" parameter, which are in the +same socket and core, but with different thread-ids. After that, the +guest has an additional five VCPUs to be hot-plugged when needed. + +CPU hot-unplug +-------------- + +In order to be able to hot unplug a CPU device, QEMU removes CPU +devices by using the ids which were assigned when hotplugging the +CPU device. + +A monitor command can be used to hot unplug CPUs: + + - "device_del": deletes a CPU device + +For example, assuming that the CPU device with id "cpu1" exists, +then the following command tries to remove it. + + (qemu) device_del cpu1 +