From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: pgcl-2.5.70-bk6-1
Date: Mon, 2 Jun 2003 01:02:01 -0700 [thread overview]
Message-ID: <20030602080201.GC20413@holomorphy.com> (raw)
(1) fix incorrect virtual address calculation in kmap_atomic()
(2) more compilefixes for arch/i386/mm/highmem.c
(3) checking for alignment of kmap() and kmap_atomic() virtualspace
in arch/i386/mm/init.c
(4) rework fixmap enums yet again so kmap() and kmap_atomic() areas
actually come out properly aligned
(5) change FIXADDR_TOP to -PAGE_SIZE so the offset calculation isn't
as easy to screw up
(6) fix mismerge of pgd_ctor() bits that installed garbage pmd's on
CONFIG_HIGHMEM64G
Also available vs. pgcl-2.5.70-bk5-2 as pgcl-2.5.70-bk5-3.
This appears to boot and run on CONFIG_HIGHMEM64G, but I've had reports
of some sysenter bug. If I could get them reproduced with this release
so I can look further into them, I'd be much obliged. Testers running
with CONFIG_HIGHMEM64G, please update to this release.
As usual, available from:
ftp://ftp.kernel.org/pub/linux/kernel/people/wli/vm/pgcl/
-- wli
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: pgcl-2.5.70-bk6-1
Date: Mon, 2 Jun 2003 01:02:01 -0700 [thread overview]
Message-ID: <20030602080201.GC20413@holomorphy.com> (raw)
(1) fix incorrect virtual address calculation in kmap_atomic()
(2) more compilefixes for arch/i386/mm/highmem.c
(3) checking for alignment of kmap() and kmap_atomic() virtualspace
in arch/i386/mm/init.c
(4) rework fixmap enums yet again so kmap() and kmap_atomic() areas
actually come out properly aligned
(5) change FIXADDR_TOP to -PAGE_SIZE so the offset calculation isn't
as easy to screw up
(6) fix mismerge of pgd_ctor() bits that installed garbage pmd's on
CONFIG_HIGHMEM64G
Also available vs. pgcl-2.5.70-bk5-2 as pgcl-2.5.70-bk5-3.
This appears to boot and run on CONFIG_HIGHMEM64G, but I've had reports
of some sysenter bug. If I could get them reproduced with this release
so I can look further into them, I'd be much obliged. Testers running
with CONFIG_HIGHMEM64G, please update to this release.
As usual, available from:
ftp://ftp.kernel.org/pub/linux/kernel/people/wli/vm/pgcl/
-- wli
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2003-06-02 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 8:02 William Lee Irwin III [this message]
2003-06-02 8:02 ` pgcl-2.5.70-bk6-1 William Lee Irwin III
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=20030602080201.GC20413@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.