All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@scarlet.be>
To: linux-parisc@vger.kernel.org
Subject: ccio_mark_invalid(): would it have to clear a bit or byte?
Date: Mon, 21 Jul 2008 14:51:08 +0000	[thread overview]
Message-ID: <4884A25C.7000902@scarlet.be> (raw)

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):
  *
  *
  * WORD 0:
  * +------+----------------+-----------------------------------------------+
  * | Phys | Virtual Index  |               Phys                            |
  * | 0:3  |     0:11       |               4:19                            |
  * |4 bits|   12 bits      |              16 bits                          |
  * +------+----------------+-----------------------------------------------+
  * WORD 1:
  * +-----------------------+-----------------------------------------------+
  * |      Phys    |  Rsvd  | Prefetch |Update |Rsvd  |Lock  |Safe  |Valid  |
  * |     20:39    |        | Enable   |Enable |      |Enable|DMA   |       |
  * |    20 bits   | 5 bits | 1 bit    |1 bit  |2 bits|1 bit |1 bit |1 bit  |
  * +-----------------------+-----------------------------------------------+
  *

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?

Is coding something like:
#define PTE_VALID_BIT_MASK      0xfffffffffffffffeULL	

		*pdir_ptr &= PTE_VALID_BIT_MASK;

wouldn't do better what comment says it does?

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.

             reply	other threads:[~2008-07-21 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 14:51 Joel Soete [this message]
2008-08-01 16:12 ` ccio_mark_invalid(): would it have to clear a bit or byte? Grant Grundler
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=4884A25C.7000902@scarlet.be \
    --to=soete.joel@scarlet.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.