linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for October 29 (x86 posttest)
Date: Mon, 09 Nov 2009 23:55:21 -0500	[thread overview]
Message-ID: <4AF8F239.4030407@redhat.com> (raw)
In-Reply-To: <20091110130841.81d76a4b.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> Hi all,
> 
> On Mon, 09 Nov 2009 19:40:11 -0500 Masami Hiramatsu<mhiramat@redhat.com>  wrote:
>>
>> Randy Dunlap wrote:
>>> On Thu, 29 Oct 2009 12:48:12 -0400 Masami Hiramatsu wrote:
>>>
>>>> Randy Dunlap wrote:
>>>>>
>>>>> I'm getting this on x86_64:
>>>>>
>>>>>      TEST    posttest
>>>>> Error: ffffffff810299e2:	f2 41 0f 28 52 b0    	repnz movaps -0x50(%r10),%xmm2
>>>>> Error: objdump says 6 bytes, but insn_get_length() says 4 (attr:0)
>>>>> make[2]: *** [posttest] Error 2
>>>>
>>>> Ah, that's should be fixed by AVX support patch which I've posted.
>>>> http://git.kernel.org/tip/e0e492e99b372c6990a5daca9e4683c341f1330e
>>>
>>> Has that been merged into linux-next?
>>> I'm still seeing this failure in linux-next-20091106.
>>
>> I checked it has been merged.
>> So, it should disappear from linux-next-20091109. :-)
> 
> That commit (e0e492e99b372c6990a5daca9e4683c341f1330e "x86: AVX
> instruction set decoder support") has been in linux-next since
> next-20091104, so if Randy's problem still existed in next-20091106, then
> it may be a different problem.

Hmm, this seems a bad sequence, movaps can't have repnz prefix,
since movaps is not string operation... It might happen since
AVX opcodes supporting processors are not released yet.

Anyway, I think we'd better change the posttest to report it
as warning instead of errors.

Thank you,

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division

e-mail: mhiramat@redhat.com

  reply	other threads:[~2009-11-10  4:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29  7:29 linux-next: Tree for October 29 Stephen Rothwell
2009-10-29 16:06 ` linux-next: Tree for October 29 (x86 posttest) Randy Dunlap
2009-10-29 16:48   ` Masami Hiramatsu
2009-11-06 16:59     ` Randy Dunlap
2009-11-10  0:40       ` Masami Hiramatsu
2009-11-10  2:08         ` Stephen Rothwell
2009-11-10  4:55           ` Masami Hiramatsu [this message]
2009-10-29 16:52 ` [PATCH] staging: fix wireless drivers depends Randy Dunlap

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=4AF8F239.4030407@redhat.com \
    --to=mhiramat@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    /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).