All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Dave Scott <Dave.Scott@eu.citrix.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	Jonathan Ludlam <Jonathan.Ludlam@eu.citrix.com>,
	xen-devel@lists.xen.org, Ian Jackson <ian.jackson@citrix.com>,
	Yang Hongyang <yanghy@cn.fujitsu.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH RFC 2/4] build: Download and build extnernal blktap2.5 repo
Date: Mon, 30 Mar 2015 15:43:07 +0100	[thread overview]
Message-ID: <551960FB.8090806@eu.citrix.com> (raw)
In-Reply-To: <20150330143322.GH25911@zion.uk.xensource.com>

On 03/30/2015 03:33 PM, Wei Liu wrote:
> On Thu, Mar 26, 2015 at 12:46:08PM +0000, George Dunlap wrote:
>> Download and build XenServer's blktap as an external tree, similar to
>> qemu-xen.
>>
>> As of this patch we just download and build it, but don't install or
>> use it.
>>
>> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
>> ---
>>
>> FIXME: Directly use the XenServer github repo for now, while we're
>> discussing things.  If we decide to take this series, we'll have to
>> clone the tree on xenbits and remove the FIXME line.
>>
> 
> IMHO we need to support --with-system-blktap= in configure in case
> distro wants to package blktap separately. Not sure if in practice this
> makes sense since AIUI blktap is only used by Xen.

I agree that would be ideal; however, it's not so simple, because at the
moment libxl links directly against libblktap.  This would mean:

1) Changing libxl so that it could dynamically detect the presence of
the proper version of libblktap at runtime and use the stubbed-out
defaults if not available.

2) Changing libxl to exec() tapctl rather than making library calls.
(This might involve making sure that tapctl actually has all the
functionality we need.)

#1 is even more difficult because at the moment blktap isn't really
designed to have stable external versions -- it would involve adding a
library version and all the fun stuff we already do with libxl.

#2 has another potential advantage: using the command-line may make it
easier to be forward-compatible, since adding options won't break
(unlike adding arguments to a function signature).

(Although, I think for API compatibility, changing the public functions
to use structs is probably a more reliable thing to do.)

Either way, I think that's something we should start to look at after
pivoting to the external blktap repo.

 -George

  parent reply	other threads:[~2015-03-30 14:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 12:46 [PATCH RFC 0/4] tools: Upstream blktap "2.5" as an external repo George Dunlap
2015-03-26 12:46 ` [PATCH RFC 1/4] build: Reorganize and briefly document "external repo" template in tools/Makefile George Dunlap
2015-03-30  9:07   ` Ian Campbell
2015-03-26 12:46 ` [PATCH RFC 2/4] build: Download and build extnernal blktap2.5 repo George Dunlap
2015-03-26 12:55   ` Ian Campbell
2015-03-26 14:04     ` George Dunlap
2015-03-30 14:33   ` Wei Liu
2015-03-30 14:41     ` Ian Campbell
2015-03-30 14:46       ` George Dunlap
2015-03-30 14:50       ` Andrew Cooper
2015-03-30 14:43     ` George Dunlap [this message]
2015-03-30 15:38       ` Wei Liu
2015-03-31  9:55         ` George Dunlap
2015-03-31 10:40           ` Stefano Stabellini
2015-03-31 11:10             ` George Dunlap
2015-03-31 12:02               ` Ian Campbell
2015-03-31 12:03               ` Ian Campbell
2015-03-26 12:46 ` [PATCH RFC 3/4] libxl: Use XenServer's blktap2.5 George Dunlap
2015-03-26 12:46 ` [PATCH RFC 4/4] tools: Remove in-tree blktap2 George Dunlap
2015-03-26 13:50 ` [PATCH RFC 0/4] tools: Upstream blktap "2.5" as an external repo George Dunlap
2015-03-26 15:47 ` Jon Ludlam
2015-03-26 16:08   ` George Dunlap
2015-03-26 16:25     ` Felipe Franciosi
2015-03-26 17:05       ` George Dunlap
2015-03-26 17:12         ` Andrew Cooper
2015-03-26 17:23           ` George Dunlap
2015-03-26 18:06             ` Felipe Franciosi
2015-03-26 16:42     ` Jon Ludlam

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=551960FB.8090806@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Dave.Scott@eu.citrix.com \
    --cc=Jonathan.Ludlam@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=wency@cn.fujitsu.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yanghy@cn.fujitsu.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 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.