06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

verify_vol pHILE+ <strong>System</strong> <strong>Calls</strong><br />

Target<br />

verify_vol() calls a user-supplied function, faultp(), for status-checking (see<br />

page 2-131). For each processor family, faultp() returns its return value in the<br />

register specified below:<br />

68K<br />

PPC<br />

960<br />

x86<br />

Return Value<br />

Error Codes<br />

pb_badblkptr Points to a user-provided list of bad blocks on the<br />

volume. A bad block is a block that cannot be read<br />

and/or written and is therefore unusable by the<br />

pHILE+ file system manager. This list is made up of<br />

32-bit entries and is terminated with a 0 entry. The<br />

entries need not be in any specific order.<br />

verify_vol() can greatly simplify the handling of<br />

bad blocks. Refer to “Bad Blocks” on page 2-139 for<br />

information on this feature. If no bad block list is<br />

provided, this entry must be 0.<br />

On 68K processors, faultp() uses the D0.L register.<br />

On PowerPC processors, faultp() uses the r3 register.<br />

On 960 processors, faultp() uses the g0 register.<br />

On x86 processors, faultp() uses the %eax register.<br />

This system call returns 0 on success or an error code on failure.<br />

Hex Mnemonic Description<br />

0x2007 E_VALIEN Wrong volume format.<br />

0x2009 E_MNTOPEN Files are open on volume.<br />

2-128 <strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!