Description of problem:

Following PTP Configuration fails with the `chrt: failed to set pid 0's policy: Operation not permitted` error.

~~~

apiVersion: ptp.openshift.io/v1
kind: PtpConfig
metadata:
  name: ordinary-clock-ptp-config
spec:
  profile:
  - name: ordinary-clock
    interface: "ens9f1np1"
    phc2sysOpts: "-w -m -n 127 -s ens9f1np1"
    ptp4lOpts: "-2 -s"
    ptpSchedulingPolicy: SCHED_FIFO
    ptpSchedulingPriority: 10
    ptp4lConf: |
      [global]
      #
      # Default Data Set
      #
      priority1 128
      priority2 127
      domainNumber 127
      use_syslog 1
      logging_level 6
      tx_timestamp_timeout 30
      hybrid_e2e 1
      dscp_event 46
      dscp_general 46

      [ens9f1np1]
      logAnnounceInterval     -2
      announceReceiptTimeout  3
      logSyncInterval         -3
      logMinDelayReqInterval  -3
      delay_mechanism         E2E
      network_transport       UDPv4
  recommend:
  - profile: ordinary-clock
    priority: 4
    match:
    - nodeLabel: "node-role.kubernetes.io/worker"
      nodeName: "example1.com"
    - nodeLabel: "node-role.kubernetes.io/worker"
      nodeName: "example2.com"

~~~

This issue is fixed by using the following tuned configurations. 
~~~
apiVersion: tuned.openshift.io/v1
kind: Tuned
metadata:
  name: xyz-tuning-profile
  namespace: openshift-cluster-node-tuning-operator
spec:
  profile:
  - data: |
      [main]
      summary=Boot time configuration
      include=openshift-node-performance
      [sysctl]
      vm.swappiness=0
      kernel.sched_rt_runtime_us=-1
    name: openshift-node-custom
  recommend:
  - machineConfigLabels:
~~~

Now customer requested the following information:

• Is that whether this is a workaround or it is considered a long-term fix?
• Does OpenShift development team plan on fixing this so that Operation not permitted errors are not seen in logs when PTP profile is applied?