diff options
Diffstat (limited to 'kernel/drivers/ptp/ptp_chardev.c')
| -rw-r--r-- | kernel/drivers/ptp/ptp_chardev.c | 332 |
1 files changed, 332 insertions, 0 deletions
diff --git a/kernel/drivers/ptp/ptp_chardev.c b/kernel/drivers/ptp/ptp_chardev.c new file mode 100644 index 000000000..da7bae991 --- /dev/null +++ b/kernel/drivers/ptp/ptp_chardev.c @@ -0,0 +1,332 @@ +/* + * PTP 1588 clock support - character device implementation. + * + * Copyright (C) 2010 OMICRON electronics GmbH + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License as published by + * the Free Software Foundation; either version 2 of the License, or + * (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + */ +#include <linux/module.h> +#include <linux/posix-clock.h> +#include <linux/poll.h> +#include <linux/sched.h> +#include <linux/slab.h> + +#include "ptp_private.h" + +static int ptp_disable_pinfunc(struct ptp_clock_info *ops, + enum ptp_pin_function func, unsigned int chan) +{ + struct ptp_clock_request rq; + int err = 0; + + memset(&rq, 0, sizeof(rq)); + + switch (func) { + case PTP_PF_NONE: + break; + case PTP_PF_EXTTS: + rq.type = PTP_CL .. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, Yin Kanglin and others.
.. 14_ykl@tongji.edu.cn
*************************************
Yardstick Test Case Description TC045
*************************************
+-----------------------------------------------------------------------------+
|Control Node Openstack Service High Availability - Neutron Server |
| |
+--------------+--------------------------------------------------------------+
|test case id | OPNFV_YARDSTICK_TC045: Control node Openstack service down - |
| | neutron server |
+--------------+--------------------------------------------------------------+
|test purpose | This test case will verify the high availability of the |
| | network service provided by OpenStack (neutro-server) on |
| | control node. |
| | |
+--------------+--------------------------------------------------------------+
|test method | This test case kills the processes of neutron-server service |
| | on a selected control node, then checks whether the request |
| | of the related Openstack command is OK and the killed |
| | processes are recovered. |
| | |
+--------------+--------------------------------------------------------------+
|attackers | In this test case, an attacker called "kill-process" is |
| | needed. This attacker includes three parameters: |
| | 1) fault_type: which is used for finding the attacker's |
| | scripts. It should be always set to "kill-process" in this |
| | test case. |
| | 2) process_name: which is the process name of the specified |
| | OpenStack service. If there are multiple processes use the |
| | same name on the host, all of them are killed by this |
| | attacker. |
| | In this case. This parameter should always set to "neutron- |
| | server". |
| | 3) host: which is the name of a control node being attacked. |
| | |
| | e.g. |
| | -fault_type: "kill-process" |
| | -process_name: "neutron-server" |
| | -host: node1 |
| | |
+--------------+--------------------------------------------------------------+
|monitors | In this test case, two kinds of monitor are needed: |
| | 1. the "openstack-cmd" monitor constantly request a specific |
| | Openstack command, which needs two parameters: |
| | 1) monitor_type: which is used for finding the monitor class |
| | and related scritps. It should be always set to |
| | "openstack-cmd" for this monitor. |
| | 2) command_name: which is the command name used for request. |
| | In this case, the command name should be neutron related |
| | commands. |
| | |
| | 2. the "process" monitor check whether a process is running |
| | on a specific node, which needs three parameters: |
| | 1) monitor_type: which used for finding the monitor class and|
| | related scritps. It should be always set to "process" |
| | for this monitor. |
| | 2) process_name: which is the process name for monitor |
| | 3) host: which is the name of the node runing the process |
| | |
| | e.g. |
| | monitor1: |
| | -monitor_type: "openstack-cmd" |
| | -command_name: "neutron agent-list" |
| | monitor2: |
| | -monitor_type: "process" |
| | -process_name: "neutron-server" |
| | -host: node1 |
| | |
+--------------+--------------------------------------------------------------+
|metrics | In this test case, there are two metrics: |
| | 1)service_outage_time: which indicates the maximum outage |
| | time (seconds) of the specified Openstack command request. |
| | 2)process_recover_time: which indicates the maximun time |
| | (seconds) from the process being killed to recovered |
| | |
+--------------+--------------------------------------------------------------+
|test tool | Developed by the project. Please see folder: |
| | "yardstick/benchmark/scenarios/availability/ha_tools" |
| | |
+--------------+--------------------------------------------------------------+
|references | ETSI NFV REL001 |
| | |
+--------------+--------------------------------------------------------------+
|configuration | This test case needs two configuration files: |
| | 1) test case file: opnfv_yardstick_tc045.yaml |
| | -Attackers: see above "attackers" discription |
| | -waiting_time: which is the time (seconds) from the process |
| | being killed to stoping monitors the monitors |
| | -Monitors: see above "monitors" discription |
| | -SLA: see above "metrics" discription |
| | |
| | 2)POD file: pod.yaml |
| | The POD configuration should record on pod.yaml first. |
| | the "host" item in this test case will use the node name in |
| | the pod.yaml. |
| | |
+--------------+--------------------------------------------------------------+
|test sequence | description and expected result |
| | |
+--------------+--------------------------------------------------------------+
|step 1 | start monitors: |
| | each monitor will run with independently process |
| | |
| | Result: The monitor info will be collected. |
| | |
+--------------+--------------------------------------------------------------+
|step 2 | do attacker: connect the host through SSH, and then execute |
| | the kill process script with param value specified by |
| | "process_name" |
| | |
| | Result: Process will be killed. |
| | |
+--------------+--------------------------------------------------------------+
|step 3 | stop monitors after a period of time specified by |
| | "waiting_time" |
| | |
| | Result: The monitor info will be aggregated. |
| | |
+--------------+--------------------------------------------------------------+
|step 4 | verify the SLA |
| | |
| | Result: The test case is passed or not. |
| | |
+--------------+--------------------------------------------------------------+
|post-action | It is the action when the test cases exist. It will check the|
| | status of the specified process on the host, and restart the |
| | process if it is not running for next test cases |
| | |
+--------------+--------------------------------------------------------------+
|test verdict | Fails only if SLA is not passed, or if there is a test case |
| | execution problem. |
| | |
+--------------+--------------------------------------------------------------+
|