| commit | 344ab907ff160f37732a9d78c9b30af1a5b85d24 | |
| author | Beth Kon <eak@us.ibm.com> | |
| Tue, 7 Jul 2009 15:50:34 +0000 (7 11:50 -0400) | ||
| committer | Avi Kivity <avi@redhat.com> | |
| Sun, 12 Jul 2009 13:37:40 +0000 (12 16:37 +0300) | ||
| tree | c0878a0cbb934e1f5e2088b20e3f2d22728908e5 | treesnapshot (tar.gz zip) |
| parent | 7eb2371c041fe1661f2108c92a46508272afa5e8 | commitdiff |
bios: allow qemu to configure irq0->inti2 override
Win2k8 expects the HPET interrupt on inti2, regardless of whether an
override exists in the BIOS. And the HPET spec states that in legacy
mode, timer interrupt is on inti2.
The irq0->inti2 override will always be used unless the kernel cannot
do irq routing (i.e., compatibility with old kernels). So if the
kernel is capable, userspace sets up irq0->inti2 via the irq routing
interface, and adds the irq0->inti2 override to the MADT interrupt
source override table, and the mp table (for the no-acpi case).
Signed-off-by: Beth Kon <eak@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Win2k8 expects the HPET interrupt on inti2, regardless of whether an
override exists in the BIOS. And the HPET spec states that in legacy
mode, timer interrupt is on inti2.
The irq0->inti2 override will always be used unless the kernel cannot
do irq routing (i.e., compatibility with old kernels). So if the
kernel is capable, userspace sets up irq0->inti2 via the irq routing
interface, and adds the irq0->inti2 override to the MADT interrupt
source override table, and the mp table (for the no-acpi case).
Signed-off-by: Beth Kon <eak@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
| kvm/bios/rombios32.c | diffblobblamehistory |