From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933343Ab2GFKuZ (ORCPT ); Fri, 6 Jul 2012 06:50:25 -0400 Received: from fgwmail7.fujitsu.co.jp ([192.51.44.37]:42702 "EHLO fgwmail7.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932831Ab2GFKuD (ORCPT ); Fri, 6 Jul 2012 06:50:03 -0400 X-Greylist: delayed 3582 seconds by postgrey-1.27 at vger.kernel.org; Fri, 06 Jul 2012 06:50:02 EDT X-SecurityPolicyCheck: OK by SHieldMailChecker v1.7.4 Date: Fri, 06 Jul 2012 17:38:50 +0900 (JST) Message-Id: <20120706.173850.11462611.d.hatayama@jp.fujitsu.com> To: wency@cn.fujitsu.com Cc: zhangyanfei@cn.fujitsu.com, dzickus@redhat.com, luto@mit.edu, kvm@vger.kernel.org, joerg.roedel@amd.com, mtosatti@redhat.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, paul.gortmaker@windriver.com, ludwig.nussel@suse.de, avi@redhat.com, gregkh@linuxfoundation.org, ebiederm@xmission.com Subject: Re: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill VMCSINFO From: HATAYAMA Daisuke In-Reply-To: <4FF6A0F3.2010201@cn.fujitsu.com> References: <4FF4155F.6070508@cn.fujitsu.com> <20120706.170410.119097767.d.hatayama@jp.fujitsu.com> <4FF6A0F3.2010201@cn.fujitsu.com> X-Mailer: Mew version 6.3 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Wen Congyang Subject: Re: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill VMCSINFO Date: Fri, 6 Jul 2012 16:25:23 +0800 > At 07/06/2012 04:04 PM, HATAYAMA Daisuke Wrote: >> From: Yanfei Zhang >> Subject: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill VMCSINFO >> Date: Wed, 4 Jul 2012 18:05:19 +0800 >> >>> Besides, this patch also exports vmcs revision identifier via >>> /sys/devices/system/cpu/vmcs_id and offsets of fields via >>> /sys/devices/system/cpu/vmcs/. >>> Individual offsets are contained in subfiles named by the filed's >>> encoding, e.g.: /sys/devices/cpu/vmcs/0800 >> >> According to the discussion starting from >> >> http://lkml.indiana.edu/hypermail/linux/kernel/1105.3/00749.html > > IIRC, kvm can not work in such environment. The vcpu can run on > different cpu. If the cpu's vmcs is different, I don't know what > will happen. So do we need to support for such environment now? > I think that if kvm can not work in such environment, we should > not provide vmcs information for each physical cpu. > I think so too. The design can be kept very simple if kvm doesn't support such case, and it would be good news. Is it true? Thanks. HATAYAMA, Daisuke