public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386: per-CPU double fault TSS and stack
Date: Mon, 3 Sep 2007 14:45:33 +0200	[thread overview]
Message-ID: <200709031445.33435.ak@suse.de> (raw)
In-Reply-To: <46DBFF65.76E4.0078.0@novell.com>


> It costs 4.xx k space per CPU - perhaps a constraint for embedded?

Not a major one.

> >In fact I would prefer to just eliminate CONFIG_DOUBLEFAULT (imho
> >it always a bad idea because the amount of code it saves is miniscule)
> > instead of adding such a ifdef maze.
>
> It's configurable for embedded only anyway, and I think there's some value
> in allowing it to be configured off for that environment.
>

With less ifdefs then please.

>
> >> +				BUG_ON(page_count(page));
> >> +				init_page_count(page);
> >> +				free_pages(stack, j);
> >> +				stack += (PAGE_SIZE << j);
> >
> >In 2.4-aa I added a alloc_pages_exact() for this. I don't think such games
> > should be played outside page_alloc.c. I would recommend to readd
> > alloc_pages_exact() and then use it.
>
> Will need to track that patch down.

http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.23aa3/00_module-gfp-7
But it'll need quite some changes for 2.6 anyways.


> >> -#define DOUBLEFAULT_STACKSIZE (1024)
> >> -static unsigned long doublefault_stack[DOUBLEFAULT_STACKSIZE];
> >> -#define STACK_START (unsigned
> >> long)(doublefault_stack+DOUBLEFAULT_STACKSIZE) +extern unsigned long
> >> max_low_pfn;
> >
> >No externs in .c
>
> The question is - is it acceptable to declare max_low_pfn in any header?

Sure, why not?

-Andi

      reply	other threads:[~2007-09-03 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 12:14 [PATCH] i386: per-CPU double fault TSS and stack Jan Beulich
2007-09-01 10:33 ` Andi Kleen
2007-09-03 10:34   ` Jan Beulich
2007-09-03 12:45     ` Andi Kleen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200709031445.33435.ak@suse.de \
    --to=ak@suse.de \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox