|
|
|
|
|
|
|
|
|
|
xense-devel
[Xense-devel] Labeling resources
Reiner,
Thanks for taking the time to reply to my questions. I'm very
curious about where you're going with ACM and want to contribute code
if I can get the powers that be to cooperate.
I spent a little time reviewing the chwall_ste policy to understand where you are headed.
I was initially thrown off by the use of ste_PersonalFinances with
multiple domains. This included dom_HomeBanking, dom_Network, and
dom_LogicalDiskPartition1. This allows dom_Network to directly
access dom_LogicalDiskPartition1 and vise versa. Expect that this
was not intended. To be specific about the allowed interactions,
I replaced the ste_PersonalFinances type with
ste_PersonalFincancesNetwork and ste_PersonalFinancesPartition. I
did the same with ste_InternetInsecure. This ensures that
dom_Network and dom_StorageDomain never directly talk to each other.
I did this to help see what would happen with resources as this relates
to the limitations I'm encountering trying to use sHype . There
is still some abiguity with a few of the labels, but I'm more concerned
about the following questions.
How does the hypervisor know that these labels actually identify a
specific hardware device? I expect that the hypervisor wouldn't
want to know anything more than the IRQ and address ranges for each
device. How do you intend to handle the association so that the
ACM can make access decisions when resources are allocated to domains?
The other issue has to do with the res_LogicalDiskPartition1 and
2. Clearly this is not a resource the hypervisor knows anything
about and is the responsiblity of dom_StorageDomain. I expect
that dom_StorageDomain will make calls into the hypervisor for the ACM
to make access decisions. There needs to be some way for
dom_Storage domain to identify a resource label with the physical
resource. Doesn't this need to be explicit in the label
template? What plans do you have for handling this? For
example, the entry for the dom_Storage label could list the resources
that are available from that domain with a <Resource> tag.
Within the <Resource> entry. there could be an <id> tag
providing a numerical identifier that the dom_StorageDomain interprets
to be a partition number.
Thanks,
Dave
_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xense-devel] Labeling resources,
David Palmer <=
|
|
|
|
|