From: Gerhard Wiesinger <lists@wiesinger.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Kernel Mailing List, Linux" <linux-kernel@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] kvm_intel fails to load on Conroe CPUs running Linux 4.12
Date: Sun, 27 Aug 2017 16:59:11 +0200 [thread overview]
Message-ID: <583438b7-4acc-5b66-0c7f-8a542b20495c@wiesinger.com> (raw)
In-Reply-To: <CABgObfZFwJMpU_D8SMkuiEhb0qBokHL0jpwmuzdE73TReHMFkg@mail.gmail.com>
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
next prev parent reply other threads:[~2017-08-27 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35eda6a9-086e-f899-e131-288f2346effe@wiesinger.com>
2017-08-17 21:14 ` Gerhard Wiesinger
2017-08-27 7:47 ` [Qemu-devel] " Gerhard Wiesinger
[not found] ` <CABgObfYzngJPgS9agXMrRENVD_e+3Hm=y+KD5dp9na8jNwuumw@mail.gmail.com>
[not found] ` <CABgObfZFwJMpU_D8SMkuiEhb0qBokHL0jpwmuzdE73TReHMFkg@mail.gmail.com>
2017-08-27 14:59 ` Gerhard Wiesinger [this message]
[not found] ` <0e69cbad-f658-03be-0191-1b6fe588147b@wiesinger.com>
[not found] ` <CABgObfaw_bMQ=Dpfs=vh_AweaidqCZSBy4bDtsddk5DSKpRP8A@mail.gmail.com>
[not found] ` <1b37b04c-349f-28f7-fb6c-fbbbe8415b33@wiesinger.com>
2017-09-15 17:07 ` Paolo Bonzini
2017-09-27 19:31 ` Gerhard Wiesinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=583438b7-4acc-5b66-0c7f-8a542b20495c@wiesinger.com \
--to=lists@wiesinger.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®