Linux PARISC architecture development
 help / color / mirror / Atom feed
From: jsoe0708@tiscali.be
To: "Grant Grundler" <grundler@dsl2.external.hp.com>
Cc: "Joel Soete" <joel.soete@freebel.net>,
	"John David Anglin" <dave@hiauly1.hia.nrc.ca>,
	parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: Unaligne access [was: Back to evms-1.0.1 && unaligne access && gdb ]
Date: Wed, 4 Sep 2002 09:14:19 +0200	[thread overview]
Message-ID: <3D3815BD0000B40C@ocpmta5.be.tiscali.com> (raw)
In-Reply-To: <20020903203317.C30834829@dsl2.external.hp.com>

>jsoe0708@tiscali.be wrote:
>...
>> And here is some data of my analyse:
>> 
>> First surprise in the two case (original checks.c and my checks.c with
>only
>> "if (p->boot_ind != 0x00 && ") p addresses are exactly the same here is
>an
>> example:
>
>...
>> with the checks.c.new:
>> p            add: 0x272ee
>> p.boot_ind   add: 0x272ee
>> p.head       add: 0x272ef
>> p.sector     add: 0x272f0
>> p.cyl        add: 0x272f1
>> p.sys_ind    add: 0x272f2
>> p.end_head   add: 0x272f3
>> p.end_sector add: 0x272f4
>> p.end_cyl    add: 0x272f5
>> p.start_sect add: 0x272f6
>> p.nr_sects   add: 0x272fa
>> 
>> What do you think?
>
>checks.c.new will generate a "misaligned access" when "p.start_sect"
>is accessed. 0x272f6 is aligned on 2byte address, not 4 byte.
>Ditto for "p.nr_sects".
>
(now I have understand, well I think :) )

>You sure checks.c.new is referencing 0x272f6 and not something else?

For this I will have to find all call to this function and write p.start_sect
address and content before.

(very tricky problem to surround isn'it ;<) )

>You reviewed dmesg output?

Yes (I have a mincom 'screen' on this system console and I also examine kern.log
as recall Dave)


Many thanks,
    Joel

PS: In the mean time I learn that this bug was already fix by:
BOOLEAN isa_null_partition_record(struct partition *p)
{
    int          i;
    u_int8_t    *uip = (u_int8_t *) p;
    int          psize = sizeof(struct partition);

    for (i=0; i<psize; i++) {
        if (*(uip+i) != 0x00) return FALSE;
    }

    return TRUE;
}

but not yet comited :?

  reply	other threads:[~2002-09-04  7:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  8:47 [parisc-linux] Back to evms-1.0.1 && unaligne access && gdb jsoe0708
2002-09-02 17:28 ` Grant Grundler
2002-09-03 16:02   ` [parisc-linux] Unaligne access [was: Back to evms-1.0.1 && unaligne access && gdb ] jsoe0708
2002-09-03 20:33     ` [parisc-linux] " Grant Grundler
2002-09-04  7:14       ` jsoe0708 [this message]
2002-09-04 11:48         ` jsoe0708
2002-09-03 20:44     ` John David Anglin
2002-09-04  6:45       ` jsoe0708
2002-09-04 14:55         ` Randolph Chung

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=3D3815BD0000B40C@ocpmta5.be.tiscali.com \
    --to=jsoe0708@tiscali.be \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=grundler@dsl2.external.hp.com \
    --cc=joel.soete@freebel.net \
    --cc=parisc-linux@lists.parisc-linux.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