Searched hist:"092 a2b76873d9e6898a0f7d822edaa30c2ab17e3" (Results 1 – 4 of 4) sorted by relevance
| /optee_os/core/arch/arm/kernel/ |
| H A D | link.mk | 092a2b76873d9e6898a0f7d822edaa30c2ab17e3 Sun Jan 24 17:33:30 UTC 2016 Jens Wiklander <jens.wiklander@linaro.org> core: pager: add support to page out r/w pages
Adds support in pager to page out read-write pages by encrypting them
with AES-GCM to avoid leaking sensitive information. With this patch there
are three different ways of providing virtual memory:
- read only, where each page is protected with a SHA-256 hash
- read write locked, corresponding with previous zero initialized where
mapped pages are removed from the usual pool of physical pages and
only returned on explicit release
- read write, *new* dirty read write pages triggers update to the
storage using encryption (AES-GCM) before the page is reused.
Reviewed-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: David Brown <david.brown@linaro.org>
Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| H A D | thread.c | 092a2b76873d9e6898a0f7d822edaa30c2ab17e3 Sun Jan 24 17:33:30 UTC 2016 Jens Wiklander <jens.wiklander@linaro.org> core: pager: add support to page out r/w pages
Adds support in pager to page out read-write pages by encrypting them
with AES-GCM to avoid leaking sensitive information. With this patch there
are three different ways of providing virtual memory:
- read only, where each page is protected with a SHA-256 hash
- read write locked, corresponding with previous zero initialized where
mapped pages are removed from the usual pool of physical pages and
only returned on explicit release
- read write, *new* dirty read write pages triggers update to the
storage using encryption (AES-GCM) before the page is reused.
Reviewed-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: David Brown <david.brown@linaro.org>
Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| /optee_os/core/arch/arm/mm/ |
| H A D | tee_pager.c | 092a2b76873d9e6898a0f7d822edaa30c2ab17e3 Sun Jan 24 17:33:30 UTC 2016 Jens Wiklander <jens.wiklander@linaro.org> core: pager: add support to page out r/w pages
Adds support in pager to page out read-write pages by encrypting them
with AES-GCM to avoid leaking sensitive information. With this patch there
are three different ways of providing virtual memory:
- read only, where each page is protected with a SHA-256 hash
- read write locked, corresponding with previous zero initialized where
mapped pages are removed from the usual pool of physical pages and
only returned on explicit release
- read write, *new* dirty read write pages triggers update to the
storage using encryption (AES-GCM) before the page is reused.
Reviewed-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: David Brown <david.brown@linaro.org>
Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| H A D | core_mmu.c | 092a2b76873d9e6898a0f7d822edaa30c2ab17e3 Sun Jan 24 17:33:30 UTC 2016 Jens Wiklander <jens.wiklander@linaro.org> core: pager: add support to page out r/w pages
Adds support in pager to page out read-write pages by encrypting them
with AES-GCM to avoid leaking sensitive information. With this patch there
are three different ways of providing virtual memory:
- read only, where each page is protected with a SHA-256 hash
- read write locked, corresponding with previous zero initialized where
mapped pages are removed from the usual pool of physical pages and
only returned on explicit release
- read write, *new* dirty read write pages triggers update to the
storage using encryption (AES-GCM) before the page is reused.
Reviewed-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: David Brown <david.brown@linaro.org>
Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
|