public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Avi Kivity <avi@qumranet.com>
Cc: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make LIST_POISON less deadly
Date: Tue, 20 May 2008 14:04:23 +0200	[thread overview]
Message-ID: <4832BE47.2070209@firstfloor.org> (raw)
In-Reply-To: <4832BB6A.8010809@qumranet.com>

Avi Kivity wrote:
> Andi Kleen wrote:
>>> Makes sense.  I'll send out v3.
>>>
>>> Is there a similar range on i386?
>>>     
>>
>> Don't think so. Address space is too precious here.
>>
>> What you could probably do is to unmap one fixed page in some range
>> that is always split to 4K pages anyways and use that. Perhaps somewhere
>> in the 640k-1MB range. But if you're unlucky this might require a
>> variable, not a constant.
>>   
> 
> I guess a fixmap would work for this.  But then the offsets added to
> that page would need to be limited to 4K.

You could make a 3 page fixmap and point to the middle page. 3 because
negative offsets are also especially importants for list_heads due to
list_entry

-Andi



  reply	other threads:[~2008-05-20 12:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18 15:38 [PATCH] Make LIST_POISON less deadly Avi Kivity
2008-05-19 13:01 ` Ingo Molnar
2008-05-19 13:18   ` Avi Kivity
2008-05-19 13:22     ` Ingo Molnar
2008-05-19 13:35       ` Avi Kivity
2008-05-19 13:45   ` Avi Kivity
2008-05-19 19:04     ` Sam Ravnborg
2008-05-20  7:06       ` Avi Kivity
2008-05-20 11:24 ` Andi Kleen
2008-05-20 11:34   ` Avi Kivity
2008-05-20 11:49     ` Andi Kleen
2008-05-20 11:52       ` Avi Kivity
2008-05-20 12:04         ` Andi Kleen [this message]
2008-05-20 12:04         ` Ingo Molnar
2008-05-20 16:47 ` Pavel Machek
2008-05-20 16:50   ` Avi Kivity

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=4832BE47.2070209@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=akpm@osdl.org \
    --cc=avi@qumranet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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