From owner-freebsd-virtualization@FreeBSD.ORG Sun Mar 17 20:56:17 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C9FD4DAF for ; Sun, 17 Mar 2013 20:56:17 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6FE85219 for ; Sun, 17 Mar 2013 20:56:17 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 47C8111D78; Mon, 18 Mar 2013 06:56:10 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro.local (c-71-56-248-150.hsd1.co.comcast.net [71.56.248.150]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BKS67244 (AUTH peterg@ptree32.com.au); Mon, 18 Mar 2013 06:56:08 +1000 Message-ID: <51462DE5.70805@freebsd.org> Date: Sun, 17 Mar 2013 13:56:05 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: Alfred Perlstein Subject: Re: bhyve in -current 4/14/13 can no longer support FreeBSD stable install References: <514350E9.4020100@mu.org> <51439239.1030404@freebsd.org> <514396E9.9010908@mu.org> In-Reply-To: <514396E9.9010908@mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Sun, 17 Mar 2013 20:56:17 -0000 Hi Alfred, >> If you do this repeatedly, it may be possible to see some patterns >> e.g. counters incrementing, %RIP values being the same etc. >> > Hmm, I keep seem to be getting this: > /usr/home/alfred # bhyvectl --get-all --cpu=0 --vm=freebsd-stable > lowmem 0x0000000000000000/536870912 > highmem 0x0000000100000000/0 > errno = 16 > /usr/home/alfred # bhyvectl --get-all --cpu=1 --vm=freebsd-stable > lowmem 0x0000000000000000/536870912 > highmem 0x0000000100000000/0 > errno = 16 Yeh, this is a problem :( Currently, the stats gathering does a trylock on the VM to avoid having the VM be perturbed by the bhyvectl process. We probably need to put something in there so it can eventually get the lock, and hence the stats, when the VM is busy rather than forcing the user to retry. The work around is to send a SIGSTOP to the bhyve process and then run the bhyvectl. A SIGSTART will then set the VM going again. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Mon Mar 18 11:06:54 2013 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 37FA9CE6 for ; Mon, 18 Mar 2013 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 82591AC7 for ; Mon, 18 Mar 2013 11:06:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2IB6pGh002337 for ; Mon, 18 Mar 2013 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2IB6pUq002335 for freebsd-virtualization@FreeBSD.org; Mon, 18 Mar 2013 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Mar 2013 11:06:51 GMT Message-Id: <201303181106.r2IB6pUq002335@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-virtualization@FreeBSD.org Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 18 Mar 2013 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/170096 virtualization[vimage] Dynamically-attached network interface will c o kern/169991 virtualization[run] [vimage] panic after device plugged in o kern/165252 virtualization[vimage] [pf] [panic] kernel panics with VIMAGE and PF o kern/161094 virtualization[vimage] [pf] [panic] kernel panic with pf + VIMAGE wh o kern/160541 virtualization[vimage][pf][patch] panic: userret: Returning on td 0x o kern/160496 virtualization[vimage] [pf] [patch] kernel panic with pf + VIMAGE o kern/148155 virtualization[vimage] [pf] Kernel panic with PF/IPFilter + VIMAGE k a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail a kern/141696 virtualization[rum] [vimage] [panic] rum(4)+ vimage = kernel panic 10 problems total. From owner-freebsd-virtualization@FreeBSD.ORG Mon Mar 18 12:36:04 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7F9D1C2E; Mon, 18 Mar 2013 12:36:04 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id ADCAF82E; Mon, 18 Mar 2013 12:36:03 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,865,1355097600"; d="scan'208";a="2605163" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Mar 2013 12:35:57 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 18 Mar 2013 12:35:56 +0000 Message-ID: <51470A2B.5040609@citrix.com> Date: Mon, 18 Mar 2013 13:35:55 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: "freebsd-xen@freebsd.org" Subject: Difference in event channel implementation for Xen PV vs HVM guests Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: dfr@FreeBSD.org, gibbs@FreeBSD.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 18 Mar 2013 12:36:04 -0000 Hello, While working on improving XENHVM (I've been looking at adding PV timers), I've realized that the event channel implementation in PV vs HVM mode differs greatly. Xen PV port uses sys/xen/evtchn/evtchn.c while Xen HVM uses sys/dev/xenpci/evtchn.c, and the Xen HVM implementation is greatly reduced (only contains the necessary functions to operate backends/frontends). To implement PV timers I need to expand the event channel interface for XENHVM, and I was wondering why FreeBSD choose to have two different implementations, the main difference between PV and HVM is the event callback, but I guess this can be abstracted between the two different implementations, and then everything else could be reused. Am I missing something obvious? Is there any known technical problem in modifying XENHVM to use the full event channel implementation present in sys/xen/evtchn/evtchn.c that prevented XENHVM from using it in the first place? (Sorry if I've Cc'ed someone not related) Thanks, Roger. From owner-freebsd-virtualization@FreeBSD.ORG Mon Mar 18 13:08:53 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 22EA558D; Mon, 18 Mar 2013 13:08:53 +0000 (UTC) (envelope-from gibbs@freebsd.org) Received: from aslan.scsiguy.com (www.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id B69AD9A9; Mon, 18 Mar 2013 13:08:52 +0000 (UTC) Received: from [192.168.0.99] (macbook.scsiguy.com [192.168.0.99]) (authenticated bits=0) by aslan.scsiguy.com (8.14.5/8.14.5) with ESMTP id r2ID8lVa076504 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 18 Mar 2013 07:08:48 -0600 (MDT) (envelope-from gibbs@freebsd.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Difference in event channel implementation for Xen PV vs HVM guests From: "Justin T. Gibbs" In-Reply-To: <51470A2B.5040609@citrix.com> Date: Mon, 18 Mar 2013 07:08:49 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <9AE68E59-739C-499C-9991-0C84D4584981@freebsd.org> References: <51470A2B.5040609@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1503) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (aslan.scsiguy.com [192.168.0.4]); Mon, 18 Mar 2013 07:08:49 -0600 (MDT) Cc: "freebsd-xen@freebsd.org" , dfr@freebsd.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 18 Mar 2013 13:08:53 -0000 On Mar 18, 2013, at 6:35 AM, Roger Pau Monn=E9 = wrote: > Hello, >=20 > While working on improving XENHVM (I've been looking at adding PV > timers), I've realized that the event channel implementation in PV vs > HVM mode differs greatly. Xen PV port uses sys/xen/evtchn/evtchn.c = while > Xen HVM uses sys/dev/xenpci/evtchn.c, and the Xen HVM implementation = is > greatly reduced (only contains the necessary functions to operate > backends/frontends). >=20 > To implement PV timers I need to expand the event channel interface = for > XENHVM, and I was wondering why FreeBSD choose to have two different > implementations, the main difference between PV and HVM is the event > callback, but I guess this can be abstracted between the two different > implementations, and then everything else could be reused. Am I = missing > something obvious? >=20 > Is there any known technical problem in modifying XENHVM to use the = full > event channel implementation present in sys/xen/evtchn/evtchn.c that > prevented XENHVM from using it in the first place? >=20 > (Sorry if I've Cc'ed someone not related) >=20 > Thanks, Roger. > _______________________________________________ > 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" Hi Roger, I know of no reasons why XENHVM cannot use the full event channel interface. In fact, Spectra Logic implemented PV timers and a general cleanup of the HVM event channel interface. I haven't merged it back yet because I know the changes break PV and I haven't found time to clean up the PV code, merge the HVM and PV event channel systems, and move IPI/MSI delivery to event channels. I've uploaded Spectra's changes here: http://people.freebsd.org/~gibbs/xen_ev/ The diffs file provides the history of the original checkins to our Perforce repository. The tar file includes all the files that have been modified and reflects our efforts to keep our code base in sync with stable/9. Apart from the PV issues outlined above, I would expect the code provided to just drop right in to stable/9. Unfortunately, Xen support is not a current priority for Spectra so I don't have a lot of day job time to focus on getting this code back into FreeBSD. However, if this code looks like it would suite your needs, and you have resources for testing i386/PV, I'd be happy to collaborate with you and will make the time to help get this committed. -- Justin From owner-freebsd-virtualization@FreeBSD.ORG Mon Mar 18 23:49:10 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7867CB5E for ; Mon, 18 Mar 2013 23:49:10 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-vc0-f180.google.com (mail-vc0-f180.google.com [209.85.220.180]) by mx1.freebsd.org (Postfix) with ESMTP id 3DBD3616 for ; Mon, 18 Mar 2013 23:49:09 +0000 (UTC) Received: by mail-vc0-f180.google.com with SMTP id m17so3469135vca.11 for ; Mon, 18 Mar 2013 16:49:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=rkdwPJpKENO40Mr93eQj0+2+dmlCuDrkiCJ4kjzm/Ic=; b=cRImu64pmZE0X7uD+Pqn6IxHHR98C4hXYLQlhEVddjT9UW2xI9C9qrcttTDI++HSCI gzLf8Rurv9DtnLyLKvZrzZmic3FLd5h5LoIm26N95o2zSZ9ZXytWmVlYi20dnPyOb6hi FMp3ngRuw346/AuuZK68mM+OR+aQrG1NEm6i3UyZT/A0sitBNHvHYdYffF4oj4qa5m/M tBS5CBqmFzRm2OaOpRYUOi7L3MoOFidSwbE1akJJ6lZYuXwOYt+3Cnb62a65eyMECdFP E9exkmWsxCDnxBH1ANFN1X5zewYszZZLOq+yPWC9GZhVYWC4TxVjAE1M+SdnD2pBMg3p 380Q== MIME-Version: 1.0 X-Received: by 10.52.100.5 with SMTP id eu5mr19309817vdb.66.1363650549300; Mon, 18 Mar 2013 16:49:09 -0700 (PDT) Received: by 10.220.153.203 with HTTP; Mon, 18 Mar 2013 16:49:09 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 Mar 2013 16:49:09 -0700 Message-ID: Subject: Re: bhyve: simplify memory assignment to VMs From: Neel Natu To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 18 Mar 2013 23:49:10 -0000 Hi, On Mon, Mar 11, 2013 at 11:08 AM, Neel Natu wrote: > Hi, > > I am going to commit a change soon that simplifies how memory is > assigned to a VM from a command line perspective. > > At the moment if you want to create a VM with say 8GB of memory you > need to express this as "-m 2048 -M 6144" or "-m 1024 -M 7168" or some > split that adds up to 8192MB. This is very flexible but is also very > confusing to most users who don't know or care about the location of > the PCI hole. > > I am going to change this so that the memory size is specified > entirely with the "-m " option and the "-M" option will > disappear altogether. > > Of course, this means that scripts using "-M" will break and hence > this heads up. > > I did consider making this a backward compatible change but given the > stage of development of bhyve it seemed early to start accumulating > compatibility crud. > Committed as r248477: http://svnweb.freebsd.org/base?view=revision&revision=248477 Please update your vmrun.sh scripts from /usr/share/examples/bhyve/vmrun.sh best Neel > best > Neel From owner-freebsd-virtualization@FreeBSD.ORG Tue Mar 19 17:23:36 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 88EED80F; Tue, 19 Mar 2013 17:23:36 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 852467E8; Tue, 19 Mar 2013 17:23:34 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,872,1355097600"; d="scan'208";a="2664769" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2013 17:23:27 +0000 Received: from [192.168.1.30] (10.30.249.104) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Tue, 19 Mar 2013 17:23:27 +0000 Message-ID: <51489F0D.7070105@citrix.com> Date: Tue, 19 Mar 2013 18:23:25 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: "Justin T. Gibbs" Subject: Re: Difference in event channel implementation for Xen PV vs HVM guests References: <51470A2B.5040609@citrix.com> <9AE68E59-739C-499C-9991-0C84D4584981@freebsd.org> In-Reply-To: <9AE68E59-739C-499C-9991-0C84D4584981@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Cc: "freebsd-xen@freebsd.org" , "dfr@freebsd.org" , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 19 Mar 2013 17:23:36 -0000 On 18/03/13 14:08, Justin T. Gibbs wrote: > On Mar 18, 2013, at 6:35 AM, Roger Pau Monné wrote: > >> Hello, >> >> While working on improving XENHVM (I've been looking at adding PV >> timers), I've realized that the event channel implementation in PV vs >> HVM mode differs greatly. Xen PV port uses sys/xen/evtchn/evtchn.c while >> Xen HVM uses sys/dev/xenpci/evtchn.c, and the Xen HVM implementation is >> greatly reduced (only contains the necessary functions to operate >> backends/frontends). >> >> To implement PV timers I need to expand the event channel interface for >> XENHVM, and I was wondering why FreeBSD choose to have two different >> implementations, the main difference between PV and HVM is the event >> callback, but I guess this can be abstracted between the two different >> implementations, and then everything else could be reused. Am I missing >> something obvious? >> >> Is there any known technical problem in modifying XENHVM to use the full >> event channel implementation present in sys/xen/evtchn/evtchn.c that >> prevented XENHVM from using it in the first place? >> >> (Sorry if I've Cc'ed someone not related) >> >> Thanks, Roger. >> _______________________________________________ >> 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" > > Hi Roger, Hello Justin, > > I know of no reasons why XENHVM cannot use the full event channel > interface. In fact, Spectra Logic implemented PV timers and a > general cleanup of the HVM event channel interface. I haven't merged > it back yet because I know the changes break PV and I haven't found > time to clean up the PV code, merge the HVM and PV event channel > systems, and move IPI/MSI delivery to event channels. That sounds great, then FreeBSD will have a fully working PVHVM port. > I've uploaded Spectra's changes here: > > http://people.freebsd.org/~gibbs/xen_ev/ > > The diffs file provides the history of the original checkins to our > Perforce repository. The tar file includes all the files that have > been modified and reflects our efforts to keep our code base in > sync with stable/9. Apart from the PV issues outlined above, I > would expect the code provided to just drop right in to stable/9. Wow, this is a lot of work to keep in a closet, I will start by rebasing those on top of HEAD, and probably try to split them into smaller commits that make logical sense. > > Unfortunately, Xen support is not a current priority for Spectra > so I don't have a lot of day job time to focus on getting this code back > into FreeBSD. However, if this code looks like it would suite > your needs, and you have resources for testing i386/PV, I'd be happy > to collaborate with you and will make the time to help get this > committed. Definitely, you guys did already a lot of work, and it will a shame to lose it, right now I got my plate quite full, but I expect to get on with this in a couple of weeks. Thanks, Roger. From owner-freebsd-virtualization@FreeBSD.ORG Thu Mar 21 12:43:41 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5F3D4A55; Thu, 21 Mar 2013 12:43:41 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id AF578365; Thu, 21 Mar 2013 12:43:40 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,884,1355097600"; d="scan'208";a="2759109" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Mar 2013 12:43:33 +0000 Received: from [192.168.1.30] (10.30.249.104) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Thu, 21 Mar 2013 12:43:32 +0000 Message-ID: <514B0073.4070406@citrix.com> Date: Thu, 21 Mar 2013 13:43:31 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: "Justin T. Gibbs" Subject: Re: Difference in event channel implementation for Xen PV vs HVM guests References: <51470A2B.5040609@citrix.com> <9AE68E59-739C-499C-9991-0C84D4584981@freebsd.org> In-Reply-To: <9AE68E59-739C-499C-9991-0C84D4584981@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 21 Mar 2013 12:43:41 -0000 On 18/03/13 14:08, Justin T. Gibbs wrote: > Hi Roger, > > I know of no reasons why XENHVM cannot use the full event channel > interface. In fact, Spectra Logic implemented PV timers and a > general cleanup of the HVM event channel interface. I haven't merged > it back yet because I know the changes break PV and I haven't found > time to clean up the PV code, merge the HVM and PV event channel > systems, and move IPI/MSI delivery to event channels. > > I've uploaded Spectra's changes here: > > http://people.freebsd.org/~gibbs/xen_ev/ Hi Justin, There's at least one file which seems to be missing: sys/x86/xen/hvm.c Could you check if you have that file around? Thanks, Roger. From owner-freebsd-virtualization@FreeBSD.ORG Thu Mar 21 12:50:36 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 50D6EB93; Thu, 21 Mar 2013 12:50:36 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id A0B493EA; Thu, 21 Mar 2013 12:50:35 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,884,1355097600"; d="scan'208";a="2759555" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Mar 2013 12:50:34 +0000 Received: from [192.168.1.30] (10.30.249.104) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Thu, 21 Mar 2013 12:50:34 +0000 Message-ID: <514B0219.3040704@citrix.com> Date: Thu, 21 Mar 2013 13:50:33 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: "Justin T. Gibbs" Subject: Re: Difference in event channel implementation for Xen PV vs HVM guests References: <51470A2B.5040609@citrix.com> <9AE68E59-739C-499C-9991-0C84D4584981@freebsd.org> <514B0073.4070406@citrix.com> In-Reply-To: <514B0073.4070406@citrix.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Cc: "freebsd-xen@freebsd.org" , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 21 Mar 2013 12:50:36 -0000 On 21/03/13 13:43, Roger Pau Monné wrote: > On 18/03/13 14:08, Justin T. Gibbs wrote: > > Hi Roger, >> >> I know of no reasons why XENHVM cannot use the full event channel >> interface. In fact, Spectra Logic implemented PV timers and a >> general cleanup of the HVM event channel interface. I haven't merged >> it back yet because I know the changes break PV and I haven't found >> time to clean up the PV code, merge the HVM and PV event channel >> systems, and move IPI/MSI delivery to event channels. >> >> I've uploaded Spectra's changes here: >> >> http://people.freebsd.org/~gibbs/xen_ev/ > > Hi Justin, > > There's at least one file which seems to be missing: Ops, there at least two files missing: sys/x86/xen/hvm.c sys/xen/evtchn/evtchnvar.h From owner-freebsd-virtualization@FreeBSD.ORG Thu Mar 21 13:03:56 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 805A68D2; Thu, 21 Mar 2013 13:03:56 +0000 (UTC) (envelope-from gibbs@freebsd.org) Received: from aslan.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id 582056E4; Thu, 21 Mar 2013 13:03:56 +0000 (UTC) Received: from [192.168.0.99] (macbook.scsiguy.com [192.168.0.99]) (authenticated bits=0) by aslan.scsiguy.com (8.14.5/8.14.5) with ESMTP id r2LD3rlU004617 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 21 Mar 2013 07:03:53 -0600 (MDT) (envelope-from gibbs@freebsd.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Difference in event channel implementation for Xen PV vs HVM guests From: "Justin T. Gibbs" In-Reply-To: <514B0219.3040704@citrix.com> Date: Thu, 21 Mar 2013 07:03:55 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <594AC468-E971-4482-9CF6-27B93D35A267@freebsd.org> References: <51470A2B.5040609@citrix.com> <9AE68E59-739C-499C-9991-0C84D4584981@freebsd.org> <514B0073.4070406@citrix.com> <514B0219.3040704@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1503) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (aslan.scsiguy.com [192.168.0.4]); Thu, 21 Mar 2013 07:03:53 -0600 (MDT) Cc: "freebsd-xen@freebsd.org" , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 21 Mar 2013 13:03:56 -0000 On Mar 21, 2013, at 6:50 AM, Roger Pau Monn=E9 = wrote: > On 21/03/13 13:43, Roger Pau Monn=E9 wrote: >> On 18/03/13 14:08, Justin T. Gibbs wrote: >>> Hi Roger, >>>=20 >>> I know of no reasons why XENHVM cannot use the full event channel >>> interface. In fact, Spectra Logic implemented PV timers and a >>> general cleanup of the HVM event channel interface. I haven't = merged >>> it back yet because I know the changes break PV and I haven't found >>> time to clean up the PV code, merge the HVM and PV event channel >>> systems, and move IPI/MSI delivery to event channels. >>>=20 >>> I've uploaded Spectra's changes here: >>>=20 >>> http://people.freebsd.org/~gibbs/xen_ev/ >>=20 >> Hi Justin, >>=20 >> There's at least one file which seems to be missing: >=20 > Ops, there at least two files missing: >=20 > sys/x86/xen/hvm.c > sys/xen/evtchn/evtchnvar.h I've regenerated the archive with those two files added. -- Justin=