All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Manfred Spraul <manfred@colorfullife.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Arjan Van de Ven <arjanv@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] take 2 of the tr-based current
Date: Fri, 9 Nov 2001 04:13:27 -0500	[thread overview]
Message-ID: <20011109041327.T4087@devserv.devel.redhat.com> (raw)
In-Reply-To: <20011108190546.A29741@redhat.com> <20011108211143.A4797@redhat.com>
In-Reply-To: <20011108211143.A4797@redhat.com>; from bcrl@redhat.com on Thu, Nov 08, 2001 at 09:11:43PM -0500

On Thu, Nov 08, 2001 at 09:11:43PM -0500, Benjamin LaHaise wrote:
> On Thu, Nov 08, 2001 at 07:05:46PM -0500, Benjamin LaHaise wrote:
> > If other people could bang on this a bit and post any problems, I'd 
> > appreciate it.  tia,
> 
> Ooops.  A slight typo is fixed below.
> 
> 		-ben (who shouldn't edit patches before hitting send)
> 
> 
> diff -ur ./v2.4.13-ac8/include/asm-i386/smp.h ../toomuch-v2.4.13-ac8+tr/include/asm-i386/smp.h
> --- ./v2.4.13-ac8/include/asm-i386/smp.h	Thu Nov  8 21:07:47 2001
> +++ toomuch-v2.4.13-ac8+tr/include/asm-i386/smp.h	Thu Nov  8 21:06:25 2001
> @@ -102,7 +102,8 @@
>   * so this is correct in the x86 case.
>   */
>  
> -static unsigned get_TR(void) __attribute__ ((pure))
> +static unsigned get_TR(void) __attribute__ ((pure));
> +static unsigned get_TR(void)
>  {
>  	unsigned tr;
>  	__asm__("str %w0" : "=g" (tr));

Why not
static inline unsigned __attribute__ ((const)) get_TR(void)
{
}
?
If TR register only ever changes during cpu_init, I don't see why you
cannot use const. Using pure would mean if you do get_TR, then store
something into global memory and do get_TR again, it will be done twice.
Also, I wonder why you don't inline it.

	Jakub

  reply	other threads:[~2001-11-09  9:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20011108190546.A29741@redhat.com>
2001-11-09  2:11 ` [PATCH] take 2 of the tr-based current Benjamin LaHaise
2001-11-09  9:13   ` Jakub Jelinek [this message]
2001-11-09 14:54     ` Manfred Spraul
2001-11-09 15:03       ` David S. Miller
2001-11-09 15:33         ` Manfred Spraul
2001-11-09 16:01           ` Richard B. Johnson
2001-11-11  0:01           ` Anton Blanchard
2001-11-11  1:01             ` Benjamin LaHaise
2001-11-11  2:27               ` Anton Blanchard
2001-11-11  9:59             ` Manfred Spraul
2001-11-11 12:36               ` Anton Blanchard
2001-11-11 14:02                 ` Manfred Spraul
2001-11-12  3:32                   ` Benjamin LaHaise

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=20011109041327.T4087@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=torvalds@transmeta.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.