![]() | This article has not yet been rated on Wikipedia's content assessment scale. |
I think the use case example under System Security needs some explanation. There are three issues. 1. It talks about subsystems - are subsystems solely software modules or can they be hardware subsystems? I suspect both given that the primary supporting/implementation technology of the VM capability is the MMU. (and potentially the embedded processors' hardware support for virtualization) which can restrict access to any memory addresseable device or software code/data space. 2. It might make sense to explicitly state that it's the Embedded Hypervisors use of the MMU that provides security. But that begs the question as to how. Maybe there should be a related section in the Implementation section to further expand on this point? 3. There is a fleeting reference to security policies for communication between sub-systems. Again this needs expansion, some examples of the types of security policies for example? and again maybe a tie in section back to implementation?
Embeddowikier ( talk) 12:29, 23 February 2009 (UTC)
The beginning of this page reads like an editorial and not like an encyclopedia. —Preceding unsigned comment added by 50.46.201.106 ( talk) 07:17, 7 March 2011 (UTC)
I do comprehend what a hypervisor is, and think I also comprehend the properties of embedded systems, but WTF is an "embedded hypervisor"? With my current understanding I see absolutely no point in this article. ScotXW ( talk) 13:49, 22 October 2013 (UTC)
This article was ahead of its time. The structure could be improved but, many years later, it is very relevant. 71.234.102.244 ( talk) 02:20, 10 March 2021 (UTC)
![]() | This article has not yet been rated on Wikipedia's content assessment scale. |
I think the use case example under System Security needs some explanation. There are three issues. 1. It talks about subsystems - are subsystems solely software modules or can they be hardware subsystems? I suspect both given that the primary supporting/implementation technology of the VM capability is the MMU. (and potentially the embedded processors' hardware support for virtualization) which can restrict access to any memory addresseable device or software code/data space. 2. It might make sense to explicitly state that it's the Embedded Hypervisors use of the MMU that provides security. But that begs the question as to how. Maybe there should be a related section in the Implementation section to further expand on this point? 3. There is a fleeting reference to security policies for communication between sub-systems. Again this needs expansion, some examples of the types of security policies for example? and again maybe a tie in section back to implementation?
Embeddowikier ( talk) 12:29, 23 February 2009 (UTC)
The beginning of this page reads like an editorial and not like an encyclopedia. —Preceding unsigned comment added by 50.46.201.106 ( talk) 07:17, 7 March 2011 (UTC)
I do comprehend what a hypervisor is, and think I also comprehend the properties of embedded systems, but WTF is an "embedded hypervisor"? With my current understanding I see absolutely no point in this article. ScotXW ( talk) 13:49, 22 October 2013 (UTC)
This article was ahead of its time. The structure could be improved but, many years later, it is very relevant. 71.234.102.244 ( talk) 02:20, 10 March 2021 (UTC)