* On Monday 14 Apr 2008 06:01:07 Samuel Masham wrote: > On Sun, Apr 13, 2008 at 9:49 PM, Dor Laor <dor.laor@xxxxxxxxxxxx> wrote: > > On Thu, 2008-04-10 at 11:48 +0300, Amit Shah wrote: > > > If kvm uses the in-kernel irqchip, interrupts are routed to > > > the guest via the kvm module (accompanied kernel changes are > > > necessar). If -no-kvm-irqchip is used, the 'irqhook' module, also > > > included here, is to be used. > > > > IMO we can drop the pci pass through support in userspace and only keep > > the in-kenel chip path. Normally we do want the option of running w/o > > kernel devices but it's only to test for regressions against userspace. > > In this case it's all new code so there is no point to compare, it's > > just lots of complicated code (userspace apic, irqhook module) that only > > helpful for qemu. Since it's not likely qemu will merge it, let's stick > > with the main path. > > Comments? > > Please keep the userspace support alive. > > I am particularly interested in using the pci-passthough to qemu > running non x86 system emulation > (at the moment mips) > > My hope is that the pci - passthough could help with developing > drivers and testing across architectures... OK; keeping support around won't be too much of a hassle, though the current support for pci-passthrough and the irqhook module are developed with x86 in mind (and only tested on x86). Since it's not tested on any other architecture, I've marked it TARGET_I386 and TARGET_X86_64 for now. Feel free to extend it to other architectures. Amit. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
