From: Rusty Russell <rusty@rustcorp.com.au>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Percpu data in a vsyscall page
Date: Thu, 03 Nov 2005 12:51:11 +1100 [thread overview]
Message-ID: <1130982671.8734.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20051102105405.GA5320@ucw.cz>
On Wed, 2005-11-02 at 11:54 +0100, Vojtech Pavlik wrote:
> Hi!
>
> I'm working on a RDTSCP support on x86-64, and for that, I'll need
> per-cpu time offset table in a vsyscall page. I saw the percpu.h header,
> and thought - "Hey, I could use that!", but I think I really can't.
>
> The data need to be in a vsyscall page, which is mapped to userspace via
> linker magic, and the percpu stuff uses a different mapping.
Yes. The percpu stuff uses a single add to find the local value of a
variable. This per-cpu offset can be kept in a register (I think
Sparc64 already does this) making it v. fast.
You're going to have to stick with an array I think.
Sorry,
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
prev parent reply other threads:[~2005-11-03 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 10:54 Percpu data in a vsyscall page Vojtech Pavlik
2005-11-03 1:51 ` Rusty Russell [this message]
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=1130982671.8734.15.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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