contain the frontend domid, not the uuid. The actual functionality is the same,
because the ID is referred to by path level, so the change in semantics is not
a problem.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
but couldn't because the device was not marked as BLKIF_CONNECTED and thus
blkif_queue_request discarded the read request. fix bug #220
Signed-off-by: Vincent Hanquez <vincent@xensource.com>
safe version for drivers to use that is aware of
save/restore. Post-restore notifications are silently
dropped, in the expectation that xenbus will eventually
get round to telling the driver it needs to reconnect.
Signed-off-by: Keir Fraser <keir@xensource.com>
unbind_evtchn_from_xxx. The bind now returns the IRQ
number on success. The unbind takes this as a parameter
instead of the event-channel port. Also, unbind closes
down the underlying event-channel port if it is still
live.
Signed-off-by: Keir Fraser <keir@xensource.com>
and binding IPIs back to the CPU. In some cases, an IPI would be sent
to CPU1 before it had allocated a new evtchn. Moving smp_resume() call
before setting the cpu online fixes this race. This fixes bug #228
(http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=228).
Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
seems to lock up the domU kernel on restore still (can be
pinged but not ssh'ed). This still needs investigation.
Signed-off-by: Keir Fraser <keir@xensource.com>
Was previously a module, caused LTP test sysfs01 to fail. Compiling in to
the kernel brings this in to line with our own -xen x86-64 kernel and
vendor kernels.
Signed-off-by: James Bulpin <james@xensource.com>
Was previously a module, which wasn't getting loaded and causing the
LTP capset01 test to fail. Compiling in to the kernel brings this in to
line with our own -xen x86-64 kernel and vendor kernels.
Signed-off-by: James Bulpin <james@xensource.com>
xenstore transaction retry loops in our device drivers.
Otherwise things get very smelly if a transaction fails and
is retried.
Signed-off-by: Keir Fraser <keir@xensource.com>
Make xenstored use tdb, transactions can soft-fail (EAGAIN)
Transactions no longer take root dir, no longer lock & block: commit can fail spuriously with EAGAIN, not ETIMEDOUT.
Speeds up transactions by over 1000 times, should be NFS safe.
New program: xs_tdb_dump to dump raw TDB contents.
Don't do failure testing: we are no longer robust against all ENOMEM 8(
Introduce "struct node" which contains perms, children and data.
Make struct xs_permissions unpadded, so we can write to tdb w/o valgrind complaints.
Gently modify TDB to use talloc, not do alloc on tdb_delete.
Fix up transaction users for new semantics.
Don't need a transaction around a single read in xen/i386/kernel/smpboot.c.
Python: transaction_start() returns True/False rather than raising exception on EAGAIN.
Fix usage comment on xs_transaction_end().
Include stdarg to xs_tdb_dump so it compiles.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
