Messages in this thread | | | Date | Wed, 8 Feb 2006 20:51:35 -0600 | From | "Serge E. Hallyn" <> | Subject | Re: [RFC][PATCH 2/7] VPIDs: pid/vpid conversions |
| |
Quoting Alexey Kuznetsov (kuznet@ms2.inr.ac.ru): > Hello! > > > In capability.c it does for_each_thread or something like that. It is > > very similar to cap_set_pg. But in a virtual context all != all :) > > Do you mean that VPID patch does not include this? Absolutely. > VPIDs are not to limit access, the patch virtualizes pids, rather > than deals with access policy. > > Take the whole openvz. Make patch -R < vpid_patch. The result is perfectly > working openvz. Only pids are not virtual, which does not matter. Capisco? > > > > I think for people doing migration a private pid space in some form is > > necessary, > > Not "private", but "virtual". VPIDs are made only for migration, not for fun. > > And word "private" is critical, f.e. for us preserving some form of pid > space is critical. It is very sad, but we cannot do anything with this,
Hi,
do you mean "preserving some sort of *global* pidspace"?
If not, then I also don't understand what you're saying...
thanks, -serge - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |