From: David Miller <davem@davemloft.net>
To: jt@hpl.hp.com
Cc: mb@bu3sch.de, shaddy_baddah@hotmail.com,
linux-wireless@vger.kernel.org, dsd@gentoo.org,
johannes@sipsolutions.net
Subject: Re: zd1211rw (2.6.22 sparc64): unaligned access (do_rx)
Date: Thu, 06 Dec 2007 19:52:14 -0800 (PST) [thread overview]
Message-ID: <20071206.195214.09557695.davem@davemloft.net> (raw)
In-Reply-To: <20071206214341.GA6821@bougret.hpl.hp.com>
From: Jean Tourrilhes <jt@hpl.hp.com>
Date: Thu, 6 Dec 2007 13:43:41 -0800
> On Thu, Dec 06, 2007 at 10:33:18PM +0100, Michael Buesch wrote:
> > Userspace handles this transparently through fault traps.
>
> This is exactly what I was assuming. On the SPARC, in this
> instance, it did not (check back earlier in this discussion).
Right, you get a SIGBUS, and this is what will happen on
MIPS as well.
It is even defined in the application ABIs for these platforms that
all objects must be aligned to their type's natural size.
next prev parent reply other threads:[~2007-12-07 3:52 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 0:56 zd1211rw (2.6.22 sparc64): unaligned access (do_rx) Shaddy Baddah
2007-11-19 8:27 ` David Miller
2007-11-19 12:11 ` Shaddy Baddah
2007-11-19 12:19 ` David Miller
2007-11-21 13:08 ` Shaddy Baddah
2007-11-19 15:03 ` Johannes Berg
2007-11-19 18:04 ` Jean Tourrilhes
2007-11-21 13:18 ` Shaddy Baddah
2007-11-21 13:30 ` Shaddy Baddah
2007-11-21 14:23 ` Daniel Drake
2007-11-21 18:05 ` Kyle McMartin
2007-11-30 5:31 ` Shaddy Baddah
2007-11-21 14:33 ` Daniel Drake
2007-11-21 18:44 ` Jean Tourrilhes
2007-11-30 3:42 ` Shaddy Baddah
2007-11-30 20:21 ` Jean Tourrilhes
2007-12-04 0:01 ` Jean Tourrilhes
[not found] ` <4756AABC.3000204@hotmail.com>
[not found] ` <20071205215600.GA28349@bougret.hpl.hp.com>
2007-12-05 23:25 ` Shaddy Baddah
2007-12-05 23:40 ` Jean Tourrilhes
2007-12-06 21:59 ` Jean Tourrilhes
2007-12-06 2:36 ` David Miller
2007-12-06 21:25 ` Jean Tourrilhes
2007-12-06 21:33 ` Michael Buesch
2007-12-06 21:43 ` Jean Tourrilhes
2007-12-07 3:52 ` David Miller [this message]
2007-12-07 11:35 ` Michael Buesch
2007-12-07 12:34 ` David Miller
2007-12-07 13:36 ` Michael Buesch
2007-12-07 14:48 ` Daniel Drake
2007-12-08 1:36 ` David Miller
2007-12-08 1:35 ` David Miller
2007-12-08 11:21 ` Michael Buesch
2007-12-08 12:54 ` Daniel Drake
2007-12-07 3:50 ` David Miller
2007-12-07 3:49 ` David Miller
2007-11-19 22:20 ` David Miller
2007-11-19 22:35 ` Jean Tourrilhes
2007-11-20 7:42 ` David Miller
2007-11-20 17:43 ` Jean Tourrilhes
2007-11-20 21:56 ` David Miller
2007-11-20 12:40 ` Johannes Berg
2007-11-20 12:46 ` David Miller
[not found] ` <20071120180016.GC1480@bougret.hpl.hp.com>
2007-11-20 21:58 ` David Miller
2007-11-20 22:08 ` John W. Linville
2007-11-20 22:38 ` David Miller
2007-11-20 22:16 ` Jean Tourrilhes
2007-11-20 22:41 ` David Miller
[not found] ` <20071120180601.GA2019@bougret.hpl.hp.com>
[not found] ` <47443430.3010504@hotmail.com>
2007-11-21 19:06 ` Jean Tourrilhes
2007-11-20 17:38 ` Jean Tourrilhes
2007-11-20 12:34 ` David Miller
2007-11-20 13:15 ` Johannes Berg
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=20071206.195214.09557695.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsd@gentoo.org \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=shaddy_baddah@hotmail.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;
as well as URLs for NNTP newsgroup(s).