From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933394AbbESO1c (ORCPT ); Tue, 19 May 2015 10:27:32 -0400 Received: from mga14.intel.com ([192.55.52.115]:64345 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932612AbbESO12 (ORCPT ); Tue, 19 May 2015 10:27:28 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,458,1427785200"; d="scan'208";a="697170017" From: "Zhang, Yang Z" To: Paolo Bonzini , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" CC: "rkrcmar@redhat.com" , "bsd@redhat.com" , "guangrong.xiao@linux.intel.com" , "wanpeng.li@linux.intel.com" Subject: RE: [RFC PATCH 00/13] KVM: x86: SMM support Thread-Topic: [RFC PATCH 00/13] KVM: x86: SMM support Thread-Index: AQHQgznre3WZe3pj8EixVLsV7a/J452Dd2Ng Date: Tue, 19 May 2015 14:25:11 +0000 Message-ID: References: <1430393772-27208-1-git-send-email-pbonzini@redhat.com> In-Reply-To: <1430393772-27208-1-git-send-email-pbonzini@redhat.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id t4JERc23002644 Paolo Bonzini wrote on 2015-04-30: > This patch series introduces system management mode support. Just curious what's motivation to add vSMM supporting? Is there any usage case inside guest requires SMM? Thanks. > There is still some work to do, namely: test without unrestricted > guest support, test on AMD, disable the capability if !unrestricted > guest and !emulate invalid guest state(*), test with a QEMU that > understand KVM_MEM_X86_SMRAM, actually post QEMU patches that let you use this. > > (*) newer chipsets moved away from legacy SMRAM at 0xa0000, > thus support for real mode CS base above 1M is necessary > > Because legacy SMRAM is a mess, I have tried these patches with Q35's > high SMRAM (at 0xfeda0000). This means that right now this isn't the > easiest thing to test; you need QEMU patches that add support for high > SMRAM, and SeaBIOS patches to use high SMRAM. Until QEMU support for > KVM_MEM_X86_SMRAM is in place, also, I'm keeping SMRAM open in SeaBIOS. > > That said, even this clumsy and incomplete userspace configuration is > enough to test all patches except 11 and 12. > > The series is structured as follows. > > Patch 1 is an unrelated bugfix (I think). Patches 2 to 6 extend some > infrastructure functions. Patches 1 to 4 could be committed right now. > > Patches 7 to 9 implement basic support for SMM in the KVM API and > teach KVM about doing the world switch on SMI and RSM. > > Patch 10 touches all places in KVM that read/write guest memory to go > through an x86-specific function. The x86-specific function takes a > VCPU rather than a struct kvm. This is used in patches 11 and 12 to > limits access to specially marked SMRAM slots unless the VCPU is in > system management mode. > > Finally, patch 13 exposes the new capability for userspace to probe. > Best regards, Yang {.n++%ݶw{.n+{G{ayʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I