Hi Andreas, My username for the gem5 wiki is Pcabre
I agree that it makes sense to have something that gets distributed with gem5 that automatically builds the kernels, the bootloaders and the DTBs (disk images may be another story though). Were you thinking about something like a python script in the "util" directory? If yes, I should be able to do it. Thanks, Pau -----Original Message----- From: Andreas Sandberg [mailto:[email protected]] Sent: jueves, 27 de abril de 2017 15:17 To: gem5 Developer List <[email protected]> Subject: Re: [gem5-dev] update ARM Full-System Files (aarch-system-2014-10.tar.xz) Hi Pau, Thanks for creating these instructions and Dockerfiles! This is something that has been on my todo/wish list for a very long time. I should be able to give you the permissions necessary to upload the system image to the wiki. Do you have a user name that I can bless? It'd be nice if we could standardise and automate the process of updating the distribution binaries using a set of scripts that get distributed with gem5. Docker is very convenient, but is a bit of overkill if you already have the necessary environment up and running on your workstation. The Docker script could then reuse these scripts for automation. This would be a much appreciated contribution. How would you feel about contributing these scripts in that way? Cheers, Andreas On 21/04/2017 15:10, Pau Cabre wrote: > Hi all, > > I made some changes to the Dockerfile in order to generated DTBs and kernel > filenames more in accordance with the current names in > aarch-system-2014-10.tar.xz. > The newly generated files can be found here: > https://github.com/metempsy/gem5_arm_fullsystem_files_generator/releas > es/download/20170421/aarch-system-20170421.tar.xz > > I have also just pushed a changeset to gerrit in order to use these > new files: https://gem5-review.googlesource.com/2841 > With these changes, if the new filenames are not found, the old ones will be > used. > > If the changes get accepted, it would be good to copy the > aarch-system-20170421.tar.xz file to somewhere in the gem5.org wiki. > > Thanks, > Pau > > -----Original Message----- > From: Pau Cabre [mailto:[email protected]] > Sent: jueves, 13 de abril de 2017 0:41 > To: [email protected] > Subject: Re: [gem5-dev] update ARM Full-System Files > (aarch-system-2014-10.tar.xz) > > Hi Mohammad, > > I have posted a Dockerfile to generate up-to-date arm full system > files (to the best of my knowledge) in this repository: > https://github.com/metempsy/gem5_arm_fullsystem_files_generator/ > You can also directly access the generated files here: > https://github.com/metempsy/gem5_arm_fullsystem_files_generator/releas > es/download/201704/aarch-system-2017-04.tar.xz > > The README.md has some information and command line examples for using the > new files. > > Please feel free to try/modify them and provide any feedback. > > If everybody agrees with these new files, ideally we should upload the > released .tar.xz file to the gem5.org wiki and do some small changes to > FSConfig.py in order to use the new files by default. > > Thank you very much! > Pau > > > -----Original Message----- > From: Mohammad Alian [mailto:[email protected]] > Sent: martes, 11 de abril de 2017 21:19 > To: gem5 Developer List <[email protected]> > Subject: Re: [gem5-dev] update ARM Full-System Files > (aarch-system-2014-10.tar.xz) > > Thanks a lot for bringing this up. I wanted to start such conversation for a > long time as all the full system files in the webpage are deprecated. > > Thank you, > Mohammad > > On Fri, Apr 7, 2017 at 9:59 AM, Pau Cabre <[email protected]> wrote: > >> Hi all, >> >> >> >> I would like to start a discussion about updating the >> http://www.gem5.org/dist/current/arm/aarch-system-2014-10.tar.xz >> file, which should contain the necessary files for running arm >> FullSystem simulations. >> >> To the best of my knowledge, it has at least a couple of deprecated files: >> >> 1) binaries/boot_emm.arm64 (generated from >> system/arm/aarch64_bootloader/boot.S, which got updated on >> 2015-07-15) >> >> 2) binaries/vexpress.aarch64.20140821.dtb (it has a misconfiguration, >> as explained by Andreas Sandberg here => >> http://www.mail-archive.com/[email protected]/msg18440.html) >> >> >> >> And I also suspect that the /sbin/m5 binary of the images in the >> disks directory is not compatible anymore with the current m5 >> initparam pseudo-instruction, as I am getting the following assertion >> failure when trying to use it in a simulated system of >> aarch64-ubuntu-trusty-headless.img: >> >> >> >> gem5.opt: build/ARM/sim/pseudo_inst.cc:398: uint64_t >> PseudoInst::initParam(ThreadContext*, uint64_t, uint64_t): Assertion >> `key_str2 == 0' failed. >> >> >> >> Given this, I think that it would be good to update such deprecated >> files, and it would be also good to add some new files required by >> simulations of the VExpress_GEM5_V1 platform, namely: >> >> >> >> a) The vmlinux files resulting from the compilations described here >> => http://gem5.org/ARM_Linux_Kernel#Linux_4.x >> >> b) The DTBs from the compilations in the system/arm/dt directory of a >> gem5 checkout >> >> >> >> Does anybody see any inconvenient? >> >> >> >> If there is a consensus on the upgrade, if you want I can provide a >> Dockerfile with the necessary steps to build the new file (or if I >> get the right permissions, I can upload the ~630MB file to the >> gem5.org wiki and add a page explaining how it was generated). >> >> >> >> Also, after these changes, we should also update "default_dtbs" and >> "default_kernels" in FSConfig.py in order to look for the right DTB >> and kernel for VExpress_GEM5_V1, and in turn, add some regression >> tests for this new platform. >> >> >> >> Thank you very much, >> >> Pau >> >> >> >> _______________________________________________ >> gem5-dev mailing list >> [email protected] >> http://m5sim.org/mailman/listinfo/gem5-dev > > > > > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
