x86: changes to apic, keyboard
Review Request #1759 - Created March 8, 2013 and submitted
| Information | |
|---|---|
| Nilay Vaish | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 9583:5919a10e6cdd --------------------------- x86: changes to apic, keyboard It is possible that operating system wants to shutdown the lapic timer by writing timer's initial count to 0. This patch adds a check that the timer event is only scheduled if the count is 0. The patch also converts few of the panics related to the keyboard to warnings since we are any way not interested in simulating the keyboard.
Issue Summary
2
2
0
0
| Description | From | Last Updated | Status |
|---|---|---|---|
| I'm not sure what the semantics are supposed to be, but isn't the "clockEdge" function in the clocked object what ... | Andreas Hansson | March 12, 2013, 8:28 a.m. | Open |
| Is this something that happens at boot with never kernels? How difficult would it be to implement it "properly"? | Andreas Hansson | March 12, 2013, 8:28 a.m. | Open |
Posted (March 12, 2013, 8:28 a.m.)
-
src/arch/x86/interrupts.cc (Diff revision 1) -
I'm not sure what the semantics are supposed to be, but isn't the "clockEdge" function in the clocked object what is more or less expressed in the if/else statement?
-
src/dev/x86/i8042.cc (Diff revision 1) -
Is this something that happens at boot with never kernels? How difficult would it be to implement it "properly"?
Ship It!
