|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v9 02/20] x86/VPMU: Manage VPMU_CONTEXT_SAVE flag in vpmu_save_force()
On 08/11/2014 09:28 AM, Jan Beulich wrote: On 08.08.14 at 18:55, <boris.ostrovsky@xxxxxxxxxx> wrote:vpmu_load() may leave VPMU_CONTEXT_SAVE set after calling vpmu_save_force() if the context is not loaded.To me this is ambiguous (and looking at the patch I can't really resolve it): Do you mean to say this can validly happen, or that it could have happened in error prior to the patch? In any event please alter the description to either clearly state what the wrong old behavior was, or what the correct new behavior is to be. What I was trying to say (not particularly successfully, apparently) is that currently (i.e. prior to the patch) we may end up not clearing VPMU_CONTEXT_SAVE flag after calling vpmu_save_forced(). And that would be a bug, which this patch is fixing. (It doesn't help that the diff doesn't show that the flag is cleared right after ->arch_vpmu_save() below) -boris Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |