diff options
| author |   Mike Rapoport <rppt@linux.vnet.ibm.com> | 2016-05-04 13:15:50 +0300 |
|---|---|---|
| committer |   Michael S. Tsirkin <mst@redhat.com> | 2016-06-06 13:00:11 +0300 |
| commit | ef1b144d23dbd745fd655b7d0a70212fcc8d0121 (patch) | |
| tree | fd1a0f8127762337be66d51ef96e3e508cc05749 /tools/virtio | |
| parent | tools/virtio/ringtest: add usage example to README (diff) | |
| download | wireguard-linux-ef1b144d23dbd745fd655b7d0a70212fcc8d0121.tar.xz wireguard-linux-ef1b144d23dbd745fd655b7d0a70212fcc8d0121.zip | |
tools/virtio/ringtest: fix run-on-all.sh to work without /dev/cpu
/dev/cpu is only available on x86 with certain modules (e.g. msr) enabled.
Using lscpu to get processors count is more portable.
Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'tools/virtio')
| -rwxr-xr-x | tools/virtio/ringtest/run-on-all.sh | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/virtio/ringtest/run-on-all.sh b/tools/virtio/ringtest/run-on-all.sh index 52b0f71ffa8d..2e69ca812b4c 100755 --- a/tools/virtio/ringtest/run-on-all.sh +++ b/tools/virtio/ringtest/run-on-all.sh @@ -3,10 +3,10 @@ #use last CPU for host. Why not the first? #many devices tend to use cpu0 by default so #it tends to be busier -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) +HOST_AFFINITY=$(lscpu -p=cpu | tail -1) #run command on all cpus -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); +for cpu in $(seq 0 $HOST_AFFINITY) do #Don't run guest and host on same CPU #It actually works ok if using signalling |