|
From: Vasily G. <vas...@gm...> - 2013-08-07 14:12:11
|
OK, thanks! And a couple of words about cross-platform checking. If I did understand you correct you propose smth like running valgrind under quemu (1) or whole quemu under valgrind (2). (2) - will be significantly slower because we need to instrument whole system (not one binary\application) (1) - as far as I know only code generation (from arm to x86 binary) made by quemu-user decreases work of application x4. And we will need to use system-wide quemu (not only user) that also decreases speed. So, now ARM has more than 1GHz and we will not improve situation with 4Ghz host. I think that we can use assessment of quemu even if we plan write our own VM in Valgrind. Maybe I am wrong. On Wed, Aug 7, 2013 at 4:54 PM, John Reiser <jr...@bi...> wrote: > > Can you specify some areas where 64 bit ARM is being used? > > I mean some links on real devices, systems, etc.? > > Does some company use it in mobile devices (phones, tablets)? > > So far, 64-bit ARM is for use in data centers which desire > lower power consumption and lower cooling costs, but still > must handle larger address spaces. Battery-powered or > portable devices prefer 32 bits because of monetary cost, > physical size, and software issues. > > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > -- Best Regards, Vasily |