On Tue, Oct 23, 2012 at 07:56:54PM +0000, Auld, Will wrote: > Having looked closer at the tacked of changing out the index and data fields in some > function calls for a struct parameter with these and a originator field (host or guest) > it is less attractive than I thought it would be. The only place where we need to know the initiator is in kvm_write_tsc() which has an implicit index. At the moment yes, but it might have other uses in the future. > I have been trying to determine whether there is a possibility for taking a context switch while a guest initiated set_msr() is in progress whereby the new thread might invoke the set_msr()/kvm_write_tsc() routines. It looks to me like this is not possible but I can't be sure. It is not possible. > If it is not possible we can set a variable for the vcpu when a guest call is in progress and this would be sufficient. > > What do you think? > Thanks, The struct parameter seems the preferred choice as there might be other uses to this information in the future. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
