From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH 8/8] raisin: RFC Add blktap2 as an external tree Date: Tue, 21 Apr 2015 11:47:20 +0100 Message-ID: <55362AB8.9030409@eu.citrix.com> References: <1429201182-1044-1-git-send-email-george.dunlap@eu.citrix.com> <1429201182-1044-8-git-send-email-george.dunlap@eu.citrix.com> <5534DC18.1010609@eu.citrix.com> <1429608339.4743.4.camel@citrix.com> <55361D37.1000205@eu.citrix.com> <553626C4.4010308@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: Dave Scott , David Vrabel , Stefano Stabellini , Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 04/21/2015 11:42 AM, Stefano Stabellini wrote: >> The only reason to disable this on ARM at the minute is because you >> *believe* that nobody will ever want to build the blktap2 kernel module >> on ARM, and so you want to avoid the build overhead and space overhead >> of compiling and using dead code. If that's your goal, you might get >> more mileage out of disabling stuff like xenmon or the paging code. :-) > > No, that is not right. The reason I would like to disable blktap2 for > ARM is that the userspace binaries and libraries won't compile on ARM at > the moment. At least that was the case the last time I tried it. If you > prove me wrong, I would be happy to have blktap2 on ARM too. Right, I didn't realize that. That's certainly a good reason to disable it on ARM. :-) -George