Some of the callback functions specified in the XENVIF_VIF interface rely on varargs callbacks. A little experimentation with the aforementioned makes me believe that varargs is not as wonderful as it should be in a kernel context. Additionally,
it’s not used in windows kernel API’s anywhere else, presumably for a reason.
Any complaints if I remove varargs from upcoming v9 of XENVIF_VIF interface? Speak now or forever …
MH.