Anthony PERARD writes ("Re: [PATCH 3/8] xen: defer call to xen_restrict until after os_setup_post"): > I'm tring to find out what does calling xen_restrict_all(0), when > running an non-Xen guest. I think it would just lock(), then unlock() > then there should not be any handle to restrict, and return 0; is that > right?
Yes. If the process has not opened any Xen control handles, xentoolcore_restrict_all is a no-op. Ian.