public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lhms-devel] RE: [PATCH 0/4] V4 ia64 SPARSEMEM
Date: Wed, 28 Sep 2005 10:36:06 +0000	[thread overview]
Message-ID: <20050928103606.GB25483@localhost.localdomain> (raw)
In-Reply-To: <1127779977.10315.6.camel@localhost>

luck wrote:	[Tue Sep 27 2005, 06:00:32PM EDT]
> >Okay. There was a bug in my Kconfig.  All defconfigs and my own memory model
> >configs build correctly and produce the correct config options.  Below is
> >a replacement for patch 1/4 which I've included for your config testing.  I'll
> >post V5 patchset when we agree on where we want to proceed with config(s).  
> 
> Yup, all my configs now build too (includes some of the distributed ones
> with CONFIG_SMP turned off).  I booted three sample kernels (zx1,
> generic and generic with s/discontig/sparse/) on rx2620 with nothing
> odd happening.
> 
> >I'm thinking all we need is sparsemem_defconfig which is defconfig but with
> >the SPARSEMEM memory model.
> 
> That would do as a starting point ... it gives me an easy hook
> into my automatic build script to make sure that SPARSEMEM is being
> test compiled.
Okay I'll provide this.
> 
> Do you have, or can you generate, the full list of all the combinations
> of memory model related options that Kconfig will accept?
Yes. I can send three of my test configurations: 1) FLATMEM, 
2) DISCONTIGMEM and 3) SPARSEMEM (which will be in sparsemem_defconfig).  This 
should be representative of what you'd like.

I'll post to you privately unless someone on this thread requests them.
> 
> -Tony
bob

  parent reply	other threads:[~2005-09-28 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27  0:12 [Lhms-devel] Re: [PATCH 0/4] V4 ia64 SPARSEMEM Dave Hansen
2005-09-27 14:07 ` Bob Picco
2005-09-27 14:25 ` Dave Hansen
2005-09-28 10:36 ` Bob Picco [this message]
2005-09-28 11:03 ` [Lhms-devel] " Robin Holt
2005-09-28 15:42 ` Bob Picco
2005-09-28 22:05 ` Greg Edwards
2005-09-28 22:10 ` Bruce Losure

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=20050928103606.GB25483@localhost.localdomain \
    --to=bob.picco@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox