All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] x86: Use __always_inline to ensure scale_delta linked to vsyscall section.
Date: Fri, 13 Nov 2009 23:10:08 -0800	[thread overview]
Message-ID: <4AFE57D0.8080100@goop.org> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC201CD31FD1D@pdsmsx503.ccr.corp.intel.com>

On 11/13/09 20:53, Zhang, Xiantao wrote:
> Hi, Jeremy
>  The attached patch should fix the bug: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1529 which blocked us for weeks.  Since scale_delta is used in the vsyscall vtime, so it should be inlined and linked to vsycall section, otherwise, dom0 should refuse the call. But due to GCC's optimization, scale_delta is compiled to a global function instead of inline function even if it is declared with inline attribute, so the issue occurs.  To ensure this function is inlined to vsyscall section, a stricter attribute __always_inline should be used in its declaration. Thanks!
>   

Thanks for tracking that down.

    J

> Xiantao
>
>
> From 3290d6e40f6c69ce3edd728f57780f088b7155e3 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Fri, 13 Nov 2009 20:33:10 -0500
> Subject: [PATCH] x86: Use __always_inline to ensure scale_delta linked to vsyscall section.
>  
> scale_delta is called in vsyscall vtime, so it should be linked to vsyscall
> section and use fixmap to access it, otherwise unexpected page fault may raise
> in vsyscall context, and leads to system dom0 panic.
>  
> Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
> ---
>  arch/x86/kernel/pvclock.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
>  
> diff --git a/arch/x86/kernel/pvclock.c b/arch/x86/kernel/pvclock.c
> index f47f91e..1b5d3e8 100644
> --- a/arch/x86/kernel/pvclock.c
> +++ b/arch/x86/kernel/pvclock.c
> @@ -28,7 +28,8 @@
>   * Scale a 64-bit delta by scaling and multiplying by a 32-bit fraction,
>   * yielding a 64-bit result.
>   */
> -static inline u64 scale_delta(u64 delta, u32 mul_frac, int shift)
> +static __always_inline
> +u64 scale_delta(u64 delta, u32 mul_frac, int shift)
>  {
>   u64 product;
>  #ifdef __i386__
>   

      reply	other threads:[~2009-11-14  7:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-14  4:53 [PATCH] x86: Use __always_inline to ensure scale_delta linked to vsyscall section Zhang, Xiantao
2009-11-14  7:10 ` Jeremy Fitzhardinge [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=4AFE57D0.8080100@goop.org \
    --to=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=xiantao.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.