mbox series

[RESEND,v1,0/2] Privileged process support on remote subsystem

Message ID 1686155407-20054-1-git-send-email-quic_ekangupt@quicinc.com
Headers
Series Privileged process support on remote subsystem |

Message

Ekansh Gupta June 7, 2023, 4:30 p.m. UTC 
  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(+)

Comments

Greg KH June 7, 2023, 6:47 p.m. UTC | #1 
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?

thanks,

greg k-h
Ekansh Gupta June 8, 2023, 9:53 a.m. UTC | #2 
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
Greg KH June 8, 2023, 10:16 a.m. UTC | #3 
On Thu, Jun 08, 2023 at 03:23:06PM +0530, Ekansh Gupta wrote:
> 
> 
> 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.

Please always say so when doing a resend as I think the documentation
asks you to, right?

thanks,

greg k-h
Ekansh Gupta June 8, 2023, 10:51 a.m. UTC | #4 
On 6/8/2023 3:46 PM, Greg KH wrote:
> On Thu, Jun 08, 2023 at 03:23:06PM +0530, Ekansh Gupta wrote:
>>
>>
>> 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.
> 
> Please always say so when doing a resend as I think the documentation
> asks you to, right?
> 
This was the first time for me to resend a patch and in documentation I 
just saw "RESEND" needs to be added to the subject. Apologies for 
missing this. I'm still learning and going forwards, for re-sending also 
I'll follow the etiquette followed when resubmitting a patch with 
changes. Thanks for the suggestion! :)
> thanks,
> 
> greg k-h