From owner-freebsd-virtualization@FreeBSD.ORG Fri Sep 19 20:52:30 2008 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC3A61065671; Fri, 19 Sep 2008 20:52:30 +0000 (UTC) (envelope-from zec@freebsd.org) Received: from xaqua.tel.fer.hr (xaqua.tel.fer.hr [161.53.19.25]) by mx1.freebsd.org (Postfix) with ESMTP id A9E768FC08; Fri, 19 Sep 2008 20:52:30 +0000 (UTC) (envelope-from zec@freebsd.org) Received: by xaqua.tel.fer.hr (Postfix, from userid 20006) id 942409B648; Fri, 19 Sep 2008 22:52:29 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on xaqua.tel.fer.hr X-Spam-Level: X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [192.168.200.110] (zec2.tel.fer.hr [161.53.19.79]) by xaqua.tel.fer.hr (Postfix) with ESMTP id B2E6D9B644; Fri, 19 Sep 2008 22:52:28 +0200 (CEST) From: Marko Zec To: freebsd-virtualization@freebsd.org Date: Fri, 19 Sep 2008 22:52:22 +0200 User-Agent: KMail/1.9.7 References: <200809191743.m8JHhZj8009388@repoman.freebsd.org> <200809192023.42904.zec@freebsd.org> <48D3FF54.2010802@elischer.org> In-Reply-To: <48D3FF54.2010802@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809192252.22640.zec@freebsd.org> Cc: Perforce Change Reviews , Julian Elischer Subject: Re: vimage and curvnet. X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Sep 2008 20:52:31 -0000 On Friday 19 September 2008 21:36:52 Julian Elischer wrote: .... > sure, well, if a running thread has curvnet in the pcpu field > and it is put back in the the thread struct on deschedule. > then what in td_vnet while the thread is running is not really > important. Yes this makes sense, and should be worth experimenting with. It's only that I feel reluctant to start touching anything in our scheduler(s) until all the other big changes settle in a bit first. Marko