| Summary: | x32: identify workload & collect benchmark data to show value of x32 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Nitin Kamble <nitin.a.kamble> |
| Component: | core | Assignee: | Anuj Mittal <anuj.mittal> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | alejandro.hernandez, meta.mr.watcher, meta.watcher, rebecca.swee.fun.chang, sgw |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Nitin Kamble
2012-06-06 22:52:34 UTC
spec CPU is coined as a good candidate for this purpose So need to collect data on a real hardware for spec CPU benchmark for x32, i686 & x86-64 ABIs Bogdan, You can use a core i5 system with sugarbay bsp for this work. I will be taking care of this one. Nitin can you give me a hint about the workload for this bug, I need to fill in some estimate to help Song plan stuff for 1.4 I'll go for now with 5days. Radu, The workload is already identified for this purpose. It is Spec CPU as seen in the comment 1 bellow. Now next part is running it in 3 different configurations. 1st with a x86 image, 2nd with x86_64 iamge & 3rd with x32 image. And all this on the same hardware, so that other than the ABI all other parameters are the same. Also you need to collect 3 sets of the same data, to understand any variation in the collected data. I am changing the title of this bug to reflect the current work involved. And I think 5 days will be highly optimistic estimate. If you don't encounter any build or runtime issues, then 5 days may be right. But I am not sure the current state of x32 support. If the current x32 support is broken then that need to be fixed 1st. Any way, you can open bugs for such blocking issues and mark this bug dependent on those. so you can go with the 5 days or add 1 or 2 more days to be more safe. I am also sending you instructions I received from HJ Lu for obtaining the benchmark files. Nitin thanks Nitin, I'm going with 6 days and update appropriately once I get into the problem. This could be similar to phoronix work also |