From: Avi Kivity <avi@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: percpu crash on NetBurst
Date: Wed, 21 Sep 2011 18:49:24 +0300 [thread overview]
Message-ID: <4E7A0784.1040602@redhat.com> (raw)
In-Reply-To: <4E79F477.2050102@redhat.com>
On 09/21/2011 05:28 PM, Avi Kivity wrote:
>
> Coming back to this, the trigger if cpuid family=6 and model>=13
> (model 12 works). Looks like the code disables rep_good is some MSR
> doesn't have the expected value. While we should configure the MSR
> correctly, it looks like the fallback code for !rep_good is broken.
> Will look further.
>
Ok, without rep_good, memcpy() sometimes copies backwards. A stale copy
of memmove_64.c I had around got picked up instead of memmove_64.S; that
memmove() used memcpy() in the copy-forward case.
So, nothing to see, sorry about the noise.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-09-21 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 15:32 percpu crash on NetBurst Avi Kivity
2011-08-08 9:55 ` Tejun Heo
2011-09-21 14:28 ` Avi Kivity
2011-09-21 15:49 ` Avi Kivity [this message]
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=4E7A0784.1040602@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).