Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1720782 > unrolled thread

Re: [Qemu-devel] kvm_intel fails to load on Conroe CPUs running Linux 4.12

Started byGerhard Wiesinger <lists@wiesinger.com>
First post2017-08-27 09:50 +0200
Last post2017-08-27 17:00 +0200
Articles 2 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [Qemu-devel] kvm_intel fails to load on Conroe CPUs running Linux  4.12 Gerhard Wiesinger <lists@wiesinger.com> - 2017-08-27 09:50 +0200
    Re: [Qemu-devel] kvm_intel fails to load on Conroe CPUs running Linux  4.12 Gerhard Wiesinger <lists@wiesinger.com> - 2017-08-27 17:00 +0200

#1720782 — Re: [Qemu-devel] kvm_intel fails to load on Conroe CPUs running Linux 4.12

FromGerhard Wiesinger <lists@wiesinger.com>
Date2017-08-27 09:50 +0200
SubjectRe: [Qemu-devel] kvm_intel fails to load on Conroe CPUs running Linux 4.12
Message-ID<uj0ut-4Cq-1@gated-at.bofh.it>
On 17.08.2017 23:14, Gerhard Wiesinger wrote:
> On 17.08.2017 22:58, Gerhard Wiesinger wrote:
> >
> > On 07.08.2017 19:50, Paolo Bonzini wrote:
> >
> > >Not much to say, unfortunately. It's pretty much the same capabilities
> > >as a Prescott/Cedar Mill processor, except that it has MSR bitmaps. It
> > >also lacks FlexPriority compared to the Conroe I had checked.
> > >
> > >It's not great that even the revert patch doesn't apply cleanly---this
> > >is *not* necessarily a boring area of the hypervisor...
> > >
> > >Given the rarity of your machine I'm currently leaning towards _not_
> > >reverting the change. I'll check another non-Xeon Core 2 tomorrow that
> > >is from December 2008 (IIRC). If that one also lacks vNMI, or if I get
> > >other reports, I suppose I will have to reconsider that.
>
> Hello Paolo,
>
> Can you please revert the patch.
>
> CPU is a Core 2 Extreme QX6700: SL9UL (B3) running VERY stable with 
> ECC RAM for years now.
> https://ark.intel.com/products/28028/Intel-Core2-Extreme-Processor-QX6700-8M-Cache-2_66-GHz-1066-MHz-FSB?q=Core%202%20Extreme%20QX6700 
>
> https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors
>
> CPU details below.
>
> Thank you.
>
> Ciao,
> Gerhard 

Hello Paolo,

Any update on this major issue?

Thnx.

Ciao,
Gerhard

[toc] | [next] | [standalone]


#1720843

FromGerhard Wiesinger <lists@wiesinger.com>
Date2017-08-27 17:00 +0200
Message-ID<uj7cB-BC-1@gated-at.bofh.it>
In reply to#1720782
On 27.08.2017 14:03, Paolo Bonzini wrote:
> Il 27 ago 2017 9:49 AM, "Gerhard Wiesinger" <lists@wiesinger.com> ha
> scritto:
>
> On 17.08.2017 23:14, Gerhard Wiesinger wrote:
>
>> On 17.08.2017 22:58, Gerhard Wiesinger wrote:
>>> On 07.08.2017 19:50, Paolo Bonzini wrote:
>>>
>>>> Not much to say, unfortunately. It's pretty much the same capabilities
>>>> as a Prescott/Cedar Mill processor, except that it has MSR bitmaps. It
>>>> also lacks FlexPriority compared to the Conroe I had checked.
>>>>
>>>> It's not great that even the revert patch doesn't apply cleanly---this
>>>> is *not* necessarily a boring area of the hypervisor...
>>>>
>>>> Given the rarity of your machine I'm currently leaning towards _not_
>>>> reverting the change. I'll check another non-Xeon Core 2 tomorrow that
>>>> is from December 2008 (IIRC). If that one also lacks vNMI, or if I get
>>>> other reports, I suppose I will have to reconsider that.
>> Hello Paolo,
>>
>> Can you please revert the patch.
>>
>> CPU is a Core 2 Extreme QX6700: SL9UL (B3) running VERY stable with ECC
>> RAM for years now.
>> https://ark.intel.com/products/28028/Intel-Core2-Extreme-
>> Processor-QX6700-8M-Cache-2_66-GHz-1066-MHz-FSB?q=Core%
>> 202%20Extreme%20QX6700
>> https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors
>>
>> CPU details below.
>>
>> Thank you.
>>
>> Ciao,
>> Gerhard
>>
> Hello Paolo,
>
> Any update on this major issue?
>
>
> We will revert the patch, but 4.13.0 will not have the fix. Expect it in
> later stable kernels (because vacations).
Thnx. Why will 4.13.0 NOT have the fix?

Thnx.

Ciao,
Gerhard

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web