From: malc <av1474@comtv.ru>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Next stable release
Date: Fri, 10 Apr 2009 06:54:49 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0904100652190.3090@linmac.oyster.ru> (raw)
In-Reply-To: <22982211.post@talk.nabble.com>
On Thu, 9 Apr 2009, TeLeMan wrote:
>
>
> malc-4 wrote:
> >
> > On Mon, 6 Apr 2009, TeLeMan wrote:
> >
> >>
> >> I hope you can fix the following bugs in the next release:
> >>
> >> http://www.nabble.com/-PATCH--i386-hard-interrupt-generation-bug-fix-p14921171.html
> >> http://www.nabble.com/MAX_OP_PER_INSTR-should-be-larger-tt22573338.html
> >>
> >
> > You should retry with the current QEMU, immediate ro[lr]s should produce a
> > lot less tcg ops currently.
> >
> > --
> > mailto:av1474@comtv.ru
> >
> >
> >
> >
>
> It is not fixed yet.
>
[..snip..]
Omitting dump before liveness analysis...
>
> ---- 0x4468c0
> ld_i32 loc24,env,$0x18
> nopn $0x3,$0x0,$0x3
> movi_i32 loc25,$0x0
> nopn $0x2,$0x2
> nopn $0x2,$0x2
> movi_i32 tmp32,$0xe
> shl_i32 tmp30,loc25,tmp32
> nopn $0x2,$0x2
> nopn $0x3,$0x21,$0x3
> movi_i32 tmp32,$0x12
> shr_i32 tmp14,loc24,tmp32
> or_i32 tmp14,tmp14,tmp30
> nopn $0x2,$0x2
> nopn $0x2,$0x2
> nopn $0x3,$0x20,$0x3
> movi_i32 tmp32,$0xe
> shl_i32 tmp30,loc24,tmp32
> nopn $0x2,$0x2
> nopn $0x3,$0x21,$0x3
> nopn $0x3,$0x21,$0x3
> mov_i32 loc24,tmp30
> or_i32 loc24,loc24,tmp14
> nopn $0x3,$0x21,$0x3
> st_i32 loc24,env,$0x18
> movi_i32 tmp8,$0x0
> nopn $0x2,$0x2
> st_i32 tmp8,env,$0x1c
> nopn $0x2,$0x2
> nopn $0x2,$0x2
> nopn $0x6,$0x14,$0x1,$0x26,$0x10,$0x6
> nopn $0x2,$0x2
> nopn $0x2,$0x2
> nopn $0x2,$0x2
> nopn $0x3,$0x2,$0x3
> nopn $0x3,$0x22,$0x3
> nopn $0x3,$0x23,$0x3
> nopn $0x2,$0x2
> nopn $0x3,$0x11,$0x3
> nopn $0x2,$0x2
> nopn $0x3,$0x11,$0x3
> nopn $0x2,$0x2
> nopn $0x3,$0x10,$0x3
> nopn $0x3,$0x10,$0x3
> nopn $0x2,$0x2
> nopn $0x2,$0x2
> nopn $0x3,$0x10,$0x3
> nopn $0x2,$0x2
> nopn $0x3,$0x2,$0x3
> nopn $0x3,$0x3,$0x3
> nopn $0x2,$0x2
> nopn $0x3,$0x21,$0x3
> nopn $0x2,$0x2
> nopn $0x3,$0x21,$0x3
> nopn $0x2,$0x2
> nopn $0x3,$0x20,$0x3
> nopn $0x3,$0x20,$0x3
> nopn $0x2,$0x2
> nopn $0x2,$0x2
> nopn $0x3,$0x20,$0x3
> nopn $0x2,$0x2
> nopn $0x3,$0x2,$0x3
> nopn $0x3,$0x3,$0x3
> discard cc_dst_0
> discard cc_dst_1
> nopn $0x2,$0x2
As you can see above most of the stuff was turned into nops by
la.. So...
[..snip..]
>
> 65 ops were translated at 0x4468c0 or 0x4468c3.
> 71 ops were translated at the last instruction(0x4468eb).
> Another question: Who can ensure no other instructions like this? just by
> testing?
>
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-04-10 2:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 19:38 [Qemu-devel] Next stable release Anthony Liguori
2009-04-06 13:08 ` TeLeMan
2009-04-06 13:43 ` Anthony Liguori
2009-04-07 1:38 ` Edgar E. Iglesias
2009-04-06 21:03 ` malc
2009-04-10 2:35 ` TeLeMan
2009-04-10 2:54 ` malc [this message]
2009-04-10 3:04 ` TeLeMan
2009-04-10 4:17 ` malc
2009-04-06 14:51 ` Stefan Weil
2009-04-07 1:11 ` Anthony Liguori
2009-04-07 6:06 ` Stefan Weil
2009-04-07 7:16 ` Aurelien Jarno
2009-04-07 9:27 ` Stefan Weil
2009-04-07 10:03 ` Aurelien Jarno
-- strict thread matches above, loose matches on Subject: below --
2009-03-20 16:23 Anthony Liguori
2009-03-20 17:02 ` René Rebe
2009-03-20 20:20 ` Robert Riebisch
2009-03-21 9:05 ` Andreas Färber
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=Pine.LNX.4.64.0904100652190.3090@linmac.oyster.ru \
--to=av1474@comtv.ru \
--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;
as well as URLs for NNTP newsgroup(s).