All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hicks <mort@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: efi_memmapwalk re-write (please test)
Date: Wed, 07 Sep 2005 19:16:24 +0000	[thread overview]
Message-ID: <20050907191624.GR13449@localhost> (raw)
In-Reply-To: <200509062048.j86KmBPD004877@agluck-lia64.sc.intel.com>


On Tue, Sep 06, 2005 at 01:48:11PM -0700, Luck, Tony wrote:
> I cleaned up my find_memmap_space() to do the right thing (allocate
> from a block of memory that will be used by the kernel).  I also
> had a couple of bugs in my code to find/divide all the memory
> between WB:kernel and UC:uncached-allocator.
> 
> Tested on tiger and zx1 (N.B. it didn't find any trimmed off scraps
> of memory that could be used as uncached on zx1).

So its really close on sn2.  I'm not sure exactly what's going wrong,
but with the new efi_memmap_walk stuff something is getting clobbered, I
think.

The efivars.c driver is looping through all the efi vars more than once,
causing efivar_create_sysfs_entry() to croak on the kobject_add() and
return -EEXIST during the first attempt to register a duplicate
variable.

This happens on an sn2 kernel without the Cross partition stuff compiled
(eliminating the uncached allocator from being the culprit).

I stuck KDB into the kernel and it doesn't crash anymore so I'm not sure
what the problem is :-/

> *) still passes region 6 addresses in efi_memmap_walk_uc() case, but
> could easily revert to physical addresses.  Comments?  Jes?  Martin?
> 

I think we can work with this either way.

Attached is a very small patch to find the uncached memory on SN2.

mh

-- 
Martin Hicks   ||   Silicon Graphics Inc.   ||   mort@sgi.com

  reply	other threads:[~2005-09-07 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 20:48 efi_memmapwalk re-write (please test) Luck, Tony
2005-09-07 19:16 ` Martin Hicks [this message]
2005-09-07 19:17 ` Martin Hicks
2005-09-07 19:33 ` Luck, Tony
2005-09-08 15:26 ` Martin Hicks
2005-09-08 18:05 ` Luck, Tony

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=20050907191624.GR13449@localhost \
    --to=mort@sgi.com \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.