All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Andrew Morton <akpm@osdl.org>, jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: net patches
Date: Tue, 4 Jan 2005 22:48:57 -0800	[thread overview]
Message-ID: <20050105064857.GD7961@holomorphy.com> (raw)
In-Reply-To: <20050104223104.2ec87f5b.davem@davemloft.net>

On Tue, 4 Jan 2005 21:59:13 -0800 Andrew Morton <akpm@osdl.org> wrote:
>> I'll unload some accumulated net patches.  I can't say that I've looked at
>> them very closely.

On Tue, Jan 04, 2005 at 10:31:04PM -0800, David S. Miller wrote:
> I'll be quiet for the next few days as I try to discover why
> sparc64 now explodes after the past week of changes.  I'm
> heavily suspecting the 4-level page table stuff.  wli kept
> saying that he was having trouble getting his sparc boxes
> working with the -mm tree over the past month and that's about
> how long the 4-level page table stuff has been in there.
> What's odd is that Andi's original 4-level page table patch
> he gave to me worked just fine on sparc64, but it's been
> changed a lot.

I eventually narrowed this down to something associated with some
unusual core fault handling changes with an unclear relationship to
Andi's 4-level code. Something odd was going on with spec-guided
definitions of pte_read(), pte_write(), et al.

sun4u seemed to do okay with Andi's earlier code in my testing; later
problems seemed to stem from elsewhere (e.g. the ioctl bogon).

$ uname -a
Linux analyticity 2.6.10-rc2-mm2 #8 SMP Sat Dec 18 07:57:42 PST 2004 sparc64 GNU/Linux


-- wli

  reply	other threads:[~2005-01-05  6:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05  5:59 net patches Andrew Morton
2005-01-05  6:31 ` David S. Miller
2005-01-05  6:48   ` William Lee Irwin III [this message]
2005-01-05  7:25 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2005-03-15 22:21 Andrew Morton

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=20050105064857.GD7961@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    /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.