[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E959C4978C3B6342920538CF579893F00C2DE2F9@SHSMSX104.ccr.corp.intel.com>
Date: Thu, 28 Jan 2016 01:51:35 +0000
From: "Wu, Feng" <feng.wu@...el.com>
To: Radim Krcmár <rkrcmar@...hat.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Wu, Feng" <feng.wu@...el.com>
Subject: RE: [PATCH v4 2/4] KVM: x86: Use vector-hashing to deliver
lowest-priority interrupts
> -----Original Message-----
> From: Radim Krčmář [mailto:rkrcmar@...hat.com]
> Sent: Wednesday, January 27, 2016 2:59 AM
> To: Wu, Feng <feng.wu@...el.com>
> Cc: pbonzini@...hat.com; linux-kernel@...r.kernel.org; kvm@...r.kernel.org
> Subject: Re: [PATCH v4 2/4] KVM: x86: Use vector-hashing to deliver lowest-
> priority interrupts
>
> 2016-01-25 16:53+0800, Feng Wu:
> > Use vector-hashing to deliver lowest-priority interrupts, As an
> > example, modern Intel CPUs in server platform use this method to
> > handle lowest-priority interrupts.
> >
> > Signed-off-by: Feng Wu <feng.wu@...el.com>
> > ---
>
> With any proposed resolution of BUG_ON in kvm_vector_to_index,
>
> Reviewed-by: Radim Krčmář <rkrcmar@...hat.com>
>
> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > @@ -123,6 +123,9 @@ module_param(tsc_tolerance_ppm, uint, S_IRUGO |
> S_IWUSR);
> > +bool __read_mostly vector_hashing = true;
>
> (Module param can be static.)
>
> > +module_param(vector_hashing, bool, S_IRUGO);
Thanks a lot for your comments, Radim & Paolo!
Paolo, given that the only two comments above, do I need to send v5? Or
you can handle it while merging them? I am fine with both methods.
Thanks,
Feng
Powered by blists - more mailing lists