From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754934AbbJ1FUb (ORCPT ); Wed, 28 Oct 2015 01:20:31 -0400 Received: from mail-ob0-f172.google.com ([209.85.214.172]:36257 "EHLO mail-ob0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754360AbbJ1FUA (ORCPT ); Wed, 28 Oct 2015 01:20:00 -0400 MIME-Version: 1.0 In-Reply-To: <1445996397-32703-2-git-send-email-pbonzini@redhat.com> References: <1445996397-32703-1-git-send-email-pbonzini@redhat.com> <1445996397-32703-2-git-send-email-pbonzini@redhat.com> From: Andy Lutomirski Date: Tue, 27 Oct 2015 22:19:40 -0700 Message-ID: Subject: Re: [PATCH 1/3] context_tracking: remove duplicate enabled check To: Paolo Bonzini Cc: "linux-kernel@vger.kernel.org" , kvm list , Andy Lutomirski , Frederic Weisbecker , Rik van Riel , Paul McKenney Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 27, 2015 at 6:39 PM, Paolo Bonzini wrote: > All calls to context_tracking_enter and context_tracking_exit > are already checking context_tracking_is_enabled, except the > context_tracking_user_enter and context_tracking_user_exit > functions left in for the benefit of assembly calls. > > Pull the check up to those functions, by making them simple > wrappers around the user_enter and user_exit inline functions. This makes my brain hurt. Assuming that this survives a boot with CONFIG_CONTEXT_TRACKING_FORCE=y and CONFIG_PROVE_LOCKING=y (with the implied CONFIG_PROVE_RCU), then: Acked-by: Andy Lutomirski