From: Chris Newport <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32: git SCSI and fs
Date: Sun, 23 Jul 2006 13:24:20 +0000 [thread overview]
Message-ID: <44C37884.6010200@netunix.com> (raw)
In-Reply-To: <20060719.134205.74563314.davem@davemloft.net>
David Miller wrote:
>From: Chris Newport <crn@netunix.com>
>Date: Fri, 21 Jul 2006 23:03:31 +0100
>
>
>
>>A year or so ago I did a few patches for Sun4d and there was a note in
>>the iommu code about sun4d not having a register that was used for
>>scratch data in sun4m.
>>Could this bug be back ?
>>
>>Sorry to be vague, this is from memory.
>>
>>
>
>It would be nice to have something specific, I see nothing
>explicit in the current tree:
>
>
>
I have not been able to find the file with the relevant comment, but
looking back in my mail archive, it seems to relate to this code in
2.4.26 include/asm-sparc/winmacro.h, looks like jj has created a workaround.
Maybe need to look at earlier 2.4 versions before the comment got dropped.
#ifdef CONFIG_SMP
#define LOAD_CURRENT4M(dest_reg, idreg) \
rd %tbr, %idreg; \
sethi %hi(C_LABEL(current_set)), %dest_reg; \
srl %idreg, 10, %idreg; \
or %dest_reg, %lo(C_LABEL(current_set)), %dest_reg; \
and %idreg, 0xc, %idreg; \
ld [%idreg + %dest_reg], %dest_reg;
/* Sliiick. We have a Linux current register :) -jj */
#define LOAD_CURRENT4D(dest_reg) \
lda [%g0] ASI_M_VIKING_TMP2, %dest_reg;
/* Blackbox - take care with this... - check smp4m and smp4d before
changing thi
s. */
prev parent reply other threads:[~2006-07-23 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 20:42 sparc32: git SCSI and fs David Miller
2006-07-19 20:47 ` Raymond Burns
2006-07-20 2:46 ` David Miller
2006-07-20 2:50 ` Raymond Burns
2006-07-20 3:44 ` Raymond Burns
2006-07-20 3:51 ` David Miller
2006-07-21 21:30 ` Raymond Burns
2006-07-21 21:39 ` David Miller
2006-07-21 21:40 ` David Miller
2006-07-21 22:03 ` Chris Newport
2006-07-21 22:33 ` Raymond Burns
2006-07-22 8:35 ` David Miller
2006-07-22 9:04 ` David Miller
2006-07-23 13:24 ` Chris Newport [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=44C37884.6010200@netunix.com \
--to=crn@netunix.com \
--cc=sparclinux@vger.kernel.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.