A. Private Process Management กระบวนการจัดการ
The first requirement for implementing PRIVEXEC is to
enable the OS to support a private execution mode for
processes. The OS must be able to launch an application as
a private process upon request from the user, generate the
PEK, store it in an easily accessible context associated with
that process, mark the process and track it during its lifetime,
and, finally, destroy the PEK when the private process terminates. Additionally, these new capabilities must not break
the established kernel process management functionality. At
the same time, the OS must expose a simple interface for
user-level applications to request private execution without
requiring modifications to existing application code.
A. Private Process Management กระบวนการจัดการ
The first requirement for implementing PRIVEXEC is to
enable the OS to support a private execution mode for
processes. The OS must be able to launch an application as
a private process upon request from the user, generate the
PEK, store it in an easily accessible context associated with
that process, mark the process and track it during its lifetime,
and, finally, destroy the PEK when the private process terminates. Additionally, these new capabilities must not break
the established kernel process management functionality. At
the same time, the OS must expose a simple interface for
user-level applications to request private execution without
requiring modifications to existing application code.
การแปล กรุณารอสักครู่..