From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/3] perf: add context field to perf_event Date: Tue, 12 Jul 2011 12:55:25 +0300 Message-ID: <4E1C1A0D.8000707@redhat.com> References: <4E1BF5A1.5070301@redhat.com> <1310459898.18678.108.camel@twins> <4E1C0F02.9040906@redhat.com> <1310462046.14978.11.camel@twins> <4E1C10F8.6010300@redhat.com> <1310462335.14978.12.camel@twins> <4E1C1373.5080500@redhat.com> <1310463060.14978.17.camel@twins> <20110712094131.GA29812@8bytes.org> <4E1C1771.9010300@redhat.com> <20110712094822.GB29812@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Zijlstra , Will Deacon , Frederic Weisbecker , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , Ingo Molnar , "acme@ghostprotocols.net" , Jason Wessel To: Joerg Roedel Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35719 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751155Ab1GLJzt (ORCPT ); Tue, 12 Jul 2011 05:55:49 -0400 In-Reply-To: <20110712094822.GB29812@8bytes.org> Sender: kvm-owner@vger.kernel.org List-ID: On 07/12/2011 12:48 PM, Joerg Roedel wrote: > On Tue, Jul 12, 2011 at 12:44:17PM +0300, Avi Kivity wrote: > > On 07/12/2011 12:41 PM, Joerg Roedel wrote: > >> > Using TIF_bits sounds like a much better solution for this, wakeups are > >> > really rather expensive and its best to avoid extra if at all possible. > >> > >> I would rather vote for Avi's solution too. Such a functionality is very > >> helpful for LWP-perf integration as well (because we need a way to call > >> do_mmap for a task != current). > >> > > > > It's not needed for that. See use_mm() (caller must be a kernel thread). > > But in our case the caller would be the process that wants to count, not > a kernel thread. > Have a helper kernel thread do it for you. Or extend use_mm() to return the old mm (without dropping its refcount) and add a way to restore it. Regarding LWP - I thought the intent was self-profiling by the process for jits and the like? If you also use it for perf, won't it be unusable for that? Also, can't the process interfere, from userspace, by executing the unprivileged LWP instructions? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.