From: Keir Fraser <keir.xen@gmail.com>
To: James Harper <james.harper@bendigoit.com.au>,
xen devel <xen-devel@lists.xensource.com>
Subject: Re: force option of xm block-detach
Date: Mon, 21 Mar 2011 08:27:25 +0000 [thread overview]
Message-ID: <C9ACBC6D.151DE%keir.xen@gmail.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01CC816F@trantor>
On 21/03/2011 05:30, "James Harper" <james.harper@bendigoit.com.au> wrote:
> 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?
I believe it means after a timeout we will simply delete the xenstore info
relating to the VBD, rather than wait an arbitrary time for the xenbus
connection to get driven into disconnected state. Thus it's not something
that is made visible to frontend/backend drivers.
-- Keir
> Thanks
>
> James
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-03-21 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 5:30 force option of xm block-detach James Harper
2011-03-21 8:27 ` Keir Fraser [this message]
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=C9ACBC6D.151DE%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=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).