HI Carl,<br><br>YOur experiment sounds like a very good idea, there is one thing I don't understand entierly, it is about faking the space-id, under which situation could this happen?<br><br>Thanks,<br><br>Jorge<br><br>
<br><div><span class="gmail_quote">On 7/9/07, <b class="gmail_sendername">Carl van Schaik</b> <<a href="mailto:carl@ok-labs.com">carl@ok-labs.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Jorge / Harry,<br><br>We have encountered this problem as well recently, although for very<br>different reasons. I'm experimenting with adding a "Sender's Space"<br>field in the UTCB, which is updated on every IPC to reflect the space-id
<br>of the sender. This would means that the roottask for example need not<br>lookup the space-id of the thread, and the kernel guarantees that the<br>value cannot be faked.<br><br>regards,<br>Carl<br><br>Jorge Torres wrote:
<br>> Yeap,<br>><br>> A syscall such as pagerof would be great in some situations,<br>><br>> Thanks,<br>><br>> JOrge<br>><br>> On 7/9/07, *Harry Vennik* < <a href="mailto:htvennik@zonnet.nl">
htvennik@zonnet.nl</a><br>> <mailto:<a href="mailto:htvennik@zonnet.nl">htvennik@zonnet.nl</a>>> wrote:<br>><br>> I have run into the same thing recently. Not often a thread needs to<br>> know its own space-id, but when implementing some memory management
<br>> server it would be very nice to be able to map the thread-id where<br>> the IPC request is coming from to a space-id to apply the memory<br>> mapping to. I think the microkernel simply has to keep track of the
<br>> thread to space relations, so why require a memory manager server to<br>> do the same thing? I think it would be better to keep that info in<br>> the micro kernel only, and provide a way for the memory manager to
<br>> request that information through a (privileged) syscall.<br>><br>> Regards,<br>><br>> Harry<br>><br>> Op 9-jul-2007, om 9:04 heeft Carl van Schaik het volgende geschreven:<br>>
<br>> > Are you asking about finding a thread's space-id? Currently it<br>> is not<br>> > possible, the OS environment should tell the thread, eg on its<br>> > stack. In<br>> > general, threads don't need to know their space-id and can't
<br>> call make<br>> > any L4 calls that require it.<br>> ><br>> > regards,<br>> > Carl<br>> ><br>> > Jorge Torres wrote:<br>> >> HI,<br>> >>
<br>> >><br>> >> Does somebody know how can one find a thread spaceid?<br>> >><br>> >> Thanks,<br>> >><br>> >> Jorge<br>> >><br>> ---------------------------------------------------------------------
<br>> >> ---<br>> >><br>> >> _______________________________________________<br>> >> Developer mailing list<br>> >> <a href="mailto:Developer@okl4.org">Developer@okl4.org
</a> <mailto:<a href="mailto:Developer@okl4.org">Developer@okl4.org</a>><br>> >> <a href="https://lists.okl4.org/mailman/listinfo/developer">https://lists.okl4.org/mailman/listinfo/developer</a><br>> >>
<br>> ><br>> ><br>> > _______________________________________________<br>> > Developer mailing list<br>> > <a href="mailto:Developer@okl4.org">Developer@okl4.org</a> <mailto:
<a href="mailto:Developer@okl4.org">Developer@okl4.org</a>><br>> > <a href="https://lists.okl4.org/mailman/listinfo/developer">https://lists.okl4.org/mailman/listinfo/developer</a><br>><br>><br><br></blockquote>
</div><br>