public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: David Hildenbrand <david@redhat.com>,
	Drew Jones <drjones@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [kvm-unit-tests PATCH] Fixes for the umip test
Date: Wed, 22 Jan 2020 17:39:25 +0100	[thread overview]
Message-ID: <878slzsawy.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20200122160944.29750-1-thuth@redhat.com>

Thomas Huth <thuth@redhat.com> writes:

> When compiling umip.c with -O2 instead of -O1, there are currently
> two problems. First, the compiler complains:
>
>  x86/umip.c: In function ‘do_ring3’:
>  x86/umip.c:162:37: error: array subscript 4096 is above array bounds of
>     ‘unsigned char[4096]’ [-Werror=array-bounds]
>        [user_stack_top]"m"(user_stack[sizeof user_stack]),
>                            ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
>
> This can be fixed by initializing the stack to point to one of the last
> bytes of the array instead.
>
> The second problem is that some tests are failing - and this is due
> to the fact that the GP_ASM macro uses inline asm without the "volatile"
> keyword - so that the compiler reorders this code in certain cases
> where it should not. Fix it by adding "volatile" here.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  x86/umip.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/x86/umip.c b/x86/umip.c
> index 7eee294..834668c 100644
> --- a/x86/umip.c
> +++ b/x86/umip.c
> @@ -22,7 +22,8 @@ static void gp_handler(struct ex_regs *regs)
>  
>  
>  #define GP_ASM(stmt, in, clobber)                  \
> -     asm ("mov" W " $1f, %[expected_rip]\n\t"      \
> +    asm volatile (                                 \
> +          "mov" W " $1f, %[expected_rip]\n\t"      \
>            "movl $2f-1f, %[skip_count]\n\t"         \
>            "1: " stmt "\n\t"                        \
>            "2: "                                    \
> @@ -159,7 +160,7 @@ static int do_ring3(void (*fn)(const char *), const char *arg)
>  		  : [ret] "=&a" (ret)
>  		  : [user_ds] "i" (USER_DS),
>  		    [user_cs] "i" (USER_CS),
> -		    [user_stack_top]"m"(user_stack[sizeof user_stack]),
> +		    [user_stack_top]"m"(user_stack[sizeof user_stack -  2]),

My eyes would definitely appreciate the missing parentheses and the
absense of the redundant space:

  sizeof(user_stack) - 2

>  		    [fn]"r"(fn),
>  		    [arg]"D"(arg),
>  		    [kernel_ds]"i"(KERNEL_DS),

Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>

-- 
Vitaly


      reply	other threads:[~2020-01-22 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 16:09 [kvm-unit-tests PATCH] Fixes for the umip test Thomas Huth
2020-01-22 16:39 ` Vitaly Kuznetsov [this message]

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=878slzsawy.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=thuth@redhat.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