aboutsummaryrefslogtreecommitdiff
path: root/vl.c
diff options
context:
space:
mode:
authorJes Sorensen <jes@sgi.com>2009-08-06 16:25:50 +0200
committerAnthony Liguori <aliguori@us.ibm.com>2009-08-24 08:01:41 -0500
commit6b35e7bf488a894f8d9315d05846aae9bf580425 (patch)
treec9413b3cdd4a92d358effda41624e7dbd40626e8 /vl.c
parente8b54394950f975c1b31d2359cf58ca4d9f51b00 (diff)
downloadqemu-6b35e7bf488a894f8d9315d05846aae9bf580425.zip
qemu-6b35e7bf488a894f8d9315d05846aae9bf580425.tar.gz
qemu-6b35e7bf488a894f8d9315d05846aae9bf580425.tar.bz2
QEMU set irq0override in fw_cfg
Hi, After discussing the issue with Avi, Gleb and a couple others on irq, we came to the conclusion that it is preferred to have QEMU request features from the BIOS, rather than notifying the BIOS that it is running on QEMU or KVM. This way memory ranges can change etc. and an older BIOS will continue to work on newer QEMU if it receives the info as a fw_cfg value. This one also matches what qemu-kvm does for irq0override, except I haven't made it configurable. I leave that as an exercise for whoever would be interested in switching off irq0override. Thanks, Jes Set irq0 override in fw_cfg, informing the BIOS that QEMU expects override on irq0. This matches qemu-kvm, and will help sharing a single BIOS binary. Signed-off-by: Jes Sorensen <jes@sgi.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'vl.c')
-rw-r--r--vl.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/vl.c b/vl.c
index 0bcc0c9..91d3f78 100644
--- a/vl.c
+++ b/vl.c
@@ -227,6 +227,7 @@ int no_reboot = 0;
int no_shutdown = 0;
int cursor_hide = 1;
int graphic_rotate = 0;
+uint8_t irq0override = 1;
#ifndef _WIN32
int daemonize = 0;
#endif