From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Friesen Subject: Re: help? need to enable VT-d for 2.6.27 Date: Tue, 30 Aug 2011 12:11:01 -0600 Message-ID: <4E5D27B5.8090004@genband.com> References: <4E5D0FF3.6030705@genband.com> <4E5D23F5.3070905@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , mtosatti@redhat.com, kvm@vger.kernel.org To: David Ahern Return-path: Received: from exprod7og116.obsmtp.com ([64.18.2.219]:33857 "EHLO exprod7og116.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752643Ab1H3SMA (ORCPT ); Tue, 30 Aug 2011 14:12:00 -0400 In-Reply-To: <4E5D23F5.3070905@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/30/2011 11:55 AM, David Ahern wrote: > On 08/30/2011 10:29 AM, Chris Friesen wrote: >> >> I'm in a bit of an odd situation. We run an embedded version of linux >> on many different boards with different vendor agreements so it's >> painful to upgrade kernel versions. >> >> I've been asked to provide VT-d support for KVM on our kernel (primarily >> for mapping NIC VFs into the guests), and I'm trying to figure out my >> best option to get a working implementation. > > I've had pains with VF passthrough with as late as a Fedora 14 kernel > (2.6.35). Ended up punting and moving to 2.6.39. Ouch. Not good news, but not entirely unexpected. Are you doing anything complicated, or was this just basic functionality that wasn't working? >> Looking at the kvm git tree, kvm-77 seems to be based off 2.6.27. Should >> I look at porting that? > > By 2.6.27 do you mean WRL3 or something else? Yes, that's correct. (Wind River Linux 3, for the non-embedded types out there.) Chris -- Chris Friesen Software Developer GENBAND chris.friesen@genband.com www.genband.com