[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <E959C4978C3B6342920538CF579893F00C2B2E73@SHSMSX104.ccr.corp.intel.com>
Date: Tue, 19 Jan 2016 13:49:02 +0000
From: "Wu, Feng" <feng.wu@...el.com>
To: Paolo Bonzini <pbonzini@...hat.com>,
Radim Krcmár <rkrcmar@...hat.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Wu, Feng" <feng.wu@...el.com>
Subject: RE: [PATCH v2 1/2] KVM: x86: Use vector-hashing to deliver
lowest-priority interrupts
> -----Original Message-----
> From: linux-kernel-owner@...r.kernel.org [mailto:linux-kernel-
> owner@...r.kernel.org] On Behalf Of Paolo Bonzini
> Sent: Tuesday, January 19, 2016 9:43 PM
> To: Wu, Feng <feng.wu@...el.com>; Radim Krcmár <rkrcmar@...hat.com>
> Cc: kvm@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH v2 1/2] KVM: x86: Use vector-hashing to deliver lowest-
> priority interrupts
>
>
>
> On 19/01/2016 05:44, Wu, Feng wrote:
> > > I think Radim's suggestion is fine. You can print an error (just once
> > > per guest) to dmesg if the result of the hashing computation corresponds
> > > to a disabled APIC.
> >
> > Good idea, is there already a convenient way to do this in KVM?
>
> No, you can just use something like the definition of printk_once (in
> include/linux/printk.h), but with a flag in struct kvm_arch.
Yes, that is a possible solution, if you don't think adding a flag in struct
kvm_arch is not too overkill, I am fine with this. :)
Thanks,
Feng
Powered by blists - more mailing lists