All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Redundant repz prefixes in generated amd64 code
Date: Fri, 16 Mar 2007 14:28:35 +0000	[thread overview]
Message-ID: <200703161428.36897.paul@codesourcery.com> (raw)
In-Reply-To: <200703161415.21283.jseward@acm.org>

On Friday 16 March 2007 14:15, Julian Seward wrote:
> I'm seeing redundant repz (0xF3) prefixes in generated code, typically
> just before jumps:
>
> <code_gen_buffer+415>:  repz mov $0xe07f,%eax
> <code_gen_buffer+421>:  mov    %eax,0x20(%rbp)
> <code_gen_buffer+424>:  lea    -25168302(%rip),%ebx  # 0xaf0420 <tbs+96>
> <code_gen_buffer+430>:  retq
> <code_gen_buffer+431>:  mov    -25168245(%rip),%eax  # 0xaf0460 <tbs+160>
> <code_gen_buffer+437>:  jmpq   *%rax
> <code_gen_buffer+439>:  repz mov $0xe092,%eax
> <code_gen_buffer+445>:  mov    %eax,0x20(%rbp)
> <code_gen_buffer+448>:  lea    -25168325(%rip),%ebx   # 0xaf0421 <tbs+97>
> <code_gen_buffer+454>:  retq
>
> I assume these are something to do with translation chaining/unchaining but
> have been unable to figure out where they come from.

0000000000008b50 <op_goto_tb1>:
    8b50:       8b 05 00 00 00 00       mov    0(%rip),%eax 
                        8b52: R_X86_64_PC32     __op_param1+0x3c
    8b56:       ff e0                   jmpq   *%rax
    8b58:       f3 c3                   repz retq

qemu only strips the final ret off.
The prefixed ret is to avoid prefetch stalls on amd cpus.

Paul

  reply	other threads:[~2007-03-16 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 14:15 [Qemu-devel] Redundant repz prefixes in generated amd64 code Julian Seward
2007-03-16 14:28 ` Paul Brook [this message]
2007-03-16 14:45   ` Julian Seward
2007-03-16 18:14     ` Paul Brook
2007-03-16 19:30 ` Igor Kovalenko
2007-03-16 23:06   ` Julian Seward
2007-03-17  7:35   ` axel
2007-03-17  9:51     ` Johannes Schindelin
2007-03-17 11:16       ` Axel Zeuner

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=200703161428.36897.paul@codesourcery.com \
    --to=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.