From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jan Beulich <JBeulich@suse.com>,
mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: x86-64: memset()/memcpy() not fully standards compliant
Date: Fri, 06 Jan 2012 15:12:29 -0800 [thread overview]
Message-ID: <4F077FDD.8080201@zytor.com> (raw)
In-Reply-To: <20120106194400.GX11715@one.firstfloor.org>
On 01/06/2012 11:44 AM, Andi Kleen wrote:
>> enough beyond 292G. At some later point ->node_page_cgroup[]
>> also exceeds 4G. Finally, the phys-to-machine mapping (which gets
>> resized during boot) exceeds 4G when crossing the 2T boundary.
>
> Ok it's moot then because the old systems with problem didn't have
> that much memory. So you could do without an errata workaround
> and just extend the moves at the minor cost of a few prefixes
> (I think that is what you did in your patch)
>
That seems like the way to go unless we can identify a real problem.
-hpa
next prev parent reply other threads:[~2012-01-06 23:13 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
2012-01-06 12:25 ` Jan Beulich
2012-01-06 19:44 ` Andi Kleen
2012-01-06 23:12 ` H. Peter Anvin [this message]
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=4F077FDD.8080201@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=andi@firstfloor.org \
--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.