On 07/16/2018 09:33 AM, Andrew Cooper wrote:
> On 06/06/18 14:37, Jan Beulich wrote:
>> >>> On 04.06.18 at 15:59, wrote:
>>> * State adjustments (and debug tracing) for #DB/#BP/#PF should not be done
>>>for `int $n` instructions. Updates to %cr2 occur even if the exception
>>>combines
On 06/06/18 14:37, Jan Beulich wrote:
> >>> On 04.06.18 at 15:59, wrote:
>> * State adjustments (and debug tracing) for #DB/#BP/#PF should not be done
>>for `int $n` instructions. Updates to %cr2 occur even if the exception
>>combines to #DF.
>> * Don't opencode DR_STEP when updating
>>> On 04.06.18 at 15:59, wrote:
> * State adjustments (and debug tracing) for #DB/#BP/#PF should not be done
>for `int $n` instructions. Updates to %cr2 occur even if the exception
>combines to #DF.
> * Don't opencode DR_STEP when updating %dr6.
> * Simplify the logic for calling
* State adjustments (and debug tracing) for #DB/#BP/#PF should not be done
for `int $n` instructions. Updates to %cr2 occur even if the exception
combines to #DF.
* Don't opencode DR_STEP when updating %dr6.
* Simplify the logic for calling svm_emul_swint_injection() as in the common
