[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: Jun Koi <junkoi2004@xxxxxxxxx>
  • Date: Tue, 1 Sep 2009 18:41:17 +0900
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 01 Sep 2009 02:42:48 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=Q5edIrjI58bntL6WIaC3mXJdLl2++ab49Awln+eIlS1VZjm6XcbXMoMv5ey5sCF9It e0v7EEBW/BrDd4/rPMwVL3PQpXq3ZLCRuOkz5yY5f8+jqXgEkADZQqT9u+ocDwvciKtJ PW+DmXEP0FyKUrFAqOTuaUYk1lmND6Fagqjt0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Sun, Aug 30, 2009 at 4:50 PM, Keir Fraser<keir.fraser@xxxxxxxxxxxxx> wrote:
> For passthrough to HVM guests without hardware IOMMU (e.g., VT-d), I
> developed the attached prototype patch. I think this may already be in the
> XCI tree. It also applies directly to Xen 3.4 branch, and could be applied
> quite easily with a small amount of manual intervention to xen-unstable. If
> passthough on 'old' system without hardware assistance is what you're after,
> you might want to give the patch a go.

Could you confirm that this patch alone is enough?

I applied the patch against unstable code, and Xen hang up (or seems
to hang up) in the middle of booting up Xen, with a black screen.

Thanks,
J





> On 29/08/2009 14:48, "Tim Moore" <timothy.moore@xxxxxxxxxxx> wrote:
>
>> All,
>>
>> I have compiled a list of the Neocleus patches that were released in Sept 07
>> and apply to changeset:  15730 (a long time ago!)
>>
>> It looks like Neocleus have continued development and may have a more recent
>> set of patches, see http://www.neocleus.com/
>>
>> As a person with interest in this subject, I have registered for their
>> "Insider Programme" but have not received an communication. I am very
>> interested in what they have been working on as it all seems to be behind
>> closed doors ! http://www.neocleus.com/insider.php
>>
>> Anyway here are the old set of 1:1 patches:
>>
>> [VTD-NEO][patch 0/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
>> http://markmail.org/message/xbk2o4mzz4coufzp
>>
>> [VTD-NEO][patch 1/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
>> http://markmail.org/message/emyygrqw3crbdhjy
>>
>> [VTD-NEO][patch 2/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
>> http://markmail.org/message/kpbxkyvpeiddxnga
>>
>> [VTD-NEO][patch 3/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
>> http://markmail.org/message/wqd3gvgiwwrf7ct5
>>
>> [VTD-NEO][patch 4/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
>> http://markmail.org/message/cdqfuc6pgyz7vqpc
>>
>> [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
>> http://markmail.org/message/nbx6pk362bdziw4u
>>
>> [VTD-NEO][patch 6/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
>> http://markmail.org/message/m2hyq2ol6r57ghhf
>>
>> I hope this helps explain that there is a lot more to be done, and from these
>> patches we may be able to extract the relevant parts .. there seems to be a
>> lot of functionality in these patches that may already be present in Xen, but
>> I haven't deeply reviewed the contents (and probably not the best man to do
>> so!)
>>
>> Tim
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.