summaryrefslogtreecommitdiffstats
path: root/qemu/dtc/tests/test01.dts
blob: f9fd165340f9de2514be32f431fec3ab6c4fcb32 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
/dts-v1/;

/memreserve/ 0x1000000000000000 0x0000000002000000;
/memreserve/ 0x2000000000000000 0x0100000000000000;
/memreserve/ 0x0000000000000000 0x0000000000000014;

/ {
	model = "MyBoardName";
	compatible = "MyBoardName", "MyBoardFamilyName";
	#address-cells = <2>;
	#size-cells = <2>;

	cpus {
		linux,phandle = <0x1>;
		#address-cells = <1>;
		#size-cells = <0>;
		PowerPC,970@0 {
			name = "PowerPC,970";
			device_type = "cpu";
			reg = <0x00000000>;
			clock-frequency = <1600000000>;
			timebase-frequency = <33333333>;
			linux,boot-cpu;
			i-cache-size = <65536>;
			d-cache-size = <32768>;
		};

		PowerPC,970@1 {
			name = "PowerPC,970";
			device_type = "cpu";
			reg = <0x00000001>;
			clock-frequency = <1600000000>;
			timebase-frequency = <33333333>;
			i-cache-size = <65536>;
			d-cache-size = <32768>;
		};

	};

	randomnode {
		string = "\xff\0stuffstuff\t\t\t\n\n\n";
		blob = [0a 0b 0c 0d de ea ad be ef];
		ref = < &{/memory@0} >;
		mixed = "abc", [1234], <0xa 0xb 0xc>;
	};

	memory@0 {
		device_type = "memory";
		memreg: reg = <0x00000000 0x00000000 0x00000000 0x20000000>;
	};

	chosen {
		bootargs = "root=/dev/sda2";
		linux,platform = <0x600>;
	};

};
| | | +--------------+--------------------------------------------------------------+ |test case id | OPNFV_YARDSTICK_TC042_DPDK pktgen latency measurements | | | | +--------------+--------------------------------------------------------------+ |metric | L2 Network Latency | | | | +--------------+--------------------------------------------------------------+ |test purpose | Measure L2 network latency when DPDK is enabled between hosts| | | on different compute blades. | | | | +--------------+--------------------------------------------------------------+ |configuration | file: opnfv_yardstick_tc042.yaml | | | | | | * Packet size: 64 bytes | | | * SLA(max_latency): 100usec | | | | +--------------+--------------------------------------------------------------+ |test tool | DPDK_ | | | Pktgen-dpdk_ | | | | | | (DPDK and Pktgen-dpdk are not part of a Linux distribution, | | | hence they needs to be installed. | | | As an example see the /yardstick/tools/ directory for how to | | | generate a Linux image with DPDK and pktgen-dpdk included.) | | | | +--------------+--------------------------------------------------------------+ |references | DPDK_ | | | | | | Pktgen-dpdk_ | | | | | | ETSI-NFV-TST001 | | | | +--------------+--------------------------------------------------------------+ |applicability | Test can be configured with different packet sizes. Default | | | values exist. | | | | +--------------+--------------------------------------------------------------+ |pre-test | The test case image needs to be installed into Glance | |conditions | with DPDK and pktgen-dpdk included in it. | | | | | | The NICs of compute nodes must support DPDK on POD. | | | | | | And at least compute nodes setup hugepage. | | | | | | If you want to achievement a hight performance result, it is | | | recommend to use NUAM, CPU pin, OVS and so on. | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | The hosts are installed on different blades, as server and | | | client. Both server and client have three interfaces. The | | | first one is management such as ssh. The other two are used | | | by DPDK. | | | | +--------------+--------------------------------------------------------------+ |step 2 | Testpmd_ is invoked with configurations to forward packets | | | from one DPDK port to the other on server. | | | | +--------------+--------------------------------------------------------------+ |step 3 | Pktgen-dpdk is invoked with configurations as a traffic | | | generator and logs are produced and stored on client. | | | | | | Result: Logs are stored. | | | | +--------------+--------------------------------------------------------------+ |test verdict | Fails only if SLA is not passed, or if there is a test case | | | execution problem. | | | | +--------------+--------------------------------------------------------------+