From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2E2E2C433E0 for ; Thu, 21 Jan 2021 04:56:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DB782205CB for ; Thu, 21 Jan 2021 04:56:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726619AbhAUE4a (ORCPT ); Wed, 20 Jan 2021 23:56:30 -0500 Received: from mail-qv1-f52.google.com ([209.85.219.52]:44277 "EHLO mail-qv1-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727610AbhAUEzX (ORCPT ); Wed, 20 Jan 2021 23:55:23 -0500 Received: by mail-qv1-f52.google.com with SMTP id d11so359536qvo.11 for ; Wed, 20 Jan 2021 20:55:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ovkYtOPUuG5VhHSVRVaRC9GgRg3OX+tBxgdnBr0JDxw=; b=P0pNl0BSDxG7UDmc8N3ikNp0vBkVBxaom4VUndPhybiqQXbz3t5/102FrZL7+v+7RY 1pt+lTpbl20f2+v7txVbLfyKQT6tyWJOar1YYhRM8HCh+G0UrHD5vGNDr/vNP18bdaaw T6+5m28LmLECkVhBS/wQCeaY17Ny2tO1bRhN8tbO1bXuXGPGsv0a+r9q9PNUiUqAkVrJ 0H6ciZwhC4wcOM0zcEChUTEhhy+mQhsqlUy1eyKP7C9JWuXPDJ2nDuMQ9WQ/17sEaJDX nMJVPArlPlK84aUPXI1TKqKXS3VNO9eZ8Wpvqg8cm5eeFN59L4b9i+8UY2tLQypuQ28X 0pTg== X-Gm-Message-State: AOAM532Xr950Q7UUqT3q3Z3+F/SgJA5e0/HF+cAKjg13dRgpHmhAJLgu l6G2hJNGzwpd5TZMBr6F2eQDGjHCVC7Nn7XXepYXmRN4x4w= X-Google-Smtp-Source: ABdhPJzrH5s7XhWslkIEmtDtussHb2Et1L/e93VpnGmi0f7h2cN4GS6WBjgHsJ0nD7Ik6x0nOJVwCm05xa4buUKOrtk= X-Received: by 2002:a0c:dc13:: with SMTP id s19mr13074921qvk.26.1611204878192; Wed, 20 Jan 2021 20:54:38 -0800 (PST) MIME-Version: 1.0 References: <20210102220441.794923-1-jolsa@kernel.org> <20210102220441.794923-9-jolsa@kernel.org> <20210119174901.GD1717058@krava> In-Reply-To: <20210119174901.GD1717058@krava> From: Namhyung Kim Date: Thu, 21 Jan 2021 13:54:27 +0900 Message-ID: Subject: Re: [PATCH 08/22] perf daemon: Add config file change check To: Jiri Olsa Cc: Jiri Olsa , Arnaldo Carvalho de Melo , lkml , Peter Zijlstra , Ingo Molnar , Mark Rutland , Alexander Shishkin , Michael Petlan , Ian Rogers , Stephane Eranian , Alexei Budankov Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 20, 2021 at 3:51 AM Jiri Olsa wrote: > > On Tue, Jan 19, 2021 at 02:31:55PM +0900, Namhyung Kim wrote: > > On Sun, Jan 3, 2021 at 7:05 AM Jiri Olsa wrote: > > > > > > Adding support to detect daemon's config file changes > > > and re-read the configuration when that happens. > > > > Hmm.. maybe some of the code in the previous commit can be moved here. > > do you mean the config file support? > > I think this patch is quite small and straightforward - adds > the inotify processing for checking config change > > perhaps we can separate some of the code from previous commit, > and make it simpler, I'll check I thought the reconfig logic could move to here. Thanks, Namhyung