From owner-freebsd-xen@FreeBSD.ORG Sun Jan 19 00:56:42 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A8FB1F7B for ; Sun, 19 Jan 2014 00:56:42 +0000 (UTC) Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 36C6C1FBA for ; Sun, 19 Jan 2014 00:56:41 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id t60so5891709wes.9 for ; Sat, 18 Jan 2014 16:56:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XJjoxoO3SYygMco9oN3CxbQ5BwGyCRaGfizJqVbiHAU=; b=IiwqxunPUnKubXXjfm5k9/Fd0iWboSVfNrE+8slb2I+CW44uIZkVVA+4MlvvMuXs95 VHQ8JhnvDSOXMZpW1Km6XZjZbcSDQg1l1MepiJP9oV5SNQSPha44SYbb7HXuTkI5xcep 3HH/d+uLGoJGcNj0711x31nk8LCflzKD0RK2Ah75DAfZP2l9O35bP8XAmgLmwIVLbkZu nqSoNMr+E0q2dG/NN063bDC1LbyCp9rYThXMNrX8AgfHpRQzkwM+ASKA2OfR+ZiqK0pB /Ap0q9FnaCUt3dAnAuIIf2emP2+yhiPS4OtA/c7YGTvNtkuZsWaTF2uk0k377KyyxiEd tbmg== X-Gm-Message-State: ALoCoQkovRVpWcSm0IdGLBVhND3TRRDCrRAUGWjxa06PthJWbMp3lo2OGcVjLGA5TA9BE+77OZkE X-Received: by 10.180.107.136 with SMTP id hc8mr4302033wib.11.1390092550774; Sat, 18 Jan 2014 16:49:10 -0800 (PST) Received: from [192.168.0.2] (cpc8-cmbg15-2-0-cust169.5-4.cable.virginm.net. [86.30.140.170]) by mx.google.com with ESMTPSA id hy8sm14011759wjb.2.2014.01.18.16.49.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Jan 2014 16:49:09 -0800 (PST) Message-ID: <52DB2104.3070808@linaro.org> Date: Sun, 19 Jan 2014 00:49:08 +0000 From: Julien Grall User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Ian Campbell Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <1389950962.6697.33.camel@kazak.uk.xensource.com> In-Reply-To: <1389950962.6697.33.camel@kazak.uk.xensource.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, Nathan Whitehorn , gibbs@freebsd.org, Warner Losh X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 00:56:42 -0000 On 01/17/2014 09:29 AM, Ian Campbell wrote: > On Fri, 2014-01-17 at 00:36 +0000, Julien Grall wrote: >> IanC: I was reading the linux binding documentation >> (devicetree/booting-without-of.txt VII.2) and it seems that the >> explanation differs from the implementation, right? > > I vaguely recall someone saying that the Linux behaviour was a quirk of > some real PPC system which supplied a DTB which required this behaviour > which has leaked into the other platforms. It does also sound like a > useful extension to the spec which makes the dtb easier to write. I've read twice the ePAR and did some test. I was completely wrong, this file is valid with the ePAR (there is even an example like that at the end at the specification). And FreeBSD doesn't complain about this since Nathan's ofw/fdt rework. Sorry for the waste time. -- Julien Grall From owner-freebsd-xen@FreeBSD.ORG Sun Jan 19 01:30:55 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 00FF57D4; Sun, 19 Jan 2014 01:30:54 +0000 (UTC) Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BDBD511DD; Sun, 19 Jan 2014 01:30:54 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MZM00D00JNT7T00@smtpauth3.wiscmail.wisc.edu>; Sat, 18 Jan 2014 19:30:47 -0600 (CST) X-Spam-PmxInfo: Server=avs-3, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.19.11815, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (adsl-76-208-68-77.dsl.mdsnwi.sbcglobal.net [76.208.68.77]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MZM009AQK77M510@smtpauth3.wiscmail.wisc.edu>; Sat, 18 Jan 2014 19:30:46 -0600 (CST) Message-id: <52DB2AC3.5000206@freebsd.org> Date: Sat, 18 Jan 2014 19:30:43 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 To: Julien Grall , Warner Losh Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> In-reply-to: <52DB1138.6010804@linaro.org> X-Enigmail-Version: 1.6 Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 01:30:55 -0000 On 01/18/14 17:41, Julien Grall wrote: > > Hello Nathan, > > On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >> On 01/16/14 18:36, Julien Grall wrote: >>> >>> >>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>> As I understand, only the simple bus code (see simplebus_attach) is >>> translating the interrupts in the device on a resource. >>> So if you have a node directly attached to the root node with >>> interrupts and MMIO, the driver won't be able to retrieve and >>> translate the interrupts via bus_alloc_resources. > >> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. > > I have digged into the code to find the reason of my issue. FreeBSD is > receiving a VM fault when the driver (xen-dt) is trying to setup the IRQ. > > This is because the GIC is not yet initialized but FreeBSD asks to > unmask the IRQ (sys/arm/arm/gic.c:306). > > With this problem, all device nodes that are before the GIC in the > device tree can't have interrupts. For instance this simple device > will segfault on FreeBSD: > > / { > > mybus { > compatible = "simple-bus"; > > mynode { > interrupt-parent = &gic; > interrupts = <...>; > }; > > gic: gic@xxxx { > interrupt-controller; > } > }; > }; > > The node "mynode" will have to move after the GIC to be able to work > correctly. > Ah, that sounds like a bug in the interrupt handling code. The PPC code is designed to handle this problem by deferring interrupt setup, as well as a number of other latent issues, and I think would make a good match for ARM as well. I made an experimental branch to port it to MIPS (the code is almost entirely machine-independent) but am waiting for testing. A general solution to this problem has to involve deferred setup. -Nathan From owner-freebsd-xen@FreeBSD.ORG Sun Jan 19 02:44:57 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 15BF0256 for ; Sun, 19 Jan 2014 02:44:57 +0000 (UTC) Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CE66F1611 for ; Sun, 19 Jan 2014 02:44:56 +0000 (UTC) Received: by mail-ig0-f173.google.com with SMTP id c10so5057003igq.0 for ; Sat, 18 Jan 2014 18:44:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=miznZQsfRtjA5VuYPXfaIynv5+4GL60bP9kdQW9VNR0=; b=hzev5L/G0J2j2WtsDK7JWZHrgO4eDPgdbHLz26gV6lDBHTK1e96tRaKXti5BARxLXm yVq+0HEr5a2+crc8lYdOMe9ClELtwiMKgweQV026pDfHeFQD9FX/dADBHTCWlMtzFeiN tKEQy8p/Vlu5TnO2H5Ec3um0K3coPcZnyzF1YqsFRuWc/A/9w8PCYmGh9/WwCos/RAFp Um8vR2euiGDzcMTiXR13Dm0reCtXsR3/dL0qMK+K0PMxS74JaCB2OdZcxRzLWrORe46t BJNj+6IO1ZCngtJFApQxrv0NOlb7TXWC77O237Tm9rWiUYDpBAC2DwddcsQKxVvTIplK FQdg== X-Gm-Message-State: ALoCoQmVBFHT4/26VB9DVdSJMbCJedhP/8Q4Saz1y9Iy5aPRCSocmmI6fzhDIvV173yn+VK+Pzil X-Received: by 10.42.122.146 with SMTP id n18mr124691icr.41.1390099490219; Sat, 18 Jan 2014 18:44:50 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id gc2sm12532065igd.6.2014.01.18.18.44.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Jan 2014 18:44:49 -0800 (PST) Sender: Warner Losh Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <52DB1138.6010804@linaro.org> Date: Sat, 18 Jan 2014 19:44:09 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> To: Julien Grall X-Mailer: Apple Mail (2.1085) Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, Nathan Whitehorn , gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 02:44:57 -0000 On Jan 18, 2014, at 4:41 PM, Julien Grall wrote: >=20 > Hello Nathan, >=20 > On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >> On 01/16/14 18:36, Julien Grall wrote: >>>=20 >>>=20 >>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>> As I understand, only the simple bus code (see simplebus_attach) is >>> translating the interrupts in the device on a resource. >>> So if you have a node directly attached to the root node with >>> interrupts and MMIO, the driver won't be able to retrieve and >>> translate the interrupts via bus_alloc_resources. >=20 >> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. >=20 > I have digged into the code to find the reason of my issue. FreeBSD is = receiving a VM fault when the driver (xen-dt) is trying to setup the = IRQ. >=20 > This is because the GIC is not yet initialized but FreeBSD asks to = unmask the IRQ (sys/arm/arm/gic.c:306). >=20 > With this problem, all device nodes that are before the GIC in the = device tree can't have interrupts. For instance this simple device will = segfault on FreeBSD: >=20 > / { >=20 > mybus { > compatible =3D "simple-bus"; >=20 > mynode { > interrupt-parent =3D &gic; > interrupts =3D <...>; > }; >=20 > gic: gic@xxxx { > interrupt-controller; > } > }; > }; >=20 > The node "mynode" will have to move after the GIC to be able to work = correctly. This stems from a difference in enumeration between FreeBSD and Linux. = FreeBSD enumerates the devices in DTB order, while Linux does a partial = ordering based on dependencies. Warner= From owner-freebsd-xen@FreeBSD.ORG Sun Jan 19 03:01:29 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F05604FD; Sun, 19 Jan 2014 03:01:28 +0000 (UTC) Received: from smtpauth4.wiscmail.wisc.edu (wmauth4.doit.wisc.edu [144.92.197.145]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B8E2E1769; Sun, 19 Jan 2014 03:01:28 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth4.wiscmail.wisc.edu by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MZM00300OD1LZ00@smtpauth4.wiscmail.wisc.edu>; Sat, 18 Jan 2014 21:01:21 -0600 (CST) X-Spam-PmxInfo: Server=avs-4, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.19.25114, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (adsl-76-208-68-77.dsl.mdsnwi.sbcglobal.net [76.208.68.77]) by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MZM000JUOE5EZ10@smtpauth4.wiscmail.wisc.edu>; Sat, 18 Jan 2014 21:01:20 -0600 (CST) Message-id: <52DB3FFD.2070503@freebsd.org> Date: Sat, 18 Jan 2014 21:01:17 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 To: Warner Losh , Julien Grall Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> In-reply-to: <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> X-Enigmail-Version: 1.6 Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 03:01:29 -0000 On 01/18/14 20:44, Warner Losh wrote: > On Jan 18, 2014, at 4:41 PM, Julien Grall wrote: > >> Hello Nathan, >> >> On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >>> On 01/16/14 18:36, Julien Grall wrote: >>>> >>>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>>> As I understand, only the simple bus code (see simplebus_attach) is >>>> translating the interrupts in the device on a resource. >>>> So if you have a node directly attached to the root node with >>>> interrupts and MMIO, the driver won't be able to retrieve and >>>> translate the interrupts via bus_alloc_resources. >>> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. >> I have digged into the code to find the reason of my issue. FreeBSD is receiving a VM fault when the driver (xen-dt) is trying to setup the IRQ. >> >> This is because the GIC is not yet initialized but FreeBSD asks to unmask the IRQ (sys/arm/arm/gic.c:306). >> >> With this problem, all device nodes that are before the GIC in the device tree can't have interrupts. For instance this simple device will segfault on FreeBSD: >> >> / { >> >> mybus { >> compatible = "simple-bus"; >> >> mynode { >> interrupt-parent = &gic; >> interrupts = <...>; >> }; >> >> gic: gic@xxxx { >> interrupt-controller; >> } >> }; >> }; >> >> The node "mynode" will have to move after the GIC to be able to work correctly. > This stems from a difference in enumeration between FreeBSD and Linux. FreeBSD enumerates the devices in DTB order, while Linux does a partial ordering based on dependencies. > > Warner Enumerating in some other order doesn't necessarily help: since the interrupt and bus trees are independent, circular dependencies can happen. This is not a hypothetical: on most powermacs, the main interrupt controller is a functional unit on a PCI device -- a PCI device whose other units have interrupt lines that eventually connect back to itself. There is no way to fix that with ordering. So I think we still need to defer interrupt setup. It's not that bad -- PPC already does this to handle the powermac case. -Nathan From owner-freebsd-xen@FreeBSD.ORG Sun Jan 19 03:08:20 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5C60691 for ; Sun, 19 Jan 2014 03:08:20 +0000 (UTC) Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 97DBE17E3 for ; Sun, 19 Jan 2014 03:08:20 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id ar20so2319564iec.20 for ; Sat, 18 Jan 2014 19:08:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=mbUcM4/PJrGkwpKLpmtu9BaBYUSjMxuRVmYbi+PFN2U=; b=RIgrgp9kcQFS5hAggru3cA3RjkF0c8PIYmqTllUArPPGIEbhAfOyPH4n2cWc1Q30SK WkGPoZe4oPnMLpTNOqmEoSR3csbQhfNm2p7oD5fJzzH6jdL6/aNjrOWtsd5tiw/P9NKD JkISyPgYWEeL30qz3GdVY0pS+pjzYYJE7xQHQ51nQH0EpskTWYc2Vo1IF4nIX18bWm4U MYvFz7EwW3VDxGNefQln7dAJUwuvNjkTBkgId67mJ93gAKPC5G5a5Qc7s5GQuQboYDwr H65gCwmIoYtto2LE1vVjAL2jKnmm1IYEKS5cfH04s23BNvwqf4SFaUJBg+pOcYnjkP/o TfqA== X-Gm-Message-State: ALoCoQl9PKf6vk84c6YpM/b44r0XPtYnxkxGRVrN2EqoIO4zQ1vZgszu6M3zInTuS0NJY19nEAZg X-Received: by 10.50.79.228 with SMTP id m4mr5710692igx.47.1390100894534; Sat, 18 Jan 2014 19:08:14 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id g6sm12630791igg.9.2014.01.18.19.08.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Jan 2014 19:08:14 -0800 (PST) Sender: Warner Losh Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <52DB3FFD.2070503@freebsd.org> Date: Sat, 18 Jan 2014 20:08:12 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <8C16C019-B9AF-417B-9B02-C016A202AAC7@bsdimp.com> References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> <52DB3FFD.2070503@freebsd.org> To: Nathan Whitehorn X-Mailer: Apple Mail (2.1085) Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 03:08:20 -0000 On Jan 18, 2014, at 8:01 PM, Nathan Whitehorn wrote: > On 01/18/14 20:44, Warner Losh wrote: >> On Jan 18, 2014, at 4:41 PM, Julien Grall wrote: >>=20 >>> Hello Nathan, >>>=20 >>> On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >>>> On 01/16/14 18:36, Julien Grall wrote: >>>>>=20 >>>>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>>>> As I understand, only the simple bus code (see simplebus_attach) = is >>>>> translating the interrupts in the device on a resource. >>>>> So if you have a node directly attached to the root node with >>>>> interrupts and MMIO, the driver won't be able to retrieve and >>>>> translate the interrupts via bus_alloc_resources. >>>> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. >>> I have digged into the code to find the reason of my issue. FreeBSD = is receiving a VM fault when the driver (xen-dt) is trying to setup the = IRQ. >>>=20 >>> This is because the GIC is not yet initialized but FreeBSD asks to = unmask the IRQ (sys/arm/arm/gic.c:306). >>>=20 >>> With this problem, all device nodes that are before the GIC in the = device tree can't have interrupts. For instance this simple device will = segfault on FreeBSD: >>>=20 >>> / { >>>=20 >>> mybus { >>> compatible =3D "simple-bus"; >>>=20 >>> mynode { >>> interrupt-parent =3D &gic; >>> interrupts =3D <...>; >>> }; >>>=20 >>> gic: gic@xxxx { >>> interrupt-controller; >>> } >>> }; >>> }; >>>=20 >>> The node "mynode" will have to move after the GIC to be able to work = correctly. >> This stems from a difference in enumeration between FreeBSD and = Linux. FreeBSD enumerates the devices in DTB order, while Linux does a = partial ordering based on dependencies. >>=20 >> Warner >=20 > Enumerating in some other order doesn't necessarily help: since the > interrupt and bus trees are independent, circular dependencies can > happen. This is not a hypothetical: on most powermacs, the main > interrupt controller is a functional unit on a PCI device -- a PCI > device whose other units have interrupt lines that eventually connect > back to itself. There is no way to fix that with ordering. So I think = we > still need to defer interrupt setup. It's not that bad -- PPC already > does this to handle the powermac case. I guess I've looked at simpler cases where interrupts and GPIO pins need = to be up before anything can work on Atmel... We kinda fake it now, but = there's some ordering issues that are solved in this way. But I've not = finished the work on bringing Atmel into the FDT world yet. Deferred = setup isn't always an option, but I'll keep that in mind in case I hit = that case... The other way to cope is to use the multi-pass enumeration stuff that = John Baldwin put into the tree a while ago. In that case, you could = enumerate bridges, interrupt controllers, gpio providers, etc first, and = then do a second pass that catches the rest of the devices and the = interrupt processing for the first pass devices. This is a variation on = the deferred enumeration stuff you are talking about, so that might be a = better, more general solution to these sorts of problems. Warner From owner-freebsd-xen@FreeBSD.ORG Sun Jan 19 03:23:54 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2412E94D; Sun, 19 Jan 2014 03:23:54 +0000 (UTC) Received: from smtpauth4.wiscmail.wisc.edu (wmauth4.doit.wisc.edu [144.92.197.145]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DE716190E; Sun, 19 Jan 2014 03:23:53 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth4.wiscmail.wisc.edu by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MZM00600OYGMO00@smtpauth4.wiscmail.wisc.edu>; Sat, 18 Jan 2014 21:23:53 -0600 (CST) X-Spam-PmxInfo: Server=avs-4, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.19.31515, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (adsl-76-208-68-77.dsl.mdsnwi.sbcglobal.net [76.208.68.77]) by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MZM0080HPFQZ500@smtpauth4.wiscmail.wisc.edu>; Sat, 18 Jan 2014 21:23:52 -0600 (CST) Message-id: <52DB4546.504@freebsd.org> Date: Sat, 18 Jan 2014 21:23:50 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 To: Warner Losh Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> <52DB3FFD.2070503@freebsd.org> <8C16C019-B9AF-417B-9B02-C016A202AAC7@bsdimp.com> In-reply-to: <8C16C019-B9AF-417B-9B02-C016A202AAC7@bsdimp.com> X-Enigmail-Version: 1.6 Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 03:23:54 -0000 On 01/18/14 21:08, Warner Losh wrote: > On Jan 18, 2014, at 8:01 PM, Nathan Whitehorn wrote: > >> On 01/18/14 20:44, Warner Losh wrote: >>> On Jan 18, 2014, at 4:41 PM, Julien Grall wrote: >>> >>>> Hello Nathan, >>>> >>>> On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >>>>> On 01/16/14 18:36, Julien Grall wrote: >>>>>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>>>>> As I understand, only the simple bus code (see simplebus_attach) is >>>>>> translating the interrupts in the device on a resource. >>>>>> So if you have a node directly attached to the root node with >>>>>> interrupts and MMIO, the driver won't be able to retrieve and >>>>>> translate the interrupts via bus_alloc_resources. >>>>> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. >>>> I have digged into the code to find the reason of my issue. FreeBSD is receiving a VM fault when the driver (xen-dt) is trying to setup the IRQ. >>>> >>>> This is because the GIC is not yet initialized but FreeBSD asks to unmask the IRQ (sys/arm/arm/gic.c:306). >>>> >>>> With this problem, all device nodes that are before the GIC in the device tree can't have interrupts. For instance this simple device will segfault on FreeBSD: >>>> >>>> / { >>>> >>>> mybus { >>>> compatible = "simple-bus"; >>>> >>>> mynode { >>>> interrupt-parent = &gic; >>>> interrupts = <...>; >>>> }; >>>> >>>> gic: gic@xxxx { >>>> interrupt-controller; >>>> } >>>> }; >>>> }; >>>> >>>> The node "mynode" will have to move after the GIC to be able to work correctly. >>> This stems from a difference in enumeration between FreeBSD and Linux. FreeBSD enumerates the devices in DTB order, while Linux does a partial ordering based on dependencies. >>> >>> Warner >> Enumerating in some other order doesn't necessarily help: since the >> interrupt and bus trees are independent, circular dependencies can >> happen. This is not a hypothetical: on most powermacs, the main >> interrupt controller is a functional unit on a PCI device -- a PCI >> device whose other units have interrupt lines that eventually connect >> back to itself. There is no way to fix that with ordering. So I think we >> still need to defer interrupt setup. It's not that bad -- PPC already >> does this to handle the powermac case. > I guess I've looked at simpler cases where interrupts and GPIO pins need to be up before anything can work on Atmel... We kinda fake it now, but there's some ordering issues that are solved in this way. But I've not finished the work on bringing Atmel into the FDT world yet. Deferred setup isn't always an option, but I'll keep that in mind in case I hit that case... > > The other way to cope is to use the multi-pass enumeration stuff that John Baldwin put into the tree a while ago. In that case, you could enumerate bridges, interrupt controllers, gpio providers, etc first, and then do a second pass that catches the rest of the devices and the interrupt processing for the first pass devices. This is a variation on the deferred enumeration stuff you are talking about, so that might be a better, more general solution to these sorts of problems. > > Warner > > I'm still not sure that helps. Take the powermac case. The PCI parent bridge assigns and routes interrupts as part of its probe stage. One device (called mac-io) is the one that actually has the interrupt controller, along with other things like ATA and sound. It has several interrupts to support e.g. ATA. How can the PCI bus attachment sensibly attach the macio device? If it delays attaching it until the interrupt controller registers, the bus probing will deadlock, since the interrupt controller is itself a child of macio! If it attaches it immediately, it will not be able to route the interrupts of the macio device. It's a catch-22. The only solution we were able to come up with when this situation arose was to treat the bus and interrupt trees as entirely separate things, built independently, which allows the kernel to break the loop. GPIOs can have similar problems. The basic issue is that newbus ultimately assumes that the system topology can be described by a single tree. Interconnections between the branches -- especially if it isn't even a DAG -- fundamentally break the model and multipass doesn't necessarily help. -Nathan From owner-freebsd-xen@FreeBSD.ORG Mon Jan 20 11:06:57 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88ED7B5D for ; Mon, 20 Jan 2014 11:06:57 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 73F711D8E for ; Mon, 20 Jan 2014 11:06:57 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s0KB6vJW088565 for ; Mon, 20 Jan 2014 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s0KB6vXf088563 for freebsd-xen@FreeBSD.org; Mon, 20 Jan 2014 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Jan 2014 11:06:57 GMT Message-Id: <201401201106.s0KB6vXf088563@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 11:06:57 -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/183139 xen [xen] [patch] ifconfig options on xn0 lost after xen v o kern/180788 xen [xen] [panic] XEN PV kernel 9.2-BETA1 panics on boot o kern/180403 xen [xen] Problems with GENERIC and XENHVM kernels with Xe o kern/180402 xen [xen] XEN kernel does not load in XenClient 4.5.5 o kern/179814 xen [xen] mountroot fails with error=19 under Xen on 9-STA o kern/176471 xen [xen] xn driver crash on detach o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 40 problems total. From owner-freebsd-xen@FreeBSD.ORG Tue Jan 21 08:50:09 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F31635B5 for ; Tue, 21 Jan 2014 08:50:08 +0000 (UTC) Received: from mail-ie0-x248.google.com (mail-ie0-x248.google.com [IPv6:2607:f8b0:4001:c03::248]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B9E9512F8 for ; Tue, 21 Jan 2014 08:50:08 +0000 (UTC) Received: by mail-ie0-f200.google.com with SMTP id tp5so12648236ieb.3 for ; Tue, 21 Jan 2014 00:50:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:message-id:date:subject:from:to:content-type; bh=rFETY8bp3eJV5f/yL0flpbIxZCnBNDajE7KDoYnogWA=; b=m6l0MbtPTy3hs3/OqLeKz60sokPN38G9dqbtPqznJiHSi75RJnm9+bRMoFlVsXy1CS aeyguVke9brFqVWiajx8LY5ljap/s4SKapCJSgOu0OGd78F8WfV3e3qbJ0J0oOvrSSZg xcfL3r5tM4SrEe61WuHhNDiNUebkhH4ZFpplS928CvFqD25JOiyBb+Z5N/HQMI6im/5N xCElsKjMThoCvIGkEaTSb48WHcus2BvOb0mQGcJegzqnACB4tvWOecEzcofuUOWoJIbA aQp0xI2KF4/9m+jT9vPFX9h7QKtMp0PxX4vqwByuRfaNQYOaXLcXs5Epg24WzpsWheIB pqSg== MIME-Version: 1.0 X-Received: by 10.182.246.39 with SMTP id xt7mr2903449obc.40.1390294208283; Tue, 21 Jan 2014 00:50:08 -0800 (PST) Message-ID: <001a11c2e2246b0dc704f0771852@google.com> Date: Tue, 21 Jan 2014 08:50:08 +0000 Subject: www.freebsd.org From: Anna Garcia To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=windows-1252; format=flowed; delsp=yes Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 08:50:09 -0000 SGksDQoNCkkganVzdCB3YW50ZWQgdG8gc2VuZCB5b3UgYSBxdWljayBub3RlLiBXaXRoIGEgZmV3 IHNpbXBsZSBjaGFuZ2VzIHRvIG1ha2UNCnlvdXIgc2l0ZSBtb3JlIFNFTy1mcmllbmRseSBJkm0g c3VyZSB5b3UgY2FuIGNvbnZlcnQgbW9yZSB2aXNpdG9ycyBpbnRvDQpsZWFkcyBhbmQgZ2V0IGl0 IHBsYWNlZCBoaWdoZXIgaW4gdGhlIG9yZ2FuaWMgc2VhcmNoIHJlc3VsdHMsIGZvciBrZXl3b3Jk cw0KdGhhdCBtYXR0ZXIgdG8geW91IHRoZSBtb3N0Lg0KDQpXZSBhcmUgYW4gQXVzdHJhbGlhbiBi YXNlZCBjb21wYW55IHdpdGggYSBncmVhdCBpbi1ob3VzZSB0ZWNobmljYWwgdGVhbSB3aG8NCnJl YWxseSBrbm93IHRoZWlyIHN0dWZmIGFib3V0IHNlYXJjaCBlbmdpbmUgb3B0aW1pemF0aW9uLg0K DQpXb3VsZCB5b3UgbGlrZSBhIGJpdCBtb3JlIGluZm9ybWF0aW9uIGFib3V0IGhvdyB0byBnaXZl IHlvdXIgd2Vic2l0ZSBhDQpib29zdCB3aXRoIGJldHRlciBTRU8/DQoNCkJlc3QgcmVnYXJkcywN Cg0KQW5uYSBHYXJjaWENClNFTy9XRUIgU3BlY2lhbGlzdA0KDQpbaW1hZ2U6IExpbmtlZEluXSBb aW1hZ2U6IEZhY2Vib29rXSBbaW1hZ2U6IFR3aXR0ZXJdIFtpbWFnZTogU2t5cGVdDQogICAgICAg ICAgICAgUyAgIEUgIE8gICAgICAgICAgICAqU2VhcmNoIEVuZ2luZSBPcHRpbWl6YXRpb24qDQoN CldlIHJlc3BlY3QgeW91ciBwcml2YWN5IGFuZCB3YW50IHRvIG1ha2Ugc3VyZSB5b3UgYXJlIGF3 YXJlIG9mIGEgZmV3DQp0aGluZ3MuIEJ5IHJlcGx5aW5nIHRvIHRoaXMgZW1haWwsIHlvdSBhdXRo b3JpemUgb3VyIEF1c3RyYWxpYW4gYWZmaWxpYXRlcw0KdGhhdCBjYW4gaGVscCB3aXRoIHlvdXIg cHJvamVjdCB0byBjYWxsIHlvdSBhdCB0aGUgbnVtYmVyIHlvdSBwcm92aWRlZCwgYW5kDQp5b3Ug dW5kZXJzdGFuZCB0aGF0IHRoZXkgbWF5IHVzZSBhdXRvbWF0ZWQgcGhvbmUgdGVjaG5vbG9neSB0 byBjYWxsIHlvdS4gQXQNCm5vIHRpbWUgYXJlIHlvdSByZXF1aXJlZCB0byBtYWtlIGEgcHVyY2hh c2UuDQo= From owner-freebsd-xen@FreeBSD.ORG Tue Jan 21 11:24:27 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3B9B32F6 for ; Tue, 21 Jan 2014 11:24:27 +0000 (UTC) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 14DA11205 for ; Tue, 21 Jan 2014 11:24:27 +0000 (UTC) Received: by mail-pa0-f46.google.com with SMTP id rd3so8197773pab.5 for ; Tue, 21 Jan 2014 03:24:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:reply-to:subject:date; bh=Iyk2K6fvYNLbDPkOF2p5SQgAED667GVP56ua58RI4bE=; b=Y3oSaUF02ibqmBLL1G3ibWJbPKabBNbEKNY93339f14kVXKjZ9OcDiTx9RzFl+XOpI jw0LpIVhKnJitR93sVigScKpEWSYlbyAKLIkaX1i00j4krn23Pwac71UeQs7HC5+gUE0 /VyebqaH/0MMAciBcyuZ5+U/hKVmPtNI01Dq2XG15dwj/S2Di0wre4pv6CTNUmWB3Eww DQLe5MGguP+58qNdpeDynNRn0UF/d7sSrQYGn06VAyFS9w2GCJaFXmOCutzvmc6iqKPG EgFYAorMB0mlnFVIwBLl9KsmK6FTlApam8d+B2o4v/yBgaDcyS4DdhhVJeW/fo5xRCaC 2VmA== X-Received: by 10.66.148.230 with SMTP id tv6mr8287845pab.155.1390303466677; Tue, 21 Jan 2014 03:24:26 -0800 (PST) Received: from localhost.localdomain ([124.253.246.183]) by mx.google.com with ESMTPSA id i10sm23627495pat.11.2014.01.21.03.24.23 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 21 Jan 2014 03:24:25 -0800 (PST) Message-ID: <52de58e9.ea42420a.508d.06ff@mx.google.com> From: angel08445@gmail.com To: freebsd-xen@freebsd.org Subject: RE: LOCAL MAP OPTIMIZATION FOR : mail-archive.com (Less Than $99/Month) Date: Tue, 21 Jan 2014 16:54:27 +0530 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Lova43432@gmail.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 11:24:27 -0000 Good Morning Sir / Mam Is your business ranking in local maps shown on PAGE 1 of google ? With new google policies they have specifically asked local business owners to optimize their website for local maps rather than JUST organics. Do you know the reason why you are not ranked well on google MAPs or why there is drop in your website rankings? Prime reason for bad rankings for a busniess is lack of local presence and local citations ie getting your business listed on directories like YELP, MANTA & Many more. These websites not just give your business a push but also help you Maintain a good Online Reputation. Why you need to optimize your website for local MAP Listings ? - MAP listings get 10 times more clicks than organic listings - Increased conversions because of real reviews posted on your Google Plus Page - Every year there is 30% increase in searches for local keywords - Increases legitimacy of a Business We will help you get your website ranked well on google for the related keywords in your niche. We specialize in LOCAL SEARCH ENGINE OPTIMIZATION increasing visibility for small businesses by ranking them for geographically-related keywords. Say for eg-: you want to search a plumber in your city, You will be typing in keywords like Plumbers + City Or Plumbers + IN + City. We make sure your website comes in google MAP listings shown on page 1 for each such keyword. Now Google believes in - BE ORIGINAL, HAVE ORIGINAL AND GIVE ORIGINAL which means that google wants to end up that frustrating experience of users who are searching for Service Or Product and seeing the results that are not even close to what they are looking for. Google only wants to give their user original and relevant results. This makes it even more important that we showcase our business in the best possible way and make sure our website in valued high by google. We at TheLOCALIST will make google feel the importance of your business by following their guidelines thus ranking your website higher in serach results. We are presently offering LOCAL OPTIMIZATION to more than 400 websites and they all rank page 1 for all possible keywords !!! Each month your website is submitted to more than 50 citations and social presence is controlled by posting videos and blogs all over the web. Email us back with your website & phone number so we can discuss this further with you. Our Packages start from as low as 99$/month. Thanks For Taking Time To Read Our Email Polly Martin Local SEO Manager ( THE Localist ) Address : 24 ST Suite 32 Downtown Provo Utah ------------------- NOT INTERESTED ? REPLY WITH NOT INTERESTED IN THE SUBJECT LINE From owner-freebsd-xen@FreeBSD.ORG Tue Jan 21 19:03:18 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C8BE3463; Tue, 21 Jan 2014 19:03:18 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9C6FB1E12; Tue, 21 Jan 2014 19:03:18 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9586DB977; Tue, 21 Jan 2014 14:03:17 -0500 (EST) From: John Baldwin To: Roger Pau Monne Subject: Re: [PATCH RFC 02/13] ioapic: introduce hooks for some ioapic ops Date: Tue, 21 Jan 2014 13:27:17 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <1387884062-41154-1-git-send-email-roger.pau@citrix.com> <1387884062-41154-3-git-send-email-roger.pau@citrix.com> In-Reply-To: <1387884062-41154-3-git-send-email-roger.pau@citrix.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201401211327.17258.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Jan 2014 14:03:17 -0500 (EST) Cc: julien.grall@citrix.com, freebsd-xen@freebsd.org, freebsd-current@freebsd.org, kib@freebsd.org, xen-devel@lists.xenproject.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 19:03:18 -0000 On Tuesday, December 24, 2013 6:20:51 am Roger Pau Monne wrote: > Create some hooks for IO APIC operations that will diverge from bare > metal when implemented for Xen Dom0. > > This patch should not introduce any changes in functionality, it's a > preparatory patch for the implementation of the Xen IO APIC hooks. I think this is fine. I should really create a sys/x86/include/apicvar.h as there is a lot shared between those two headers. -- John Baldwin From owner-freebsd-xen@FreeBSD.ORG Tue Jan 21 19:03:17 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AACFC460; Tue, 21 Jan 2014 19:03:17 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7F2F81E10; Tue, 21 Jan 2014 19:03:17 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 71FC2B94C; Tue, 21 Jan 2014 14:03:16 -0500 (EST) From: John Baldwin To: Roger Pau Monne Subject: Re: [PATCH RFC 01/13] xen: use the hardware e820 map on Dom0 Date: Tue, 21 Jan 2014 13:25:29 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <1387884062-41154-1-git-send-email-roger.pau@citrix.com> <1387884062-41154-2-git-send-email-roger.pau@citrix.com> In-Reply-To: <1387884062-41154-2-git-send-email-roger.pau@citrix.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201401211325.29460.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Jan 2014 14:03:16 -0500 (EST) Cc: julien.grall@citrix.com, freebsd-xen@freebsd.org, freebsd-current@freebsd.org, kib@freebsd.org, xen-devel@lists.xenproject.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 19:03:17 -0000 On Tuesday, December 24, 2013 6:20:50 am Roger Pau Monne wrote: > We need to do some tweaking of the hardware e820 map, since the memory > layout provided by Xen and the e820 map doesn't match. > > This consists in clamping the e820 map so that regions above max_pfn > are marked as unusuable. > --- > sys/x86/xen/pv.c | 35 +++++++++++++++++++++++++++++++++-- > 1 files changed, 33 insertions(+), 2 deletions(-) > > diff --git a/sys/x86/xen/pv.c b/sys/x86/xen/pv.c > index 4f7415e..ab4afba 100644 > --- a/sys/x86/xen/pv.c > +++ b/sys/x86/xen/pv.c > @@ -297,17 +297,48 @@ static void > xen_pv_parse_memmap(caddr_t kmdp, vm_paddr_t *physmap, int *physmap_idx) > { > struct xen_memory_map memmap; > + unsigned long max_pfn = HYPERVISOR_start_info->nr_pages; > + u_int64_t mem_end = ptoa(max_pfn); > u_int32_t size; > - int rc; > + int rc, mem_op, i; One minor nit is that it is preferred to not initalize variables in declarations style-wise. Aside from that, this looks fine to me. > /* Fetch the E820 map from Xen */ > memmap.nr_entries = MAX_E820_ENTRIES; > set_xen_guest_handle(memmap.buffer, xen_smap); > - rc = HYPERVISOR_memory_op(XENMEM_memory_map, &memmap); > + mem_op = xen_initial_domain() ? > + XENMEM_machine_memory_map : > + XENMEM_memory_map; > + rc = HYPERVISOR_memory_op(mem_op, &memmap); > if (rc) > panic("unable to fetch Xen E820 memory map"); > size = memmap.nr_entries * sizeof(xen_smap[0]); > > + /* > + * This should be improved, Xen provides us with a single > + * chunk of physical memory that goes from 0 to max_pfn, > + * and what we do here is clamp the HW memory map to make > + * sure regions above max_pfn are marked as reserved. > + * > + * TRTTD would be to move the memory not used because of > + * the holes in the HW memory map to the now clamped regions > + * using XENMEM_{decrease/increase}_reservation. > + */ > + for (i = 0; i < memmap.nr_entries; i++) { > + u_int64_t end = xen_smap[i].base + xen_smap[i].length; > + if (xen_smap[i].type == SMAP_TYPE_MEMORY) { > + if (xen_smap[i].base > mem_end) { > + /* Mark as reserved */ > + xen_smap[i].type = SMAP_TYPE_RESERVED; > + continue; > + } > + if (end > mem_end) { > + /* Truncate region */ > + xen_smap[i].length -= end - mem_end; > + } > + } > + } > + > + > bios_add_smap_entries(xen_smap, size, physmap, physmap_idx); > } > > -- > 1.7.7.5 (Apple Git-26) > > -- John Baldwin From owner-freebsd-xen@FreeBSD.ORG Tue Jan 21 19:03:20 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 761D1486; Tue, 21 Jan 2014 19:03:20 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4A7FF1E13; Tue, 21 Jan 2014 19:03:20 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B3974B945; Tue, 21 Jan 2014 14:03:18 -0500 (EST) From: John Baldwin To: Roger Pau Monne Subject: Re: [PATCH RFC 04/13] xen: implement basic PIRQ support for Dom0 Date: Tue, 21 Jan 2014 13:52:44 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <1387884062-41154-1-git-send-email-roger.pau@citrix.com> <1387884062-41154-5-git-send-email-roger.pau@citrix.com> In-Reply-To: <1387884062-41154-5-git-send-email-roger.pau@citrix.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201401211352.44784.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Jan 2014 14:03:19 -0500 (EST) Cc: julien.grall@citrix.com, freebsd-xen@freebsd.org, freebsd-current@freebsd.org, kib@freebsd.org, xen-devel@lists.xenproject.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 19:03:20 -0000 On Tuesday, December 24, 2013 6:20:53 am Roger Pau Monne wrote: > This allows Dom0 to manage physical hardware, redirecting the > physical interrupts to event channels. > --- > sys/x86/xen/xen_intr.c | 190 +++++++++++++++++++++++++++++++++++++++++++++-- > sys/xen/xen_intr.h | 11 +++ > 2 files changed, 192 insertions(+), 9 deletions(-) > > diff --git a/sys/x86/xen/xen_intr.c b/sys/x86/xen/xen_intr.c > index bc0781e..340e5ed 100644 > --- a/sys/x86/xen/xen_intr.c > +++ b/sys/x86/xen/xen_intr.c > @@ -104,6 +104,8 @@ DPCPU_DECLARE(struct vcpu_info *, vcpu_info); > > #define is_valid_evtchn(x) ((x) != 0) > > +#define EEXIST 17 /* Xen "already exists" error */ Is there a xen_errno.h header? Might be nice to have one and give these constants unique names (e.g. XEN_EEXIST or some such) to avoid confusion/conflicts with . Other than that I think this looks fine. -- John Baldwin From owner-freebsd-xen@FreeBSD.ORG Tue Jan 21 19:03:21 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBA09562; Tue, 21 Jan 2014 19:03:21 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A0E531E15; Tue, 21 Jan 2014 19:03:21 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5EBAEB946; Tue, 21 Jan 2014 14:03:20 -0500 (EST) From: John Baldwin To: Roger Pau Monne Subject: Re: [PATCH RFC 05/13] xen: implement Xen IO APIC ops Date: Tue, 21 Jan 2014 13:55:13 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <1387884062-41154-1-git-send-email-roger.pau@citrix.com> <1387884062-41154-6-git-send-email-roger.pau@citrix.com> In-Reply-To: <1387884062-41154-6-git-send-email-roger.pau@citrix.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201401211355.13800.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Jan 2014 14:03:20 -0500 (EST) Cc: julien.grall@citrix.com, freebsd-xen@freebsd.org, freebsd-current@freebsd.org, kib@freebsd.org, xen-devel@lists.xenproject.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 19:03:22 -0000 On Tuesday, December 24, 2013 6:20:54 am Roger Pau Monne wrote: > Implement a different set of hooks for IO APIC to use when running > under Xen Dom0. > --- > sys/x86/xen/pv.c | 44 ++++++++++++++++++++++++++++++++++++++++++++ > 1 files changed, 44 insertions(+), 0 deletions(-) > > diff --git a/sys/x86/xen/pv.c b/sys/x86/xen/pv.c > index ab4afba..e5ad200 100644 > --- a/sys/x86/xen/pv.c > +++ b/sys/x86/xen/pv.c > @@ -49,6 +49,7 @@ __FBSDID("$FreeBSD$"); > #include > #include > > +#include > #include > #include > #include > @@ -58,6 +59,7 @@ __FBSDID("$FreeBSD$"); > #include > #include > #include > +#include > > #include > > @@ -73,6 +75,11 @@ static caddr_t xen_pv_parse_preload_data(u_int64_t); > static void xen_pv_parse_memmap(caddr_t, vm_paddr_t *, int *); > > static void xen_pv_set_init_ops(void); > + > +static u_int xen_pv_ioapic_read(volatile ioapic_t *, int); > +static void xen_pv_ioapic_write(volatile ioapic_t *, int, u_int); > +static void xen_pv_ioapic_register_intr(struct ioapic_intsrc *); > + > /*---------------------------- Extern Declarations ---------------------------*/ > /* Variables used by amd64 mp_machdep to start APs */ > extern struct mtx ap_boot_mtx; > @@ -92,6 +99,13 @@ struct init_ops xen_init_ops = { > .parse_memmap = xen_pv_parse_memmap, > }; > > +/* Xen ioapic_ops implementation */ > +struct ioapic_ops xen_ioapic_ops = { > + .read = xen_pv_ioapic_read, > + .write = xen_pv_ioapic_write, > + .register_intr = xen_pv_ioapic_register_intr, > +}; > + > static struct > { > const char *ev; > @@ -342,6 +356,34 @@ xen_pv_parse_memmap(caddr_t kmdp, vm_paddr_t *physmap, int *physmap_idx) > bios_add_smap_entries(xen_smap, size, physmap, physmap_idx); > } > > +static u_int > +xen_pv_ioapic_read(volatile ioapic_t *apic, int reg) > +{ > + struct physdev_apic apic_op; > + int rc; > + > + mtx_assert(&icu_lock, MA_OWNED); > + > + apic_op.apic_physbase = pmap_kextract((vm_offset_t) apic); Seems a shame to have to do this. I wouldn't mind if you changed the read/write callbacks to take 'struct ioapic *' instead and then use the 'io_paddr' member. I do think that would be cleaner. > + apic_op.reg = reg; > + rc = HYPERVISOR_physdev_op(PHYSDEVOP_apic_read, &apic_op); > + if (rc) > + panic("apic_read operation failed"); > + > + return (apic_op.value); > +} > + > +static void > +xen_pv_ioapic_write(volatile ioapic_t *apic, int reg, u_int val) > +{ > +} I guess not allowing writes is on purpose? > + > +static void > +xen_pv_ioapic_register_intr(struct ioapic_intsrc *pin) > +{ > + xen_register_pirq(pin->io_irq, pin->io_activehi, pin->io_edgetrigger); > +} > + > static void > xen_pv_set_init_ops(void) > { > @@ -349,4 +391,6 @@ xen_pv_set_init_ops(void) > init_ops = xen_init_ops; > /* Disable lapic */ > lapic_disabled = true; > + /* IOAPIC ops for Xen PV */ > + ioapic_ops = xen_ioapic_ops; > } > -- > 1.7.7.5 (Apple Git-26) > > -- John Baldwin From owner-freebsd-xen@FreeBSD.ORG Tue Jan 21 19:03:22 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD6A96AA; Tue, 21 Jan 2014 19:03:22 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B450E1E16; Tue, 21 Jan 2014 19:03:22 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B55EEB99A; Tue, 21 Jan 2014 14:03:21 -0500 (EST) From: John Baldwin To: Roger Pau Monne Subject: Re: [PATCH RFC 06/13] xen: Dom0 console fixes Date: Tue, 21 Jan 2014 14:02:58 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <1387884062-41154-1-git-send-email-roger.pau@citrix.com> <1387884062-41154-7-git-send-email-roger.pau@citrix.com> In-Reply-To: <1387884062-41154-7-git-send-email-roger.pau@citrix.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201401211402.58721.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Jan 2014 14:03:21 -0500 (EST) Cc: julien.grall@citrix.com, freebsd-xen@freebsd.org, freebsd-current@freebsd.org, kib@freebsd.org, xen-devel@lists.xenproject.org, gibbs@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 19:03:22 -0000 On Tuesday, December 24, 2013 6:20:55 am Roger Pau Monne wrote: > Minor fixes and workarounds to make the Xen Dom0 console work. Looks ok to me. -- John Baldwin