[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 0/5] hvf: stability fixes for HVF
|
From: |
Cameron Esfahani |
|
Subject: |
Re: [PATCH v2 0/5] hvf: stability fixes for HVF |
|
Date: |
Tue, 26 Nov 2019 12:10:15 -0800 |
Let me see if I can add some assertions.
Cameron Esfahani
address@hidden
"The cake is a lie."
Common wisdom
> On Nov 25, 2019, at 2:28 AM, Paolo Bonzini <address@hidden> wrote:
>
> Certainly no doubt about patches 1-4, while for patch 5 I'm wondering if
> it's masking another bug; I'd prefer to have also some assertions that
> interrupt_injected is never an exception and exception_nr is never an
> interrupt.
>
- [PATCH v2 0/5] hvf: stability fixes for HVF, Cameron Esfahani, 2019/11/24
- [PATCH v2 4/5] hvf: more accurately match SDM when setting CR0 and PDPTE registers, Cameron Esfahani, 2019/11/24
- [PATCH v2 2/5] hvf: remove TSC synchronization code because it isn't fully complete, Cameron Esfahani, 2019/11/24
- [PATCH v2 3/5] hvf: correctly handle REX prefix in relation to legacy prefixes, Cameron Esfahani, 2019/11/24
- [PATCH v2 5/5] hvf: save away type as well as vector so we can reinject them, Cameron Esfahani, 2019/11/24
- [PATCH v2 1/5] hvf: non-RAM, non-ROMD memory ranges are now correctly mapped in, Cameron Esfahani, 2019/11/24
- Re: [PATCH v2 0/5] hvf: stability fixes for HVF, Paolo Bonzini, 2019/11/25
- Re: [PATCH v2 0/5] hvf: stability fixes for HVF,
Cameron Esfahani <=