[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <6A3B67DA-EDAA-4DE5-BE59-96B693D7BB86@gmail.com>
Date: Tue, 20 Jan 2015 23:04:14 +0200
From: Nadav Amit <nadav.amit@...il.com>
To: Radim Kr?má? <rkrcmar@...hat.com>
Cc: "Wu, Feng" <feng.wu@...el.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"eric.auger@...aro.org" <eric.auger@...aro.org>,
"gleb@...nel.org" <gleb@...nel.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
Paolo Bonzini <pbonzini@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"jiang.liu@...ux.intel.com" <jiang.liu@...ux.intel.com>
Subject: Re: [v3 13/26] KVM: Define a new interface kvm_find_dest_vcpu() for VT-d PI
Radim Kr?má? <rkrcmar@...hat.com> wrote:
> 2015-01-14 01:27+0000, Wu, Feng:
>>> the new
>>>> hardware even doesn't consider the TPR for lowest priority interrupts
>>> delivery.
>>>
>>> A bold move ... what hardware was the first to do so?
>>
>> I think it was starting with Nehalem.
>
> Thanks, (Could be that QPI can't inform about TPR changes anymore ...)
>
> I played with Linux's TPR on Haswell and found that is has no effect.
Sorry for jumping into the discussion, but doesn’t it depend on
IA32_MISC_ENABLE[23]? This bit disables xTPR messages. On my machine it is
set (probably by the BIOS), but since there is no IA32_MISC_ENABLE is not
locked for changes, the OS can control it.
Nadav--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists