Re: [Qemu-devel] [PATCH v2 4/7] s390x/tcg: SET CLOCK COMPARATOR can clear CKC interrupts

[David Hildenbrand]

On 21.06.2018 14:09, Thomas Huth wrote:
> On 20.06.2018 12:08, David Hildenbrand wrote:
>> Let's stop the timer and delete any pending CKC IRQ before doing
>> anything else.
>>
>> Signed-off-by: David Hildenbrand <address@hidden>
>> ---
>>  target/s390x/misc_helper.c | 6 ++++++
>>  1 file changed, 6 insertions(+)
>>
>> diff --git a/target/s390x/misc_helper.c b/target/s390x/misc_helper.c
>> index 6ccbe1fe9a..d5f9f5e1d3 100644
>> --- a/target/s390x/misc_helper.c
>> +++ b/target/s390x/misc_helper.c
>> @@ -158,6 +158,12 @@ void HELPER(sckc)(CPUS390XState *env, uint64_t time)
>>      Error *err = NULL;
>>      S390TOD tod_base;
>>  
>> +    /* stop the timer and remove pending CKC IRQs */
>> +    timer_del(env->tod_timer);
>> +    qemu_mutex_lock_iothread();
>> +    env->pending_int &= ~INTERRUPT_EXT_CLOCK_COMPARATOR;
>> +    qemu_mutex_unlock_iothread();
> 
> Reviewed-by: Thomas Huth <address@hidden>
> 
>>      if (time == -1ULL) {
> 
> I wonder whether that check is still adequate? Is there really a way to
> disable the clock comparator like this? At least I haven't seen it in
> the PoP.

e.g. 4-61 (Control)

4. When the clock-comparator sign control is zero,
(a) the program can set the clock comparator to
all zeros to ensure that an interruption condition
is immediately present, and (b) the program can
set the clock comparator to a value of all binary
ones to ensure that a clock-comparator interrup-
tion is never recognized. [...]

Rational from 4-59 (Control):

The clock comparator provides a means of causing
an interruption when the TOD-clock value exceeds a
value specified by the program.

We can never exceed all binary 1s. So it is really exceeding, not "hitting"


> 
>>          return;
>>      }
>>
> 


-- 

Thanks,

David / dhildenb