Hello Andrea, I have applied the patch to kvm and userland, but, when I tried to port the host kernel patch I noticed that the changes were over the file e820.c. However, on kernel 2.6.26 there are two e820 files, e820_32.c and e820_64.c and most of the changes maps on the e820_64.c file. So, I have a couple of questions if you don't mind: - Against which kernel version was this patch generated? - Did you try this on a 32 or 64 bits system? Thanks, Pablo >-----Original Message----- >From: Andrea Arcangeli [mailto:aarcange@xxxxxxxxxx] >Sent: Monday, April 27, 2009 2:43 PM >To: Passera, Pablo R >Cc: kvm@xxxxxxxxxxxxxxx >Subject: Re: [PATCH] reserved-ram for pci-passthrough without VT-d >capable hardware > >Hello Pablo, > >On Mon, Apr 27, 2009 at 11:00:51AM -0600, Passera, Pablo R wrote: >> Andrea, >> We are working with embedded hardware that does not have >>VT-d and we need 1-1 mapping. I wonder which is the status of this >>patch. Have you continued updating it with the latest KVM version? > >Sorry to say but it isn't updated to latest KVM and latest >mainline. Porting normally should be easy. I attached last versions. > >> Since you mentioned this ;), I take opportunity to add that those >> embedded usages are the ones that are totally fine with the compile >> time passthrough-guest-ram decision, instead of a boot time >> decision. Those host kernels will likely have RT patches (KVM works >> great with preempt-RT indeed) and in turn the compile time ram >> selection is the least of their problems as you can imagine ;). So you >> can see my patch as an embedded-build option, similar to "Configure >> standard kernel features (for small systems)" and no distro is >> shipping new kernels with that feature on either. >> >> Than if we decide 1:1 should have larger userbase instead of only the >> people that knows what they're doing (i.e. 1:1 guest can destroy >> linux-hypervisor) we can always add a bit of strtol parsing to 16bit >> kernelloader. > >Agreed! -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
