From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: David Brownell <david-b@pacbell.net>,
linux-ide@vger.kernel.org,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [patch 2.6.29-rc2] palm_bk3710 buildfix
Date: Mon, 19 Jan 2009 13:07:33 +0100 [thread overview]
Message-ID: <200901191307.33405.bzolnier@gmail.com> (raw)
In-Reply-To: <4974408A.9050608@ru.mvista.com>
On Monday 19 January 2009, Sergei Shtylyov wrote:
> Hello, I wrote:
>
> >>>> Someone should fix hw_regs_t to neither be a typedef, nor
> >>>> use "unsigned long" where it should use "void __iomem *".
> >>>>
> >>> It cannot use pointers of course -- as the addresses can be I/O
> >>> ports.
> >>>
> >>
> >> It could use the ioread*() calls, which take pointers
> >> and handle both types of I/O in a type-safe manner.
> >>
> >
> > Probably they can... though using those would only slow down
> > register access on x86.
>
> ... and cause code bloat due to switching to real function calls from
> inlines which now should render into in/out isns.
OTOH it would allow to unify a lot of 'if (hwif->host_flags & IDE_HFLAG_MMIO)'
cases so the code may even shrink. I also suspect that register access slow
down is most likely negligable (we can always measure and check it).
The real reason for not using ioread*() and co. is that not all archs support
them (though I checked some time ago, maybe they do now?) and we don't want to
break IDE support for them.
Thanks,
Bart
next prev parent reply other threads:[~2009-01-19 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 16:33 [patch 2.6.29-rc2] palm_bk3710 buildfix David Brownell
2009-01-18 17:14 ` Sergei Shtylyov
2009-01-19 0:29 ` David Brownell
2009-01-19 8:35 ` Sergei Shtylyov
2009-01-19 8:57 ` Sergei Shtylyov
2009-01-19 12:07 ` Bartlomiej Zolnierkiewicz [this message]
2009-01-19 13:06 ` Sergei Shtylyov
2009-01-19 14:14 ` Sergei Shtylyov
2009-01-19 12:00 ` Bartlomiej Zolnierkiewicz
2009-01-19 13:03 ` Sergei Shtylyov
2009-01-19 13:21 ` Bartlomiej Zolnierkiewicz
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=200901191307.33405.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=david-b@pacbell.net \
--cc=khilman@deeprootsystems.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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.