forkloop

VFIO

Not KVM bound. The VFIO API deconstructs a device into regions, irqs, etc. The userspace application (QEMU, cloud-hypervisor, etc..) is responsible for reconstructing it into a device for e.g. a guest VM to consume.

Boot with intel_iommu=on.

IOMMU groups

Devices are bound together for isolation, IOMMU capabilities and platform topology reasons. It is not configurable.

forkloop

# https://github.com/mehrdada/grpc/blob/aa477becd1a7c44f8150ad24539cf6d40af24b37/examples/python/interceptors/service-latency-interceptor/service_latency_interceptor.py

import logging
import threading
import grpc


def _wrap_rpc_behavior(handler, fn):
    if handler is None:
        return None

forkloop

#!/usr/bin/osascript

on run(argv)
    if count of argv is equal to 0 then
        set msg to "Usage\n\tset_bg URI"
        return msg
    end if

    set uri to item 1 of argv
    set dest to do shell script "echo /tmp/$(date +%Y%m%d%H%M%S).jpg"

forkloop

#!/usr/bin/ruby

require 'set'
require 'yaml'

# sync the Android DCIM foler periodically

PATH = '/mnt/sdcard/DCIM/Camera'
DEST = "#{ENV['HOME']}/Pictures/Android"

forkloop

set -g default-terminal "screen-256color"

set -g prefix C-b
set -g base-index 1

# Split window
bind | split-window -h
bind - split-window -v

# Reload config file

forkloop

#! /usr/bin/env python
"""
particle filter
http://people.csail.mit.edu/rplatt/hw5.html

using SIR
@forkloop
"""
from __future__ import division
import numpy as np