search for: ccontroller

Hi all, The next obvious step for paravirt_ops seems to me to be higher-level mmu operations: from reading the VMI patches it seems to do flushing, whereas Xen opts for batching. In the spirit of ops structures, this would be done by putting higher-level operations into the ops structure, and batching done by the op itself (perhaps with a default implementation for those too lazy to implement

Hi all, The next obvious step for paravirt_ops seems to me to be higher-level mmu operations: from reading the VMI patches it seems to do flushing, whereas Xen opts for batching. In the spirit of ops structures, this would be done by putting higher-level operations into the ops structure, and batching done by the op itself (perhaps with a default implementation for those too lazy to implement

Move header includes for the nopud / nopmd types to the location of the actual pte / pgd type definitions. This allows generic 4-level page type code to be written before the split 2/3 level page table headers are included. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

Move header includes for the nopud / nopmd types to the location of the actual pte / pgd type definitions. This allows generic 4-level page type code to be written before the split 2/3 level page table headers are included. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

AFAICT we'll pay one extra TLB entry for this patch. Zach had a patch which left the vsyscall page at the top of memory (minus hole for hypervisor) and patched the ELF header at boot. Thoughts welcome, Rusty. Name: Move vsyscall page out of fixmap, above stack Author: Gerd Hoffmann <kraxel@suse.de> Hypervisors want to use memory at the top of the address space (eg. 64MB for Xen, or

AFAICT we'll pay one extra TLB entry for this patch. Zach had a patch which left the vsyscall page at the top of memory (minus hole for hypervisor) and patched the ELF header at boot. Thoughts welcome, Rusty. Name: Move vsyscall page out of fixmap, above stack Author: Gerd Hoffmann <kraxel@suse.de> Hypervisors want to use memory at the top of the address space (eg. 64MB for Xen, or

Hi all, I've been looking at finding common ground between the VMI, Xen and other paravirtualization approaches, and after some discussion, we're getting somewhere. These first two patches are the fundamentals, stolen mainly from the VMI patches: removing assumptions about the kernel running in ring 0, and macro-izing all the obvious para-virtualize-needing insns. The third patch is

Hi all, I've been looking at finding common ground between the VMI, Xen and other paravirtualization approaches, and after some discussion, we're getting somewhere. These first two patches are the fundamentals, stolen mainly from the VMI patches: removing assumptions about the kernel running in ring 0, and macro-izing all the obvious para-virtualize-needing insns. The third patch is

When I used to write Perl CGI scripts I displayed an animated gif image whilst waiting for a long database query to load, and some javascript to remove the image once the content was available. I''d like to do the same thing with Rails, but it''s not clear to me how to do this in Rails. Does anyone have any suggestions? -- Posted via http://www.ruby-forum.com/.

Hi all, Sorry for the delay. This implements binary patching of call sites for interrupt-related paravirt ops, since no-doubt Andi wasn't the only one to believe this approach is slow. The benchmarks were done on a UP 3GHz Pentium 4 with 512MB of RAM. 2.6.17-rc4 vs 2.6.17-rc4 with CONFIG_PARAVIRT=y vs 2.6.17-rc4 CONFIG_PARAVIRT=y with patch. Summary: with binary patching, the difference

Hi all, Sorry for the delay. This implements binary patching of call sites for interrupt-related paravirt ops, since no-doubt Andi wasn't the only one to believe this approach is slow. The benchmarks were done on a UP 3GHz Pentium 4 with 512MB of RAM. 2.6.17-rc4 vs 2.6.17-rc4 with CONFIG_PARAVIRT=y vs 2.6.17-rc4 CONFIG_PARAVIRT=y with patch. Summary: with binary patching, the difference

So, is everyone happy with this smerge of Ingo and Gerd's work? Reposted below. Thanks, Rusty. -------- Forwarded Message -------- From: Linus Torvalds <torvalds@osdl.org> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Andrew Morton <akpm@osdl.org> Subject: Re: [Fwd: [Fwd: FW: argh]] Date: Wed, 17 May 2006 21:35:51 -0700 (PDT) On Thu, 18 May 2006, Rusty Russell wrote: >

So, is everyone happy with this smerge of Ingo and Gerd's work? Reposted below. Thanks, Rusty. -------- Forwarded Message -------- From: Linus Torvalds <torvalds@osdl.org> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Andrew Morton <akpm@osdl.org> Subject: Re: [Fwd: [Fwd: FW: argh]] Date: Wed, 17 May 2006 21:35:51 -0700 (PDT) On Thu, 18 May 2006, Rusty Russell wrote: >

The rails docs are so horrible on the collection_select method. They need to show a *complete* form, and show two examples: one that calls f.collection_select(), and another that calls collection_select(), and explain the differences. Given this line: f.collection_select :topic, Topic.all, :id, :category What the !@#$!@#$ is :topic? -- Posted via http://www.ruby-forum.com/. -- You received

Hi: I need install in one solaris9-sparc Samba, but in the http://us4samba.org/ftp/Binary_Packages/solaris/ <http://us4samba.org/ftp/Binary_Packages/solaris/> I dont see the binaries. Somebody could please help me to find samba for solaris sparc. Thanks a lot E.