From: Andi Kleen <ak@suse.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH] x86: Add portable getcpu call
Date: Wed, 27 Sep 2006 14:04:09 +0200 [thread overview]
Message-ID: <200609271404.09621.ak@suse.de> (raw)
In-Reply-To: <20060927113739.GB6872@osiris.boeblingen.de.ibm.com>
>
> So this means that the contents of getcpu_cache will look completely
> different if a process runs in 32bit mode or 64bit mode. Even if you're
> saying "user programs should not..." this looks odd to me.
> Is this really on purpose and do you really think that no user space
> application will ever rely on the format of getcpu_cache?
The vsyscalls do, but if anything else does it deserves breaking.
In the user headers it will also be just a array blob.
I was considering to xor it with a random value to bring the point across
more strongly, but then didn't do it. Do you think I should?
-Andi
next prev parent reply other threads:[~2006-09-27 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609262300.k8QN06dD013707@hera.kernel.org>
2006-09-27 11:37 ` [PATCH] x86: Add portable getcpu call Heiko Carstens
2006-09-27 12:04 ` Andi Kleen [this message]
2006-09-27 12:39 ` Heiko Carstens
2006-09-27 12:43 ` Andi Kleen
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=200609271404.09621.ak@suse.de \
--to=ak@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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