[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 6/6] x86/boot: Drop INVALID_VCPU
On 06.01.2020 16:54, Andrew Cooper wrote: > Now that NULL will fault at boot, there is no need for a special constant to > signify "current not set up yet". Mind making this "... no strong need ..."? The benefit of an easily recognizable value goes away, but I guess we'll be fine without. IOW I'm not meaning to object. > --- a/xen/arch/x86/setup.c > +++ b/xen/arch/x86/setup.c > @@ -705,7 +705,7 @@ void __init noreturn __start_xen(unsigned long mbi_p) > /* Critical region without IDT or TSS. Any fault is deadly! */ > > set_processor_id(0); > - set_current(INVALID_VCPU); /* debug sanity. */ > + set_current(NULL); /* debug sanity. */ > idle_vcpu[0] = current; Is any of this actually changing any value in memory? I.e. wouldn't it be better to delete all of this, or leave it in a comment for documentation purposes? (I'm willing to ack the patch as is, but I'd like this alternative to at least be considered.) Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |