Hi Jan,

> -----Original Message-----
> From: Jan Beulich <[email protected]>
> Sent: 2022年7月14日 18:37
> To: Wei Chen <[email protected]>
> Cc: nd <[email protected]>; Andrew Cooper <[email protected]>; Roger Pau
> Monné <[email protected]>; Wei Liu <[email protected]>; xen-
> [email protected]
> Subject: Re: [PATCH v2 2/9] xen/x86: Use enumerations to indicate NUMA
> status
> >>
> >> Well, this makes the table complete, but it doesn't explain how you
> mean
> >> to fold the settings of the two command line options into one variable.
> >>
> >
> > No matter how many separate "numa=" parameters have been parsed from
> > Command line, the values of these original variables are determined
> > after parsing the command line. So the determined status can be mapped
> > to the new one variable from above table.
> 
> Hmm, I was partly wrong - the initial values of both variables are
> indeed set from just the single "numa=" parsing. But later on they
> "evolve" independently, and multiple "numa=" on the command line
> can also have "interesting" effects. I'm afraid I still can't

Can you provide some examples? This way I can better understand your
concerns.

Cheers,
Wei Chen

> convince myself that the new mapping fully represents all originally
> possible combinations (nor can I convince myself that in the existing
> code everything is working as intended).
> 
> Jan

Reply via email to