[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] [VTD-NEO][patch 0/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
Attached are header file patches I rebased to cs# 15837. I moved neo's include file from xen to xen/asm. I couldn't move them to xen/arch/x86/pt directory because some generic file reference them. Vtd_inc.patch: include generic changes and one vt-d file (intel-iommu.h) P2m_inc.patch: changes to p2m.h Neo_inc.patch: Neocleus specific changes Signed-off-by: Allen Kay <allen.m.kay@xxxxxxxxx> Signed-off-by: Guy Zana <guy@xxxxxxxxxxxx> Allen >-----Original Message----- >From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] >Sent: Tuesday, September 11, 2007 5:50 AM >To: Kay, Allen M; xen-devel@xxxxxxxxxxxxxxxxxxx >Cc: Guy Zana >Subject: Re: [Xen-devel] [VTD-NEO][patch 0/6] Intel >VT-d/Neocleus 1:1 mreged code for PCI passthrough > >On 5/9/07 01:08, "Kay, Allen M" <allen.m.kay@xxxxxxxxx> wrote: > >> The following 6 patches contains merge of Intel VT-d and >Neocleus' 1:1 >> mapping patches for enabling HVM guest direct device access that were >> last submitted around end of May. These patches applied cleanly to >> changeset 15730. > >The 'include' patch doesn't apply any more, and in any case >needs splitting >up logically (vtd bits go in vtd patch; neo bits in neo patch; >any generic >bits in xen patch). The 'pt' (neo) code looks to throw way too >much stuff in >include/xen/ of which I suspect most is private definitions that really >belong in the pt/ directory. Also consider which bits should be in >include/asm rather than include/xen. > >The presence of the E820_1TO1 stuff makes me suspect that the 1:1 area >allocation hasn't been cleaned up as much as it should have been. There >shouldn't be any need to modify Xen's permanent e820 map I think. > >Haven't looked any further at the Xen parts, but I'll take a >look at the >tools patch... > > -- Keir > Attachment:
vtd_inc.patch Attachment:
p2m_inc.patch Attachment:
neo_inc.patch _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |