public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: James Ewing <james.ewing@sveasoft.com>
To: raque@research.bell-labs.com
Cc: pthreads-win32@sources.redhat.com
Subject: Re: use pthread under winCE
Date: Sat, 18 Oct 2003 13:06:00 -0000	[thread overview]
Message-ID: <3F913A57.8000102@sveasoft.com> (raw)
In-Reply-To: <3F903F95.80205@lucent.com>

Hi Benoit,

I've attached my modifications to the ptw32_getprocessors.c file that 
fixes the GetProcessAffinityMask for WINCE. It just forces the processor 
count to one.

I looked in the pthread.h file and found that if you don't have _UWIN 
defined, pthreads own internal _errno will be used. Make sure _UWIN is 
*not* defined. See line 1143 in pthread.h.

It was many moons ago that I tweaked pthreads for WIN32 for WINCE and 
I've forgotten much of what needed to be done. If anyone wants a diff of 
my build against the current CVS version just let me know and I'll send 
it out. It might be a good idea to test it a bit and then merge it into 
the main CVS tree. I use the same source for both WIN32 and WINCE 
pthreads builds.

Best,

James


[ ptw32_getprocessors.c]
----------------------------------------------------------------------
/*
 * ptw32_getprocessors()
 *
 * Get the number of CPUs available to the process.
 *
 * If the available number of CPUs is 1 then pthread_spin_lock()
 * will block rather than spin if the lock is already owned.
 *
 * pthread_spin_init() calls this routine when initialising
 * a spinlock. If the number of available processors changes
 * (after a call to SetProcessAffinityMask()) then only
 * newly initialised spinlocks will notice.
 */
int
ptw32_getprocessors(int * count)
{
  int result = 0;

#ifndef WINCE
  DWORD vProcessCPUs;
  DWORD vSystemCPUs;

  if (GetProcessAffinityMask(GetCurrentProcess(),
                 &vProcessCPUs,
                 &vSystemCPUs))
    {
      DWORD bit;
      int CPUs = 0;

      for (bit = 1; bit != 0; bit <<= 1)
    {
      if (vProcessCPUs & bit)
        {
          CPUs++;
        }
    }
      *count = CPUs;
    }
  else
    {
      result = EAGAIN;
    }
#else
  *count = 1;
#endif
  return(result);
// end of file -----------------------------------------------------------

  reply	other threads:[~2003-10-18 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16 21:43 Benoit Raque
2003-10-17  8:40 ` James Ewing
2003-10-17 19:14   ` Benoit Raque
2003-10-18 13:06     ` James Ewing [this message]
2003-10-20 15:40       ` Benoit Raque
2003-10-20 17:19         ` James Ewing

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=3F913A57.8000102@sveasoft.com \
    --to=james.ewing@sveasoft.com \
    --cc=pthreads-win32@sources.redhat.com \
    --cc=raque@research.bell-labs.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).