public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: tst-getcpu failure
Date: Sat, 12 May 2007 21:05:00 -0000	[thread overview]
Message-ID: <m3mz09bvnq.fsf@gromit.moeb> (raw)
In-Reply-To: <4645E9BC.2050701@redhat.com> (Ulrich Drepper's message of "Sat\, 12 May 2007 09\:22\:20 -0700")

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

Ulrich Drepper <drepper@redhat.com> writes:

> Andreas Jaeger wrote:
>> tst-getcpu fails for me on x86-64:
>> getcpu results 14 not possible
>
> AMD or Intel machine?

AMD64.

My  4 CPU AMD64 machine gives:
getcpu results 14 not possible
getcpu results 0 not possible
getcpu results 0 not possible
getcpu results 0 not possible

both running 2.6.18.

>
>
>
>> Btw. the following patch fixes a warning about a missing getpid
>> prototype.  Ok to commit?
>
> Yes.

Thanks, will do now,
Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
   Maxfeldstr. 5, 90409 Nürnberg, Germany
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

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

  reply	other threads:[~2007-05-12 21:05 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 [this message]
2007-05-12 21:09     ` Ulrich Drepper
2007-05-13 18:15       ` Andreas Jaeger
2007-05-13 18:19         ` Ulrich Drepper

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=m3mz09bvnq.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=drepper@redhat.com \
    --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).