On Wed, May 23, 2012 at 07:16:14PM +0300, Michael S. Tsirkin wrote: > The logic in find_highest_vector looks > strange until you realize the reason for the > weird memory layout, which is because this is > what the CPU microcode expects. > > Add a comment so this stops tripping people up. > > Signed-off-by: Michael S. Tsirkin <[email protected]> > --- > arch/x86/kvm/lapic.h | 5 +++++ > 1 files changed, 5 insertions(+), 0 deletions(-) > > diff --git a/arch/x86/kvm/lapic.h b/arch/x86/kvm/lapic.h > index 41c62c7..1d1ec08 100644 > --- a/arch/x86/kvm/lapic.h > +++ b/arch/x86/kvm/lapic.h > @@ -15,6 +15,11 @@ struct kvm_lapic { > bool irr_pending; > s16 isr_count; > int isr_cache;
Wrong branch. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
