From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id CB15A81DA4 for ; Thu, 10 Nov 2016 04:26:16 -0800 (PST) Received: by mail-wm0-x241.google.com with SMTP id u144so2809157wmu.0 for ; Thu, 10 Nov 2016 04:26:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=nMKHK5Mt6aBZZgvuYojiEhNHPtSt1xBQmhCZO6LkgHA=; b=cluv5PgcZTYi1Arn7mlmb9v00A3USdLyh3pcyBmYs4AK1WvSJAJRpO4lMpNWbrJ2xP QIahUpCiG6cuetLSE2PcBbhihwwB51FbAeipXrTx5f5O+GHnhlxhdSa6K6hWyQvzn7co w+HoC2ysldRS284dwTssWXAmNJeSdCBxx4gMMI60q0m4W+YE6AhcGUnqfZjIw2tctNrb WnRpHXTF9r4CBQnyjh02rbizQXITlyaYRsgqPmEoLKb9HN4sl5UCtu3Ihw7b/pfX+iJS rBXKik+NCUk5ZHwjeA/nzaaQpeumKYU0fAdSuuBa3qb/GRVfA5doLwHEZWkJ8G90KiXo wJHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=nMKHK5Mt6aBZZgvuYojiEhNHPtSt1xBQmhCZO6LkgHA=; b=XEklvSZzbLJVFRhNWb0gkFNbAWazTvJT4SkFxe4+VfduzI+q68mqxea0trxyLIw8gk WZTTaLwi1TBOLXIeTDIMXxoxlHX0Nj2PZTy5F5UuqgUsQpMzAGeZjCaOnvtv1tOg5Dt1 Kfytyk0Pht79btw/dDE4sC5/x6cHKtEU8r/WbWds8DKQn6303A+T3/bAJoEW7pqy5knV LNZZ9EgMlzoFANjP423n4SK3JBLUOj9WcDqT6JFWTlulROAd0ThLlbxtuG9qaV1ove8b xU8E3YgYmRCfPUNHdB2SE5NCu4LNVfD1+4XKKMBY678vxY5QvXNy5vqglTAPIPl7LqCk l2kg== X-Gm-Message-State: ABUngveSao1VpoLQobmUNE3uahclO1nCY6mVUkEpd1pYlp5zrp7XsMz32ztVla3l7r3JGQ== X-Received: by 10.195.11.166 with SMTP id ej6mr5074974wjd.60.1478780778756; Thu, 10 Nov 2016 04:26:18 -0800 (PST) Received: from [192.168.10.165] (94-39-185-129.adsl-ull.clienti.tiscali.it. [94.39.185.129]) by smtp.googlemail.com with ESMTPSA id n3sm5176196wjq.34.2016.11.10.04.26.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Nov 2016 04:26:17 -0800 (PST) Sender: Paolo Bonzini To: Laszlo Ersek , Jeff Fan References: <20161110060708.13932-1-jeff.fan@intel.com> <0528a12e-3755-99cb-861a-ac927d484ec1@redhat.com> Cc: edk2-devel@ml01.01.org, Jiewen Yao From: Paolo Bonzini Message-ID: Date: Thu, 10 Nov 2016 13:26:16 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <0528a12e-3755-99cb-861a-ac927d484ec1@redhat.com> Subject: Re: [PATCH 0/2] Put AP into safe hlt-loop code on S3 path X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 12:26:17 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit On 10/11/2016 11:41, Laszlo Ersek wrote: > Here's an excerpt from the KVM trace: > >> CPU-23509 [002] 8406.908787: kvm_enter_smm: vcpu 1: entering SMM, smbase 0x30000 >> CPU-23509 [002] 8406.908836: kvm_enter_smm: vcpu 1: leaving SMM, smbase 0x7ffb3000 >> CPU-23510 [003] 8406.908850: kvm_enter_smm: vcpu 2: entering SMM, smbase 0x30000 >> CPU-23510 [003] 8406.908881: kvm_enter_smm: vcpu 2: leaving SMM, smbase 0x7ffb5000 >> CPU-23511 [001] 8406.908908: kvm_enter_smm: vcpu 3: entering SMM, smbase 0x30000 >> CPU-23511 [001] 8406.908941: kvm_enter_smm: vcpu 3: leaving SMM, smbase 0x7ffb7000 >> CPU-23508 [005] 8406.908951: kvm_enter_smm: vcpu 0: entering SMM, smbase 0x30000 >> CPU-23508 [005] 8406.908989: kvm_enter_smm: vcpu 0: leaving SMM, smbase 0x7ffb1000 >> CPU-23511 [001] 8406.920215: kvm_enter_smm: vcpu 3: entering SMM, smbase 0x7ffb7000 >> CPU-23509 [002] 8406.920225: kvm_enter_smm: vcpu 1: entering SMM, smbase 0x7ffb3000 >> CPU-23510 [003] 8406.920225: kvm_enter_smm: vcpu 2: entering SMM, smbase 0x7ffb5000 >> CPU-23508 [005] 8406.920227: kvm_enter_smm: vcpu 0: entering SMM, smbase 0x7ffb1000 >> CPU-23508 [005] 8406.920262: kvm_enter_smm: vcpu 0: leaving SMM, smbase 0x7ffb1000 >> CPU-23511 [001] 8406.920263: kvm_enter_smm: vcpu 3: leaving SMM, smbase 0x7ffb7000 >> CPU-23508 [005] 8407.020292: kvm_enter_smm: vcpu 0: entering SMM, smbase 0x7ffb1000 >> CPU-23509 [006] 8407.020338: kvm_enter_smm: vcpu 1: leaving SMM, smbase 0x7ffb3000 >> CPU-23510 [003] 8407.020338: kvm_enter_smm: vcpu 2: leaving SMM, smbase 0x7ffb5000 >> CPU-23508 [005] 8407.020338: kvm_enter_smm: vcpu 0: leaving SMM, smbase 0x7ffb1000 > > It seems that VCPU#0 still leaves (and then re-enters) SMM while VCPU#1 and VCPU#2 are firmly in SMM. > > So this series is a clear improvement, but something else remains amiss. > > If I remove Jiewen's v2 series, and apply only this one, then the symptom shows up much less frequently, but it does exist: > - With (Jiewen's v2 + this one), testing case 13, I hit the symptom on the second resume, > - With just this set applied, I hit the symptom (= one AP disappearing from Linux after resume) only on the 24th resume. Any trace I can look at? What about case 14, with PcdCpuSmmStaticPageTable=TRUE? Paolo