From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] tools/thermal: thermal library and tools
Date: Tue, 19 Apr 2022 20:16:40 -0700 [thread overview]
Message-ID: <b78bd722081baa4db571c0360559f105d0a7d175.camel@linux.intel.com> (raw)
In-Reply-To: <51d63f20-4834-184b-2ac2-30c399bd9988@linaro.org>
Hi Daniel,
On Tue, 2022-04-19 at 22:26 +0200, Daniel Lezcano wrote:
>
> Hi Srinivas,
>
>
> On 18/04/2022 05:36, srinivas pandruvada wrote:
> > Hi Daniel,
> >
> > The attached diff fixes the crash,
> >
> > Also when you run in daemon mode, you need to use some pid lock
> > file.
> > Otherwise it launches multiple daemons.
>
> I've been thinking about it and I don't think it is a problem to have
> multiple instances of the daemon. The netlink allows multicast and
> can
> be run as non-root user.
>
> If the finality of the thermal engine is to manage the system and has
> some code making actions on the system with the root privilege, the
> init
> scripts can take care of the pid lock
>
If there is use case, then this is fine otherwise wasting system
resources.
Thanks,
Srinivas
>
>
prev parent reply other threads:[~2022-04-20 3:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 10:04 [PATCH v2 0/4] tools/thermal: thermal library and tools Daniel Lezcano
2022-03-30 10:04 ` [PATCH v2 1/4] tools/lib/thermal: Add a thermal library Daniel Lezcano
2022-03-30 10:04 ` [PATCH v2 2/4] tools/thermal: Add util library Daniel Lezcano
2022-03-30 10:04 ` [PATCH v2 3/4] tools/thermal: A temperature capture tool Daniel Lezcano
2022-03-30 10:04 ` [PATCH v2 4/4] tools/thermal: Add thermal daemon skeleton Daniel Lezcano
2022-04-06 8:00 ` [PATCH v2 0/4] tools/thermal: thermal library and tools Daniel Lezcano
2022-04-06 14:28 ` srinivas pandruvada
2022-04-06 14:44 ` Daniel Lezcano
2022-04-13 15:06 ` Rafael J. Wysocki
2022-04-13 17:21 ` srinivas pandruvada
2022-04-16 3:50 ` srinivas pandruvada
2022-04-16 7:55 ` Daniel Lezcano
2022-04-17 4:23 ` srinivas pandruvada
2022-04-17 8:20 ` Daniel Lezcano
2022-04-18 3:36 ` srinivas pandruvada
2022-04-18 3:38 ` srinivas pandruvada
2022-04-18 7:46 ` Daniel Lezcano
2022-04-19 20:26 ` Daniel Lezcano
2022-04-20 3:16 ` srinivas pandruvada [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b78bd722081baa4db571c0360559f105d0a7d175.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).