security: nv_tee_driver: fix incorrect cpu affinity
authorVarun Wadekar <vwadekar@nvidia.com>
Thu, 18 Apr 2013 05:11:29 +0000 (10:11 +0530)
committerDan Willemsen <dwillemsen@nvidia.com>
Sat, 14 Sep 2013 20:09:48 +0000 (13:09 -0700)
commit009b77f597b5d12099d6747ed8fa82aa1089822c
treeb80463d38b909aeb1b211f4b76804f6acef9df81
parentfcc1c2d5b9d7855b15fdc4ca928954b45072c6a5
security: nv_tee_driver: fix incorrect cpu affinity

The process using ns_driver sometimes can't be scheduled to
available onlined cpu. It is because cpu affinity has changed
after using ns_driver. ns_driver saves current cpu affinity by
calling sched_getaffinity which returns cpu affinity AND-masked
by onlined cpus. ns_driver should save just current cpu affinity,
not cpu affinity AND-masked by onlined cpus.

More info: http://git-master/r/198844

Change-Id: Iae89fa71f7c130f67dce908d916b80bba2fc84bb
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/220453
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Hyung Taek Ryoo <hryoo@nvidia.com>
GVS: Gerrit_Virtual_Submit
security/nv_tee_driver/tee_comms.c