> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Wednesday, April 19, 2017 11:58 PM
>
> * Use gprintk rather than gdprintk. These logging messages shouldn't
>disappear in release builds, as they usually happen immediately before a
>domain crash. Raise them from WARNING
Hi Andrew,
On 19/04/17 16:58, Andrew Cooper wrote:
* Use gprintk rather than gdprintk. These logging messages shouldn't
disappear in release builds, as they usually happen immediately before a
domain crash. Raise them from WARNING to ERR.
* Format the vmexit reason in the same base as
>>> On 20.04.17 at 13:01, wrote:
> On 20/04/17 11:52, Jan Beulich wrote:
>> >>> On 19.04.17 at 17:58, wrote:
>>> --- a/xen/arch/x86/hvm/svm/svm.c
>>> +++ b/xen/arch/x86/hvm/svm/svm.c
>>> @@ -2833,10 +2833,9 @@ void svm_vmexit_handler(struct
On 20/04/17 11:52, Jan Beulich wrote:
> >>> On 19.04.17 at 17:58, wrote:
>> --- a/xen/arch/x86/hvm/svm/svm.c
>> +++ b/xen/arch/x86/hvm/svm/svm.c
>> @@ -2833,10 +2833,9 @@ void svm_vmexit_handler(struct cpu_user_regs *regs)
>>
>> default:
>>
>>> On 19.04.17 at 17:58, wrote:
> --- a/xen/arch/x86/hvm/svm/svm.c
> +++ b/xen/arch/x86/hvm/svm/svm.c
> @@ -2833,10 +2833,9 @@ void svm_vmexit_handler(struct cpu_user_regs *regs)
>
> default:
> unexpected_exit_type:
> -gdprintk(XENLOG_ERR,
On 04/19/2017 11:58 AM, Andrew Cooper wrote:
> * Use gprintk rather than gdprintk. These logging messages shouldn't
>disappear in release builds, as they usually happen immediately before a
>domain crash. Raise them from WARNING to ERR.
> * Format the vmexit reason in the same base as
* Use gprintk rather than gdprintk. These logging messages shouldn't
disappear in release builds, as they usually happen immediately before a
domain crash. Raise them from WARNING to ERR.
* Format the vmexit reason in the same base as is used in the vendor
manuals (decimal for Intel,