From: Manfred Spraul <manfred@colorfullife.com>
To: "David S. Miller" <davem@redhat.com>
Cc: jakub@redhat.com, bcrl@redhat.com, torvalds@transmeta.com,
alan@lxorguk.ukuu.org.uk, arjanv@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] take 2 of the tr-based current
Date: Fri, 09 Nov 2001 16:33:04 +0100 [thread overview]
Message-ID: <3BEBF730.86CAE1CC@colorfullife.com> (raw)
In-Reply-To: <20011108211143.A4797@redhat.com> <20011109041327.T4087@devserv.devel.redhat.com> <3BEBEE0B.BA1FD7EE@colorfullife.com> <20011109.070312.88700201.davem@redhat.com>
"David S. Miller" wrote:
>
> From: Manfred Spraul <manfred@colorfullife.com>
> Date: Fri, 09 Nov 2001 15:54:03 +0100
>
> Jakub Jelinek wrote:
> > If TR register only ever changes during cpu_init, I don't see why you
> > cannot use const.
>
> The task register is only pure, not const.
>
> As far as what the compiler can see or care about, it is
> const.
>
No. const == never changes.
get_TR changes if a task calls schedule, and return on another cpu.
<<<
+static unsigned get_TR(void) __attribute__ ((pure))
+{
+ unsigned tr;
+ __asm__("str %w0" : "=g" (tr));
+ return tr;
+}
+
+#define smp_processor_id() ( ((get_TR() >> 3) - __FIRST_TSS_ENTRY)
>> 2 )
<<<
smp_processor_id() is definitively not const.
OTHO 'current' is const.
--
Manfred
next prev parent reply other threads:[~2001-11-09 15:33 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
2001-11-09 14:54 ` Manfred Spraul
2001-11-09 15:03 ` David S. Miller
2001-11-09 15:33 ` Manfred Spraul [this message]
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=3BEBF730.86CAE1CC@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=bcrl@redhat.com \
--cc=davem@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox