Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752665Ab0FVFrA (ORCPT ); Tue, 22 Jun 2010 01:47:00 -0400 Received: from mga03.intel.com ([143.182.124.21]:16813 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751856Ab0FVFq7 (ORCPT ); Tue, 22 Jun 2010 01:46:59 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.53,458,1272870000"; d="scan'208";a="291500795" Subject: Re: [PATCH V2 3/5] ara virt interface of perf to support kvm guest os statistics collection in guest os From: "Zhang, Yanmin" To: Gleb Natapov Cc: LKML , kvm@vger.kernel.org, Avi Kivity , Ingo Molnar , Fr??d??ric Weisbecker , Arnaldo Carvalho de Melo , Cyrill Gorcunov , Lin Ming , Sheng Yang , Marcelo Tosatti , oerg Roedel , Jes Sorensen , Zachary Amsden , zhiteng.huang@intel.com, tim.c.chen@intel.com, Peter Zijlstra In-Reply-To: <20100621135659.GL4689@redhat.com> References: <1277112703.2096.511.camel@ymzhang.sh.intel.com> <20100621135659.GL4689@redhat.com> Content-Type: text/plain; charset="ISO-8859-1" Date: Tue, 22 Jun 2010 13:47:16 +0800 Message-Id: <1277185636.2096.675.camel@ymzhang.sh.intel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.0 (2.28.0-2.fc12) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2063 Lines: 59 On Mon, 2010-06-21 at 16:56 +0300, Gleb Natapov wrote: > On Mon, Jun 21, 2010 at 05:31:43PM +0800, Zhang, Yanmin wrote: > > The 3rd patch is to implement para virt perf at host kernel. > > > > Signed-off-by: Zhang Yanmin > > > > + > > +static void kvm_copy_event_to_guest(struct kvm_vcpu *vcpu, > > + struct perf_event *host_event) > > +{ > > + struct host_perf_shadow *shadow = host_event->host_perf_shadow; > > + struct guest_perf_event counter; > > + int ret; > > + s32 overflows; > > + > > + ret = kvm_read_guest(vcpu->kvm, shadow->guest_event_addr, > > + &counter, sizeof(counter)); > > + if (ret < 0) > > + return; > > + > > +again: > > + overflows = atomic_read(&shadow->counter.overflows); > > + if (atomic_cmpxchg(&shadow->counter.overflows, overflows, 0) != > > + overflows) > > + goto again; > > + > > + counter.count = shadow->counter.count; > > + atomic_add(overflows, &counter.overflows); > > + > > + kvm_write_guest(vcpu->kvm, > > + shadow->guest_event_addr, > > + &counter, > > + sizeof(counter)); > Those kind of interfaces worry me since the can cause bugs that are > very hard to catch. What if guest enables some events and crashes into > kdump kernel (or kexec new kernel) without reseting HW. Now host may > write over guest memory without guest expecting it. Do you handle this > scenario in a guest side? I think you need to register reboot notify > and disable events from there. Sorry for missing your comments. My patch could take care of dead guest os by cleaning up all events in function kvm_arch_destroy_vm, so all events are closed if host user kills the guest qemu process. As for your scenario, I will register reboot notify and add a new pv perf hypercall interface to vmexit to host kernel to do cleanup. Thanks, Yanmin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/