Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
	linux-parisc@vger.kernel.org
Subject: Re: HPMC in lba_pat_out8 on rp3440
Date: Tue, 16 Nov 2010 22:42:10 -0700	[thread overview]
Message-ID: <20101117054210.GD27930@lackof.org> (raw)
In-Reply-To: <20101117052642.GF22651@bombadil.infradead.org>

On Wed, Nov 17, 2010 at 12:26:42AM -0500, Kyle McMartin wrote:
> On Tue, Nov 16, 2010 at 10:22:18PM -0700, Grant Grundler wrote:
> > I agree. The kernel is expected to emulate/handle unaligned loads/stores.
> > 
> > I thought we had all that misaligned access handlers working years ago and
> > somewhere probably have a user space program to test it. Oh...ldd won't be
> > user space since we don't have a PA2.0 64-bit user space. LDD support
> > can't be as well tested.
> > 
> > On that note, can you try a 32-bit kernel? (SMP maybe)
> > 
> 
> We really shouldn't be fixing up unaligned access in the kernel, since
> we can just fix the code... If ipv6 is causing them, there must be some
> missing define that's getting defaulted to something un-padded,
> otherwise sparc wouldn't work at all (it definitely does /not/ fix
> unalignd accesses, period.)

I agree but thought davem refused patches to use get/put_unaligned macros
in networking code. Searching for "davem ulog put_unaligned" shows him
accepting such patches. So this is clearly the right path to pursue.

thanks,
grant

  reply	other threads:[~2010-11-17  5:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 17:40 HPMC in lba_pat_out8 on rp3440 John David Anglin
2010-10-31 18:02 ` John David Anglin
2010-10-31 19:46   ` John David Anglin
2010-11-02  5:32     ` Grant Grundler
2010-11-02  5:00   ` Grant Grundler
2010-11-02  6:26 ` Grant Grundler
2010-11-02 14:24   ` John David Anglin
2010-11-02 14:38     ` James Bottomley
2010-11-03  3:19   ` John David Anglin
2010-11-04 15:35     ` Grant Grundler
2010-11-07 19:31       ` John David Anglin
2010-11-10  3:35         ` John David Anglin
2010-11-14 23:42           ` John David Anglin
2010-11-15  2:14             ` John David Anglin
2010-11-16 22:51             ` John David Anglin
2010-11-17  2:21             ` John David Anglin
2010-11-17  5:22               ` Grant Grundler
2010-11-17  5:26                 ` Kyle McMartin
2010-11-17  5:42                   ` Grant Grundler [this message]
2010-11-17 14:38                     ` John David Anglin
2010-11-17 15:33                       ` Kyle McMartin
2010-11-17 17:45                         ` Thibaut VARÈNE
2010-11-17 15:38                     ` James Bottomley
2010-11-17 16:03                 ` John David Anglin
2010-11-20 21:01                   ` John David Anglin
2010-11-21 15:38                     ` John David Anglin
2010-11-23  0:51                       ` John David Anglin
2010-11-18 15:08                 ` John David Anglin

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=20101117054210.GD27930@lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@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