The more I'm thinking about this whole issue, the more I'm thinking this
is really misdirected.

I'm starting to think that the right thing to do might very well be as
follows:

- Change the payload of the bzImage file from a flat binary to an ELF
  file -- a stripped vmlinux.gz.
- Change the decompressor to incorporate a (simple) ELF parser.
- Incorporate a couple of pointer fields in the bzImage header that
  points directly to the payload, the format of which can be identified
  via its magic number (currently gzip).

That way the environments that want to enter at the protected-mode
entrypoint can do their own setup using whatever information is retained
in the payload.  Since most of these environments are currently using
vmlinux as their boot file, this seems to make sense.

The more I hear about copying notes and various things from vmlinux to
bzImage the more I'm convinced that this is a huge kluge.  Furthermore,
there are *definitely* virtual environments which would be much happier
to be able to decompress in host space.  The decompressor doesn't run
well in many simulators.

        -hpa
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/virtualization

Reply via email to