From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: redhat.com, ip: 209.85.128.44, mailfrom: pbonzini@redhat.com) Received: from mail-wm1-f44.google.com (mail-wm1-f44.google.com [209.85.128.44]) by groups.io with SMTP; Thu, 15 Aug 2019 09:04:08 -0700 Received: by mail-wm1-f44.google.com with SMTP id l2so1694728wmg.0 for ; Thu, 15 Aug 2019 09:04:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=12CmPXDKohJIalirQWLIymjm76aqAmjolo9JFT55CfI=; b=tWnna+/J2hBWJAyvO4j61sT6dS9PsE4oBn9o78xZQPs9rSAW3yGJsaomd/fXLeUtuM pXhBvUh5pMDCjgnC3Oq9oL5iervJWp/BJtKJEA82phXmPPisW4CmIMld2c1Vw0yepRE4 alMqVwqgtlB723n6lkGVnLYh84DDmOZqoRF/zno+xJb1W9E3LMFKn+xEYt1sFdMS9nrk 5p6FYwhTqv4vn/0rHkr+DC4t2bK0lg2+L8iBC6HKMNg/wYLEQ1zQ0OR4K7uug59O1Hc2 diODYGJSKJW/sqG4qvq/dFdwyANNz6tO+t7RMA3Wmyju9uZYy3aQkEP2li33cLrztdGg 2dCg== X-Gm-Message-State: APjAAAW6DLZK/z0SOqVk4p8+uXfSKvtaPEcJdhqgHUYFAyR3OcqnU1KJ yGM7ShnmheaTeljk0xod3wMBOQ== X-Google-Smtp-Source: APXvYqyCgR9nyP3oIWWPvbZlOfkCKQomPMTsxIfhP9S+ZkYqKC0bUJHNEYieFprlEnuxW+YpF+UTyg== X-Received: by 2002:a1c:4c02:: with SMTP id z2mr3669896wmf.92.1565885046124; Thu, 15 Aug 2019 09:04:06 -0700 (PDT) Return-Path: Received: from ?IPv6:2001:b07:6468:f312:2cae:66cd:dd43:92d9? ([2001:b07:6468:f312:2cae:66cd:dd43:92d9]) by smtp.gmail.com with ESMTPSA id c1sm1465195wmc.40.2019.08.15.09.04.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 15 Aug 2019 09:04:05 -0700 (PDT) Subject: Re: CPU hotplug using SMM with QEMU+OVMF To: "Yao, Jiewen" , Laszlo Ersek , edk2-devel-groups-io Cc: edk2-rfc-groups-io , qemu devel list , Igor Mammedov , "Chen, Yingwen" , "Nakajima, Jun" , Boris Ostrovsky , Joao Marcal Lemos Martins , Phillip Goerl References: <8091f6e8-b1ec-f017-1430-00b0255729f4@redhat.com> <74D8A39837DF1E4DA445A8C0B3885C503F75B680@shsmsx102.ccr.corp.intel.com> <047801f8-624a-2300-3cf7-1daa1395ce59@redhat.com> <74D8A39837DF1E4DA445A8C0B3885C503F75E4E9@shsmsx102.ccr.corp.intel.com> From: Paolo Bonzini Openpgp: preference=signencrypt Message-ID: Date: Thu, 15 Aug 2019 18:04:03 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C503F75E4E9@shsmsx102.ccr.corp.intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 15/08/19 11:55, Yao, Jiewen wrote: > Hi Paolo > I am not sure what do you mean - "You do not need a reset vector ...". > If so, where is the first instruction of the new CPU in the virtualization environment? > Please help me understand that at first. Then we can continue the discussion. The BSP starts running from 0xFFFFFFF0. APs do not start running at all and just sit waiting for an INIT-SIPI-SIPI sequence. Please see my proposal in the reply to Laszlo. Paolo