linux-kernel - Re: [PATCH v3 4/5] remoteproc: qcom: Introduce sysmon

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 17 Nov 2017 17:27:21 -0800
From:   Chris Lew <clew@...eaurora.org>
To:     Bjorn Andersson <bjorn.andersson@...aro.org>
Cc:     Andy Gross <andy.gross@...aro.org>,
        Ohad Ben-Cohen <ohad@...ery.com>,
        Arun Kumar Neelakantam <aneela@...eaurora.org>,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        linux-soc@...r.kernel.org, linux-remoteproc@...r.kernel.org,
        runminw@...eaurora.org
Subject: Re: [PATCH v3 4/5] remoteproc: qcom: Introduce sysmon



On 11/16/2017 9:58 PM, Bjorn Andersson wrote:
> On Thu 16 Nov 12:05 PST 2017, Chris Lew wrote:
>>> +	req.event = SSCTL_SSR_EVENT_BEFORE_SHUTDOWN;
>>
>> Are there plans to add the other SSR events to sysmon notifiers? I think the
>> SSCTL service expects to receive events about remote procs starting as well.
>>
> 
> We could easily add support here to send out the AFTER_BOOTUP
> notification, beyond that we would need to extend the subdev notifiers
> as well.
> 
> But the downstream code paths does confuse me, can you confirm that
> these messages are actually sent to the remote ssctl services?
> 
> Regards,
> Bjorn
> 

Yea the other three events are definitely sent to the remote. The remote 
side posts the events for other modules to query. I'm not sure if all of 
the events are used by other other modules though.

Thanks,
Chris
-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project