[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 mregedcode for PCI passthrough
Better to use a boolean param called 'nativedom'. Then the user can automatically specify any one of 'nativedom', 'nativedom=on', 'nativedom=1', 'nativedom=true', ... -- Keir On 16/9/07 18:26, "Guy Zana" <guy@xxxxxxxxxxxx> wrote: > That will be "enable_nativedom=1" (without the 'd'). > > Thanks, > Guy. > >> -----Original Message----- >> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx >> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of >> Kay, Allen M >> Sent: Wednesday, September 05, 2007 3:09 AM >> To: xen-devel@xxxxxxxxxxxxxxxxxxx >> Cc: Guy Zana; Keir Fraser >> Subject: [Xen-devel] [VTD-NEO][patch 0/6] Intel VT-d/Neocleus >> 1:1 mregedcode for PCI passthrough >> >> 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. >> >> To enabled xen vt-d code, add "ioapic_ack=old" to xen boot >> parameter in grub.conf on systems with VT-d hardware. >> >> To enabled xen 1:1 mapping code, add "enabled_nativedom=1" to >> xen boot parameter in grub.conf. >> >> Signed-off-by: Allen Kay <allen.m.kay@xxxxxxxxx> >> Signed-off-by: Guy Zana <guy@xxxxxxxxxxxx> >> >> _______________________________________________ >> 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 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |