Dear Hideki EIRAKU, Thank you very much for your help. We were wrongly tracing sys_msgsetfunc() instead of msgsetfunc(). We are looking for the ways of adding storage virtualization to bitvisor, if it will be possible. Can anyone help us about this issue, is it possible with the current architecture of bitvisor? or we can only offer an enhanced storage to the guest OS with this architecture? Thanks in advance, Regards, Nafise <div class="gmail_quote">On Mon, Aug 23, 2010 at 2:42 PM, Hideki EIRAKU <<a href="mailto:hdk@igel.co.jp">hdk@igel.co.jp</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> From: Nafise Sadat Moosavi <<a href="mailto:ns.moosavi@gmail.com">ns.moosavi@gmail.com</a>> Subject: [BitVisor-devel-en:3] A question about process[pid].msgdsc[desc].func Date: Sat, 21 Aug 2010 12:09:37 +0430 Message-ID: <<a href="mailto:AANLkTikF3qh7eCnGS23Wx84Vm5ugk7FhgyAEpnRv%2BAfQ@mail.gmail.com">AANLkTikF3qh7eCnGS23Wx84Vm5ugk7FhgyAEpnRv+AfQ@mail.gmail.com</a>> <div class="im"> > But unfortunately we cannot find out where the related functions of msgdesc > of each process (process[pid].msgdsc[desc].func]) have been set; Thus we > could not found out how the protection domain mechanism works? </div>process[pid].msgdsc[desc].func is set by msgregister() or msgsetfunc(). In the case of storage protection domain, msgregister() is called by storage_init() function. <div class="im"> > Is this a fully implemented feature, or it is just an initial idea to be > completed later? </div>It works well. -- Hideki EIRAKU <<a href="mailto:hdk@igel.co.jp">hdk@igel.co.jp</a>> _______________________________________________ BitVisor-devel-en mailing list <a href="mailto:BitVisor-devel-en@bitvisor.org">BitVisor-devel-en@bitvisor.org</a> <a href="https://www.bitvisor.org/mailman/listinfo/bitvisor-devel-en" target="_blank">https://www.bitvisor.org/mailman/listinfo/bitvisor-devel-en</a> </blockquote></div>