Il 26/03/2014 21:20, Matt Lupfer ha scritto:
On 02/22/2014 02:01 AM, Paolo Bonzini wrote:
Il 22/02/2014 05:37, Matt Lupfer ha scritto:
A HPET timer can be started when HPET is not yet
enabled. This will not generate an interrupt
to the guest, but causes problems when HPET is later
enabled.
A
On Fri, Feb 21, 2014 at 09:37:23PM -0700, Matt Lupfer wrote:
A HPET timer can be started when HPET is not yet
enabled. This will not generate an interrupt
to the guest, but causes problems when HPET is later
enabled.
A timer that is created and expires at least once before
HPET is enabled
On 02/22/2014 02:01 AM, Paolo Bonzini wrote:
Il 22/02/2014 05:37, Matt Lupfer ha scritto:
A HPET timer can be started when HPET is not yet
enabled. This will not generate an interrupt
to the guest, but causes problems when HPET is later
enabled.
A timer that is created and expires at least
Il 22/02/2014 05:37, Matt Lupfer ha scritto:
A HPET timer can be started when HPET is not yet
enabled. This will not generate an interrupt
to the guest, but causes problems when HPET is later
enabled.
A timer that is created and expires at least once before
HPET is enabled will have an
On 22 Feb 2014, at 04:37, Matt Lupfer wrote:
A HPET timer can be started when HPET is not yet
enabled. This will not generate an interrupt
to the guest, but causes problems when HPET is later
enabled.
A timer that is created and expires at least once before
HPET is enabled will have an
Il 22/02/2014 10:03, Alex Bligh ha scritto:
I am unfamiliar with the HPET code but symmetry suggests perhaps the 'else'
condition should be changed too:
} else if (deactivating_bit(old_val, new_val, HPET_TN_ENABLE) ||
!hpet_enabled(s)) {
Paolo,
On 22 Feb 2014, at 10:55, Paolo Bonzini wrote:
Il 22/02/2014 10:03, Alex Bligh ha scritto:
I am unfamiliar with the HPET code but symmetry suggests perhaps the 'else'
condition should be changed too:
} else if (deactivating_bit(old_val, new_val, HPET_TN_ENABLE) ||
Il 22/02/2014 13:25, Alex Bligh ha scritto:
Paolo,
On 22 Feb 2014, at 10:55, Paolo Bonzini wrote:
Il 22/02/2014 10:03, Alex Bligh ha scritto:
I am unfamiliar with the HPET code but symmetry suggests perhaps the 'else'
condition should be changed too:
} else if
A HPET timer can be started when HPET is not yet
enabled. This will not generate an interrupt
to the guest, but causes problems when HPET is later
enabled.
A timer that is created and expires at least once before
HPET is enabled will have an initialized comparator based
on a hpet_offset of 0
