[CRIU] [PATCH 2/9] opt: cpu-cap -- Introduce "none" and "cpuinfo" arguments

[Cyrill Gorcunov]

On Tue, Sep 30, 2014 at 02:22:00PM +0400, Pavel Emelyanov wrote:
> On 09/30/2014 02:20 PM, Cyrill Gorcunov wrote:
> > On Tue, Sep 30, 2014 at 02:02:50PM +0400, Pavel Emelyanov wrote:
> >>> -"     --cpu-cap CAP      require certain cpu capability. CAP: may be one of:\n"
> >>> -"                        'fpu','all'. To disable capability, prefix it with '^'.\n"
> >>> +"     --cpu-cap [CAP]    require certain cpu capability. CAP: may be one of:\n"
> >>> +"                        'cpuinfo','fpu','all','none'. To disable capability, prefix it with '^'.\n"
> >>
> >> What's the point in none? Does it differ from "no option"?
> > 
> > The image may have cpuinfo dumped and it will refusre to restore if destination
> > node doesn't have all caps matched. For this sake if user still needs to proceed
> > he may pass "none" parameter and criu ignore any caps.
> 
> OK. This makes sense. Can we have a wiki page describing the cpu features
> management policy?

I tried to describe it in our man first. But sure it can be propagated to wiki as well.