From: Dave Brolley <brolley@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: [patch][rfa]: SID mapper component - wordsize
Date: Fri, 14 Feb 2003 19:38:00 -0000 [thread overview]
Message-ID: <3E4D45ED.8020502@redhat.com> (raw)
In-Reply-To: <o5of5ewufk.fsf@toenail.toronto.redhat.com>
Frank Ch. Eigler wrote:
>brolley wrote:
>
>
>
>>[...] The specification
>>[4*1000-1010]
>>should allow access to the range 4000-4043, however, the upper bound
>>is simply being multiplied by the wordsize, resulting in an upper
>>bound of 4040.
>>
>>
>
>Actually, addresses in the mapper specs are inclusive, not exclusive.
>That's why one often sees ranges ending with ...ffff. Plain raw
>scaling such inclusive limits doesn't make sense though, so a special
>case calculation like yours would make sense. However, care should be
>taken not to confuse exclusive vs inclusive bounds.
>
Right. That's precisely what the patch does. It computes the intended
inclusive bounds.
>>If the mapper is accessed using wordsized elements, the problem goes
>>unnoticed, since the mapper does not check the ending address of the
>>range being accessed.
>>
>>
>
>That's a peculiar other bug. To be consistent with the byte-oriented
>addressing across sid::bus, the size of the access would need to be
>included in the checks.
>
>
That's a separate bug (wasn't sure if it was intentional or not) and an
exercise for someone's copious spare time :-)
Dave
prev parent reply other threads:[~2003-02-14 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 23:58 Dave Brolley
2003-02-14 2:52 ` Ben Elliston
2003-02-14 19:09 ` Frank Ch. Eigler
2003-02-14 19:38 ` Dave Brolley [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=3E4D45ED.8020502@redhat.com \
--to=brolley@redhat.com \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).