diff options
| author | Scott Moser <smoser@ubuntu.com> | 2012-03-26 15:27:00 -0400 |
|---|---|---|
| committer | Anthony Liguori <aliguori@us.ibm.com> | 2012-05-29 20:19:24 -0500 |
| commit | 9c3a596a03cc10c2d9097f057b9ccb9d557a4d5f (patch) | |
| tree | 32dd3d1afcf98f9bd08a901a2aff073dbe5678e8 /hw/acpi_piix4.c | |
| parent | 8294a64d7f9ecc428cd58ba36ad0b913084a8824 (diff) | |
| download | qemu-9c3a596a03cc10c2d9097f057b9ccb9d557a4d5f.zip qemu-9c3a596a03cc10c2d9097f057b9ccb9d557a4d5f.tar.gz qemu-9c3a596a03cc10c2d9097f057b9ccb9d557a4d5f.tar.bz2 | |
fix multiboot loading if load_end_addr == 0
The previous multiboot load code did not treat the case where
load_end_addr was 0 specially. The multiboot specification says the
following:
* load_end_addr
Contains the physical address of the end of the data segment.
(load_end_addr - load_addr) specifies how much data to load. This
implies that the text and data segments must be consecutive in the
OS image; this is true for existing a.out executable formats. If
this field is zero, the boot loader assumes that the text and data
segments occupy the whole OS image file.
Signed-off-by: Scott Moser <smoser@ubuntu.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'hw/acpi_piix4.c')
0 files changed, 0 insertions, 0 deletions