All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Andi Kleen <andi@firstfloor.org>,
	tglx@linutronix.de, mingo@redhat.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: asm-x86/msr.h for sanitized headers: clean it or punt it
Date: Wed, 2 Jan 2008 03:20:26 +0200	[thread overview]
Message-ID: <20080102012026.GM27566@does.not.exist> (raw)
In-Reply-To: <200712311349.28081.vapier@gentoo.org>

On Mon, Dec 31, 2007 at 01:49:27PM -0500, Mike Frysinger wrote:
> Use __asm__ and __volatile__ in code that is exported to userspace.  Wrap
> kernel functions with __KERNEL__ so they get scrubbed.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> diff --git a/include/asm-x86/msr.h b/include/asm-x86/msr.h
> index ba4b314..664a2fa 100644
> --- a/include/asm-x86/msr.h
> +++ b/include/asm-x86/msr.h
>...
>  #define rdtscp(low,high,aux) \
> -     asm volatile (".byte 0x0f,0x01,0xf9" : "=a" (low), "=d" (high), "=c" (aux))
> +     __asm__ __volatile__ (".byte 0x0f,0x01,0xf9" : "=a" (low), "=d" (high), "=c" (aux))
>  
>  #define rdtscll(val) do { \
>       unsigned int __a,__d; \
> -     asm volatile("rdtsc" : "=a" (__a), "=d" (__d)); \
> +     __asm__ __volatile__("rdtsc" : "=a" (__a), "=d" (__d)); \
>       (val) = ((unsigned long)__a) | (((unsigned long)__d)<<32); \
>  } while(0)
>  
>  #define rdtscpll(val, aux) do { \
>       unsigned long __a, __d; \
> -     asm volatile (".byte 0x0f,0x01,0xf9" : "=a" (__a), "=d" (__d), "=c" (aux)); \
> +     __asm__ __volatile__ (".byte 0x0f,0x01,0xf9" : "=a" (__a), "=d" (__d), "=c" (aux)); \
>       (val) = (__d << 32) | __a; \
>  } while (0)
>...

How is this part of the kernel<->userspace interface?

Unless I miss anything this sounds more like userspace abusing kernel 
headers as a utility library?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      parent reply	other threads:[~2008-01-02  1:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-31  5:45 asm-x86/msr.h for sanitized headers: clean it or punt it Mike Frysinger
2007-12-31  5:51 ` H. Peter Anvin
2007-12-31 12:26 ` Andi Kleen
2007-12-31 15:33   ` Mike Frysinger
2007-12-31 16:36     ` Andi Kleen
2007-12-31 18:10       ` Mike Frysinger
2007-12-31 18:15         ` H. Peter Anvin
2007-12-31 18:49           ` Mike Frysinger
2008-01-01 15:47             ` Ingo Molnar
2008-01-02  1:20             ` Adrian Bunk [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=20080102012026.GM27566@does.not.exist \
    --to=bunk@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vapier@gentoo.org \
    /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.