From: "Dugger's" <ddugger@qwest.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Pagesize is different between IA32 and IA64
Date: Wed, 14 Nov 2001 06:43:55 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805502@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805465@msgid-missing>
Never mind, I found the `calloc' code and I'm very depressed because it
does indeed assume that `brk' zeros out newly allocated memory which is
obviously going to create problems if `calloc' thinks the kernel has 4K
pages when it really has bigger ones.
Unfortunately, this means I'll have to make an IA32 specific `brk' call that
zero's out the last part of the last page currently allocated to a process.
Oh well, patch to follow later.
--
Don Dugger
n0ano@indstorage.com
----- Original Message -----
From: "Dugger's" <ddugger@qwest.net>
To: <davidm@hpl.hp.com>; <n0ano@indstorage.com>
Cc: "Hideki Yamamoto" <hideki@hpc.bs1.fc.nec.co.jp>;
<linux-ia64@linuxia64.org>
Sent: Tuesday, November 13, 2001 11:16 PM
Subject: Re: [Linux-ia64] Pagesize is different between IA32 and IA64
> I'm a little confused. From Hideki's test program the problem actually
> seems
> to be using `sbrk' to return memory and then allocating memory again. The
> second
> time the re-allocated memory is not zeroed, e.g.:
>
> p = sbrk(4096);
> q = sbrk(-4096);
> r = sbrk(4096);
>
> and the memory pointed to by `r' is not zeroed. I just got through
reading
> the
> man page for `brk' and `sbrk' and neither one specifies that newly
allocated
> memory is zeroed and therefore I interpret this issue as undefined
behavior.
> Any program that depends upon the contents of newly allocated memory is
> broken. In fact, if you compile the test program, `d.c', for IA64 and run
> it it
> fails. Also, if you compile the test program for IA32 and use 1K
allocation
> blocks
> the program fails on an IA32 machine also.
>
> Someone correct me if I'm wrong about this.
>
> PS: I know that `calloc' is defined to zero out the allocated memory but
> from
> what I can tell it does this by explicitly calling `memset'. I'm trying
to
> verify this
> but I haven't found the `calloc' code in the `glibc' tree yet. (The
`glibc'
> tree always
> confuses me, if anyone can tell me exactly where to find the `calloc' code
> I'd
> appreciate it :-)
> --
> Don Dugger
> n0ano@indstorage.com
> ----- Original Message -----
> From: "David Mosberger" <davidm@hpl.hp.com>
> To: <n0ano@indstorage.com>
> Cc: "Hideki Yamamoto" <hideki@hpc.bs1.fc.nec.co.jp>;
> <linux-ia64@linuxia64.org>
> Sent: Monday, November 12, 2001 4:58 PM
> Subject: Re: [Linux-ia64] Pagesize is different between IA32 and IA64
>
>
> > But I think the page size problem with brk() is real and can be fixed
> > quite easily. If I understood correctly, the problem is that doing
> > something along the lines of:
> >
> > x = ALIGN_TO_4K(sbrk(8192));
> > memset(x, 0xff, 4096);
> > brk(x);
> > brk(x+4096);
> >
> > might preserve the contents of the page at X on under the ia32
> > subsystem of ia64 when in fact it should be cleared to zero.
> >
> > Would you be able/interested into looking into this?
> >
> > --david
> >
>
next prev parent reply other threads:[~2001-11-14 6:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 8:15 [Linux-ia64] Pagesize is different between IA32 and IA64 Hideki Yamamoto
2001-11-12 15:28 ` n0ano
2001-11-12 23:58 ` David Mosberger
2001-11-13 4:58 `
2001-11-13 15:15 ` n0ano
2001-11-14 6:16 ` Dugger's
2001-11-14 6:43 ` Dugger's [this message]
2001-11-14 6:53 ` Hideki Yamamoto
2001-11-14 7:00 ` Hideki Yamamoto
2001-11-15 15:33 ` n0ano
2001-11-16 6:17 ` miyoshi
2001-11-16 15:09 ` n0ano
2001-11-22 6:48 ` miyoshi
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=marc-linux-ia64-105590698805502@msgid-missing \
--to=ddugger@qwest.net \
--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.