Reserve the V4V hypercall number to prevent its use prior to the up-streaming of the rest of the V4V functionality. Signed-off-by: Ross Philipson <ross.philipson@citrix.com<mailto:ross.philipson@citrix.com>> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
At 11:03 -0400 on 13 Jul (1310554989), Ross Philipson wrote:> Reserve the V4V hypercall number to prevent its use prior to the > up-streaming of the rest of the V4V functionality.When can we expect patches for the actual hypercall? If it''s not imminent, if would be better to use language like 22626:ceb508436e6e so as not to confuse readers of the code. Cheers, Tim. -- Tim Deegan <Tim.Deegan@citrix.com> Principal Software Engineer, Xen Platform Team Citrix Systems UK Ltd. (Company #02937203, SL9 0BG) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ross Philipson
2011-Jul-13 15:27 UTC
RE: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number
OK, I will resubmit with language like that. I also forgot the VIRQ we use... Thanks Ross -----Original Message----- From: Tim Deegan Sent: Wednesday, July 13, 2011 11:25 AM To: Ross Philipson Cc: xen-devel@lists.xensource.com; James McKenzie Subject: Re: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number At 11:03 -0400 on 13 Jul (1310554989), Ross Philipson wrote:> Reserve the V4V hypercall number to prevent its use prior to the > up-streaming of the rest of the V4V functionality.When can we expect patches for the actual hypercall? If it''s not imminent, if would be better to use language like 22626:ceb508436e6e so as not to confuse readers of the code. Cheers, Tim. -- Tim Deegan <Tim.Deegan@citrix.com> Principal Software Engineer, Xen Platform Team Citrix Systems UK Ltd. (Company #02937203, SL9 0BG) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel