Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Integrate AFM with WAM

Description

WAM follows the Chromium process model, which can be summarized as follows:

  • There is one render process per open site/web application.

  • There is one common browser process, which performs I/O and networking for all sites/webapps.

As a consequence of this process model, the browser process must have access to the APIs (via WebSockets) requested by all of the running webapps. This behavior doesn't match the AFM security model, where each application process is expected to access only the authorized APIs and this is enforced via SMACK labels.

The proposal to solve this problem is to create a proxy process for each render process, which would have the correct SMACK label for the corresponding webapp to access its authorized APIs. The browser process would redirect all the networking requested by render processes to the proxy process and wouldn't have special permissions. 

Repositories :

WebAppMgr : https://github.com/webosose/wam Branch : @1.agl.flounder

meta-agl-lge : https://github.com/webosose/meta-agl-lge Branch : flounder

chromium53 : https://github.com/webosose/chromium53 Branch : @1.agl.flounder

 

Hardware :

  1. Renesas m3 board : Reproducible 

  2. Minnowboard : Non reproducible 

  3. Raspberry pi : -

Environment

None

Attachments

9

Activity

Walt Miner 
February 11, 2019 at 11:11 PM

Close for FF 6.0.4 and GG 7.0.0

AK 
November 30, 2018 at 5:48 AM
(edited)

The main goal of this issue was to track the integration of AFM with WAM which is completed.

Moreover, this issue is not reproducible on minnowboard. It is not even reproducible on all Renesas m3 board. 

 ticket specifically to handle issue related to the m3 board.

AK 
November 30, 2018 at 5:40 AM

From CHROME_IPC_LOGGIGN its confirmed that message from BROWSER to GPU  for GpuMsg_EstablishChannel is not completed and respective message as the reply from GPU to BROWSER is not received.

Other than that, pvrtrace tracing shows that FRAMES are not getting recorded for the second application. There is not recording related log in journal and PVRTRACE viewer doesn't show any frame painted related to the second application.

AK 
November 28, 2018 at 7:26 PM
(edited)

Analyzing GPU trace using pvrtrace utility.

Documentation :
http://cdn.imgtec.com/sdk-documentation/PVRTrace.User+Manual.pdf
https://www.imgtec.com/developers/powervr-sdk-tools/pvrtrace/

How to setup :
1. Download pvrtrace from https://www.imgtec.com/developers/powervr-sdk-tools/installers/
2. Copy /opt/Imagination/PowerVR_Graphics/PowerVR_Tools/PVRHub to HOME folder of image on sdcard.

3. Perform steps below :

4.

 5.

6. Modify WebAppMgr.service:

       

AK 
November 26, 2018 at 10:16 AM

Hi san,

I would like to trace out GPU calls and analyze further. Do we have any Renesas specific tools to debug/ analyze?

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Priority

Created October 31, 2018 at 8:34 AM
Updated February 11, 2019 at 11:11 PM
Resolved November 30, 2018 at 5:48 AM