Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <soete.joel@scarlet.be>
Cc: linux-parisc@vger.kernel.org
Subject: Re: ccio_mark_invalid(): would it have to clear a bit or byte?
Date: Fri, 1 Aug 2008 10:12:48 -0600	[thread overview]
Message-ID: <20080801161248.GA22961@colo.lackof.org> (raw)
In-Reply-To: <4884A25C.7000902@scarlet.be>

On Mon, Jul 21, 2008 at 02:51:08PM +0000, Joel Soete wrote:
> Hello all,
>
> given this comment:
>  * Given a virtual address (vba, arg2) and space id, (sid, arg1),
>  * load the I/O PDIR entry pointed to by pdir_ptr (arg0). Each IO Pdir
>  * entry consists of 8 bytes as shown below (MSB == bit 0):
...
> and also this:
>         while (byte_cnt > 0) {
>                 /* clear I/O Pdir entry "valid" bit first */
>                 ((unsigned char *) pdir_ptr)[7] = 0;
>
> So if I well understand 'Valid' field of a pdir entry is well of 1 bit but 
> the code cleanup a all byte?

That's just a convenient way to clobber the bit we care about.
The fact that the rest of the pdir remains available is irrelevant
except for debugging (when we might dump IO Pdir to see the history.)

>
> Is coding something like:
> #define PTE_VALID_BIT_MASK      0xfffffffffffffffeULL	
>
> 		*pdir_ptr &= PTE_VALID_BIT_MASK;

That's a load/modify store of a 64-bit value.
That substantially more instructions than a single byte store.

> wouldn't do better what comment says it does?

Yes, but the comment is just describing what needs to happen, not exactly how.
The "entry valid" bit just needs to be cleared and it doesn't matter how.

hth
grant

>
> Well a short test seems to help but doesn't fix all issue:
>
> patst007 login: end_request: I/O error, dev sdl, sector 6659574
> __ratelimit: 32 messages suppressed 
> Buffer I/O error on device sdl9, logical block 193374 
> lost page write due to I/O error on sdl9 
> Buffer I/O error on device sdl9, logical block 193375 
> lost page write due to I/O error on sdl9 
> Buffer I/O error on device sdl9, logical block 193376 
> lost page write due to I/O error on sdl9 
> Buffer I/O error on device sdl9, logical block 193377 
> lost page write due to I/O error on sdl9 
> Buffer I/O error on device sdl9, logical block 193378 
> lost page write due to I/O error on sdl9 
> Buffer I/O error on device sdl9, logical block 193379 
> lost page write due to I/O error on sdl9 
> Buffer I/O error on device sdl9, logical block 193380 
> lost page write due to I/O error on sdl9
> Buffer I/O error on device sdl9, logical block 193381
> lost page write due to I/O error on sdl9
> Buffer I/O error on device sdl9, logical block 193382
> lost page write due to I/O error on sdl9
> Buffer I/O error on device sdl9, logical block 193383
>
> Tia for all advise,
> 	J.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-08-01 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 14:51 ccio_mark_invalid(): would it have to clear a bit or byte? Joel Soete
2008-08-01 16:12 ` Grant Grundler [this message]
2008-08-02  7:59   ` Joel Soete

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=20080801161248.GA22961@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=soete.joel@scarlet.be \
    /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