From owner-freebsd-virtualization@FreeBSD.ORG  Sat Jun 13 18:00:20 2015
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 81673A4E
 for <freebsd-virtualization@hub.freebsd.org>;
 Sat, 13 Jun 2015 18:00:20 +0000 (UTC)
 (envelope-from neelnatu@gmail.com)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com
 [IPv6:2a00:1450:400c:c05::235])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1BECBA59
 for <freebsd-virtualization@freebsd.org>; Sat, 13 Jun 2015 18:00:20 +0000 (UTC)
 (envelope-from neelnatu@gmail.com)
Received: by wibdq8 with SMTP id dq8so41454098wib.1
 for <freebsd-virtualization@freebsd.org>; Sat, 13 Jun 2015 11:00:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=YHWUhI5/koumKo/ImWAzzQD8RGihpJtZKF+ExalK9hg=;
 b=w7Qm74CQWXrYlW+ZTo8M1VEENmCmvChkamqtBILUdx+/afFuEkoAraFoD643IkKr6T
 eoETQ/gfjqJOKeBSbGw7+4hNh61v86KTxkqeCnKfuRQRtGIBmejrcj83BJY/MGpRKb0+
 2UsVP0y1jcX27R0qRimKZu5krhknQXIbER1nTSnHA6YoTyoYyu0fh2uLdTXMsZtviI71
 i7tp4h05mOfA36/jGRWKiiq+gw0Qu0N7XqnCsongB8N2gtXIkrtkqDnmM/kRX96HBza5
 rAgvHxYFbd0HYzvWKGDNwFt1TCSNbX7muvPjWqWU9TWwycpOOx6sRG9KF7Iu5/1QKwmf
 fBRA==
MIME-Version: 1.0
X-Received: by 10.194.2.137 with SMTP id 9mr2268435wju.75.1434218418592; Sat,
 13 Jun 2015 11:00:18 -0700 (PDT)
Received: by 10.27.52.18 with HTTP; Sat, 13 Jun 2015 11:00:18 -0700 (PDT)
In-Reply-To: <CAO3d8=b1dZU+fEi-r0P=WRMZ=rOF0D7WbGepsZ4Oe5q3eUrrLg@mail.gmail.com>
References: <CAO3d8=b1dZU+fEi-r0P=WRMZ=rOF0D7WbGepsZ4Oe5q3eUrrLg@mail.gmail.com>
Date: Sat, 13 Jun 2015 11:00:18 -0700
Message-ID: <CAFgRE9FxHWB9bFHNxj+v2fW79XoWDbWZ_4i456OCED7YGn9w7A@mail.gmail.com>
Subject: Re: How to bind a thread to a CPU?
From: Neel Natu <neelnatu@gmail.com>
To: Stefan Andritoiu <stefan.andritoiu@gmail.com>
Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jun 2015 18:00:20 -0000

Hi Stefan,

On Sat, Jun 13, 2015 at 3:33 AM, Stefan Andritoiu
<stefan.andritoiu@gmail.com> wrote:
> Hi,
>
> How can I pin a thread to run only on a specific CPU?
> Is it enough just to set the "struct cpuset *td_cpuset" of the thread?
>

sched_bind() is the proper way to do this.

best
Neel

> Thank you,
> Stefan
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org"