Re: [PATCH] xen/argo: Command line handling improvements

2025-05-29 Thread Christopher Clark
On Wed, May 21, 2025 at 9:43 PM Andrew Cooper wrote: > On 21/05/2025 2:01 am, Christopher Clark wrote: > > On Tue, May 20, 2025 at 3:10 PM Andrew Cooper > > wrote: > > > > Treat "argo" on the command line as a positive boolean, rather > > than requiring > > the user to pass "argo=1/o

Re: [PATCH] xen/argo: Command line handling improvements

2025-05-21 Thread Andrew Cooper
On 21/05/2025 2:01 am, Christopher Clark wrote: > On Tue, May 20, 2025 at 3:10 PM Andrew Cooper > wrote: > > Treat "argo" on the command line as a positive boolean, rather > than requiring > the user to pass "argo=1/on/enable/true". > > Move both opt_argo* variables into __ro_after

Re: [PATCH] xen/argo: Command line handling improvements

2025-05-20 Thread Jan Beulich
On 20.05.2025 20:45, Daniel P. Smith wrote: > On 5/20/25 10:10, Andrew Cooper wrote: >> Treat "argo" on the command line as a positive boolean, rather than requiring >> the user to pass "argo=1/on/enable/true". >> >> Move both opt_argo* variables into __ro_after_init. They're set during >> command

Re: [PATCH] xen/argo: Command line handling improvements

2025-05-20 Thread Christopher Clark
On Tue, May 20, 2025 at 3:10 PM Andrew Cooper wrote: > Treat "argo" on the command line as a positive boolean, rather than > requiring > the user to pass "argo=1/on/enable/true". > > Move both opt_argo* variables into __ro_after_init. They're set during > command line parsing and never modified

Re: [PATCH] xen/argo: Command line handling improvements

2025-05-20 Thread dmkhn
On Tue, May 20, 2025 at 03:10:27PM +0100, Andrew Cooper wrote: > Treat "argo" on the command line as a positive boolean, rather than requiring > the user to pass "argo=1/on/enable/true". > > Move both opt_argo* variables into __ro_after_init. They're set during > command line parsing and never mo

Re: [PATCH] xen/argo: Command line handling improvements

2025-05-20 Thread Daniel P. Smith
On 5/20/25 10:10, Andrew Cooper wrote: Treat "argo" on the command line as a positive boolean, rather than requiring the user to pass "argo=1/on/enable/true". Move both opt_argo* variables into __ro_after_init. They're set during command line parsing and never modified thereafter. Signed-off-b

[PATCH] xen/argo: Command line handling improvements

2025-05-20 Thread Andrew Cooper
Treat "argo" on the command line as a positive boolean, rather than requiring the user to pass "argo=1/on/enable/true". Move both opt_argo* variables into __ro_after_init. They're set during command line parsing and never modified thereafter. Signed-off-by: Andrew Cooper --- CC: Christopher Cla