TW201106345A - System and method for testing hard disks under extensible firmware interface - Google Patents

Abstract

The present invention provides a method for testing hard disks under extensible firmware interface. The method includes: (a) obtaining a device path which can be recognized by the extensible firmware interface from a device tree; (b) obtaining a handle corresponding to the device path; (c) searching a handle of a father code of a code that the device path belongs to; (d) detecting if there are any obtained handles in step (b) are the same as the handle of the father code, if there are any obtained handles in step (b) are the same as the handle of the father code, the procedure goes to step (e), if there is no obtained handle in step (b) is the same as the handle of the father code, the procedure goes to step (f); (e) obtaining a handle of a code which is a father code of the code having the same handle, and the procedure returns to step (b); (f) obtaining a number of the last obtained handles; (g) searching the device paths according to the last obtained handles, the device paths are types of the testing hard devices.

Description

201106345 VI. Description of the Invention: [Technical Leadership of the Invention] [0001] The present invention relates to a hard disk test method, and more particularly to a hard test method under an expandable firmware interface. [The previous four techniques] [0002] The hard disk is the main part of the computer's performance directly affects the performance of the entire computer, so the performance test of the hard disk is the key to determine the performance of the hard disk. In the extended firmware interface (Extensible Firmware

Interface, EFI), the motherboard manufacturer's test of the hard disk performance of the motherboard is mainly under DOS or Windows or Linux. Testing under these operating systems requires certain restrictions on the test time. Moreover, when performing the read/write test of the block device of the hard disk, it is necessary to avoid the area where the operating system is located, which increases the test difficulty and reduces the test efficiency. [Summary of the Invention] [〇〇〇3] In view of the above, it is necessary to provide a hard disk test method under the expandable firmware interface to test the performance of the hard disk under EFI. [0004] A method for testing a hard disk under an extensible firmware interface, the method comprising: (a) obtaining a device path recognizable by all extensible firmware interfaces in a hard disk device tree; and (b) obtaining according to the acquired device path a control code corresponding to the device path; (c) finding a parent node of a node where each device path is located, and acquiring a control code in the parent node information; (d) determining step (b) Whether there is a control code in the control code that is the same as the control code in the parent node information acquired in step (c), and if the control code acquired in step (b) has the parent node obtained in step (c) 098126654 Form No. A0101 Page 4 of 20 0982045671-0 201106345 The control code with the same control code enters step (e). If the control code obtained in step (b) does not exist, step (c) The obtained control code with the same control code in the parent node information enters the dream (f); (e) acquires the control code in the parent node information of the node where the same control code is located, and proceeds to the step (d); (f) view the number of control codes finally obtained, Number of the test system is the number of code Drive; and (g) to find the path of the device according to the control code corresponding to the final obtained, i.e. the path of the device under test Drive models. 0005 [0005] [0006] Compared to the prior art, the hard disk test method under the extensible firmware interface 'utilizes the characteristics of EFI to realize the test of hard disk performance of the host board in a short time' Efficiency ^ Embodiments As shown in FIG. 1, it is an operating environment diagram of a preferred embodiment of a hard disk test method under the extensible firmware interface of the present invention. The hard disk performance test system 100 operates in the storage device 1, which may be a USB disk, a mobile hard disk, or the like. The storage device 1 is connected to the host 2 via a USB interface. The host 2 tests the tussock performance test in the storage device 1: the system 10 0 tests the hard disk 3 to be tested. In the preferred embodiment, the hard disk 3 to be tested may be one or more. Each hard disk to be tested 3 includes a plurality of block devices and a file system, and the parent block devices are independently readable and writable. Each hard disk to be tested 3 can be represented by a device tree. The root node of the device tree indicates the hard disk 3 to be tested, and the leaf node indicates the block device and the file system of the hard disk 3 to be tested. In the preferred embodiment, each hard disk 3 to be tested includes at least two formatted partitions. It is assumed that the formatted partitions are partition C and partition d, respectively, and partition c is a file allocation table (File Allocation Table 32). , FAT32) Department 098126654 Form No. A0101 Page 5 / Total 20 pages 0982045671-0 201106345, 'First knife area D is New Techn〇1〇gy FUe plus ^^ Grab system, 'charged' The FAT32 system is used to test hard The read and write performance of the disc file system and the read and write performance of the block device, the NTFS system is used to test the block device, and the hard disk test under the scalable firmware interface of the invention includes three parts of the test: Test the hard disk 3 information, test the block device of the hard disk 3 to be tested, and test the file system of the hard disk 3 to be tested. [0007] FIG. 2 is a schematic diagram of a device tree of the hard disk 3 to be tested. Each leaf of the device tree shows a block device or a __ text, system, and each node information includes a device path and a control code (

Handle) 'The device path table is stupid. The block has the path of the arrow or the ancient document system. The control code indicates the control code corresponding to the path of the device. ^ The device tree shown in Figure 2 includes two hard disks to be tested. The models of the hard disk to be tested are respectively .Hitachi HDT725025VLA380 and ST38021 5AS, and the present invention finds all the block devices and file systems in each hard disk 3 to be tested through the device tree, and then finds through these block devices and the file system. The information of the hard disk 3 to be tested, the information packet of the hard disk 3 to be tested, the number of hard disks 3 to be tested, the manufacturer of each hard disk 3 to be tested, the interface type and firmware (firmware version), and the like. For example, the node information pointed to by the label 201 is: [17〇] FAT File System 'This node represents the file system, where "FAT File System" indicates the device path of the node, and "17〇" indicates the The control code corresponding to the device path. The node information pointed to by the label 202 is: [171] PciRoot (0x0)/Pci (OxlF, 0x5)/ATA (Primary, Master, 0x0)/HD (2, MBR, 0xl9EFDlA8, 0xl40249A, 0xC80343F), the node Indicates a block device, where "Pci Root (〇x〇)/pci ( 098126654 Form No. A0101 Page 6 / Total 20 Page 0982045671-0 201106345 [0008] [0009] Ο [0010] [0011] Ο [0012 [0013] 098126654 0982045671-0

OxlF, 0χ5)/ΑΤΑ (Primary, Master, 〇x〇)/HD (2, MBR, 0xl9EFDlA8, 0xl40249A, 0xC80343F) M indicates the device path of the node, and “171” indicates the control code corresponding to the device path. As shown in FIG. 3, it is a flowchart of a preferred embodiment of a method for testing hard disk information under the extensible firmware interface of the present invention. In step S30, the hard disk performance test system 1 obtains the device path that all EFIs can recognize in the device tree. As shown in FIG. 2, the device path that the EFI can identify includes the device path in the node information corresponding to the labels 201, 202 '203' 204, 301, 302, and 303. Step S31' acquires a control code corresponding to the device path according to the acquired set arrow path. - - Step S32 ' Find the parent node of the transferred point where the obtained device path is located, and obtain the control code in the parent node information. For example, as shown in FIG. 2, the control code of the parent node of the node pointed to by the label 203 is 171 'The control code of the parent node of the node pointed to by 2〇4 is 171, and the knot pointed to by 3〇3 The control code for the parent node of the point is 175. Step S33, it is judged whether there is a control code identical to the control code in the acquired parent node information in the control code acquired in step S31. If there is a control code identical to the control code in the acquired parent node information in the control code acquired in the step, the process proceeds to step S34. If there is no control code in the control code acquired in step S31 that is the same as the control code in the acquired parent node information, proceed to step S35 » step S34 to obtain the parent node of the node where the same control code is located. The control code of the form number A0101 on page 7 of 20 pages 201106345 is passed, and the process goes to step S33. For example, in FIG. 2, the control code of the parent node of the node pointed to by the label 203 and the label 204 is 171, which is the same as the control code of the node pointed to by the label 202 obtained in step S31, and the node pointed to by the label 303. The control code of the parent node is 175, which is the same as the control code of the node pointed to by the label 3 0 2 obtained in step S 31, and then continues to search for the parent node of the node where the control code 171 and the control code 175 are located. The control code in the information, the obtained control code is 16Ε and 16F, and the process goes to step S33. If the control code 16Ε and 16F are not present in the control code acquired in step S31, the process proceeds to step S35. [0014] Step S35, the number of control codes finally obtained is checked, and the number of the control codes is the number of hard disks 3 to be tested. As shown in FIG. 2, the finally obtained control codes are: 16E and 16F, that is, the number of hard disks 3 to be tested is 2. [0015] Step S36: Find a corresponding device path according to the finally obtained control code, where the device path is the model of the hard disk 3 to be tested, and the information of the hard disk 3 to be tested is obtained from the model. For example, the control code 16E is a control code of the hard disk 3 to be tested, and the device path corresponding to the control code is Hitachi I j

The HDT725025VLA380 is the model of the hard disk 3 to be tested. The information of the hard disk 3 to be tested is known from the model: J: Manufacturer: Hitachi, capacity: 250G, interface type is SATAII 8M. [0016] As shown in FIG. 4, it is a flowchart of a preferred embodiment of a test method for a hard disk block device in the scalable firmware interface of the present invention. [0017] Step S40, each block device of the hard disk 3 to be tested identified by the EFI is divided into a plurality of small blocks, and the number of the small blocks can be set by the tester. In the preferred embodiment, each small block can be At the same time, the test can also be carried out according to the first 098126654 form number A0101 page 8 / total 20 pages 0982045671-0 201106345 [0018] ❹ [0020] [0021] [0022] [0023] 098126654 after the test in sequence The order can be set by the tester. The size of each tile must be an integer multiple of 512 bytes. For example, suppose each block device size is TotalSize MB, and each block device is divided into N small blocks, and the size of each small block is TotalSize*1〇24;)(1()24/N bytes. Steps S41, a test space is divided in each small block, and the test space is used for reading and writing of small blocks. The size of the test space must be an integer multiple of 5 丨 2 bytes. In the preferred embodiment, The test space is the first byte of each tile. For example, if the size of the K block is l〇MB, the test of the small block (4) is 1M. The job space of the small block is the front of the small block. 1G24 byte. If the number of small blocks is large, the test byte is large, the test time is long, and the test surface of the hard disk 3 is large. If the number of J blocks is small, the test bit is small. If the group is small, the test time is short, and the test record of the hard disk 3 to be tested, if the test space of each device is equal to the size of each small block, then the test is to test the entire hard disk to be tested 3. Step S42, will be Test _ (10) The stored data is stored in the buffer of the small block in the test space: the buffer is the record of the small block Step S43, write the test data in the test space. Step _, read the data in the test space. Step S45 ' _ Whether the f material read is the same as the test data of the writer. Step S46. If not, proceed to step S47. Step S46' prompts that the small block read/write test is successful, and restores the data stored in the buffer to the test space. 0982045671-0 201106345 [0024] Step S47, The small block read/write test fails. [0025] As shown in FIG. 5, it is a flowchart of a preferred embodiment of a test method for reading and writing free space of a hard disk file system in the scalable firmware interface of the present invention. S50, enumerating all the file system partitions supported by the hard disk 3 under the EF I. In the preferred embodiment, the file system partition supported by the hard disk 3 to be tested under the EFI can be obtained according to the device tree. The document system partitions can be tested at the same time, or can be tested in sequence, and the sequence can be set by the tester. [0027] Step S51, copying the standard documents into the free space of each document system partition, The standard document can be copied in multiple copies to fill the free space of the document system partition. The standard document includes the content of the standard document and the attributes of the standard document, the attributes of the standard document include the size of the standard document, and the standard document is copied under EFI. The required standard time, etc. [0028] Step S52, reading out the documents in each document system partition. [0029] Step S53, comparing the read documents with the standard documents copied to each document system partition. If they are the same, the process proceeds to step S54. If they are not the same, the process proceeds to step S56. [0030] In step S54, it is determined whether the time for reading the document is normal. The time at which the document is read is judged to be normal according to the standard time in which the standard document in the standard document attribute is copied under EF I. If the time for reading the document is normal, the flow proceeds to step S55. If the time for reading the document is not normal, the process proceeds to step S56. [0031] Step S55, prompting the user that the document system partition test is successful. [0032] Step S56, prompting the user that the document system partition test fails. 098126654 Form No. A0101 Page 10 of 20 0982045671-0 201106345 [0033] It should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention and are not limiting, although the present invention is described with reference to the above preferred embodiments. The detailed description of the technical solutions of the present invention may be made without departing from the spirit and scope of the technical solutions of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS [0034] FIG. 1 is a diagram showing an operational environment of a preferred embodiment of a hard disk test method in an extensible firmware interface of the present invention. [0035] FIG. 2 is a schematic diagram of a device tree of a hard disk 3 to be tested. 3 is a flow chart of a preferred embodiment of a method for testing hard disk information under the extensible firmware interface of the present invention. 4 is a flow chart of a preferred embodiment of a method for testing a hard disk block device in an extensible firmware interface of the present invention. 5 is a flow chart of a preferred embodiment of a test method for reading and writing free space of a hard disk file system in the scalable firmware interface of the present invention. [Main Component Symbol Description] [0040] Storage Device 1 [0040] Host 2 [0041] Hard Disk to Be Tested 3 [0042] Hard Disk Performance Test System 100 [0043] Acquires all the expandable firmware interfaces in the device tree that can be recognized Device path S30 098126654 Form number A0101 Page 11 / Total 20 pages 0982045671-0 201106345 [0044] Obtain the control code corresponding to the device path S31 [0045] Find the parent node of the node where each acquired device path is located, and Obtaining the control code S32 in the parent node information. [0046] Is there a control code with the same control code in the acquired parent node information in the control code obtained in step S31? S33. The control code S34 in the parent node information of the node where the same control code is located is obtained. [0048] The number of control codes finally obtained is S35. [0049] The corresponding device path S is found according to the finally obtained control code. 3 6 098126654 Form No. A0101 Page 12 of 20 0982045671-0

Claims (1)

201106345 VII. Patent Application Scope: This method includes steps to test the hard disk under the extensible firmware interface. (a) Obtain the device path of the hard disk device tree so that all the extensible firmware interfaces can recognize; (b) According to the acquired device The path acquires a control code corresponding to the path of the device; ^, (c) finds a parent node of each of the device paths, and obtains a control code in the parent node information; Whether there is a control code stored in the control horse acquired by the acquired acquisition: if the control code is the same as the step (1), the control code phase code in the 乂 node information acquired does not exist and the acquired step If the control code obtained in the step (b) is entered, the control (e) entering the step (f)·and the point information is the same control (e), and the same control code is obtained, and the step (d) is transferred to the step (d). Control the control in the parent node information of the node (1) to see the number of hard disks that are finally measured; and 'the number of control codes is to wait (g) according to the final 2 device path is the model of the hard disk to be tested To the corresponding device road According to the above-mentioned (4), the H test method of the first item of the patent scope, the method further includes the steps of: obtaining the hard disk to be picked up by the hard disk of the hard disk to be tested from the hard disk test under the firmware interface of the household exhibition. No. of disk capacity size and interface type The information of the hard disk to be tested includes the manufacturer, hard 098126654 Form No. A0101 » ^ 0982045671 Page 13 of 20 201106345 3. Extensible firmware as described in claim 1 A hard disk test method under the interface, where each node of the device tree represents a block device or a file system. 4. The method for testing a hard disk in an extensible firmware interface according to claim 3, further comprising a test step of the block device, wherein the step of testing the block device comprises: identifying the device under the extensible firmware interface Each block device of the hard disk to be tested is divided into several small blocks; one test space is divided in each small block; the originally stored data in each test space is stored in a buffer of the small block in the test space; Write the test data in the space; read the data in the test space; when the read data is the same as the written test data, the small block read/write test is successful, and the data stored in the buffer is restored and stored Within the test space; and when the read data is different from the written test data, the small block read/write test fails. 5. A hard disk test method in an extensible firmware interface as described in claim 4, wherein the size of each tile is an integer multiple of 512 bytes. 6. The hard disk test method according to the extensible firmware interface described in claim 4, wherein the size of the test space is an integer multiple of 512 bytes, and the test space is the front of each small block. The byte. 7. The method for testing a hard disk in an extensible firmware interface according to claim 3, further comprising: a read/write test step of a free space of the file system, wherein the read and write test steps of the free space of the file system include: 098126654 Form No. A0101 Page 14 of 20 0982045671-0 201106345 List all the document system partitions supported by the hard disk under the Extensible Firmware Interface, copy the standard documents into the free space of each file system partition; Read a document within each document system partition; if the read document is different from the marked document copied into each document system partition, the read/write test indicating that the document system partition free space fails; if the read document and copy If the standard document in each file system partition is the same, it is judged whether the time for reading the document is normal; Ο if the time for reading the document is normal, the read/write test of the free space of the document system partition is successful; and if the reading is successful; If the time of the document is not normal, the read/write test of the free space of the document system partition is failed. A hard disk test method in an extensible firmware interface according to claim 7, wherein the standard document includes a content of a standard document and an attribute of the standard document, and the attribute of the standard document includes a size of the standard document and is expandable. The standard time required to copy the standard document under the firmware interface. ❹ For example, in the hard disk test method under the extensible firmware interface described in claim 8, the normal reading of the document means that the time for reading the document is the same as the standard time required for copying the standard document. 098126654 Form NumberΑ0101 Page 15/Total 20 Page 0982045671-0