From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1SKTVD-0000yb-Br for kexec@lists.infradead.org; Wed, 18 Apr 2012 11:56:52 +0000 Message-ID: <4F8EABF7.805@redhat.com> Date: Wed, 18 Apr 2012 14:56:39 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump References: <4F84E0DF.8040206@cn.fujitsu.com> <4F8D1F46.3090901@redhat.com> <4F8D4B4C.8070705@cn.fujitsu.com> <4F8D4D1C.4010400@redhat.com> <4F8E6DA5.8030503@cn.fujitsu.com> <4F8E7A5B.5030904@redhat.com> <4F8E8E3D.8040707@cn.fujitsu.com> In-Reply-To: <4F8E8E3D.8040707@cn.fujitsu.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: zhangyanfei Cc: dzickus@redhat.com, luto@mit.edu, gregkh@suse.de, 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, ebiederm@xmission.com On 04/18/2012 12:49 PM, zhangyanfei wrote: > >> > > > > What type of resource? Can you give an example? > > > Sorry. No concrete example for now. > > We are developing this on a conservative policy and I have put the vmcs processing > in a new module in patch set v2 as you required. The new module is auto-loaded when > the vmx cpufeature is detected and it depends on module kvm-intel. Loading and unloading > this module will have no side effect on the running guests. > > And one thing I have to stress is that, we can see guest image as crash dump from > guest machine's view if we have the vmcsinfo, this itself is useful. Why is it useful? Without a concrete example, it's hard to justify the code bloat. -- error compiling committee.c: too many arguments to function _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump Date: Wed, 18 Apr 2012 14:56:39 +0300 Message-ID: <4F8EABF7.805@redhat.com> References: <4F84E0DF.8040206@cn.fujitsu.com> <4F8D1F46.3090901@redhat.com> <4F8D4B4C.8070705@cn.fujitsu.com> <4F8D4D1C.4010400@redhat.com> <4F8E6DA5.8030503@cn.fujitsu.com> <4F8E7A5B.5030904@redhat.com> <4F8E8E3D.8040707@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: dzickus-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, luto-3s7WtUTddSA@public.gmane.org, gregkh-l3A5Bk7waGM@public.gmane.org, kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, joerg.roedel-5C7GfCeVMHo@public.gmane.org, mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, paul.gortmaker-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org, ludwig.nussel-l3A5Bk7waGM@public.gmane.org, ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org To: zhangyanfei Return-path: In-Reply-To: <4F8E8E3D.8040707-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kexec-bounces-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Errors-To: kexec-bounces+glkk-kexec=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: kvm.vger.kernel.org On 04/18/2012 12:49 PM, zhangyanfei wrote: > >> > > > > What type of resource? Can you give an example? > > > Sorry. No concrete example for now. > > We are developing this on a conservative policy and I have put the vmcs processing > in a new module in patch set v2 as you required. The new module is auto-loaded when > the vmx cpufeature is detected and it depends on module kvm-intel. Loading and unloading > this module will have no side effect on the running guests. > > And one thing I have to stress is that, we can see guest image as crash dump from > guest machine's view if we have the vmcsinfo, this itself is useful. Why is it useful? Without a concrete example, it's hard to justify the code bloat. -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753340Ab2DRL45 (ORCPT ); Wed, 18 Apr 2012 07:56:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20614 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753252Ab2DRL44 (ORCPT ); Wed, 18 Apr 2012 07:56:56 -0400 Message-ID: <4F8EABF7.805@redhat.com> Date: Wed, 18 Apr 2012 14:56:39 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 MIME-Version: 1.0 To: zhangyanfei CC: mtosatti@redhat.com, ebiederm@xmission.com, luto@mit.edu, joerg.roedel@amd.com, dzickus@redhat.com, paul.gortmaker@windriver.com, gregkh@suse.de, ludwig.nussel@suse.de, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, kexec@lists.infradead.org Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump References: <4F84E0DF.8040206@cn.fujitsu.com> <4F8D1F46.3090901@redhat.com> <4F8D4B4C.8070705@cn.fujitsu.com> <4F8D4D1C.4010400@redhat.com> <4F8E6DA5.8030503@cn.fujitsu.com> <4F8E7A5B.5030904@redhat.com> <4F8E8E3D.8040707@cn.fujitsu.com> In-Reply-To: <4F8E8E3D.8040707@cn.fujitsu.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/18/2012 12:49 PM, zhangyanfei wrote: > >> > > > > What type of resource? Can you give an example? > > > Sorry. No concrete example for now. > > We are developing this on a conservative policy and I have put the vmcs processing > in a new module in patch set v2 as you required. The new module is auto-loaded when > the vmx cpufeature is detected and it depends on module kvm-intel. Loading and unloading > this module will have no side effect on the running guests. > > And one thing I have to stress is that, we can see guest image as crash dump from > guest machine's view if we have the vmcsinfo, this itself is useful. Why is it useful? Without a concrete example, it's hard to justify the code bloat. -- error compiling committee.c: too many arguments to function