From owner-freebsd-virtualization@FreeBSD.ORG Fri Jun 12 07:51:21 2015 Return-Path: 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 AC7D5813 for ; Fri, 12 Jun 2015 07:51:21 +0000 (UTC) (envelope-from stefan.andritoiu@gmail.com) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (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 763201B83 for ; Fri, 12 Jun 2015 07:51:21 +0000 (UTC) (envelope-from stefan.andritoiu@gmail.com) Received: by obcej4 with SMTP id ej4so18520711obc.0 for ; Fri, 12 Jun 2015 00:51:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UFnGnixUEBqVQryd3v5YCLimJw4K9CFbJmau5WSH2wA=; b=ZRA6UXVHVlLQO659CEk7yew9xdnqcpzc7EwAAogK+GMWRnkiC0yPU9Qyoghwd3E9dh 4Mr/nZnYvluksy16x6rhP0/R50A0EDgFWj6si6aJR5Evd6g5QNodlEYxkqx1VgLZsKkE wCz8VIUSEe/ZDnjseIBQiF7hLKoWaxmmyWYZZxKE63SJnuB5V8+5SMRdiAOcL4js1OAf PRNsTsNv4Fmf4r3ZAOWaQ7xjzQveA9rqXKk5y/dxQP3z8wBuThAwS1e+dBi0jdj2uMaB 7RFKqOuar64S/FGacjPNBtzhZCzy9wq9bGTjsnVstBIZJ3XzYRlTeLUTe/7aAuONQO8s HXXA== MIME-Version: 1.0 X-Received: by 10.202.106.147 with SMTP id f141mr1159911oic.65.1434095480806; Fri, 12 Jun 2015 00:51:20 -0700 (PDT) Received: by 10.60.82.168 with HTTP; Fri, 12 Jun 2015 00:51:20 -0700 (PDT) Date: Fri, 12 Jun 2015 10:51:20 +0300 Message-ID: Subject: Are the sched_choose() or tdq_choose() functions called after returning from an interrupt? From: Stefan Andritoiu To: 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2015 07:51:21 -0000 Hello, When returning from an interrupt, does it switch directly the thread that was interrupted? Or is the scheduler called to choose a thread to run (most probable the thread that was interrupted)? More specifically, are the sched_choose() or tdq_choose() functions called after returning from an IPI? Does an interrupt have it's own thread, or does it run in the context of the interrupted thread as in Linux? Thank you, Stefan