On Mon, 8 Aug 2011 12:56:10 -0700, nathan binkert <[email protected]>
wrote:
If you can provide me the diff, that would be great!
This diff doesn't give you too much, but I started by creating a
qcow_compat.cc and qcow_compat.hh in addition to sucking in a few
files from qemu that do the actual implementation. Basically, the
qcow code from qemu requires a bunch of functions from qemu (which
are
listed in a comment in qcow_compat.h). Some of those just have
different names in gem5 and some of them simply need to be
implemented. The goal should be to include the minimal qcow code and
not suck in all of qemu. I started this as basically a side project
a
long time ago and never got anywhere. Sparse files give you much of
the savings of qcow, so I've tended to use them instead. My guess is
that to get qcow working shouldn't be too much work (it's only about
2400 lines of code). You'll notice that the AES code is in the diff,
but I think it should be easy to avoid compiling that in as you'll
see
that I stubbed it out in qcow_compat.cc
Nate
Hopefully you could just use openssl for aes instead of having our own
implementation.
Ali
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
