mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Jan Beulich <JBeulich@suse.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
	Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org
Subject: Re: x86-64: memset()/memcpy() not fully standards compliant
Date: Fri, 06 Jan 2012 15:40:19 -0500	[thread overview]
Message-ID: <73464.1325882419@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 05 Jan 2012 14:04:30 GMT." <4F05BBFE020000780006A983@nat28.tlf.novell.com>

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

On Thu, 05 Jan 2012 14:04:30 GMT, Jan Beulich said:
> Forever these two functions have been limited to deal with at most 4G
> at a time. While I cannot point out an in-tree user that would require
> larger sizes, it is now the second time that within our Xen kernel we got
> bitten by that limitation.

Wow.  Second time?  What the heck is the Xen kernel *doing* that it's
trying to do over 4G in a single memset/memcpy?

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2012-01-06 20:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 14:04 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
2012-01-06 11:08           ` Ingo Molnar
2012-01-06 20:40 ` Valdis.Kletnieks [this message]
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=73464.1325882419@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=JBeulich@suse.com \
    --cc=andi@firstfloor.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®