devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ekansh Gupta <quic_ekangupt@quicinc.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <srinivas.kandagatla@linaro.org>, <linux-arm-msm@vger.kernel.org>,
	<ekangupt@qti.qualcomm.com>, <linux-kernel@vger.kernel.org>,
	<fastrpc.upstream@qti.qualcomm.com>, <agross@kernel.org>,
	<andersson@kernel.org>, <konrad.dybcio@linaro.org>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<conor+dt@kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [RESEND PATCH v1 0/2] Privileged process support on remote subsystem
Date: Thu, 8 Jun 2023 15:23:06 +0530	[thread overview]
Message-ID: <a665978d-f1e7-380e-f5f2-cf1270fa7961@quicinc.com> (raw)
In-Reply-To: <2023060722-zap-fiftieth-4323@gregkh>



On 6/8/2023 12:17 AM, Greg KH wrote:
> On Wed, Jun 07, 2023 at 10:00:05PM +0530, Ekansh Gupta wrote:
>> Add support to run remote user process as privileged on remote
>> subsystem. The privileged user process can be given prioritized
>> access to remote processor resources. This is achieved in kernel
>> based on the group ID of the process. The kernel will have a
>> pre-defined fastrpc group ID and if the process's group ID matches
>> with it, then the process is treated as a privileged process. This
>> information is sent to the remote processor during PD initialization
>> and the PD is treated as a privileged PD.
>>
>> Ekansh Gupta (2):
>>    dt-bindings: misc: fastrpc: add fastrpc group IDs property
>>    misc: fastrpc: detect privileged processes based on group ID
>>
>>   .../devicetree/bindings/misc/qcom,fastrpc.yaml     |   6 +
>>   drivers/misc/fastrpc.c                             | 124 +++++++++++++++++++++
>>   2 files changed, 130 insertions(+)
>>
>> -- 
>> 2.7.4
>>
> 
> Why is this a RESEND?
> 
I missed sending the patches to some necessary people and lists. Hence, 
resent the patch series.

Thanks,
Ekansh
> thanks,
> 
> greg k-h

  reply	other threads:[~2023-06-08  9:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 16:30 [RESEND PATCH v1 0/2] Privileged process support on remote subsystem Ekansh Gupta
2023-06-07 16:30 ` [RESEND PATCH v1 1/2] dt-bindings: misc: fastrpc: add fastrpc group IDs property Ekansh Gupta
2023-06-07 17:21   ` Rob Herring
2023-06-08  9:43     ` Ekansh Gupta
2023-06-07 18:44   ` Krzysztof Kozlowski
2023-06-08 10:36     ` Ekansh Gupta
2023-06-08 11:33       ` Krzysztof Kozlowski
2023-06-07 16:30 ` [RESEND PATCH v1 2/2] misc: fastrpc: detect privileged processes based on group ID Ekansh Gupta
2023-06-07 18:47   ` Krzysztof Kozlowski
2023-06-08 10:44     ` Ekansh Gupta
2023-06-08 11:36       ` Krzysztof Kozlowski
2023-06-07 18:47 ` [RESEND PATCH v1 0/2] Privileged process support on remote subsystem Greg KH
2023-06-08  9:53   ` Ekansh Gupta [this message]
2023-06-08 10:16     ` Greg KH
2023-06-08 10:51       ` Ekansh Gupta

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=a665978d-f1e7-380e-f5f2-cf1270fa7961@quicinc.com \
    --to=quic_ekangupt@quicinc.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ekangupt@qti.qualcomm.com \
    --cc=fastrpc.upstream@qti.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.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).