From: Christoph Hellwig <hch@lst.de>
To: Emoore@lsil.com
Cc: linux-scsi@vger.kernel.org
Subject: fusion problems on 64bit hosts
Date: Sat, 25 Sep 2004 15:57:14 +0200 [thread overview]
Message-ID: <20040925135714.GA19990@lst.de> (raw)
compiling fusion on ppc64 gives:
drivers/message/fusion/mptbase.c: In function `mpt_interrupt':
drivers/message/fusion/mptbase.c:360: warning: cast to pointer from integer of different size
drivers/message/fusion/mptbase.c:384: warning: cast to pointer from integer of different size
drivers/message/fusion/mptlan.c: In function `lan_reply':
drivers/message/fusion/mptlan.c:214: warning: cast from pointer to integer of different size
This is because of:
#if defined(__alpha__) || defined(__sparc_v9__) || defined(__ia64__) || defined(__x86_64__)
#define CAST_U32_TO_PTR(x) ((void *)(u64)x)
#define CAST_PTR_TO_U32(x) ((u32)(u64)x)
#else
#define CAST_U32_TO_PTR(x) ((void *)x)
#define CAST_PTR_TO_U32(x) ((u32)x)
#endif
which shuts the warning up on some 64bit architectures but doesn't solve
the problem. You're trying to keep a 64bit pointer in a 32bit hardware
register which can't work on 64bit architectures (the code if for the
networking and target modules that few people use)
The right fix is to only store a 32bit lookup key for some datastructure
in the register and use it as lookup key in the intr handler.
next reply other threads:[~2004-09-25 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 13:57 Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-27 22:12 fusion problems on 64bit hosts Moore, Eric Dean
2004-09-27 22:20 ` James Bottomley
2004-09-27 22:23 ` Christoph Hellwig
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=20040925135714.GA19990@lst.de \
--to=hch@lst.de \
--cc=Emoore@lsil.com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox