Re: [PATCH][2/2] double stack limit (rfc)

On Thu, 22 Mar 2007 21:56:03 -0700 "Tony Luck" <[EMAIL PROTECTED]> wrote: > On 3/22/07, KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote: > > I hear some people says that "When I set stack-size-limit to 32M, > > I want to use 32M of memory stack..." and register-stack expansion can > > fail because sta

Re: [PATCH][2/2] double stack limit (rfc)

On 3/22/07, KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote: I hear some people says that "When I set stack-size-limit to 32M, I want to use 32M of memory stack..." and register-stack expansion can fail because stack is used up by memory-stack. An interesting dilemma. If you apply this patch thoug

[PATCH][2/2] double stack limit (rfc)

Now, ia64's hard-stack-size (rlimit.max) is sum of register-stack size and memory-stack size. But soft-stack-size (rlimit.cur) accounitng is not sum.. they are accounted independently. This is inconsistent. I hear some people says that "When I set stack-size-limit to 32M, I want to use 32M of memo

[PATCH][ia64][1/2] bugfix stack layout upside-down

ia64 expects following vm layout == [register-stack] [memory-stack] == But, when ulimit -s is used and stack-base-address-randomization works, vm layout is sometimes following. == [memory-stack] [register-stack] == If this happens, register-stack cannot be expanded. This patch fixes this bug by

Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0)

On Fri, 23 Mar 2007 00:04:07 +0100 Bernhard Walle <[EMAIL PROTECTED]> wrote: > * Andrew Morton <[EMAIL PROTECTED]> [2007-03-22 22:09]: > > On Tue, 20 Mar 2007 16:00:27 +0100 > > Bernhard Walle <[EMAIL PROTECTED]> wrote: > > > > > On IA64, the timer interrupt is not (always?) zero as it is on x86

Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0)

* Andrew Morton <[EMAIL PROTECTED]> [2007-03-22 22:09]: > On Tue, 20 Mar 2007 16:00:27 +0100 > Bernhard Walle <[EMAIL PROTECTED]> wrote: > > > On IA64, the timer interrupt is not (always?) zero as it is on x86 > > platforms. > > Also, the timer interrupt is CPU-local. Two things need to be change

Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0)

Hello, * Thomas Gleixner <[EMAIL PROTECTED]> [2007-03-22 22:23]: > > > Also, the code presently passes the magic IRQ number into the generic IRQ > > code. I wonder if we'd get a more pleasing result if we were to make the > > generic IRQ code call _out_ to the architecture: > > > Then, ia64 can

Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0)

On Thu, 22 Mar 2007 22:23:21 +0100 Thomas Gleixner <[EMAIL PROTECTED]> wrote: > On Thu, 2007-03-22 at 14:09 -0700, Andrew Morton wrote: > > I think the term 'timer_interrupt' is a bit generic-sounding. Would it be > > better to call it irqpoll_interrupt? After all, some architecture might > > wa

Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0)

On Thu, 2007-03-22 at 14:09 -0700, Andrew Morton wrote: > I think the term 'timer_interrupt' is a bit generic-sounding. Would it be > better to call it irqpoll_interrupt? After all, some architecture might > want to use, umm, the keyboard interrupt to trigger IRQ polling ;) Interesting thought

Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0)

On Tue, 20 Mar 2007 16:00:27 +0100 Bernhard Walle <[EMAIL PROTECTED]> wrote: > On IA64, the timer interrupt is not (always?) zero as it is on x86 platforms. > Also, the timer interrupt is CPU-local. Two things need to be changed to make > the irqpoll option make also working on IA64: > > o Call

Re: [patch 5/5] ia64: update memory attribute aliasing documentation & test cases

> > + Failing all of the above, we have to all back to a UC mapping. > > s/all back/fall back/ Thanks, corrected version below. ia64: update memory attribute aliasing documentation & test cases Updates documentation and adds some test cases. Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]>