From: Andi Kleen <andi@firstfloor.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andi Kleen <andi@firstfloor.org>,
mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: x86-64: memset()/memcpy() not fully standards compliant
Date: Fri, 6 Jan 2012 12:08:45 +0100 [thread overview]
Message-ID: <20120106110845.GW11715@one.firstfloor.org> (raw)
In-Reply-To: <4F06DFEF020000780006AC84@nat28.tlf.novell.com>
> It's not the traditional bootmem implementation anymore, but
> alloc_bootmem() et al still exist, and still clear the allocated memory
> (in __alloc_memory_core_early()). So there is a code path that can
> validly be used (and it is this code path that is presenting one of the
> problems with the non-pv-ops Xen kernels, as they're using flatmem
> rather than sparsemem since their physical address space is always
> fully continuous).
Yes but there should be no callers that do alloc_bootmem(4G)
The biggest ones afak are the 1GB pages I added some time ago.
How is it a problem in the non pv Xen kernels?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2012-01-06 11:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 14:04 x86-64: memset()/memcpy() not fully standards compliant Jan Beulich
2012-01-05 15:27 ` hpanvin@gmail.com
2012-01-05 18:28 ` Andi Kleen
2012-01-05 23:22 ` H. Peter Anvin
2012-01-06 1:47 ` Andi Kleen
2012-01-06 2:03 ` H. Peter Anvin
2012-01-06 7:22 ` Jan Beulich
2012-01-06 9:49 ` Andi Kleen
2012-01-06 10:22 ` Jan Beulich
2012-01-06 10:37 ` Andi Kleen
2012-01-06 10:50 ` Jan Beulich
2012-01-06 11:08 ` Andi Kleen [this message]
2012-01-06 12:25 ` Jan Beulich
2012-01-06 19:44 ` Andi Kleen
2012-01-06 23:12 ` H. Peter Anvin
2012-01-06 11:08 ` Ingo Molnar
2012-01-06 20:40 ` Valdis.Kletnieks
2012-01-09 8:29 ` Jan Beulich
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=20120106110845.GW11715@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.