public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Feiner <pfeiner@google.com>,
	kvm@vger.kernel.org, drjones@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH kvm-unit-tests] build: enable -Werror
Date: Fri, 4 Mar 2016 09:47:53 +0100	[thread overview]
Message-ID: <56D94BB9.3030705@redhat.com> (raw)
In-Reply-To: <1457042122-30727-1-git-send-email-pfeiner@google.com>

On 03.03.2016 22:55, Peter Feiner wrote:
> Tested with arch=i386, x86_64, ppc64, and arm64.
> 
> Signed-off-by: Peter Feiner <pfeiner@google.com>
> ---
>  Makefile        | 2 +-
>  x86/hypercall.c | 2 +-
>  x86/vmx_tests.c | 4 ++--
>  3 files changed, 4 insertions(+), 4 deletions(-)
...
> @@ -1392,6 +1390,7 @@ static void dbgctls_main(void)
>  	asm volatile("mov %%dr7,%0" : "=r" (dr7));
>  	debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR);
>  	/* Commented out: KVM does not support DEBUGCTL so far */
> +	assert(debugctl == debugctl);
>  	report("Load debug controls", dr7 == 0x404 /* && debugctl == 0x2 */);
>  
>  	dr7 = 0x408;
> @@ -1413,6 +1412,7 @@ static void dbgctls_main(void)
>  	asm volatile("mov %%dr7,%0" : "=r" (dr7));
>  	debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR);
>  	/* Commented out: KVM does not support DEBUGCTL so far */
> +	assert(debugctl == debugctl);
>  	report("Guest=host debug controls", dr7 == 0x402 /* && debugctl == 0x1 */);

Now these assert()s are really ugly. Wouldn't it be better do comment
out the "debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR);" line instead?

 Thomas


  reply	other threads:[~2016-03-04  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 21:55 [PATCH kvm-unit-tests] build: enable -Werror Peter Feiner
2016-03-04  8:47 ` Thomas Huth [this message]
2016-03-04  8:49   ` Paolo Bonzini
2016-03-04  9:00     ` Thomas Huth
2016-03-04 16:57       ` Peter Feiner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56D94BB9.3030705@redhat.com \
    --to=thuth@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pfeiner@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox