linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trilok Soni <quic_tsoni@quicinc.com>
To: Deepti Jaggi <quic_djaggi@quicinc.com>, <james.morse@arm.com>,
	<mchehab@kernel.org>, <rric@kernel.org>, <bp@alien8.de>,
	<tony.luck@intel.com>
Cc: <linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kernel@quicinc.com>, <quic_psodagud@quicinc.com>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] EDAC/device: Add sysfs notification for UE,CE count change
Date: Mon, 31 Jul 2023 22:48:11 -0700	[thread overview]
Message-ID: <ce06c845-f3c8-a733-dc21-ee0ba4b4ca68@quicinc.com> (raw)
In-Reply-To: <3e2bf03e-2bc1-445e-d8ce-4975c044eea0@quicinc.com>

On 7/31/2023 3:40 PM, Trilok Soni wrote:
> On 7/31/2023 3:00 PM, Deepti Jaggi wrote:
>> A daemon running in user space collects information on correctable
>> and uncorrectable errors from EDAC driver by reading corresponding
>> sysfs entries and takes appropriate action.
> 
> Which daemon we are referring here? Can you please provide the link to 
> the project?
> 
> Are you using this daemon?
> 
> https://mcelog.org/ - It is for x86, but is your daemon project different?
> 
>> This patch adds support for user space daemon to wait on poll() until
>> the sysfs entries for UE count and CE count change and then read updated
>> counts instead of continuously monitoring the sysfs entries for
>> any changes.
> 
> The modifications below are architecture agnostic so I really want to 
> know what exactly we are fixing and if there is a problem.

+ CC linux-arm-msm

Please keep linux-arm-msm in CC if there is a next revision.

-- 
---Trilok Soni


  reply	other threads:[~2023-08-01  5:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 22:00 [PATCH] EDAC/device: Add sysfs notification for UE,CE count change Deepti Jaggi
2023-07-31 22:40 ` Trilok Soni
2023-08-01  5:48   ` Trilok Soni [this message]
2023-08-01 22:37     ` Deepti Jaggi
2023-09-13 17:22       ` Trilok Soni
2023-09-29 18:40 ` Adrien Thierry

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=ce06c845-f3c8-a733-dc21-ee0ba4b4ca68@quicinc.com \
    --to=quic_tsoni@quicinc.com \
    --cc=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=kernel@quicinc.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=quic_djaggi@quicinc.com \
    --cc=quic_psodagud@quicinc.com \
    --cc=rric@kernel.org \
    --cc=tony.luck@intel.com \
    /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).