From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] kernel bug
Date: Tue, 3 Jun 2014 13:08:17 -0400 [thread overview]
Message-ID: <3a7852401c785a3a7f6958167c972c9e@mikro.quanstro.net> (raw)
In-Reply-To: <CAOw7k5gEPo0Qf_43PFqYu=Zn7CrQ8CjoTo5zRBChkeoOdQknRg@mail.gmail.com>
> I made the change you suggest in the PAE kernel but perhaps Erik missed it
> during his merge:
> if(mapsize > nelem(s->ssegmap)){
> mapsize *= 2;
> if(mapsize > SEGMAPSIZE)
> mapsize = SEGMAPSIZE;
> s->map = smalloc(mapsize*sizeof(Pte*));
> s->mapsize = mapsize;
> }
ok. good. that's what happened. perhaps some change needs
to be made to segattach to mirror this change.
- erik
next prev parent reply other threads:[~2014-06-03 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 1:14 Yoann Padioleau
2014-06-03 5:49 ` cinap_lenrek
2014-06-03 6:00 ` Anthony Martin
2014-06-03 15:47 ` erik quanstrom
2014-06-03 15:56 ` andrey mirtchovski
2014-06-03 16:04 ` erik quanstrom
2014-06-04 19:12 ` Anthony Martin
2014-06-03 16:08 ` Charles Forsyth
2014-06-03 17:08 ` erik quanstrom [this message]
2014-06-03 18:04 ` Charles Forsyth
2014-06-03 18:09 ` Charles Forsyth
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=3a7852401c785a3a7f6958167c972c9e@mikro.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).