Alexander Graf <ag...@suse.de> writes: [...] > Imagine, your host can only do 32 bit file offsets. You want to > emulate a 64bit guest though. To load an image, you say "load the > image at offset x, max size <guest ram size - x>". If you use size_t, > it would break for large ram guests, because the size really means > semantically that you want to be able to load into address > [x...ram_size] of the guest's physical memory range. If the host can > actually load images that big is an orthogonal question.
A host with 64 bit virtual address space, yet file offsets (and thus file sizes) limited to 32 bits? That's a contrived example if I ever saw one. You need to come up with a remotely practical one to convince me :)
