From: "Andrew Fish" <afish@apple.com>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: rebecca@bsdio.com, sean.brogan@microsoft.com,
Bret Barkelew <bret.barkelew@microsoft.com>
Subject: Re: [edk2-devel] [EXTERNAL] [edk2-devel] Information about the VMs used to do EDK2 CI?
Date: Sat, 28 Mar 2020 14:41:57 -0700 [thread overview]
Message-ID: <E4F4B3DC-F71E-448A-82A8-8D23A86C1AB5@apple.com> (raw)
In-Reply-To: <f5c7afeb-b582-c757-572f-d8c833d51b8e@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
This works on my MacBook Pro
$ getconf _NPROCESSORS_ONLN
8
The macOS centric way is this:
$ sysctl -n hw.logicalcpu
8
Thanks,
Andrew FIsh
> On Mar 23, 2020, at 5:38 AM, Laszlo Ersek <lersek@redhat.com> wrote:
>
> On 03/22/20 00:03, Rebecca Cran wrote:
>> Thank you. I think we probably do want to detect the number of threads
>> available: I'll see if I can work on that.
>
> In a Linux environment, you can run "getconf _NPROCESSORS_ONLN".
>
> In fact that's how I build the native BaseTools on my laptop:
>
> $ . edksetup.sh
> $ nice make -C "$EDK_TOOLS_PATH" -j $(getconf _NPROCESSORS_ONLN)
>
> And from a cursory web search:
>
> https://stackoverflow.com/a/23569003 <https://stackoverflow.com/a/23569003>
>
> it is supposed to work on macOS too, and with a small tweak, on the BSDs
> as well.
>
> Thanks
> Laszlo
>
>
>
[-- Attachment #2: Type: text/html, Size: 14789 bytes --]
prev parent reply other threads:[~2020-03-28 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 1:33 Information about the VMs used to do EDK2 CI? Rebecca Cran
2020-03-21 1:46 ` [EXTERNAL] [edk2-devel] " Bret Barkelew
2020-03-21 3:15 ` Rebecca Cran
2020-03-21 16:41 ` [edk2-devel] " Sean
2020-03-21 23:03 ` Rebecca Cran
2020-03-23 12:38 ` Laszlo Ersek
2020-03-28 20:23 ` Sean
2020-03-28 21:41 ` Andrew Fish [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-list 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=E4F4B3DC-F71E-448A-82A8-8D23A86C1AB5@apple.com \
--to=devel@edk2.groups.io \
/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