search for: reply_error

...+ nvkm_error(subdev, "found queued message without getting an interrupt\n"); + schedule_work(&pmu->recv.work); + + if (!wait_event_timeout(pmu->recv.wait, (pmu->recv.process == 0), jiffies)) { + nvkm_error(subdev, "failed to repair PMU state\n"); + goto reply_error; + } + } else + goto reply_error; + } + + reply[0] = pmu->recv.data[0]; + reply[1] = pmu->recv.data[1]; + mutex_unlock(&subdev->mutex); + return 0; + +reply_error: + reply[0] = 0; + reply[1] = 0; + mutex_unlock(&subdev->mutex); + return -ETIMEDOUT; +} + int nvkm_pmu_send(...

...packets_sent 354199901 node_packets_recv 266253799 keepalive_packets_sent 394382 keepalive_packets_recv 394374 node req_call 143496620 reply_call 90253 req_dmaster 55005319 reply_dmaster 60629271 reply_error 0 req_message 1720274 req_control 74416680 reply_control 29674368 client req_call 253163227 req_message 1113562 req_control 71335811 timeouts call 0...

On Thu, Dec 11, 2014 at 02:11:29PM +0800, Hu Tao wrote: > Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> > --- > daemon/btrfs.c | 104 +++++++++++++++++++++++++++++++-------------------------- > 1 file changed, 56 insertions(+), 48 deletions(-) > > diff --git a/daemon/btrfs.c b/daemon/btrfs.c > index 754fdcd..2e9859d 100644 > --- a/daemon/btrfs.c > +++

Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel" hang when run against oxenstored because it does not handle the unknown XS_RESET_WATCHES operation and does not reply. The symptom of this issue is a hang during boot at this point: cpu 1 spinlock event irq 70 CPU 1 irqstacks, hard=dec94000

This patch set is a follow up to "Add a vhost RPMsg API" [1], it is marked as an RFC because firstly it depends on the RPMsg API series and secondly it is currently being reviewed on ALSA and SOF mailing lists, but any early comments from virtualisation developers would be highly appreciated too! Thanks Guennadi [1]

This patch set is a follow up to "Add a vhost RPMsg API" [1], it is marked as an RFC because firstly it depends on the RPMsg API series and secondly it is currently being reviewed on ALSA and SOF mailing lists, but any early comments from virtualisation developers would be highly appreciated too! Thanks Guennadi [1]