From: Sean Chen <sean.chen1234@gmail.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: Jakob Engblom <jakob@virtutech.com>,
Michael Snyder <msnyder@vmware.com>,
Hui Zhu <teawater@gmail.com>,
gdb@sourceware.org
Subject: Re: porting reversible on arm/mips
Date: Fri, 11 Dec 2009 16:42:00 -0000 [thread overview]
Message-ID: <5e81cb500912110842v5f2990ay9019e0ba4562d8c1@mail.gmail.com> (raw)
In-Reply-To: <947215.16059.qm@web112506.mail.gq1.yahoo.com>
On Fri, Dec 11, 2009 at 9:24 PM, paawan oza <paawan1982@yahoo.com> wrote:
> I am not sure how arm can be drastically slower than x86 ! considering arm 32 bit.
> but at the first point, if in some way if prec arch level stuff and abis related framework are in place,
> then optimization on the same may lead us to get faster recording like cache implementation and so on.
> But I am not sure of any specific reason why on arm it could be very slower, having the same conf as x86.
>
> Regards,
> Oza.
>
>
> ----- Original Message ----
> From: Jakob Engblom <jakob@virtutech.com>
> To: Sean Chen <sean.chen1234@gmail.com>; Michael Snyder <msnyder@vmware.com>
> Cc: paawan oza <paawan1982@yahoo.com>; Hui Zhu <teawater@gmail.com>; gdb@sourceware.org
> Sent: Fri, December 11, 2009 1:45:48 PM
> Subject: RE: porting reversible on arm/mips
>
>> I was interested in the porting on ARM. But later I found that the
>> performance impact on ARM might damage the usage of process record. In
>> my experiment, reversible debugging is about 20000x slower, which
>> might be endurable on the modern computer. However, ARM target is tens
>> of times (or even more if we consider the memory) slower than PC. So
>> recording instructions will be very slow, about thousands of
>> instructions per second.
>
> I just must pitch in and say that it depends on the simulator.
>
> An advantage to using a full simulator is that you simplify the system and no
> longer have to care about OS calls: the OS is just part of the context you save
> and reverse. So the overhead actually goes down compared to native prec. I
> think a reversible ARM simulator can be made to run within a factor of ten of
> native speed, easily.
>
>
> Best regards,
>
> /jakob
>
> _______________________________________________________
>
> Jakob Engblom, PhD, Technical Marketing Manager
>
> Virtutech Direct: +46 8 690 07 47
> Drottningholmsvägen 22 Mobile: +46 709 242 646
> 11243 Stockholm Web: www.virtutech.com
> Sweden
> ________________________________________________________
>
>
>
>
I think ARM does be at least tens of times slower than x86. Image a PC
and a phone, ARM architecture has to sacrifice the performance to gain
the advantage of power and size saving.
Here I assume that process record is more than 20000x slower on both
x86 and ARM. I agree with you and believe this can be improved a lot
in the future.
--
Best Regards,
Sean Chen
next prev parent reply other threads:[~2009-12-11 16:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 2:42 About the link to wiki in reversible.html Hui Zhu
2009-12-10 8:14 ` porting reversible on arm/mips paawan oza
2009-12-10 23:59 ` Michael Snyder
2009-12-11 2:10 ` paawan oza
2009-12-11 2:15 ` Hui Zhu
2009-12-11 13:03 ` paawan oza
2009-12-11 16:38 ` Sean Chen
2009-12-11 3:12 ` Michael Snyder
2009-12-11 3:48 ` Sean Chen
2009-12-11 8:16 ` Jakob Engblom
2009-12-11 13:24 ` paawan oza
2009-12-11 16:42 ` Sean Chen [this message]
2009-12-11 16:35 ` Sean Chen
2009-12-11 13:07 ` paawan oza
2009-12-11 18:50 ` Michael Snyder
2009-12-11 19:04 ` Ramana Radhakrishnan
2009-12-11 19:14 ` Michael Snyder
2009-12-11 19:37 ` Ramana Radhakrishnan
2009-12-12 3:28 ` paawan oza
2009-12-14 15:42 ` paawan oza
2009-12-14 18:27 ` Michael Snyder
2009-12-10 8:15 ` About the link to wiki in reversible.html Joel Brobecker
2010-03-20 9:28 porting reversible on arm/mips paawan oza
2010-03-22 4:30 ` Sean Chen
2010-03-22 12:31 ` Joseph S. Myers
2010-03-22 14:08 ` paawan oza
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=5e81cb500912110842v5f2990ay9019e0ba4562d8c1@mail.gmail.com \
--to=sean.chen1234@gmail.com \
--cc=gdb@sourceware.org \
--cc=jakob@virtutech.com \
--cc=msnyder@vmware.com \
--cc=paawan1982@yahoo.com \
--cc=teawater@gmail.com \
/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