From: "James Harper" <james.harper@bendigoit.com.au>
To: xen devel <xen-devel@lists.xensource.com>
Subject: force option of xm block-detach
Date: Mon, 21 Mar 2011 16:30:53 +1100 [thread overview]
Message-ID: <AEC6C66638C05B468B556EA548C1A77D01CC816F@trantor> (raw)
How does the 'force' option to block-detach differ to not using it? Can
DomU PV drivers tell if this is a forceful detach request?
Thanks
James
next reply other threads:[~2011-03-21 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 5:30 James Harper [this message]
2011-03-21 8:27 ` force option of xm block-detach Keir Fraser
2011-03-21 13:42 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AEC6C66638C05B468B556EA548C1A77D01CC816F@trantor \
--to=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).