From: Robin Holt <holt@sgi.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: "Luck, Tony" <tony.luck@intel.com>,
DuanZhenzhong <zhenzhong.duan@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>
Subject: Re: memcpy_fromio in dmi_scan.c
Date: Thu, 25 Apr 2013 05:02:46 -0500 [thread overview]
Message-ID: <20130425100246.GR3672@sgi.com> (raw)
In-Reply-To: <1366831328.4618.476.camel@chaos.site>
On Wed, Apr 24, 2013 at 09:22:08PM +0200, Jean Delvare wrote:
> Hi Tony,
>
> Thanks for stepping in.
>
> Le Tuesday 23 April 2013 à 22:00 +0000, Luck, Tony a écrit :
> > > I don't have much knowledge about IA64 either. All I see is that while
> > > x86 implements memcpy_fromio() with memcpy [1], ia64 implements it with
> > > readb [2]. There must be a reason for that, and I can only suppose that
> > > memcpy on __iomem pointers doesn't work on IA64. If memcpy doesn't work
> > > then I can't see memcmp working.
> >
> > On most platforms readb() just ends up doing a regular dereference of the
> > address ... so I'd expect that memcmp would work just fine. The exception
> > is the old SGI sn2 which end up calling ___sn_readb() ... which does something
> > weird with sn_dma_flush() after doing the dereference of *addr. I don't
sn_dma_flush has a good description at the beginning of it. It is only
related to activity on PCI attached devices and a memcmp should be fine.
It must be that our prom produces a bad DMI table.
Robin
prev parent reply other threads:[~2013-04-25 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 13:18 memcpy_fromio in dmi_scan.c Jean Delvare
2013-04-23 3:25 ` DuanZhenzhong
2013-04-23 7:28 ` Jean Delvare
2013-04-23 22:00 ` Luck, Tony
2013-04-24 19:22 ` Jean Delvare
2013-04-24 20:16 ` Luck, Tony
2013-04-25 2:07 ` Robin Holt
2013-04-25 9:52 ` Robin Holt
2013-04-25 20:37 ` Andrew Morton
2013-07-08 13:54 ` Jean Delvare
2013-04-25 1:51 ` Zhenzhong Duan
2013-04-25 10:02 ` Robin Holt [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=20130425100246.GR3672@sgi.com \
--to=holt@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=zhenzhong.duan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox