All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Ross Philipson <ross.philipson@gmail.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 1/2] tools: remove blktap2 related code and documentation
Date: Tue, 30 Aug 2016 14:20:49 +0100	[thread overview]
Message-ID: <20160830132049.GK8502@citrix.com> (raw)
In-Reply-To: <22469.33273.133558.131000@mariner.uk.xensource.com>

On Tue, Aug 30, 2016 at 01:54:17PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH v2 1/2] tools: remove blktap2 related code and documentation"):
> > Blktap2 is effectively dead code for a few years.
> > 
> > Notable changes in this patch:
> > 
> > 0. Unhook blktap2 from build system
> > 1. Now libxl no longer supports TAP disk backend, appropriate assertions
> >    are added and some code paths now return ERROR_FAIL
> > 2. Tap is no longer a supported backend in doc
> > 3. Remove relevant entries in MAINTAINERS
> > 
> > A patch to actually remove blktap2 directory will come later.
> 
> The change to libxl seems OK to me, although:
> 
> > This version is tested: libxl bails when trying to set backend to tap.
> 
> What error message and error code do you get ?  If we're removing
> this, we should make sure that the error message makes sense.
> 

The error code is going to be ERROR_INVAL. The error message is going to
be:

Disk vdev=XXX, backend tap unsuitable because blktap not supported
no suitable backend for disk XXX

See libxl__device_disk_set_backend.

> All the rest is fine by me.  But we should wait a bit more to see if
> anyone objects IMO.
> 
> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-08-30 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 10:59 [PATCH v2 0/2] Remove blktap2 Wei Liu
2016-08-26 10:59 ` [PATCH v2 1/2] tools: remove blktap2 related code and documentation Wei Liu
2016-08-30 12:54   ` Ian Jackson
2016-08-30 13:20     ` Wei Liu [this message]
2016-09-06  9:47       ` Ian Jackson
2016-08-26 10:59 ` [PATCH v2 2/2] tools: remove blktap2 source code Wei Liu
2016-09-06 10:04   ` Wei Liu
2016-09-06  9:57 ` [PATCH v2 0/2] Remove blktap2 Wei Liu
2016-09-06 10:18   ` Lars Kurth

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=20160830132049.GK8502@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=lars.kurth@citrix.com \
    --cc=ross.philipson@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.