From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: tst-getcpu failure
Date: Sun, 13 May 2007 18:19:00 -0000 [thread overview]
Message-ID: <464756B6.3090309@redhat.com> (raw)
In-Reply-To: <20070513061910.GA8371@gromit.moeb>
Andreas Jaeger wrote:
> 2 sockets with 2 cores each.
Then this...
>>> getcpu results 14 not possible
... is very wrong and should be reported as a kernel bug.
>>> getcpu results 0 not possible
>>> getcpu results 0 not possible
>>> getcpu results 0 not possible
This is probably the rdtscp instruction which doesn't need/use the cache
and is not reset.
The problem can be ignored for now. I think the kernel should adjust
the information when it explicitly reschedules a thread.
--
⧠Ulrich Drepper ⧠Red Hat, Inc. ⧠444 Castro St ⧠Mountain View, CA â
prev parent reply other threads:[~2007-05-13 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 7:42 Andreas Jaeger
2007-05-12 16:22 ` Ulrich Drepper
2007-05-12 21:05 ` Andreas Jaeger
2007-05-12 21:09 ` Ulrich Drepper
2007-05-13 18:15 ` Andreas Jaeger
2007-05-13 18:19 ` Ulrich Drepper [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=464756B6.3090309@redhat.com \
--to=drepper@redhat.com \
--cc=aj@suse.de \
--cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).