From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
fischer@linux-buechse.de, linux-scsi@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: Why is AHA152X_CS !64BIT?
Date: Tue, 7 Sep 2010 17:12:54 -0400 [thread overview]
Message-ID: <201009071712.54867.konrad@darnok.org> (raw)
In-Reply-To: <4C7B924D.6030703@panasas.com>
On Monday 30 August 2010 07:13:17 Boaz Harrosh wrote:
> On 08/23/2010 10:59 PM, Jiri Slaby wrote:
> > Hi,
> >
> > I see that the aha152x driver for pcmcia is marked as unsupported on
> > 64bit. But I also see a patch [1] which removes the restriction based on
> > user's testing in bugzilla [2].
> >
> > Is there a reason why it would have to be marked as !64BIT? I'm asking
> > because there is an opensuse user with this card who updated to 64-bit
> > distro and lost this driver thereafter.
> >
> > [1] http://kerneltrap.org/mailarchive/linux-scsi/2010/3/6/6832393
> > [2] https://bugzilla.kernel.org/show_bug.cgi?id=14333
> >
> > thanks,
>
> If memory serves correctly, it might be that you need more then 4 Gbyte
> of memory installed to exercise the bug, something about IO bouncing
> addresses > 4G.
If the machine is using SWIOTLB, then the bounce buffer would be activated. By
default if your machine has more than 4GB compiled under x86_64 the SWIOTLB
is turned on - but if you have an Intel/AMD IOMMU it gets turned off. Which
is OK as the Intel/AMD IOMMUs would handle the 4GB restricted devices. So as
long as the driver has pci_dma_mask_set.
Looking at the git gui blame tool history, the reason that was added was
for 'allow drivers to be built non-modular'.
So, does this driver build if you make it non-modular?
next prev parent reply other threads:[~2010-09-07 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 19:59 Why is AHA152X_CS !64BIT? Jiri Slaby
2010-08-30 11:13 ` Boaz Harrosh
2010-09-07 21:12 ` Konrad Rzeszutek Wilk [this message]
2010-09-07 21:41 ` Randy Dunlap
2010-09-07 21:48 ` Randy Dunlap
2010-09-07 22:10 ` James Bottomley
2010-09-07 22:16 ` Jiri Slaby
2010-09-09 20:01 ` =?unknown-8bit?B?SvxyZ2VuIEUu?= Fischer
2010-09-07 22:10 ` Jiri Slaby
2010-09-08 6:05 ` Andi Kleen
2010-09-08 15:30 ` James Bottomley
2010-09-09 6:50 ` Andi Kleen
2010-09-24 19:55 ` Jiri Slaby
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=201009071712.54867.konrad@darnok.org \
--to=konrad@darnok.org \
--cc=bharrosh@panasas.com \
--cc=fischer@linux-buechse.de \
--cc=jslaby@suse.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.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.