xenbus: Fix S3 frontend resume when xenstored is not running
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v5 Latest2 patches 3 repliesIn review
- v42 patches 5 repliesSuperseded
- v32 patches 6 repliesSuperseded
Earlier versions · 2
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v2 | 2 patches | 3 replies | Superseded | |
| v1 | 2 patches | 6 replies | Superseded |
Patches in v5 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | xenbus: save xenstore local status for later usedrivers/ drivers/ drivers/ | +20 | 0 replies | |
| 2/2 | xenbus: delay xenbus frontend resume if xenstored is not runningdrivers/ include/ | +37 | 3 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | David Vrabel | Jan Beulich |
|---|---|---|
| 1/2 | R-b | |
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH V5 0/2] xenbus: Fix S3 frontend resume when xenstored is not running
Hi,
This patch series fixes the S3 resume of a domain running xenstored and a frontend over xenbus (xen-netfront in my use case).
As device resume is happening before process resume, the xenbus frontend resume is hanging if xenstored is not running, thus causing a deadlock. This patch series is fixing that issue by deferring the xenbus frontend resume when we are running xenstored in that same domain.
Aurelien Chartier (2):
xenbus: save xenstore local status for later use
xenbus: delay xenbus frontend resume if xenstored is not running
drivers/xen/xenbus/xenbus_comms.h | 1 + drivers/xen/xenbus/xenbus_probe.c | 27 +++++++++----------- drivers/xen/xenbus/xenbus_probe.h | 7 ++++++ drivers/xen/xenbus/xenbus_probe_frontend.c | 37 +++++++++++++++++++++++++++- include/xen/xenbus.h | 1 + 5 files changed, 57 insertions(+), 16 deletions(-)
Signature · 1 line
1.7.10.4