Re: [uml-devel] [PATCH] UML - support checkstack

2006-08-09 Thread Jeff Dike
On Wed, Aug 09, 2006 at 09:09:22PM -0500, Matt Mackall wrote: > On Wed, Aug 09, 2006 at 02:15:24PM -0400, Jeff Dike wrote: > > Make checkstack work for UML. We need to pass the underlying architecture > > name, rather than "um" to checkstack.pl. > > Does this do the right thing with something lik

Re: [uml-devel] [PATCH] UML - support checkstack

2006-08-09 Thread Matt Mackall
On Wed, Aug 09, 2006 at 02:15:24PM -0400, Jeff Dike wrote: > Make checkstack work for UML. We need to pass the underlying architecture > name, rather than "um" to checkstack.pl. Does this do the right thing with something like Voyager? Or should we just get together a small fund to send the rema

[uml-devel] [PATCH] UML - support checkstack

2006-08-09 Thread Jeff Dike
Make checkstack work for UML. We need to pass the underlying architecture name, rather than "um" to checkstack.pl. Signed-off-by: Jeff Dike <[EMAIL PROTECTED]> Index: linux-2.6.18-mm/Makefile === --- linux-2.6.18-mm.orig/Makefile

[uml-devel] [PATCH] UML - Stack usage reduction

2006-08-09 Thread Jeff Dike
The KSTK_* macros used an inordinate amount of stack. In order to overcome an impedance mismatch between their interface, which just returns a single register value, and the interface of get_thread_regs, which took a full pt_regs, the implementation created an on-stack pt_regs, filled it in, and r

Re: [uml-devel] Which version to use

2006-08-09 Thread Alejandro Liu
Since I am shy, I am posting this here (and not to the LKML). I am including to patch files: patch-hostfsfix.gz This one fixes a crash when trying to mount hostfs, an error on how the mount options were passed and fixed the setattr to set the time correctly (touch command works now). p

Re: [uml-devel] [PATCH 2/3] uml: fix proc-vs-interrupt context spinlock deadlock

2006-08-09 Thread Paolo Giarrusso
Jeff Dike <[EMAIL PROTECTED]> ha scritto: > On Tue, Aug 08, 2006 at 12:59:05PM +0200, Paolo Giarrusso wrote: > > I could be wrong, but I trust that thanks to deep and good work > by > > who designed locking in the network layer, this patch is correct. > And > > indeed I addressed your issues belo