From xen-arm-bounces@lists.xen.org Mon Jul 01 03:59:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 03:59:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtVGn-0004fB-2e; Mon, 01 Jul 2013 03:59:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtVGl-0004f3-Ib; Mon, 01 Jul 2013 03:59:15 +0000 Received: from [85.158.139.211:43469] by server-9.bemta-5.messagelabs.com id 7C/E5-26025-29EF0D15; Mon, 01 Jul 2013 03:59:14 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1372651152!19615008!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18412 invoked from network); 1 Jul 2013 03:59:14 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 03:59:14 -0000 Received: by mail-pb0-f47.google.com with SMTP id rr13so4274210pbb.20 for ; Sun, 30 Jun 2013 20:59:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=XgUXzBixxr7FbsIpRriervPnCaQ6kTRgbHeCUmMuoEg=; b=frt1FDluyTqZW0/M/3BM9RitjKZxv0ey+EajXN7ccPuXea0t+YeJo6Bp1Dws/W2+9M Tn3lVYJLOwYfRD1mVs8AwpfhBl9nDFeoEQ69y9dSjJgHfb3M7Z5CyA3/P0YT/8S9KF01 aA1RMz6YZ2bUEwq2MOGtZ7fraY2UsUGf+I9w/kVLDAd3476LHC/KevlujF9d8Wseiu0L QDk0cJm9JBZ2mDBbJU2VgMOuxEvfBZOVE+5AAc5yhz382hJCFNE59psdj4lUAUcNNBgq kCXyA9Rj+85O9N+x9SWPAkJks4Wl41vkIrNJPUAY4sZUsc6CzPEvc7sY9iH31xZh54RX BRPQ== X-Received: by 10.68.175.33 with SMTP id bx1mr22000077pbc.21.1372651151885; Sun, 30 Jun 2013 20:59:11 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id to6sm21570474pab.0.2013.06.30.20.59.09 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 30 Jun 2013 20:59:11 -0700 (PDT) Date: Mon, 1 Jul 2013 11:54:13 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130701035413.GA12358@cbz-workstation> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1372335001.7996.7.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > > Hi Ian, > > > > After enabling the UART, I have been tring to finish the rest of booting. > > However, the output information stops at "Placing Xen at XXXX-XXXX" like > > following: > > > > Starting kernel ... > > > > - UART enabled - > > - CPU 00000000 booting - > > - Machine ID 00000ec1 - > > - Started in Hyp mode - > > - Zero BSS - > > - Setting up control registers - > > - Turning on paging - > > - Ready - > > RAM: 0000000080000000 - 00000000ffffffff > > > > MODULE[1]: 00000000a0000000 - 00000000a0400000 > > Placing Xen at 0x00000000ffe00000-0x0000000100000000 > > > > What could be the most possible problem of this case? > > This is a about the point where we would shift from early_printk to the > proper console driver, so I expect you simply don't have the console > setup. > Hi Ian, I guess that it might not all about console driver, because early_printk does not work properly just after we have updated "the copy of boot_pgtable to use the new paddrs" in setup_pagetables(). It seems that FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without being restored. I'm looking into those related codes. Cheers, Baozi _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 03:59:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 03:59:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtVGn-0004fB-2e; Mon, 01 Jul 2013 03:59:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtVGl-0004f3-Ib; Mon, 01 Jul 2013 03:59:15 +0000 Received: from [85.158.139.211:43469] by server-9.bemta-5.messagelabs.com id 7C/E5-26025-29EF0D15; Mon, 01 Jul 2013 03:59:14 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1372651152!19615008!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18412 invoked from network); 1 Jul 2013 03:59:14 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 03:59:14 -0000 Received: by mail-pb0-f47.google.com with SMTP id rr13so4274210pbb.20 for ; Sun, 30 Jun 2013 20:59:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=XgUXzBixxr7FbsIpRriervPnCaQ6kTRgbHeCUmMuoEg=; b=frt1FDluyTqZW0/M/3BM9RitjKZxv0ey+EajXN7ccPuXea0t+YeJo6Bp1Dws/W2+9M Tn3lVYJLOwYfRD1mVs8AwpfhBl9nDFeoEQ69y9dSjJgHfb3M7Z5CyA3/P0YT/8S9KF01 aA1RMz6YZ2bUEwq2MOGtZ7fraY2UsUGf+I9w/kVLDAd3476LHC/KevlujF9d8Wseiu0L QDk0cJm9JBZ2mDBbJU2VgMOuxEvfBZOVE+5AAc5yhz382hJCFNE59psdj4lUAUcNNBgq kCXyA9Rj+85O9N+x9SWPAkJks4Wl41vkIrNJPUAY4sZUsc6CzPEvc7sY9iH31xZh54RX BRPQ== X-Received: by 10.68.175.33 with SMTP id bx1mr22000077pbc.21.1372651151885; Sun, 30 Jun 2013 20:59:11 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id to6sm21570474pab.0.2013.06.30.20.59.09 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 30 Jun 2013 20:59:11 -0700 (PDT) Date: Mon, 1 Jul 2013 11:54:13 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130701035413.GA12358@cbz-workstation> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1372335001.7996.7.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > > Hi Ian, > > > > After enabling the UART, I have been tring to finish the rest of booting. > > However, the output information stops at "Placing Xen at XXXX-XXXX" like > > following: > > > > Starting kernel ... > > > > - UART enabled - > > - CPU 00000000 booting - > > - Machine ID 00000ec1 - > > - Started in Hyp mode - > > - Zero BSS - > > - Setting up control registers - > > - Turning on paging - > > - Ready - > > RAM: 0000000080000000 - 00000000ffffffff > > > > MODULE[1]: 00000000a0000000 - 00000000a0400000 > > Placing Xen at 0x00000000ffe00000-0x0000000100000000 > > > > What could be the most possible problem of this case? > > This is a about the point where we would shift from early_printk to the > proper console driver, so I expect you simply don't have the console > setup. > Hi Ian, I guess that it might not all about console driver, because early_printk does not work properly just after we have updated "the copy of boot_pgtable to use the new paddrs" in setup_pagetables(). It seems that FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without being restored. I'm looking into those related codes. Cheers, Baozi _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 08:23:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 08:23:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZOr-0008Td-0U; Mon, 01 Jul 2013 08:23:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZOo-0008TF-T6; Mon, 01 Jul 2013 08:23:51 +0000 Received: from [85.158.136.67:58637] by server-14.bemta-5.messagelabs.com id FA/A6-11419-59C31D15; Mon, 01 Jul 2013 08:23:49 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-207.messagelabs.com!1372667029!34102762!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23515 invoked from network); 1 Jul 2013 08:23:49 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-207.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 08:23:49 -0000 X-IronPort-AV: E=Sophos;i="4.87,972,1363132800"; d="scan'208";a="6234398" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 08:23:48 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 09:23:47 +0100 Message-ID: <1372667026.14691.16.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Date: Mon, 1 Jul 2013 09:23:46 +0100 In-Reply-To: <51CDC255.7060902@xen.org> References: <51CDC255.7060902@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: "xen-users@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , publicity@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] First go at Planet Xen ... X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Fri, 2013-06-28 at 18:05 +0100, Lars Kurth wrote: > Hi all, > > I created http://www.xenproject.org/planet-xen.html and we can now add > blogs from community members and organizations that talk about Xen. You > can get to it from "Xen Planet" in the global navigation bar from all > *.xenproject.org sites (or will be able to soon). Is there an RSS link for the planet itself? I couldn't find one. [...] > At some point I hope I can include news search query for "Xen > Hypervisor", "Xen Project", ... but this does not seem to work at the > moment. I think this would reduce the utility of the "planet", at least for me. e.g. I wouldn't want to subscribe to an rss feed which contained this sort of thing. I want to see actual content by people involved with or related to the project. Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 08:23:55 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 08:23:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZOr-0008Td-0U; Mon, 01 Jul 2013 08:23:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZOo-0008TF-T6; Mon, 01 Jul 2013 08:23:51 +0000 Received: from [85.158.136.67:58637] by server-14.bemta-5.messagelabs.com id FA/A6-11419-59C31D15; Mon, 01 Jul 2013 08:23:49 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-207.messagelabs.com!1372667029!34102762!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23515 invoked from network); 1 Jul 2013 08:23:49 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-207.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 08:23:49 -0000 X-IronPort-AV: E=Sophos;i="4.87,972,1363132800"; d="scan'208";a="6234398" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 08:23:48 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 09:23:47 +0100 Message-ID: <1372667026.14691.16.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Date: Mon, 1 Jul 2013 09:23:46 +0100 In-Reply-To: <51CDC255.7060902@xen.org> References: <51CDC255.7060902@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: "xen-users@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , publicity@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] First go at Planet Xen ... X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Fri, 2013-06-28 at 18:05 +0100, Lars Kurth wrote: > Hi all, > > I created http://www.xenproject.org/planet-xen.html and we can now add > blogs from community members and organizations that talk about Xen. You > can get to it from "Xen Planet" in the global navigation bar from all > *.xenproject.org sites (or will be able to soon). Is there an RSS link for the planet itself? I couldn't find one. [...] > At some point I hope I can include news search query for "Xen > Hypervisor", "Xen Project", ... but this does not seem to work at the > moment. I think this would reduce the utility of the "planet", at least for me. e.g. I wouldn't want to subscribe to an rss feed which contained this sort of thing. I want to see actual content by people involved with or related to the project. Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 08:50:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 08:50:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZoU-0001g5-QH; Mon, 01 Jul 2013 08:50:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZoS-0001fd-F5; Mon, 01 Jul 2013 08:50:20 +0000 Received: from [85.158.138.51:65000] by server-12.bemta-3.messagelabs.com id AE/41-17731-BC241D15; Mon, 01 Jul 2013 08:50:19 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1372668618!27709364!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5704 invoked from network); 1 Jul 2013 08:50:18 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 08:50:18 -0000 X-IronPort-AV: E=Sophos;i="4.87,972,1363132800"; d="scan'208";a="6236149" Received: from lonpex01cl02.citrite.net ([10.30.203.102]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 08:50:19 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL02.citrite.net (10.30.203.102) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 09:50:17 +0100 Message-ID: <1372668616.14691.35.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 09:50:16 +0100 In-Reply-To: <20130701035413.GA12358@cbz-workstation> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: > On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > > On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > > > Hi Ian, > > > > > > After enabling the UART, I have been tring to finish the rest of booting. > > > However, the output information stops at "Placing Xen at XXXX-XXXX" like > > > following: > > > > > > Starting kernel ... > > > > > > - UART enabled - > > > - CPU 00000000 booting - > > > - Machine ID 00000ec1 - > > > - Started in Hyp mode - > > > - Zero BSS - > > > - Setting up control registers - > > > - Turning on paging - > > > - Ready - > > > RAM: 0000000080000000 - 00000000ffffffff > > > > > > MODULE[1]: 00000000a0000000 - 00000000a0400000 > > > Placing Xen at 0x00000000ffe00000-0x0000000100000000 > > > > > > What could be the most possible problem of this case? > > > > This is a about the point where we would shift from early_printk to the > > proper console driver, so I expect you simply don't have the console > > setup. > > > Hi Ian, > > I guess that it might not all about console driver, because early_printk > does not work properly just after we have updated "the copy of boot_pgtable > to use the new paddrs" in setup_pagetables(). It seems that > FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without > being restored. Hrm, I think the expectation is that the fixmap will be copied as part of that and doesn't need (or receive) any additional fixups (see around "Link in the fixmap pagetable"), but it is worth checking for sure. You could probably profitably sprinkle some more early_print around the place during that sequence for debugging purposes. BTW I've just checked a boot here and after the "Placing Xen" message there should be two more early_printk's which are the "Xen heap: XXX pages..." and "Looking for UART.." ones before things switch to the real console, so you are right that it isn't making it to the real console driver. Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 08:50:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 08:50:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZoU-0001g5-QH; Mon, 01 Jul 2013 08:50:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZoS-0001fd-F5; Mon, 01 Jul 2013 08:50:20 +0000 Received: from [85.158.138.51:65000] by server-12.bemta-3.messagelabs.com id AE/41-17731-BC241D15; Mon, 01 Jul 2013 08:50:19 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1372668618!27709364!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5704 invoked from network); 1 Jul 2013 08:50:18 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 08:50:18 -0000 X-IronPort-AV: E=Sophos;i="4.87,972,1363132800"; d="scan'208";a="6236149" Received: from lonpex01cl02.citrite.net ([10.30.203.102]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 08:50:19 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL02.citrite.net (10.30.203.102) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 09:50:17 +0100 Message-ID: <1372668616.14691.35.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 09:50:16 +0100 In-Reply-To: <20130701035413.GA12358@cbz-workstation> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: > On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > > On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > > > Hi Ian, > > > > > > After enabling the UART, I have been tring to finish the rest of booting. > > > However, the output information stops at "Placing Xen at XXXX-XXXX" like > > > following: > > > > > > Starting kernel ... > > > > > > - UART enabled - > > > - CPU 00000000 booting - > > > - Machine ID 00000ec1 - > > > - Started in Hyp mode - > > > - Zero BSS - > > > - Setting up control registers - > > > - Turning on paging - > > > - Ready - > > > RAM: 0000000080000000 - 00000000ffffffff > > > > > > MODULE[1]: 00000000a0000000 - 00000000a0400000 > > > Placing Xen at 0x00000000ffe00000-0x0000000100000000 > > > > > > What could be the most possible problem of this case? > > > > This is a about the point where we would shift from early_printk to the > > proper console driver, so I expect you simply don't have the console > > setup. > > > Hi Ian, > > I guess that it might not all about console driver, because early_printk > does not work properly just after we have updated "the copy of boot_pgtable > to use the new paddrs" in setup_pagetables(). It seems that > FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without > being restored. Hrm, I think the expectation is that the fixmap will be copied as part of that and doesn't need (or receive) any additional fixups (see around "Link in the fixmap pagetable"), but it is worth checking for sure. You could probably profitably sprinkle some more early_print around the place during that sequence for debugging purposes. BTW I've just checked a boot here and after the "Placing Xen" message there should be two more early_printk's which are the "Xen heap: XXX pages..." and "Looking for UART.." ones before things switch to the real console, so you are right that it isn't making it to the real console driver. Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 08:54:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 08:54:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZs7-0002Bb-L2; Mon, 01 Jul 2013 08:54:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZs5-0002B3-Da; Mon, 01 Jul 2013 08:54:05 +0000 Received: from [193.109.254.147:58625] by server-8.bemta-14.messagelabs.com id 48/41-19397-CA341D15; Mon, 01 Jul 2013 08:54:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1372668791!8533542!1 X-Originating-IP: [209.85.214.175] X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,SUSPICIOUS_RECIPS,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17085 invoked from network); 1 Jul 2013 08:53:14 -0000 Received: from mail-ob0-f175.google.com (HELO mail-ob0-f175.google.com) (209.85.214.175) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 08:53:14 -0000 Received: by mail-ob0-f175.google.com with SMTP id xn12so3948465obc.6 for ; Mon, 01 Jul 2013 01:53:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wisM6yUnq7WbMYsFe/5lIVWPhFSXHgvHpMIL0m2zAe8=; b=MUWx668lkd+DnCSgAMZhidFOLceaTInzdjYh8GP3UmHj412YSSoIcqirBOwb3EfFCj aKDlhoiMAfOIr/WlZVMGtHyYCR8OJ+cx+d+CzH4jXlunqkrgY6Dn2JZxMr/f2vAbbS2h 9MkeqaJyEkS8V61U5j0KcBZYwxCqRaQo69oZu8rPbOLhAgQBtf/XBWPK4iP0EMFhZ50g IzpJPuvbTcYYABFHXnXhnAkybd0LTd5jNgMN1mK0TRx9wH0YTYzZhCvAf41ikBmPki6l WhJMiIWx6KmssNsQl85PXpO4M/B6LpeeBHi1ZkiZnGIvjVsup/lhlw1IKZvD3t0mVqAY uRqQ== MIME-Version: 1.0 X-Received: by 10.182.61.19 with SMTP id l19mr10653958obr.55.1372668791220; Mon, 01 Jul 2013 01:53:11 -0700 (PDT) Received: by 10.60.121.6 with HTTP; Mon, 1 Jul 2013 01:53:11 -0700 (PDT) In-Reply-To: <1372667026.14691.16.camel@zakaz.uk.xensource.com> References: <51CDC255.7060902@xen.org> <1372667026.14691.16.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 09:53:11 +0100 Message-ID: From: Lars Kurth To: Ian Campbell Cc: "xen-users@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , publicity@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] First go at Planet Xen ... X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7588732548655740479==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============7588732548655740479== Content-Type: multipart/alternative; boundary=e89a8fb1ef72b1ef2e04e06f5b17 --e89a8fb1ef72b1ef2e04e06f5b17 Content-Type: text/plain; charset=ISO-8859-1 > Is there an RSS link for the planet itself? I couldn't find one. No. I still need to set it up. Didn't get round to it yet. > I think this would reduce the utility of the "planet", at least for me. > e.g. I wouldn't want to subscribe to an rss feed which contained this > sort of thing. I want to see actual content by people involved with or > related to the project. Agreed. In fact this occurred to me after I sent the mail. So I added that feed to http://xenproject.org/about/in-the-news.html There is another question: I had a request from a Brazilian community member (who writes a Portuguese language Xen blog). I am not sure what the feeling with regards to mixing languages is. We could set up different pages for different languages, but the question is whether we get enough feeds to be of use. Any views? Lars On Mon, Jul 1, 2013 at 9:23 AM, Ian Campbell wrote: > On Fri, 2013-06-28 at 18:05 +0100, Lars Kurth wrote: > > Hi all, > > > > I created http://www.xenproject.org/planet-xen.html and we can now add > > blogs from community members and organizations that talk about Xen. You > > can get to it from "Xen Planet" in the global navigation bar from all > > *.xenproject.org sites (or will be able to soon). > > Is there an RSS link for the planet itself? I couldn't find one. > > [...] > > At some point I hope I can include news search query for "Xen > > Hypervisor", "Xen Project", ... but this does not seem to work at the > > moment. > > I think this would reduce the utility of the "planet", at least for me. > e.g. I wouldn't want to subscribe to an rss feed which contained this > sort of thing. I want to see actual content by people involved with or > related to the project. > > Ian. > > --e89a8fb1ef72b1ef2e04e06f5b17 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>=A0Is there an RSS link for the planet itself? I couldn't find on= e.
No. I still need to set it up. Didn't get round to it yet.<= /div>

=
>=A0I think this would reduce the utility of the "planet", at= least for me.
> e.g. I wou= ldn't want to subscribe to an rss feed which contained this
> sort of thing. I wa= nt to see actual content by people involved with or
> related to the project.
Agreed. In fact=A0this=A0occurred=A0to me after I sent the mail. So I a= dded that feed to=A0http://xenproject.org/about/in-the-news.html

There is another question: I had a request = from a Brazilian community member (who writes a Portuguese language Xen blo= g). I am not sure what the feeling with regards to mixing languages is. We = could set up different pages for different languages, but the question is w= hether we get enough feeds to be of use. Any views?

Lars
=

On Mon, Jul 1, 2013 at 9:23 AM, Ian Camp= bell <Ian.Campbell@citrix.com> wrote:
On Fri, 2013-06-28 at 18:0= 5 +0100, Lars Kurth wrote:
> Hi all,
>
> I created http://www.xenproject.org/planet-xen.html and we can now ad= d
> blogs from community members and organizations that talk about Xen. Yo= u
> can get to it from "Xen Planet" in the global navigation bar= from all
> *.xenproject.org sites (or will be able to soon).

Is there an RSS link for the planet itself? I couldn't find one.<= br>
[...]
> At some point I hope I can include news search query= for "Xen
> Hypervisor", "Xen Project", ... =A0but this does not se= em to work at the
> moment.

I think this would reduce the utility of the "planet", at l= east for me.
e.g. I wouldn't want to subscribe to an rss feed which contained this sort of thing. I want to see actual content by people involved with or
related to the project.

Ian.


--e89a8fb1ef72b1ef2e04e06f5b17-- --===============7588732548655740479== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm --===============7588732548655740479==-- From xen-arm-bounces@lists.xen.org Mon Jul 01 08:54:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 08:54:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZs7-0002Bb-L2; Mon, 01 Jul 2013 08:54:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZs5-0002B3-Da; Mon, 01 Jul 2013 08:54:05 +0000 Received: from [193.109.254.147:58625] by server-8.bemta-14.messagelabs.com id 48/41-19397-CA341D15; Mon, 01 Jul 2013 08:54:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1372668791!8533542!1 X-Originating-IP: [209.85.214.175] X-SpamReason: No, hits=3.1 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,SUSPICIOUS_RECIPS,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17085 invoked from network); 1 Jul 2013 08:53:14 -0000 Received: from mail-ob0-f175.google.com (HELO mail-ob0-f175.google.com) (209.85.214.175) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 08:53:14 -0000 Received: by mail-ob0-f175.google.com with SMTP id xn12so3948465obc.6 for ; Mon, 01 Jul 2013 01:53:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wisM6yUnq7WbMYsFe/5lIVWPhFSXHgvHpMIL0m2zAe8=; b=MUWx668lkd+DnCSgAMZhidFOLceaTInzdjYh8GP3UmHj412YSSoIcqirBOwb3EfFCj aKDlhoiMAfOIr/WlZVMGtHyYCR8OJ+cx+d+CzH4jXlunqkrgY6Dn2JZxMr/f2vAbbS2h 9MkeqaJyEkS8V61U5j0KcBZYwxCqRaQo69oZu8rPbOLhAgQBtf/XBWPK4iP0EMFhZ50g IzpJPuvbTcYYABFHXnXhnAkybd0LTd5jNgMN1mK0TRx9wH0YTYzZhCvAf41ikBmPki6l WhJMiIWx6KmssNsQl85PXpO4M/B6LpeeBHi1ZkiZnGIvjVsup/lhlw1IKZvD3t0mVqAY uRqQ== MIME-Version: 1.0 X-Received: by 10.182.61.19 with SMTP id l19mr10653958obr.55.1372668791220; Mon, 01 Jul 2013 01:53:11 -0700 (PDT) Received: by 10.60.121.6 with HTTP; Mon, 1 Jul 2013 01:53:11 -0700 (PDT) In-Reply-To: <1372667026.14691.16.camel@zakaz.uk.xensource.com> References: <51CDC255.7060902@xen.org> <1372667026.14691.16.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 09:53:11 +0100 Message-ID: From: Lars Kurth To: Ian Campbell Cc: "xen-users@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , publicity@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] First go at Planet Xen ... X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7588732548655740479==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============7588732548655740479== Content-Type: multipart/alternative; boundary=e89a8fb1ef72b1ef2e04e06f5b17 --e89a8fb1ef72b1ef2e04e06f5b17 Content-Type: text/plain; charset=ISO-8859-1 > Is there an RSS link for the planet itself? I couldn't find one. No. I still need to set it up. Didn't get round to it yet. > I think this would reduce the utility of the "planet", at least for me. > e.g. I wouldn't want to subscribe to an rss feed which contained this > sort of thing. I want to see actual content by people involved with or > related to the project. Agreed. In fact this occurred to me after I sent the mail. So I added that feed to http://xenproject.org/about/in-the-news.html There is another question: I had a request from a Brazilian community member (who writes a Portuguese language Xen blog). I am not sure what the feeling with regards to mixing languages is. We could set up different pages for different languages, but the question is whether we get enough feeds to be of use. Any views? Lars On Mon, Jul 1, 2013 at 9:23 AM, Ian Campbell wrote: > On Fri, 2013-06-28 at 18:05 +0100, Lars Kurth wrote: > > Hi all, > > > > I created http://www.xenproject.org/planet-xen.html and we can now add > > blogs from community members and organizations that talk about Xen. You > > can get to it from "Xen Planet" in the global navigation bar from all > > *.xenproject.org sites (or will be able to soon). > > Is there an RSS link for the planet itself? I couldn't find one. > > [...] > > At some point I hope I can include news search query for "Xen > > Hypervisor", "Xen Project", ... but this does not seem to work at the > > moment. > > I think this would reduce the utility of the "planet", at least for me. > e.g. I wouldn't want to subscribe to an rss feed which contained this > sort of thing. I want to see actual content by people involved with or > related to the project. > > Ian. > > --e89a8fb1ef72b1ef2e04e06f5b17 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>=A0Is there an RSS link for the planet itself? I couldn't find on= e.
No. I still need to set it up. Didn't get round to it yet.<= /div>

=
>=A0I think this would reduce the utility of the "planet", at= least for me.
> e.g. I wou= ldn't want to subscribe to an rss feed which contained this
> sort of thing. I wa= nt to see actual content by people involved with or
> related to the project.

There is another question: I had a request = from a Brazilian community member (who writes a Portuguese language Xen blo= g). I am not sure what the feeling with regards to mixing languages is. We = could set up different pages for different languages, but the question is w= hether we get enough feeds to be of use. Any views?

Lars
=

On Mon, Jul 1, 2013 at 9:23 AM, Ian Camp= bell <Ian.Campbell@citrix.com> wrote:
On Fri, 2013-06-28 at 18:0= 5 +0100, Lars Kurth wrote:
> Hi all,
>
> I created http://www.xenproject.org/planet-xen.html and we can now ad= d
> blogs from community members and organizations that talk about Xen. Yo= u
> can get to it from "Xen Planet" in the global navigation bar= from all
> *.xenproject.org sites (or will be able to soon).

Is there an RSS link for the planet itself? I couldn't find one.<= br>
[...]
> At some point I hope I can include news search query= for "Xen
> Hypervisor", "Xen Project", ... =A0but this does not se= em to work at the
> moment.

I think this would reduce the utility of the "planet", at l= east for me.
e.g. I wouldn't want to subscribe to an rss feed which contained this sort of thing. I want to see actual content by people involved with or
related to the project.

Ian.


--e89a8fb1ef72b1ef2e04e06f5b17-- --===============7588732548655740479== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm --===============7588732548655740479==-- From xen-arm-bounces@lists.xen.org Mon Jul 01 08:59:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 08:59:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZwy-00034r-Qo; Mon, 01 Jul 2013 08:59:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZwx-00034N-Mc; Mon, 01 Jul 2013 08:59:07 +0000 Received: from [85.158.143.99:56341] by server-1.bemta-4.messagelabs.com id 56/02-28540-AD441D15; Mon, 01 Jul 2013 08:59:06 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1372669145!21931350!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4776 invoked from network); 1 Jul 2013 08:59:06 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 08:59:06 -0000 X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="6236535" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 08:59:07 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 09:59:05 +0100 Message-ID: <1372669144.14691.40.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Lars Kurth Date: Mon, 1 Jul 2013 09:59:04 +0100 In-Reply-To: References: <51CDC255.7060902@xen.org> <1372667026.14691.16.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: "xen-users@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , publicity@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] First go at Planet Xen ... X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 09:53 +0100, Lars Kurth wrote: > > Is there an RSS link for the planet itself? I couldn't find one. > No. I still need to set it up. Didn't get round to it yet. > > > > I think this would reduce the utility of the "planet", at least for > me. > > e.g. I wouldn't want to subscribe to an rss feed which contained > this > > sort of thing. I want to see actual content by people involved with > or > > related to the project. > Agreed. In fact this occurred to me after I sent the mail. So I added > that feed to http://xenproject.org/about/in-the-news.html Great, thanks. > There is another question: I had a request from a Brazilian community > member (who writes a Portuguese language Xen blog). I am not sure what > the feeling with regards to mixing languages is. We could set up > different pages for different languages, but the question is whether > we get enough feeds to be of use. Any views? Personally I think planets should be single language. Unless it's a lot of administrative faff I don't see why not to have per-language planets. An alternative would be to tag the posts from each constituent feed appropriately such that .../planet/ was everything and .../planet/{en,pt,es}/ etc were only the posts in the given language. Again this depends on the power of the backend. > > Lars > > > On Mon, Jul 1, 2013 at 9:23 AM, Ian Campbell > wrote: > On Fri, 2013-06-28 at 18:05 +0100, Lars Kurth wrote: > > Hi all, > > > > I created http://www.xenproject.org/planet-xen.html and we > can now add > > blogs from community members and organizations that talk > about Xen. You > > can get to it from "Xen Planet" in the global navigation bar > from all > > *.xenproject.org sites (or will be able to soon). > > > Is there an RSS link for the planet itself? I couldn't find > one. > > [...] > > At some point I hope I can include news search query for > "Xen > > Hypervisor", "Xen Project", ... but this does not seem to > work at the > > moment. > > > I think this would reduce the utility of the "planet", at > least for me. > e.g. I wouldn't want to subscribe to an rss feed which > contained this > sort of thing. I want to see actual content by people involved > with or > related to the project. > > Ian. > > > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 08:59:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 08:59:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZwy-00034r-Qo; Mon, 01 Jul 2013 08:59:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtZwx-00034N-Mc; Mon, 01 Jul 2013 08:59:07 +0000 Received: from [85.158.143.99:56341] by server-1.bemta-4.messagelabs.com id 56/02-28540-AD441D15; Mon, 01 Jul 2013 08:59:06 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1372669145!21931350!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4776 invoked from network); 1 Jul 2013 08:59:06 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 08:59:06 -0000 X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="6236535" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 08:59:07 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 09:59:05 +0100 Message-ID: <1372669144.14691.40.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Lars Kurth Date: Mon, 1 Jul 2013 09:59:04 +0100 In-Reply-To: References: <51CDC255.7060902@xen.org> <1372667026.14691.16.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: "xen-users@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , publicity@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] First go at Planet Xen ... X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 09:53 +0100, Lars Kurth wrote: > > Is there an RSS link for the planet itself? I couldn't find one. > No. I still need to set it up. Didn't get round to it yet. > > > > I think this would reduce the utility of the "planet", at least for > me. > > e.g. I wouldn't want to subscribe to an rss feed which contained > this > > sort of thing. I want to see actual content by people involved with > or > > related to the project. > Agreed. In fact this occurred to me after I sent the mail. So I added > that feed to http://xenproject.org/about/in-the-news.html Great, thanks. > There is another question: I had a request from a Brazilian community > member (who writes a Portuguese language Xen blog). I am not sure what > the feeling with regards to mixing languages is. We could set up > different pages for different languages, but the question is whether > we get enough feeds to be of use. Any views? Personally I think planets should be single language. Unless it's a lot of administrative faff I don't see why not to have per-language planets. An alternative would be to tag the posts from each constituent feed appropriately such that .../planet/ was everything and .../planet/{en,pt,es}/ etc were only the posts in the given language. Again this depends on the power of the backend. > > Lars > > > On Mon, Jul 1, 2013 at 9:23 AM, Ian Campbell > wrote: > On Fri, 2013-06-28 at 18:05 +0100, Lars Kurth wrote: > > Hi all, > > > > I created http://www.xenproject.org/planet-xen.html and we > can now add > > blogs from community members and organizations that talk > about Xen. You > > can get to it from "Xen Planet" in the global navigation bar > from all > > *.xenproject.org sites (or will be able to soon). > > > Is there an RSS link for the planet itself? I couldn't find > one. > > [...] > > At some point I hope I can include news search query for > "Xen > > Hypervisor", "Xen Project", ... but this does not seem to > work at the > > moment. > > > I think this would reduce the utility of the "planet", at > least for me. > e.g. I wouldn't want to subscribe to an rss feed which > contained this > sort of thing. I want to see actual content by people involved > with or > related to the project. > > Ian. > > > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 09:19:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 09:19:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtaH5-0004Rj-4k; Mon, 01 Jul 2013 09:19:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtaH3-0004RW-Ft; Mon, 01 Jul 2013 09:19:53 +0000 Received: from [85.158.137.99:3185] by server-10.bemta-3.messagelabs.com id F8/BA-02530-8B941D15; Mon, 01 Jul 2013 09:19:52 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1372670389!15304025!1 X-Originating-IP: [209.85.192.169] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14353 invoked from network); 1 Jul 2013 09:19:51 -0000 Received: from mail-pd0-f169.google.com (HELO mail-pd0-f169.google.com) (209.85.192.169) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 09:19:51 -0000 Received: by mail-pd0-f169.google.com with SMTP id y10so2473610pdj.14 for ; Mon, 01 Jul 2013 02:19:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=EuNNWDWmsvdJMD+qSFxVwMHScWXheiRUSLy82jRj3qU=; b=DCkPd9IJwfbw0gpx+dOPh6d7Q8zYhCmeMHYhBz7cQIzhqi+3JexY+65bsFDNkO2LMJ nwNouv641H+c/Son5nDnsxy4cddH2IMLg5JI2+MAWsXitpb1FIRpKElURnF+d9Q8ABOk ISbOxpLZXqwXe5+c25smkm8gGLVRfA7UUVlgpCbbZ+Ou+BSmjbPItLH/DbkT5u9e/3ol DEz+K2Ru0DyFXKZjMiODGFUPW2q7gPnUjalQdJ8/fdRp+cHJD9ZRQx+QQiBL2cxFMylq Gfy/F7/ARPTWPa4SuS0iej/8HmcaVwfYj3bintBWxa7uyi6KT5JoPRbJ4Ch2fqMikOBP 0/qQ== X-Received: by 10.68.186.193 with SMTP id fm1mr22875050pbc.163.1372670389309; Mon, 01 Jul 2013 02:19:49 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id qe10sm21400361pbb.2.2013.07.01.02.19.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 02:19:48 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372668616.14691.35.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 17:19:27 +0800 Message-Id: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: >> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: >>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: >>>> Hi Ian, >>>> >>>> After enabling the UART, I have been tring to finish the rest of booting. >>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like >>>> following: >>>> >>>> Starting kernel ... >>>> >>>> - UART enabled - >>>> - CPU 00000000 booting - >>>> - Machine ID 00000ec1 - >>>> - Started in Hyp mode - >>>> - Zero BSS - >>>> - Setting up control registers - >>>> - Turning on paging - >>>> - Ready - >>>> RAM: 0000000080000000 - 00000000ffffffff >>>> >>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 >>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 >>>> >>>> What could be the most possible problem of this case? >>> >>> This is a about the point where we would shift from early_printk to the >>> proper console driver, so I expect you simply don't have the console >>> setup. >>> >> Hi Ian, >> >> I guess that it might not all about console driver, because early_printk >> does not work properly just after we have updated "the copy of boot_pgtable >> to use the new paddrs" in setup_pagetables(). It seems that >> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without >> being restored. > > Hrm, I think the expectation is that the fixmap will be copied as part > of that and doesn't need (or receive) any additional fixups (see around > "Link in the fixmap pagetable"), but it is worth checking for sure. > > You could probably profitably sprinkle some more early_print around the > place during that sequence for debugging purposes. That's exactly what I did just now. And it is interesting that early_printk doesn't work just after the updated boot_pgtable (p = (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been accessed (e.g. access to p[i].pt.base). Baozi. > > BTW I've just checked a boot here and after the "Placing Xen" message > there should be two more early_printk's which are the "Xen heap: XXX > pages..." and "Looking for UART.." ones before things switch to the real > console, so you are right that it isn't making it to the real console > driver. > > Ian. > > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 09:19:57 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 09:19:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtaH5-0004Rj-4k; Mon, 01 Jul 2013 09:19:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtaH3-0004RW-Ft; Mon, 01 Jul 2013 09:19:53 +0000 Received: from [85.158.137.99:3185] by server-10.bemta-3.messagelabs.com id F8/BA-02530-8B941D15; Mon, 01 Jul 2013 09:19:52 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1372670389!15304025!1 X-Originating-IP: [209.85.192.169] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14353 invoked from network); 1 Jul 2013 09:19:51 -0000 Received: from mail-pd0-f169.google.com (HELO mail-pd0-f169.google.com) (209.85.192.169) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 09:19:51 -0000 Received: by mail-pd0-f169.google.com with SMTP id y10so2473610pdj.14 for ; Mon, 01 Jul 2013 02:19:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=EuNNWDWmsvdJMD+qSFxVwMHScWXheiRUSLy82jRj3qU=; b=DCkPd9IJwfbw0gpx+dOPh6d7Q8zYhCmeMHYhBz7cQIzhqi+3JexY+65bsFDNkO2LMJ nwNouv641H+c/Son5nDnsxy4cddH2IMLg5JI2+MAWsXitpb1FIRpKElURnF+d9Q8ABOk ISbOxpLZXqwXe5+c25smkm8gGLVRfA7UUVlgpCbbZ+Ou+BSmjbPItLH/DbkT5u9e/3ol DEz+K2Ru0DyFXKZjMiODGFUPW2q7gPnUjalQdJ8/fdRp+cHJD9ZRQx+QQiBL2cxFMylq Gfy/F7/ARPTWPa4SuS0iej/8HmcaVwfYj3bintBWxa7uyi6KT5JoPRbJ4Ch2fqMikOBP 0/qQ== X-Received: by 10.68.186.193 with SMTP id fm1mr22875050pbc.163.1372670389309; Mon, 01 Jul 2013 02:19:49 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id qe10sm21400361pbb.2.2013.07.01.02.19.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 02:19:48 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372668616.14691.35.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 17:19:27 +0800 Message-Id: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: >> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: >>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: >>>> Hi Ian, >>>> >>>> After enabling the UART, I have been tring to finish the rest of booting. >>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like >>>> following: >>>> >>>> Starting kernel ... >>>> >>>> - UART enabled - >>>> - CPU 00000000 booting - >>>> - Machine ID 00000ec1 - >>>> - Started in Hyp mode - >>>> - Zero BSS - >>>> - Setting up control registers - >>>> - Turning on paging - >>>> - Ready - >>>> RAM: 0000000080000000 - 00000000ffffffff >>>> >>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 >>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 >>>> >>>> What could be the most possible problem of this case? >>> >>> This is a about the point where we would shift from early_printk to the >>> proper console driver, so I expect you simply don't have the console >>> setup. >>> >> Hi Ian, >> >> I guess that it might not all about console driver, because early_printk >> does not work properly just after we have updated "the copy of boot_pgtable >> to use the new paddrs" in setup_pagetables(). It seems that >> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without >> being restored. > > Hrm, I think the expectation is that the fixmap will be copied as part > of that and doesn't need (or receive) any additional fixups (see around > "Link in the fixmap pagetable"), but it is worth checking for sure. > > You could probably profitably sprinkle some more early_print around the > place during that sequence for debugging purposes. That's exactly what I did just now. And it is interesting that early_printk doesn't work just after the updated boot_pgtable (p = (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been accessed (e.g. access to p[i].pt.base). Baozi. > > BTW I've just checked a boot here and after the "Placing Xen" message > there should be two more early_printk's which are the "Xen heap: XXX > pages..." and "Looking for UART.." ones before things switch to the real > console, so you are right that it isn't making it to the real console > driver. > > Ian. > > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 09:30:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 09:30:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtaRW-00053T-07; Mon, 01 Jul 2013 09:30:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtaRU-00053H-LN; Mon, 01 Jul 2013 09:30:40 +0000 Received: from [85.158.138.51:28860] by server-8.bemta-3.messagelabs.com id D2/DE-18692-F3C41D15; Mon, 01 Jul 2013 09:30:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1372671038!29502116!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25034 invoked from network); 1 Jul 2013 09:30:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 09:30:39 -0000 X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="6238523" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 09:30:39 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 10:30:38 +0100 Message-ID: <1372671036.14691.49.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 10:30:36 +0100 In-Reply-To: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: > > > On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: > >> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > >>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > >>>> Hi Ian, > >>>> > >>>> After enabling the UART, I have been tring to finish the rest of booting. > >>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like > >>>> following: > >>>> > >>>> Starting kernel ... > >>>> > >>>> - UART enabled - > >>>> - CPU 00000000 booting - > >>>> - Machine ID 00000ec1 - > >>>> - Started in Hyp mode - > >>>> - Zero BSS - > >>>> - Setting up control registers - > >>>> - Turning on paging - > >>>> - Ready - > >>>> RAM: 0000000080000000 - 00000000ffffffff > >>>> > >>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 > >>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 > >>>> > >>>> What could be the most possible problem of this case? > >>> > >>> This is a about the point where we would shift from early_printk to the > >>> proper console driver, so I expect you simply don't have the console > >>> setup. > >>> > >> Hi Ian, > >> > >> I guess that it might not all about console driver, because early_printk > >> does not work properly just after we have updated "the copy of boot_pgtable > >> to use the new paddrs" in setup_pagetables(). It seems that > >> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without > >> being restored. > > > > Hrm, I think the expectation is that the fixmap will be copied as part > > of that and doesn't need (or receive) any additional fixups (see around > > "Link in the fixmap pagetable"), but it is worth checking for sure. > > > > You could probably profitably sprinkle some more early_print around the > > place during that sequence for debugging purposes. > That's exactly what I did just now. And it is interesting that > early_printk doesn't work just after the updated boot_pgtable (p = > (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been > accessed (e.g. access to p[i].pt.base). How odd, that set of tables isn't even used until the call to WRITE_TTBR several lines below! I'm pretty certain it isn't updating anything which is live. Unless perhaps the new destination overlaps the current location of Xen, I bet we don't handle that case well... Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 09:30:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 09:30:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtaRW-00053T-07; Mon, 01 Jul 2013 09:30:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtaRU-00053H-LN; Mon, 01 Jul 2013 09:30:40 +0000 Received: from [85.158.138.51:28860] by server-8.bemta-3.messagelabs.com id D2/DE-18692-F3C41D15; Mon, 01 Jul 2013 09:30:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1372671038!29502116!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25034 invoked from network); 1 Jul 2013 09:30:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 09:30:39 -0000 X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="6238523" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 09:30:39 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 10:30:38 +0100 Message-ID: <1372671036.14691.49.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 10:30:36 +0100 In-Reply-To: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: > > > On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: > >> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > >>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > >>>> Hi Ian, > >>>> > >>>> After enabling the UART, I have been tring to finish the rest of booting. > >>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like > >>>> following: > >>>> > >>>> Starting kernel ... > >>>> > >>>> - UART enabled - > >>>> - CPU 00000000 booting - > >>>> - Machine ID 00000ec1 - > >>>> - Started in Hyp mode - > >>>> - Zero BSS - > >>>> - Setting up control registers - > >>>> - Turning on paging - > >>>> - Ready - > >>>> RAM: 0000000080000000 - 00000000ffffffff > >>>> > >>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 > >>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 > >>>> > >>>> What could be the most possible problem of this case? > >>> > >>> This is a about the point where we would shift from early_printk to the > >>> proper console driver, so I expect you simply don't have the console > >>> setup. > >>> > >> Hi Ian, > >> > >> I guess that it might not all about console driver, because early_printk > >> does not work properly just after we have updated "the copy of boot_pgtable > >> to use the new paddrs" in setup_pagetables(). It seems that > >> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without > >> being restored. > > > > Hrm, I think the expectation is that the fixmap will be copied as part > > of that and doesn't need (or receive) any additional fixups (see around > > "Link in the fixmap pagetable"), but it is worth checking for sure. > > > > You could probably profitably sprinkle some more early_print around the > > place during that sequence for debugging purposes. > That's exactly what I did just now. And it is interesting that > early_printk doesn't work just after the updated boot_pgtable (p = > (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been > accessed (e.g. access to p[i].pt.base). How odd, that set of tables isn't even used until the call to WRITE_TTBR several lines below! I'm pretty certain it isn't updating anything which is live. Unless perhaps the new destination overlaps the current location of Xen, I bet we don't handle that case well... Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 09:49:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 09:49:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utajh-0005gr-BA; Mon, 01 Jul 2013 09:49:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utajf-0005gZ-Op; Mon, 01 Jul 2013 09:49:27 +0000 Received: from [85.158.138.51:18685] by server-10.bemta-3.messagelabs.com id 06/7D-02530-6A051D15; Mon, 01 Jul 2013 09:49:26 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1372672163!21448111!1 X-Originating-IP: [209.85.220.41] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21544 invoked from network); 1 Jul 2013 09:49:25 -0000 Received: from mail-pa0-f41.google.com (HELO mail-pa0-f41.google.com) (209.85.220.41) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 09:49:25 -0000 Received: by mail-pa0-f41.google.com with SMTP id bj3so4868472pad.28 for ; Mon, 01 Jul 2013 02:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=DvFg0LOkqTD30Ra26/Y4EHkxaHj44AnVaPjzSFLV5a8=; b=bV/iRe3iCEPKNthmE+jb6mboY0EAHGBbTmoalYpwOVbysw6VDNJamOFYTdsGmYzxs3 oGZu1X7QKwvfQ8uwRiCKcLw/rU92xZPI2xVMXOA33NC9ICMHIUhy/RyVb3VROef2BoMX A5DWgK9IhmxzSLKNe5Cm0ZKlHepR7GBEWLAmqSIesos7QI4Qs18tt7p4lya88oPmWJ6r HwMriCc0yvlTdTZSHaFdDB0ogBfeefUOepwUEYAKP3b+ArPLXmOJnK5riv2+p+s+rT4+ 2VQqh1tAaIGSM+uy1woYpEK3BA+iCm8Iji+DfVdTuotW7fQxGpMZlud4qBTPQdSYGcBr 2Lrg== X-Received: by 10.68.41.106 with SMTP id e10mr23337316pbl.136.1372672163410; Mon, 01 Jul 2013 02:49:23 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id 4sm6182625pbw.32.2013.07.01.02.49.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 02:49:22 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372671036.14691.49.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 17:49:13 +0800 Message-Id: References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: >> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: >> >>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: >>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: >>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: >>>>>> Hi Ian, >>>>>> >>>>>> After enabling the UART, I have been tring to finish the rest of booting. >>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like >>>>>> following: >>>>>> >>>>>> Starting kernel ... >>>>>> >>>>>> - UART enabled - >>>>>> - CPU 00000000 booting - >>>>>> - Machine ID 00000ec1 - >>>>>> - Started in Hyp mode - >>>>>> - Zero BSS - >>>>>> - Setting up control registers - >>>>>> - Turning on paging - >>>>>> - Ready - >>>>>> RAM: 0000000080000000 - 00000000ffffffff >>>>>> >>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 >>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 >>>>>> >>>>>> What could be the most possible problem of this case? >>>>> >>>>> This is a about the point where we would shift from early_printk to the >>>>> proper console driver, so I expect you simply don't have the console >>>>> setup. >>>>> >>>> Hi Ian, >>>> >>>> I guess that it might not all about console driver, because early_printk >>>> does not work properly just after we have updated "the copy of boot_pgtable >>>> to use the new paddrs" in setup_pagetables(). It seems that >>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without >>>> being restored. >>> >>> Hrm, I think the expectation is that the fixmap will be copied as part >>> of that and doesn't need (or receive) any additional fixups (see around >>> "Link in the fixmap pagetable"), but it is worth checking for sure. >>> >>> You could probably profitably sprinkle some more early_print around the >>> place during that sequence for debugging purposes. >> That's exactly what I did just now. And it is interesting that >> early_printk doesn't work just after the updated boot_pgtable (p = >> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been >> accessed (e.g. access to p[i].pt.base). > > How odd, that set of tables isn't even used until the call to WRITE_TTBR > several lines below! I'm pretty certain it isn't updating anything which > is live. Yes. And I found it happened even if reading the p[i].pt.base. I have tried to print the p[i].pt.base before updating its content. Then, all the early_printk would fail after it. > > Unless perhaps the new destination overlaps the current location of Xen, > I bet we don't handle that case well... > > Ian. > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 09:49:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 09:49:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utajh-0005gr-BA; Mon, 01 Jul 2013 09:49:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utajf-0005gZ-Op; Mon, 01 Jul 2013 09:49:27 +0000 Received: from [85.158.138.51:18685] by server-10.bemta-3.messagelabs.com id 06/7D-02530-6A051D15; Mon, 01 Jul 2013 09:49:26 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1372672163!21448111!1 X-Originating-IP: [209.85.220.41] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21544 invoked from network); 1 Jul 2013 09:49:25 -0000 Received: from mail-pa0-f41.google.com (HELO mail-pa0-f41.google.com) (209.85.220.41) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 09:49:25 -0000 Received: by mail-pa0-f41.google.com with SMTP id bj3so4868472pad.28 for ; Mon, 01 Jul 2013 02:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=DvFg0LOkqTD30Ra26/Y4EHkxaHj44AnVaPjzSFLV5a8=; b=bV/iRe3iCEPKNthmE+jb6mboY0EAHGBbTmoalYpwOVbysw6VDNJamOFYTdsGmYzxs3 oGZu1X7QKwvfQ8uwRiCKcLw/rU92xZPI2xVMXOA33NC9ICMHIUhy/RyVb3VROef2BoMX A5DWgK9IhmxzSLKNe5Cm0ZKlHepR7GBEWLAmqSIesos7QI4Qs18tt7p4lya88oPmWJ6r HwMriCc0yvlTdTZSHaFdDB0ogBfeefUOepwUEYAKP3b+ArPLXmOJnK5riv2+p+s+rT4+ 2VQqh1tAaIGSM+uy1woYpEK3BA+iCm8Iji+DfVdTuotW7fQxGpMZlud4qBTPQdSYGcBr 2Lrg== X-Received: by 10.68.41.106 with SMTP id e10mr23337316pbl.136.1372672163410; Mon, 01 Jul 2013 02:49:23 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id 4sm6182625pbw.32.2013.07.01.02.49.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 02:49:22 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372671036.14691.49.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 17:49:13 +0800 Message-Id: References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: >> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: >> >>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: >>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: >>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: >>>>>> Hi Ian, >>>>>> >>>>>> After enabling the UART, I have been tring to finish the rest of booting. >>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like >>>>>> following: >>>>>> >>>>>> Starting kernel ... >>>>>> >>>>>> - UART enabled - >>>>>> - CPU 00000000 booting - >>>>>> - Machine ID 00000ec1 - >>>>>> - Started in Hyp mode - >>>>>> - Zero BSS - >>>>>> - Setting up control registers - >>>>>> - Turning on paging - >>>>>> - Ready - >>>>>> RAM: 0000000080000000 - 00000000ffffffff >>>>>> >>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 >>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 >>>>>> >>>>>> What could be the most possible problem of this case? >>>>> >>>>> This is a about the point where we would shift from early_printk to the >>>>> proper console driver, so I expect you simply don't have the console >>>>> setup. >>>>> >>>> Hi Ian, >>>> >>>> I guess that it might not all about console driver, because early_printk >>>> does not work properly just after we have updated "the copy of boot_pgtable >>>> to use the new paddrs" in setup_pagetables(). It seems that >>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without >>>> being restored. >>> >>> Hrm, I think the expectation is that the fixmap will be copied as part >>> of that and doesn't need (or receive) any additional fixups (see around >>> "Link in the fixmap pagetable"), but it is worth checking for sure. >>> >>> You could probably profitably sprinkle some more early_print around the >>> place during that sequence for debugging purposes. >> That's exactly what I did just now. And it is interesting that >> early_printk doesn't work just after the updated boot_pgtable (p = >> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been >> accessed (e.g. access to p[i].pt.base). > > How odd, that set of tables isn't even used until the call to WRITE_TTBR > several lines below! I'm pretty certain it isn't updating anything which > is live. Yes. And I found it happened even if reading the p[i].pt.base. I have tried to print the p[i].pt.base before updating its content. Then, all the early_printk would fail after it. > > Unless perhaps the new destination overlaps the current location of Xen, > I bet we don't handle that case well... > > Ian. > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 09:58:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 09:58:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utas0-0006I5-0c; Mon, 01 Jul 2013 09:58:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utarz-0006Hr-3v; Mon, 01 Jul 2013 09:58:03 +0000 Received: from [85.158.139.83:17645] by server-9.bemta-5.messagelabs.com id 40/07-26025-AA251D15; Mon, 01 Jul 2013 09:58:02 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1372672681!28768389!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31774 invoked from network); 1 Jul 2013 09:58:01 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 09:58:01 -0000 X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="6239643" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 09:58:02 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 10:58:00 +0100 Message-ID: <1372672679.14691.50.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 10:57:59 +0100 In-Reply-To: References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 17:49 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: > > > On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: > >> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: > >> > >>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: > >>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > >>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > >>>>>> Hi Ian, > >>>>>> > >>>>>> After enabling the UART, I have been tring to finish the rest of booting. > >>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like > >>>>>> following: > >>>>>> > >>>>>> Starting kernel ... > >>>>>> > >>>>>> - UART enabled - > >>>>>> - CPU 00000000 booting - > >>>>>> - Machine ID 00000ec1 - > >>>>>> - Started in Hyp mode - > >>>>>> - Zero BSS - > >>>>>> - Setting up control registers - > >>>>>> - Turning on paging - > >>>>>> - Ready - > >>>>>> RAM: 0000000080000000 - 00000000ffffffff > >>>>>> > >>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 > >>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 > >>>>>> > >>>>>> What could be the most possible problem of this case? > >>>>> > >>>>> This is a about the point where we would shift from early_printk to the > >>>>> proper console driver, so I expect you simply don't have the console > >>>>> setup. > >>>>> > >>>> Hi Ian, > >>>> > >>>> I guess that it might not all about console driver, because early_printk > >>>> does not work properly just after we have updated "the copy of boot_pgtable > >>>> to use the new paddrs" in setup_pagetables(). It seems that > >>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without > >>>> being restored. > >>> > >>> Hrm, I think the expectation is that the fixmap will be copied as part > >>> of that and doesn't need (or receive) any additional fixups (see around > >>> "Link in the fixmap pagetable"), but it is worth checking for sure. > >>> > >>> You could probably profitably sprinkle some more early_print around the > >>> place during that sequence for debugging purposes. > >> That's exactly what I did just now. And it is interesting that > >> early_printk doesn't work just after the updated boot_pgtable (p = > >> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been > >> accessed (e.g. access to p[i].pt.base). > > > > How odd, that set of tables isn't even used until the call to WRITE_TTBR > > several lines below! I'm pretty certain it isn't updating anything which > > is live. > Yes. And I found it happened even if reading the p[i].pt.base. I have > tried to print the p[i].pt.base before updating its content. Then, > all the early_printk would fail after it. That's just weird. Any chance that reading/writing p[i]...base is actually causing a fault of some description such that the following prints never even get run? _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 09:58:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 09:58:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utas0-0006I5-0c; Mon, 01 Jul 2013 09:58:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utarz-0006Hr-3v; Mon, 01 Jul 2013 09:58:03 +0000 Received: from [85.158.139.83:17645] by server-9.bemta-5.messagelabs.com id 40/07-26025-AA251D15; Mon, 01 Jul 2013 09:58:02 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1372672681!28768389!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31774 invoked from network); 1 Jul 2013 09:58:01 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 09:58:01 -0000 X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="6239643" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 09:58:02 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 10:58:00 +0100 Message-ID: <1372672679.14691.50.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 10:57:59 +0100 In-Reply-To: References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 17:49 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: > > > On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: > >> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: > >> > >>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: > >>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > >>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > >>>>>> Hi Ian, > >>>>>> > >>>>>> After enabling the UART, I have been tring to finish the rest of booting. > >>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like > >>>>>> following: > >>>>>> > >>>>>> Starting kernel ... > >>>>>> > >>>>>> - UART enabled - > >>>>>> - CPU 00000000 booting - > >>>>>> - Machine ID 00000ec1 - > >>>>>> - Started in Hyp mode - > >>>>>> - Zero BSS - > >>>>>> - Setting up control registers - > >>>>>> - Turning on paging - > >>>>>> - Ready - > >>>>>> RAM: 0000000080000000 - 00000000ffffffff > >>>>>> > >>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 > >>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 > >>>>>> > >>>>>> What could be the most possible problem of this case? > >>>>> > >>>>> This is a about the point where we would shift from early_printk to the > >>>>> proper console driver, so I expect you simply don't have the console > >>>>> setup. > >>>>> > >>>> Hi Ian, > >>>> > >>>> I guess that it might not all about console driver, because early_printk > >>>> does not work properly just after we have updated "the copy of boot_pgtable > >>>> to use the new paddrs" in setup_pagetables(). It seems that > >>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without > >>>> being restored. > >>> > >>> Hrm, I think the expectation is that the fixmap will be copied as part > >>> of that and doesn't need (or receive) any additional fixups (see around > >>> "Link in the fixmap pagetable"), but it is worth checking for sure. > >>> > >>> You could probably profitably sprinkle some more early_print around the > >>> place during that sequence for debugging purposes. > >> That's exactly what I did just now. And it is interesting that > >> early_printk doesn't work just after the updated boot_pgtable (p = > >> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been > >> accessed (e.g. access to p[i].pt.base). > > > > How odd, that set of tables isn't even used until the call to WRITE_TTBR > > several lines below! I'm pretty certain it isn't updating anything which > > is live. > Yes. And I found it happened even if reading the p[i].pt.base. I have > tried to print the p[i].pt.base before updating its content. Then, > all the early_printk would fail after it. That's just weird. Any chance that reading/writing p[i]...base is actually causing a fault of some description such that the following prints never even get run? _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 11:19:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 11:19:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utc8c-00087K-AU; Mon, 01 Jul 2013 11:19:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utc8a-000878-Mo; Mon, 01 Jul 2013 11:19:16 +0000 Received: from [85.158.143.99:7046] by server-2.bemta-4.messagelabs.com id CD/E0-09492-3B561D15; Mon, 01 Jul 2013 11:19:15 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1372677553!24207291!1 X-Originating-IP: [209.85.220.48] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16772 invoked from network); 1 Jul 2013 11:19:15 -0000 Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com) (209.85.220.48) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 11:19:15 -0000 Received: by mail-pa0-f48.google.com with SMTP id kp12so4860820pab.7 for ; Mon, 01 Jul 2013 04:19:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=IDXoWinMT6Z2Stgo/J3rtUPQWSKld6mzN0s+ufpDtaA=; b=feoATgoPmoU5uk+M0VHT1chDJKRDv3aLIAAAOZbiIwzlWrwlz0y3ngLTQnPLTIr9o9 8Wqhx4gaQkFa0Jbu4O22CnNC1eAtoe577ZgAW5Ib/QL1l28auZUhuWC1qZzZU2whKVxj rfNMkReabgcXCkZXMcsOO+kqmzsUEeVvUxGVaL9qzGNAb+0WfAXwoTQIgV02OOk+ZA4g JXBd2p+FPnnKTLJhNqzHEQzyeLneMFrHs63hSUHwFzMUkFQHoE6TAr6wxm77ehoRrjOZ fSqKdIRfyhFbzvC8AzFBvapk+cjkYpCBVuRmO70nDbzZxOP0qfWhJYZ+Wvn+WebZtQRo mCKg== X-Received: by 10.68.131.168 with SMTP id on8mr23302443pbb.97.1372677552902; Mon, 01 Jul 2013 04:19:12 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id oy10sm23472178pac.9.2013.07.01.04.18.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 04:19:12 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372672679.14691.50.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 19:18:39 +0800 Message-Id: <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 5:57 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 17:49 +0800, Chen Baozi wrote: >> On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: >> >>> On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: >>>> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: >>>> >>>>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: >>>>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: >>>>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: >>>>>>>> Hi Ian, >>>>>>>> >>>>>>>> After enabling the UART, I have been tring to finish the rest of booting. >>>>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like >>>>>>>> following: >>>>>>>> >>>>>>>> Starting kernel ... >>>>>>>> >>>>>>>> - UART enabled - >>>>>>>> - CPU 00000000 booting - >>>>>>>> - Machine ID 00000ec1 - >>>>>>>> - Started in Hyp mode - >>>>>>>> - Zero BSS - >>>>>>>> - Setting up control registers - >>>>>>>> - Turning on paging - >>>>>>>> - Ready - >>>>>>>> RAM: 0000000080000000 - 00000000ffffffff >>>>>>>> >>>>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 >>>>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 >>>>>>>> >>>>>>>> What could be the most possible problem of this case? >>>>>>> >>>>>>> This is a about the point where we would shift from early_printk to the >>>>>>> proper console driver, so I expect you simply don't have the console >>>>>>> setup. >>>>>>> >>>>>> Hi Ian, >>>>>> >>>>>> I guess that it might not all about console driver, because early_printk >>>>>> does not work properly just after we have updated "the copy of boot_pgtable >>>>>> to use the new paddrs" in setup_pagetables(). It seems that >>>>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without >>>>>> being restored. >>>>> >>>>> Hrm, I think the expectation is that the fixmap will be copied as part >>>>> of that and doesn't need (or receive) any additional fixups (see around >>>>> "Link in the fixmap pagetable"), but it is worth checking for sure. >>>>> >>>>> You could probably profitably sprinkle some more early_print around the >>>>> place during that sequence for debugging purposes. >>>> That's exactly what I did just now. And it is interesting that >>>> early_printk doesn't work just after the updated boot_pgtable (p = >>>> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been >>>> accessed (e.g. access to p[i].pt.base). >>> >>> How odd, that set of tables isn't even used until the call to WRITE_TTBR >>> several lines below! I'm pretty certain it isn't updating anything which >>> is live. >> Yes. And I found it happened even if reading the p[i].pt.base. I have >> tried to print the p[i].pt.base before updating its content. Then, >> all the early_printk would fail after it. > > That's just weird. Any chance that reading/writing p[i]...base is > actually causing a fault of some description such that the following > prints never even get run? Yes. But it is OK if we don't access the its copy in "early boot misc" area. for example: 01 memcpy((void *) dest_va, _start, _end - _start); 02 03 p = (void *) boot_pgtable; 04 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); 05 06 p = (void *) boot_pgtable + dest_va - (unsigned long)_start; 07 early_printk("hello 1?\n"); 08 early_printk("p: 0x%lx\n", (unsigned long)p); 09 early_printk("hello 2?\n"); 10 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); 11 early_printk("hello 3?\n"); Output: p[0].pt.base: 0x802cc hello 1? p: 0x6d2000 hello 2? _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 11:19:21 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 11:19:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utc8c-00087K-AU; Mon, 01 Jul 2013 11:19:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utc8a-000878-Mo; Mon, 01 Jul 2013 11:19:16 +0000 Received: from [85.158.143.99:7046] by server-2.bemta-4.messagelabs.com id CD/E0-09492-3B561D15; Mon, 01 Jul 2013 11:19:15 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1372677553!24207291!1 X-Originating-IP: [209.85.220.48] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16772 invoked from network); 1 Jul 2013 11:19:15 -0000 Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com) (209.85.220.48) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 11:19:15 -0000 Received: by mail-pa0-f48.google.com with SMTP id kp12so4860820pab.7 for ; Mon, 01 Jul 2013 04:19:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=IDXoWinMT6Z2Stgo/J3rtUPQWSKld6mzN0s+ufpDtaA=; b=feoATgoPmoU5uk+M0VHT1chDJKRDv3aLIAAAOZbiIwzlWrwlz0y3ngLTQnPLTIr9o9 8Wqhx4gaQkFa0Jbu4O22CnNC1eAtoe577ZgAW5Ib/QL1l28auZUhuWC1qZzZU2whKVxj rfNMkReabgcXCkZXMcsOO+kqmzsUEeVvUxGVaL9qzGNAb+0WfAXwoTQIgV02OOk+ZA4g JXBd2p+FPnnKTLJhNqzHEQzyeLneMFrHs63hSUHwFzMUkFQHoE6TAr6wxm77ehoRrjOZ fSqKdIRfyhFbzvC8AzFBvapk+cjkYpCBVuRmO70nDbzZxOP0qfWhJYZ+Wvn+WebZtQRo mCKg== X-Received: by 10.68.131.168 with SMTP id on8mr23302443pbb.97.1372677552902; Mon, 01 Jul 2013 04:19:12 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id oy10sm23472178pac.9.2013.07.01.04.18.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 04:19:12 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372672679.14691.50.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 19:18:39 +0800 Message-Id: <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 5:57 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 17:49 +0800, Chen Baozi wrote: >> On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: >> >>> On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: >>>> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: >>>> >>>>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: >>>>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: >>>>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: >>>>>>>> Hi Ian, >>>>>>>> >>>>>>>> After enabling the UART, I have been tring to finish the rest of booting. >>>>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like >>>>>>>> following: >>>>>>>> >>>>>>>> Starting kernel ... >>>>>>>> >>>>>>>> - UART enabled - >>>>>>>> - CPU 00000000 booting - >>>>>>>> - Machine ID 00000ec1 - >>>>>>>> - Started in Hyp mode - >>>>>>>> - Zero BSS - >>>>>>>> - Setting up control registers - >>>>>>>> - Turning on paging - >>>>>>>> - Ready - >>>>>>>> RAM: 0000000080000000 - 00000000ffffffff >>>>>>>> >>>>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 >>>>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 >>>>>>>> >>>>>>>> What could be the most possible problem of this case? >>>>>>> >>>>>>> This is a about the point where we would shift from early_printk to the >>>>>>> proper console driver, so I expect you simply don't have the console >>>>>>> setup. >>>>>>> >>>>>> Hi Ian, >>>>>> >>>>>> I guess that it might not all about console driver, because early_printk >>>>>> does not work properly just after we have updated "the copy of boot_pgtable >>>>>> to use the new paddrs" in setup_pagetables(). It seems that >>>>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without >>>>>> being restored. >>>>> >>>>> Hrm, I think the expectation is that the fixmap will be copied as part >>>>> of that and doesn't need (or receive) any additional fixups (see around >>>>> "Link in the fixmap pagetable"), but it is worth checking for sure. >>>>> >>>>> You could probably profitably sprinkle some more early_print around the >>>>> place during that sequence for debugging purposes. >>>> That's exactly what I did just now. And it is interesting that >>>> early_printk doesn't work just after the updated boot_pgtable (p = >>>> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been >>>> accessed (e.g. access to p[i].pt.base). >>> >>> How odd, that set of tables isn't even used until the call to WRITE_TTBR >>> several lines below! I'm pretty certain it isn't updating anything which >>> is live. >> Yes. And I found it happened even if reading the p[i].pt.base. I have >> tried to print the p[i].pt.base before updating its content. Then, >> all the early_printk would fail after it. > > That's just weird. Any chance that reading/writing p[i]...base is > actually causing a fault of some description such that the following > prints never even get run? Yes. But it is OK if we don't access the its copy in "early boot misc" area. for example: 01 memcpy((void *) dest_va, _start, _end - _start); 02 03 p = (void *) boot_pgtable; 04 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); 05 06 p = (void *) boot_pgtable + dest_va - (unsigned long)_start; 07 early_printk("hello 1?\n"); 08 early_printk("p: 0x%lx\n", (unsigned long)p); 09 early_printk("hello 2?\n"); 10 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); 11 early_printk("hello 3?\n"); Output: p[0].pt.base: 0x802cc hello 1? p: 0x6d2000 hello 2? _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 11:31:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 11:31:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtcKb-0000as-Tx; Mon, 01 Jul 2013 11:31:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtcKa-0000ab-MN; Mon, 01 Jul 2013 11:31:40 +0000 Received: from [85.158.136.67:47227] by server-15.bemta-5.messagelabs.com id 5D/03-01226-B9861D15; Mon, 01 Jul 2013 11:31:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-207.messagelabs.com!1372678299!27728207!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24462 invoked from network); 1 Jul 2013 11:31:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-207.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 11:31:39 -0000 X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="6243566" Received: from lonpex01cl02.citrite.net ([10.30.203.102]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 11:31:39 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL02.citrite.net (10.30.203.102) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 12:31:38 +0100 Message-ID: <1372678297.14691.61.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 12:31:37 +0100 In-Reply-To: <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 19:18 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 5:57 PM, Ian Campbell wrote: > > > On Mon, 2013-07-01 at 17:49 +0800, Chen Baozi wrote: > >> On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: > >> > >>> On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: > >>>> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: > >>>> > >>>>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: > >>>>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > >>>>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > >>>>>>>> Hi Ian, > >>>>>>>> > >>>>>>>> After enabling the UART, I have been tring to finish the rest of booting. > >>>>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like > >>>>>>>> following: > >>>>>>>> > >>>>>>>> Starting kernel ... > >>>>>>>> > >>>>>>>> - UART enabled - > >>>>>>>> - CPU 00000000 booting - > >>>>>>>> - Machine ID 00000ec1 - > >>>>>>>> - Started in Hyp mode - > >>>>>>>> - Zero BSS - > >>>>>>>> - Setting up control registers - > >>>>>>>> - Turning on paging - > >>>>>>>> - Ready - > >>>>>>>> RAM: 0000000080000000 - 00000000ffffffff > >>>>>>>> > >>>>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 > >>>>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 > >>>>>>>> > >>>>>>>> What could be the most possible problem of this case? > >>>>>>> > >>>>>>> This is a about the point where we would shift from early_printk to the > >>>>>>> proper console driver, so I expect you simply don't have the console > >>>>>>> setup. > >>>>>>> > >>>>>> Hi Ian, > >>>>>> > >>>>>> I guess that it might not all about console driver, because early_printk > >>>>>> does not work properly just after we have updated "the copy of boot_pgtable > >>>>>> to use the new paddrs" in setup_pagetables(). It seems that > >>>>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without > >>>>>> being restored. > >>>>> > >>>>> Hrm, I think the expectation is that the fixmap will be copied as part > >>>>> of that and doesn't need (or receive) any additional fixups (see around > >>>>> "Link in the fixmap pagetable"), but it is worth checking for sure. > >>>>> > >>>>> You could probably profitably sprinkle some more early_print around the > >>>>> place during that sequence for debugging purposes. > >>>> That's exactly what I did just now. And it is interesting that > >>>> early_printk doesn't work just after the updated boot_pgtable (p = > >>>> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been > >>>> accessed (e.g. access to p[i].pt.base). > >>> > >>> How odd, that set of tables isn't even used until the call to WRITE_TTBR > >>> several lines below! I'm pretty certain it isn't updating anything which > >>> is live. > >> Yes. And I found it happened even if reading the p[i].pt.base. I have > >> tried to print the p[i].pt.base before updating its content. Then, > >> all the early_printk would fail after it. > > > > That's just weird. Any chance that reading/writing p[i]...base is > > actually causing a fault of some description such that the following > > prints never even get run? > Yes. Random stab in the dark: are you loading the Xen binary at a 2MB aligned address? > But it is OK if we don't access the its copy in "early boot misc" area. for example: > > 01 memcpy((void *) dest_va, _start, _end - _start); > 02 > 03 p = (void *) boot_pgtable; > 04 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); > 05 > 06 p = (void *) boot_pgtable + dest_va - (unsigned long)_start; > 07 early_printk("hello 1?\n"); > 08 early_printk("p: 0x%lx\n", (unsigned long)p); > 09 early_printk("hello 2?\n"); > 10 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); > 11 early_printk("hello 3?\n"); > > Output: > > p[0].pt.base: 0x802cc > hello 1? > p: 0x6d2000 > hello 2? So it is more than likely faulting on the access at 10. I don't suppose you have a hardware debugger? You device has 2GB RAM, what happens if you hack the DTS to say it only has 1GB? Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 11:31:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 11:31:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtcKb-0000as-Tx; Mon, 01 Jul 2013 11:31:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtcKa-0000ab-MN; Mon, 01 Jul 2013 11:31:40 +0000 Received: from [85.158.136.67:47227] by server-15.bemta-5.messagelabs.com id 5D/03-01226-B9861D15; Mon, 01 Jul 2013 11:31:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-207.messagelabs.com!1372678299!27728207!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24462 invoked from network); 1 Jul 2013 11:31:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-207.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 11:31:39 -0000 X-IronPort-AV: E=Sophos;i="4.87,973,1363132800"; d="scan'208";a="6243566" Received: from lonpex01cl02.citrite.net ([10.30.203.102]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 11:31:39 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL02.citrite.net (10.30.203.102) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 12:31:38 +0100 Message-ID: <1372678297.14691.61.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 12:31:37 +0100 In-Reply-To: <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 19:18 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 5:57 PM, Ian Campbell wrote: > > > On Mon, 2013-07-01 at 17:49 +0800, Chen Baozi wrote: > >> On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: > >> > >>> On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: > >>>> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: > >>>> > >>>>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: > >>>>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: > >>>>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: > >>>>>>>> Hi Ian, > >>>>>>>> > >>>>>>>> After enabling the UART, I have been tring to finish the rest of booting. > >>>>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like > >>>>>>>> following: > >>>>>>>> > >>>>>>>> Starting kernel ... > >>>>>>>> > >>>>>>>> - UART enabled - > >>>>>>>> - CPU 00000000 booting - > >>>>>>>> - Machine ID 00000ec1 - > >>>>>>>> - Started in Hyp mode - > >>>>>>>> - Zero BSS - > >>>>>>>> - Setting up control registers - > >>>>>>>> - Turning on paging - > >>>>>>>> - Ready - > >>>>>>>> RAM: 0000000080000000 - 00000000ffffffff > >>>>>>>> > >>>>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 > >>>>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 > >>>>>>>> > >>>>>>>> What could be the most possible problem of this case? > >>>>>>> > >>>>>>> This is a about the point where we would shift from early_printk to the > >>>>>>> proper console driver, so I expect you simply don't have the console > >>>>>>> setup. > >>>>>>> > >>>>>> Hi Ian, > >>>>>> > >>>>>> I guess that it might not all about console driver, because early_printk > >>>>>> does not work properly just after we have updated "the copy of boot_pgtable > >>>>>> to use the new paddrs" in setup_pagetables(). It seems that > >>>>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without > >>>>>> being restored. > >>>>> > >>>>> Hrm, I think the expectation is that the fixmap will be copied as part > >>>>> of that and doesn't need (or receive) any additional fixups (see around > >>>>> "Link in the fixmap pagetable"), but it is worth checking for sure. > >>>>> > >>>>> You could probably profitably sprinkle some more early_print around the > >>>>> place during that sequence for debugging purposes. > >>>> That's exactly what I did just now. And it is interesting that > >>>> early_printk doesn't work just after the updated boot_pgtable (p = > >>>> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been > >>>> accessed (e.g. access to p[i].pt.base). > >>> > >>> How odd, that set of tables isn't even used until the call to WRITE_TTBR > >>> several lines below! I'm pretty certain it isn't updating anything which > >>> is live. > >> Yes. And I found it happened even if reading the p[i].pt.base. I have > >> tried to print the p[i].pt.base before updating its content. Then, > >> all the early_printk would fail after it. > > > > That's just weird. Any chance that reading/writing p[i]...base is > > actually causing a fault of some description such that the following > > prints never even get run? > Yes. Random stab in the dark: are you loading the Xen binary at a 2MB aligned address? > But it is OK if we don't access the its copy in "early boot misc" area. for example: > > 01 memcpy((void *) dest_va, _start, _end - _start); > 02 > 03 p = (void *) boot_pgtable; > 04 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); > 05 > 06 p = (void *) boot_pgtable + dest_va - (unsigned long)_start; > 07 early_printk("hello 1?\n"); > 08 early_printk("p: 0x%lx\n", (unsigned long)p); > 09 early_printk("hello 2?\n"); > 10 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); > 11 early_printk("hello 3?\n"); > > Output: > > p[0].pt.base: 0x802cc > hello 1? > p: 0x6d2000 > hello 2? So it is more than likely faulting on the access at 10. I don't suppose you have a hardware debugger? You device has 2GB RAM, what happens if you hack the DTS to say it only has 1GB? Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:00:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:00:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utcme-0002pe-VE; Mon, 01 Jul 2013 12:00:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utcmd-0002pI-8H; Mon, 01 Jul 2013 12:00:39 +0000 Received: from [85.158.139.83:63782] by server-7.bemta-5.messagelabs.com id 56/A7-21002-56F61D15; Mon, 01 Jul 2013 12:00:37 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1372680034!25459987!1 X-Originating-IP: [209.85.160.54] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15265 invoked from network); 1 Jul 2013 12:00:36 -0000 Received: from mail-pb0-f54.google.com (HELO mail-pb0-f54.google.com) (209.85.160.54) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:00:36 -0000 Received: by mail-pb0-f54.google.com with SMTP id ro2so4744091pbb.13 for ; Mon, 01 Jul 2013 05:00:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=PGFFptDJda3q9zQBrabRQrlMx628X2W4IeMU8fHTGBc=; b=iM4+d6Yf4CKAD0hnyvM5uI4VOLDag5XEoU1miYqC2D7m4UKmEYctib51W5PNTO8/d8 1Haek8TKjiwtq99uT9l8j0YJ+4EACRLwAM8pIIBocKAAvzgd0Eq1WWGyV9SLdr5oUs7J cJsqiUaYm8NfTP/4765XHkfNgGy0Miy9WySuF7/1z8Kn/esNDHUh21bg7Naq+gMOlWc9 GI7WsHQE02RmHqLBeNIRBCoSapc6boHJGAOjR4UNRdhLJ64Fs0SuuUBohROcJj6jySK2 7HPYqFzkM9btMVoxPFp18fVPXs2GsuRKb00+ntfp/c5i4wMGbtmuM+Vhco55oLHEn3/E FeZw== X-Received: by 10.68.182.130 with SMTP id ee2mr8516796pbc.26.1372680033645; Mon, 01 Jul 2013 05:00:33 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id vb8sm22022880pbc.11.2013.07.01.05.00.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 05:00:32 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372678297.14691.61.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 20:00:19 +0800 Message-Id: <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 7:31 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 19:18 +0800, Chen Baozi wrote: >> On Jul 1, 2013, at 5:57 PM, Ian Campbell wrote: >> >>> On Mon, 2013-07-01 at 17:49 +0800, Chen Baozi wrote: >>>> On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: >>>> >>>>> On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: >>>>>> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: >>>>>> >>>>>>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: >>>>>>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: >>>>>>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: >>>>>>>>>> Hi Ian, >>>>>>>>>> >>>>>>>>>> After enabling the UART, I have been tring to finish the rest of booting. >>>>>>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like >>>>>>>>>> following: >>>>>>>>>> >>>>>>>>>> Starting kernel ... >>>>>>>>>> >>>>>>>>>> - UART enabled - >>>>>>>>>> - CPU 00000000 booting - >>>>>>>>>> - Machine ID 00000ec1 - >>>>>>>>>> - Started in Hyp mode - >>>>>>>>>> - Zero BSS - >>>>>>>>>> - Setting up control registers - >>>>>>>>>> - Turning on paging - >>>>>>>>>> - Ready - >>>>>>>>>> RAM: 0000000080000000 - 00000000ffffffff >>>>>>>>>> >>>>>>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 >>>>>>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 >>>>>>>>>> >>>>>>>>>> What could be the most possible problem of this case? >>>>>>>>> >>>>>>>>> This is a about the point where we would shift from early_printk to the >>>>>>>>> proper console driver, so I expect you simply don't have the console >>>>>>>>> setup. >>>>>>>>> >>>>>>>> Hi Ian, >>>>>>>> >>>>>>>> I guess that it might not all about console driver, because early_printk >>>>>>>> does not work properly just after we have updated "the copy of boot_pgtable >>>>>>>> to use the new paddrs" in setup_pagetables(). It seems that >>>>>>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without >>>>>>>> being restored. >>>>>>> >>>>>>> Hrm, I think the expectation is that the fixmap will be copied as part >>>>>>> of that and doesn't need (or receive) any additional fixups (see around >>>>>>> "Link in the fixmap pagetable"), but it is worth checking for sure. >>>>>>> >>>>>>> You could probably profitably sprinkle some more early_print around the >>>>>>> place during that sequence for debugging purposes. >>>>>> That's exactly what I did just now. And it is interesting that >>>>>> early_printk doesn't work just after the updated boot_pgtable (p = >>>>>> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been >>>>>> accessed (e.g. access to p[i].pt.base). >>>>> >>>>> How odd, that set of tables isn't even used until the call to WRITE_TTBR >>>>> several lines below! I'm pretty certain it isn't updating anything which >>>>> is live. >>>> Yes. And I found it happened even if reading the p[i].pt.base. I have >>>> tried to print the p[i].pt.base before updating its content. Then, >>>> all the early_printk would fail after it. >>> >>> That's just weird. Any chance that reading/writing p[i]...base is >>> actually causing a fault of some description such that the following >>> prints never even get run? >> Yes. > > Random stab in the dark: are you loading the Xen binary at a 2MB aligned > address? > >> But it is OK if we don't access the its copy in "early boot misc" area. for example: >> >> 01 memcpy((void *) dest_va, _start, _end - _start); >> 02 >> 03 p = (void *) boot_pgtable; >> 04 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); >> 05 >> 06 p = (void *) boot_pgtable + dest_va - (unsigned long)_start; >> 07 early_printk("hello 1?\n"); >> 08 early_printk("p: 0x%lx\n", (unsigned long)p); >> 09 early_printk("hello 2?\n"); >> 10 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); >> 11 early_printk("hello 3?\n"); >> >> Output: >> >> p[0].pt.base: 0x802cc >> hello 1? >> p: 0x6d2000 >> hello 2? > > So it is more than likely faulting on the access at 10. I don't suppose > you have a hardware debugger? > > You device has 2GB RAM, what happens if you hack the DTS to say it only > has 1GB? Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: memory { device_type = "memory" - reg = <0x80000000 0x80000000>; /* 2 GB */ + reg = <0x80000000 0x40000000>; /* 1 GB */ }; I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". Cheers, Baozi. > > Ian. > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:00:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:00:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utcme-0002pe-VE; Mon, 01 Jul 2013 12:00:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utcmd-0002pI-8H; Mon, 01 Jul 2013 12:00:39 +0000 Received: from [85.158.139.83:63782] by server-7.bemta-5.messagelabs.com id 56/A7-21002-56F61D15; Mon, 01 Jul 2013 12:00:37 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1372680034!25459987!1 X-Originating-IP: [209.85.160.54] X-SpamReason: No, hits=1.2 required=7.0 tests=HOT_NASTY, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15265 invoked from network); 1 Jul 2013 12:00:36 -0000 Received: from mail-pb0-f54.google.com (HELO mail-pb0-f54.google.com) (209.85.160.54) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:00:36 -0000 Received: by mail-pb0-f54.google.com with SMTP id ro2so4744091pbb.13 for ; Mon, 01 Jul 2013 05:00:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=PGFFptDJda3q9zQBrabRQrlMx628X2W4IeMU8fHTGBc=; b=iM4+d6Yf4CKAD0hnyvM5uI4VOLDag5XEoU1miYqC2D7m4UKmEYctib51W5PNTO8/d8 1Haek8TKjiwtq99uT9l8j0YJ+4EACRLwAM8pIIBocKAAvzgd0Eq1WWGyV9SLdr5oUs7J cJsqiUaYm8NfTP/4765XHkfNgGy0Miy9WySuF7/1z8Kn/esNDHUh21bg7Naq+gMOlWc9 GI7WsHQE02RmHqLBeNIRBCoSapc6boHJGAOjR4UNRdhLJ64Fs0SuuUBohROcJj6jySK2 7HPYqFzkM9btMVoxPFp18fVPXs2GsuRKb00+ntfp/c5i4wMGbtmuM+Vhco55oLHEn3/E FeZw== X-Received: by 10.68.182.130 with SMTP id ee2mr8516796pbc.26.1372680033645; Mon, 01 Jul 2013 05:00:33 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id vb8sm22022880pbc.11.2013.07.01.05.00.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 05:00:32 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372678297.14691.61.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 20:00:19 +0800 Message-Id: <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 7:31 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 19:18 +0800, Chen Baozi wrote: >> On Jul 1, 2013, at 5:57 PM, Ian Campbell wrote: >> >>> On Mon, 2013-07-01 at 17:49 +0800, Chen Baozi wrote: >>>> On Jul 1, 2013, at 5:30 PM, Ian Campbell wrote: >>>> >>>>> On Mon, 2013-07-01 at 17:19 +0800, Chen Baozi wrote: >>>>>> On Jul 1, 2013, at 4:50 PM, Ian Campbell wrote: >>>>>> >>>>>>> On Mon, 2013-07-01 at 11:54 +0800, Chen Baozi wrote: >>>>>>>> On Thu, Jun 27, 2013 at 01:10:01PM +0100, Ian Campbell wrote: >>>>>>>>> On Thu, 2013-06-27 at 19:55 +0800, Chen Baozi wrote: >>>>>>>>>> Hi Ian, >>>>>>>>>> >>>>>>>>>> After enabling the UART, I have been tring to finish the rest of booting. >>>>>>>>>> However, the output information stops at "Placing Xen at XXXX-XXXX" like >>>>>>>>>> following: >>>>>>>>>> >>>>>>>>>> Starting kernel ... >>>>>>>>>> >>>>>>>>>> - UART enabled - >>>>>>>>>> - CPU 00000000 booting - >>>>>>>>>> - Machine ID 00000ec1 - >>>>>>>>>> - Started in Hyp mode - >>>>>>>>>> - Zero BSS - >>>>>>>>>> - Setting up control registers - >>>>>>>>>> - Turning on paging - >>>>>>>>>> - Ready - >>>>>>>>>> RAM: 0000000080000000 - 00000000ffffffff >>>>>>>>>> >>>>>>>>>> MODULE[1]: 00000000a0000000 - 00000000a0400000 >>>>>>>>>> Placing Xen at 0x00000000ffe00000-0x0000000100000000 >>>>>>>>>> >>>>>>>>>> What could be the most possible problem of this case? >>>>>>>>> >>>>>>>>> This is a about the point where we would shift from early_printk to the >>>>>>>>> proper console driver, so I expect you simply don't have the console >>>>>>>>> setup. >>>>>>>>> >>>>>>>> Hi Ian, >>>>>>>> >>>>>>>> I guess that it might not all about console driver, because early_printk >>>>>>>> does not work properly just after we have updated "the copy of boot_pgtable >>>>>>>> to use the new paddrs" in setup_pagetables(). It seems that >>>>>>>> FIXMAP_ADDR(FIXMAP_CONSOLE) has been destroyed after the updating without >>>>>>>> being restored. >>>>>>> >>>>>>> Hrm, I think the expectation is that the fixmap will be copied as part >>>>>>> of that and doesn't need (or receive) any additional fixups (see around >>>>>>> "Link in the fixmap pagetable"), but it is worth checking for sure. >>>>>>> >>>>>>> You could probably profitably sprinkle some more early_print around the >>>>>>> place during that sequence for debugging purposes. >>>>>> That's exactly what I did just now. And it is interesting that >>>>>> early_printk doesn't work just after the updated boot_pgtable (p = >>>>>> (void *) boot_pgtable + dest_va - (unsigned long) _start;) has been >>>>>> accessed (e.g. access to p[i].pt.base). >>>>> >>>>> How odd, that set of tables isn't even used until the call to WRITE_TTBR >>>>> several lines below! I'm pretty certain it isn't updating anything which >>>>> is live. >>>> Yes. And I found it happened even if reading the p[i].pt.base. I have >>>> tried to print the p[i].pt.base before updating its content. Then, >>>> all the early_printk would fail after it. >>> >>> That's just weird. Any chance that reading/writing p[i]...base is >>> actually causing a fault of some description such that the following >>> prints never even get run? >> Yes. > > Random stab in the dark: are you loading the Xen binary at a 2MB aligned > address? > >> But it is OK if we don't access the its copy in "early boot misc" area. for example: >> >> 01 memcpy((void *) dest_va, _start, _end - _start); >> 02 >> 03 p = (void *) boot_pgtable; >> 04 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); >> 05 >> 06 p = (void *) boot_pgtable + dest_va - (unsigned long)_start; >> 07 early_printk("hello 1?\n"); >> 08 early_printk("p: 0x%lx\n", (unsigned long)p); >> 09 early_printk("hello 2?\n"); >> 10 early_printk("p[%d].pt.base: 0x%lx\n", 0, (unsigned long)p[0].pt.base); >> 11 early_printk("hello 3?\n"); >> >> Output: >> >> p[0].pt.base: 0x802cc >> hello 1? >> p: 0x6d2000 >> hello 2? > > So it is more than likely faulting on the access at 10. I don't suppose > you have a hardware debugger? > > You device has 2GB RAM, what happens if you hack the DTS to say it only > has 1GB? Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: memory { device_type = "memory" - reg = <0x80000000 0x80000000>; /* 2 GB */ + reg = <0x80000000 0x40000000>; /* 1 GB */ }; I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". Cheers, Baozi. > > Ian. > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:06:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:06:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtcsJ-0003Bm-VL; Mon, 01 Jul 2013 12:06:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtcsI-0003Be-Sc; Mon, 01 Jul 2013 12:06:31 +0000 Received: from [85.158.139.83:2847] by server-5.bemta-5.messagelabs.com id 76/2C-27868-5C071D15; Mon, 01 Jul 2013 12:06:29 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1372680389!29332661!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15520 invoked from network); 1 Jul 2013 12:06:29 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:06:29 -0000 X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="6245031" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 12:06:28 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 13:06:28 +0100 Message-ID: <1372680387.14691.62.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 13:06:27 +0100 In-Reply-To: <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > > You device has 2GB RAM, what happens if you hack the DTS to say it only > > has 1GB? > > Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > > memory { > device_type = "memory" > - reg = <0x80000000 0x80000000>; /* 2 GB */ > + reg = <0x80000000 0x40000000>; /* 1 GB */ > }; > > I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". Excellent! So I guess if you keep the 2GB but put it at the right address it will also work? Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:06:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:06:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtcsJ-0003Bm-VL; Mon, 01 Jul 2013 12:06:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtcsI-0003Be-Sc; Mon, 01 Jul 2013 12:06:31 +0000 Received: from [85.158.139.83:2847] by server-5.bemta-5.messagelabs.com id 76/2C-27868-5C071D15; Mon, 01 Jul 2013 12:06:29 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1372680389!29332661!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15520 invoked from network); 1 Jul 2013 12:06:29 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:06:29 -0000 X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="6245031" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 12:06:28 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 13:06:28 +0100 Message-ID: <1372680387.14691.62.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 13:06:27 +0100 In-Reply-To: <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > > You device has 2GB RAM, what happens if you hack the DTS to say it only > > has 1GB? > > Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > > memory { > device_type = "memory" > - reg = <0x80000000 0x80000000>; /* 2 GB */ > + reg = <0x80000000 0x40000000>; /* 1 GB */ > }; > > I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". Excellent! So I guess if you keep the 2GB but put it at the right address it will also work? Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:32:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:32:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdHZ-00049b-41; Mon, 01 Jul 2013 12:32:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdHX-00049J-SJ; Mon, 01 Jul 2013 12:32:36 +0000 Received: from [85.158.139.83:62529] by server-4.bemta-5.messagelabs.com id 5C/47-17085-2E671D15; Mon, 01 Jul 2013 12:32:34 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1372681952!26614770!1 X-Originating-IP: [209.85.192.171] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12536 invoked from network); 1 Jul 2013 12:32:34 -0000 Received: from mail-pd0-f171.google.com (HELO mail-pd0-f171.google.com) (209.85.192.171) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:32:34 -0000 Received: by mail-pd0-f171.google.com with SMTP id y14so2586037pdi.16 for ; Mon, 01 Jul 2013 05:32:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Om+fLE01I7OVQjouMm2Il9oOluq/jflBh1VMwJevLbs=; b=LxsyWsMHiM1JoCL4YO0JSkmbp/vpWlA/imaM5a1zyglQZBV/5Gs/91xQO9mzqXwh4E ygrd1m9hw/XFuth5nx9m0plYvR6k1MFdeWlsvbOY2J0RCMlaYfmMbI/685lPpUMN9sAo GWO7Ez2Rx007IPXLF7Jz2+hppxvbInsj7FvR/8Ur70m/cDU96Ay7rrYkr912fHb/MAn1 MmMuwKpydmfv7HfQXz1lyH63rJZeq2TEa6KjSEgFA8CQexXdrYj5Z3paIKVzKtJKpI1b PSH2ufukPLB3xywr2+kA+MBhWipAe0goLWEkUSXUqO0Fo0Yov18TaU/GhCur+tkSKzdv npCQ== X-Received: by 10.68.25.102 with SMTP id b6mr23413682pbg.105.1372681951783; Mon, 01 Jul 2013 05:32:31 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id qv4sm22129943pbc.16.2013.07.01.05.32.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 05:32:31 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372680387.14691.62.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 20:32:05 +0800 Message-Id: References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > >>> You device has 2GB RAM, what happens if you hack the DTS to say it only >>> has 1GB? >> >> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: >> >> memory { >> device_type = "memory" >> - reg = <0x80000000 0x80000000>; /* 2 GB */ >> + reg = <0x80000000 0x40000000>; /* 1 GB */ >> }; >> >> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > > Excellent! > > So I guess if you keep the 2GB but put it at the right address it will > also work? I'm afraid no, :-( Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage reading xen-uImage 902572 bytes read in 59 ms (14.6 MiB/s) OMAP5430 EVM # bootm 0x80000000 - ## Booting kernel from Legacy Image at 80000000 ... Image Name: Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 902508 Bytes = 881.4 KiB Load Address: 80200000 Entry Point: 80200000 Verifying Checksum ... OK Loading Kernel Image ... OK OK And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both cases. It works for 1GB but fails in 2GB case too. Something wrong? Cheers, Baozi. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:32:41 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:32:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdHZ-00049b-41; Mon, 01 Jul 2013 12:32:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdHX-00049J-SJ; Mon, 01 Jul 2013 12:32:36 +0000 Received: from [85.158.139.83:62529] by server-4.bemta-5.messagelabs.com id 5C/47-17085-2E671D15; Mon, 01 Jul 2013 12:32:34 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1372681952!26614770!1 X-Originating-IP: [209.85.192.171] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12536 invoked from network); 1 Jul 2013 12:32:34 -0000 Received: from mail-pd0-f171.google.com (HELO mail-pd0-f171.google.com) (209.85.192.171) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:32:34 -0000 Received: by mail-pd0-f171.google.com with SMTP id y14so2586037pdi.16 for ; Mon, 01 Jul 2013 05:32:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Om+fLE01I7OVQjouMm2Il9oOluq/jflBh1VMwJevLbs=; b=LxsyWsMHiM1JoCL4YO0JSkmbp/vpWlA/imaM5a1zyglQZBV/5Gs/91xQO9mzqXwh4E ygrd1m9hw/XFuth5nx9m0plYvR6k1MFdeWlsvbOY2J0RCMlaYfmMbI/685lPpUMN9sAo GWO7Ez2Rx007IPXLF7Jz2+hppxvbInsj7FvR/8Ur70m/cDU96Ay7rrYkr912fHb/MAn1 MmMuwKpydmfv7HfQXz1lyH63rJZeq2TEa6KjSEgFA8CQexXdrYj5Z3paIKVzKtJKpI1b PSH2ufukPLB3xywr2+kA+MBhWipAe0goLWEkUSXUqO0Fo0Yov18TaU/GhCur+tkSKzdv npCQ== X-Received: by 10.68.25.102 with SMTP id b6mr23413682pbg.105.1372681951783; Mon, 01 Jul 2013 05:32:31 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id qv4sm22129943pbc.16.2013.07.01.05.32.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 05:32:31 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372680387.14691.62.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 20:32:05 +0800 Message-Id: References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > >>> You device has 2GB RAM, what happens if you hack the DTS to say it only >>> has 1GB? >> >> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: >> >> memory { >> device_type = "memory" >> - reg = <0x80000000 0x80000000>; /* 2 GB */ >> + reg = <0x80000000 0x40000000>; /* 1 GB */ >> }; >> >> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > > Excellent! > > So I guess if you keep the 2GB but put it at the right address it will > also work? I'm afraid no, :-( Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage reading xen-uImage 902572 bytes read in 59 ms (14.6 MiB/s) OMAP5430 EVM # bootm 0x80000000 - ## Booting kernel from Legacy Image at 80000000 ... Image Name: Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 902508 Bytes = 881.4 KiB Load Address: 80200000 Entry Point: 80200000 Verifying Checksum ... OK Loading Kernel Image ... OK OK And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both cases. It works for 1GB but fails in 2GB case too. Something wrong? Cheers, Baozi. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:39:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:39:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdNt-0004Zk-6x; Mon, 01 Jul 2013 12:39:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdNr-0004Yw-4u; Mon, 01 Jul 2013 12:39:07 +0000 Received: from [85.158.137.99:5591] by server-5.bemta-3.messagelabs.com id 6D/77-15398-A6871D15; Mon, 01 Jul 2013 12:39:06 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1372682344!14220864!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9126 invoked from network); 1 Jul 2013 12:39:05 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:39:05 -0000 X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="6246347" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 12:39:05 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 13:39:03 +0100 Message-ID: <1372682342.14691.65.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 13:39:02 +0100 In-Reply-To: References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > > > On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > > > >>> You device has 2GB RAM, what happens if you hack the DTS to say it only > >>> has 1GB? > >> > >> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > >> > >> memory { > >> device_type = "memory" > >> - reg = <0x80000000 0x80000000>; /* 2 GB */ > >> + reg = <0x80000000 0x40000000>; /* 1 GB */ > >> }; > >> > >> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > > > > Excellent! > > > > So I guess if you keep the 2GB but put it at the right address it will > > also work? > > I'm afraid no, :-( > > Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): > > OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage > reading xen-uImage > 902572 bytes read in 59 ms (14.6 MiB/s) > OMAP5430 EVM # bootm 0x80000000 - > ## Booting kernel from Legacy Image at 80000000 ... > Image Name: > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 902508 Bytes = 881.4 KiB > Load Address: 80200000 > Entry Point: 80200000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both > cases. It works for 1GB but fails in 2GB case too. What is the base address of RAM on the A31 SoC? I don't have a DTS for an A31 system but all arch/arm/boot/dts/sun* (which covers A10 and A13 I think) have it at 0x40000000. Which means that *if* your system has 2GB then the correct memory line is: reg = <0x40000000 0x80000000>; /* 2 GB */ Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:39:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:39:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdNt-0004Zk-6x; Mon, 01 Jul 2013 12:39:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdNr-0004Yw-4u; Mon, 01 Jul 2013 12:39:07 +0000 Received: from [85.158.137.99:5591] by server-5.bemta-3.messagelabs.com id 6D/77-15398-A6871D15; Mon, 01 Jul 2013 12:39:06 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-217.messagelabs.com!1372682344!14220864!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9126 invoked from network); 1 Jul 2013 12:39:05 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-12.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:39:05 -0000 X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="6246347" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 12:39:05 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 13:39:03 +0100 Message-ID: <1372682342.14691.65.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 13:39:02 +0100 In-Reply-To: References: <20130627115553.GA4918@cbz-workstation> <1372335001.7996.7.camel@zakaz.uk.xensource.com> <20130701035413.GA12358@cbz-workstation> <1372668616.14691.35.camel@zakaz.uk.xensource.com> <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > > > On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > > > >>> You device has 2GB RAM, what happens if you hack the DTS to say it only > >>> has 1GB? > >> > >> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > >> > >> memory { > >> device_type = "memory" > >> - reg = <0x80000000 0x80000000>; /* 2 GB */ > >> + reg = <0x80000000 0x40000000>; /* 1 GB */ > >> }; > >> > >> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > > > > Excellent! > > > > So I guess if you keep the 2GB but put it at the right address it will > > also work? > > I'm afraid no, :-( > > Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): > > OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage > reading xen-uImage > 902572 bytes read in 59 ms (14.6 MiB/s) > OMAP5430 EVM # bootm 0x80000000 - > ## Booting kernel from Legacy Image at 80000000 ... > Image Name: > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 902508 Bytes = 881.4 KiB > Load Address: 80200000 > Entry Point: 80200000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both > cases. It works for 1GB but fails in 2GB case too. What is the base address of RAM on the A31 SoC? I don't have a DTS for an A31 system but all arch/arm/boot/dts/sun* (which covers A10 and A13 I think) have it at 0x40000000. Which means that *if* your system has 2GB then the correct memory line is: reg = <0x40000000 0x80000000>; /* 2 GB */ Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:48:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:48:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdWy-0004pE-Kd; Mon, 01 Jul 2013 12:48:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdWx-0004p4-IZ; Mon, 01 Jul 2013 12:48:31 +0000 Received: from [85.158.139.211:63843] by server-9.bemta-5.messagelabs.com id 31/E8-26025-C9A71D15; Mon, 01 Jul 2013 12:48:28 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1372682905!18878519!1 X-Originating-IP: [209.85.160.41] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24481 invoked from network); 1 Jul 2013 12:48:27 -0000 Received: from mail-pb0-f41.google.com (HELO mail-pb0-f41.google.com) (209.85.160.41) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:48:27 -0000 Received: by mail-pb0-f41.google.com with SMTP id rp16so4820592pbb.0 for ; Mon, 01 Jul 2013 05:48:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=6BgRm8S0MF0E5AXIlDJUByrIM0A0XX4xFVsi9IT2MHc=; b=uOw6REkJlNlUiobvwgnck42RfivEMmALXpVT6mayoQ46qApNrJocIRfn+PN23p3ztD sItGeCru8ZrWKAOPVKUBNuO8fEFj0Wvrn4g6ofFokk8ir0mDip2TuifS4qONUkGs48hp jVwDLHmRytp1dP3vX+EMQx73+qs4FVGLvN0SD6/DThTQWPZ3oLYeCKey0X1gc7kvmwdk C621mXY333R417gJkqntAkrz62ffAWouGIMFCK0XwCU3SIeQk/kTvZothsEPz4x4UtJY tYR9No8NaEHs4176iNgvlIAPC/tLF2CMKewNlpSKNLixeMq/IZS+Sc9TAfL6uqfWowCu pOoA== X-Received: by 10.68.175.228 with SMTP id cd4mr24026449pbc.40.1372682905273; Mon, 01 Jul 2013 05:48:25 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id hu6sm15968903pbc.28.2013.07.01.05.48.22 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 01 Jul 2013 05:48:24 -0700 (PDT) Date: Mon, 1 Jul 2013 20:43:27 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130701124327.GA25341@cbz-workstation> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: <1372682342.14691.65.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 01, 2013 at 01:39:02PM +0100, Ian Campbell wrote: > On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: > > On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > > > > > On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > > > > > >>> You device has 2GB RAM, what happens if you hack the DTS to say it only > > >>> has 1GB? > > >> > > >> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > > >> > > >> memory { > > >> device_type = "memory" > > >> - reg = <0x80000000 0x80000000>; /* 2 GB */ > > >> + reg = <0x80000000 0x40000000>; /* 1 GB */ > > >> }; > > >> > > >> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > > > > > > Excellent! > > > > > > So I guess if you keep the 2GB but put it at the right address it will > > > also work? > > > > I'm afraid no, :-( > > > > Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): > > > > OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage > > reading xen-uImage > > 902572 bytes read in 59 ms (14.6 MiB/s) > > OMAP5430 EVM # bootm 0x80000000 - > > ## Booting kernel from Legacy Image at 80000000 ... > > Image Name: > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 902508 Bytes = 881.4 KiB > > Load Address: 80200000 > > Entry Point: 80200000 > > Verifying Checksum ... OK > > Loading Kernel Image ... OK > > OK > > > And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both > > cases. It works for 1GB but fails in 2GB case too. > > What is the base address of RAM on the A31 SoC? A31 SoC? I use OMAP5432 ES2.0 uEVM (OMAP5 Panda) board. The attachment is the dts file which the linux kernel uses on this board by default, which the memory line is: reg = <0x80000000 0x80000000>; /* 2 GB */ > I don't have a DTS for > an A31 system but all arch/arm/boot/dts/sun* (which covers A10 and A13 I > think) have it at 0x40000000. Which means that *if* your system has 2GB > then the correct memory line is: > reg = <0x40000000 0x80000000>; /* 2 GB */ > > Ian. > > --J2SCkAp4GZ/dPZZf Content-Type: audio/vnd.dts Content-Disposition: attachment; filename="omap5-panda.dts" Content-Transfer-Encoding: quoted-printable /*=0A * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.c= om/=0A *=0A * This program is free software; you can redistribute it and/or= modify=0A * it under the terms of the GNU General Public License version 2= as=0A * published by the Free Software Foundation.=0A */=0A/dts-v1/;=0A=0A= /include/ "omap5.dtsi"=0A=0A/ {=0A model =3D "TI OMAP5 EVM board";=0A compa= tible =3D "ti,omap5-panda", "ti,omap5";=0A=0A memory {=0A device_type =3D = "memory";=0A reg =3D <0x80000000 0x80000000>; /* 2 GB */=0A };=0A=0A vmmcs= d_fixed: fixedregulator-mmcsd {=0A compatible =3D "regulator-fixed";=0A r= egulator-name =3D "vmmcsd_fixed";=0A regulator-min-microvolt =3D <3000000>= ;=0A regulator-max-microvolt =3D <3000000>;=0A };=0A=0A leds {=0A compati= ble =3D "gpio-leds";=0A usr1 {=0A label =3D "usr1";=0A gpios =3D <&tca= 6424a 2 0>; /* TCA6424A P02, GRN_LED0 */=0A default-state =3D "off";=0A = };=0A usr2 {=0A label =3D "usr2";=0A gpios =3D <&tca6424a 3 0>; /* TCA= 6424A P03, GRN_LED1 */=0A default-state =3D "off";=0A };=0A usr3 {=0A = label =3D "usr3";=0A gpios =3D <&tca6424a 4 0>; /* TCA6424A P04, GRN_LED= 2 */=0A default-state =3D "off";=0A };=0A usr4 {=0A label =3D "usr4";= =0A gpios =3D <&tca6424a 5 0>; /* TCA6424A P05, GRN_LED3 */=0A default-= state =3D "off";=0A };=0A usr5 {=0A label =3D "usr5";=0A gpios =3D <&= tca6424a 6 0>; /* TCA6424A P06, GRN_LED4 */=0A default-state =3D "off";= =0A };=0A tcr {=0A label =3D "tcr";=0A gpios =3D <&tca6424a 17 0>; /*= TCA6424A P21, TC_LED_RED */=0A linux,default-trigger =3D "heartbeat";=0A= };=0A tcg {=0A label =3D "tcg";=0A gpios =3D <&tca6424a 18 0>; /* TC= A6424A P22, TC_LED_GRN */=0A default-state =3D "off";=0A };=0A tcb {=0A= label =3D "tcb";=0A gpios =3D <&tca6424a 19 0>; /* TCA6424A P23, TC_LE= D_BLUE */=0A default-state =3D "off";=0A };=0A };=0A=0A sound {=0A comp= atible =3D "ti,abe-twl6040";=0A ti,model =3D "PandaBoard5";=0A=0A ti,jack= -detection =3D <1>;=0A ti,mclk-freq =3D <19200000>;=0A=0A ti,mcpdm =3D <&= mcpdm>;=0A ti,mcbsp1 =3D <&mcbsp1>;=0A ti,mcbsp2 =3D <&mcbsp2>;=0A ti,ae= ss =3D <&aess>;=0A=0A ti,twl6040 =3D <&twl6040>;=0A=0A /* Audio routing *= /=0A ti,audio-routing =3D=0A "Headset Stereophone", "HSOL",=0A "Headse= t Stereophone", "HSOR",=0A "Line Out", "AUXL",=0A "Line Out", "AUXR",= =0A "HSMIC", "Headset Mic",=0A "Headset Mic", "Headset Mic Bias",=0A = "AFML", "Line In",=0A "AFMR", "Line In",=0A "Headset Playback", "PDM_DL= 1",=0A "PDM_UL1", "Capture",=0A "40122000.mcbsp Playback", "BT_VX_DL",= =0A "BT_VX_UL", "40122000.mcbsp Capture",=0A "40124000.mcbsp Playback",= "MM_EXT_DL",=0A "MM_EXT_UL", "40124000.mcbsp Capture";=0A };=0A=0A sound= _hdmi {=0A compatible =3D "ti,omap-hdmi-tpd12s015-audio";=0A ti,model =3D= "OMAP5HDMI";=0A=0A ti,hdmi_audio =3D <&hdmi>;=0A ti,level_shifter =3D <&= tpd12s015>;=0A };=0A=0A /* HS USB Port 2 RESET */=0A hsusb2_reset: hsusb2_r= eset_reg {=0A compatible =3D "regulator-fixed";=0A regulator-name =3D "hs= usb2_reset";=0A regulator-min-microvolt =3D <3300000>;=0A regulator-max-m= icrovolt =3D <3300000>;=0A gpio =3D <&gpio3 16 0>; /* gpio3_80 HUB_NRESET = */=0A startup-delay-us =3D <70000>;=0A enable-active-high;=0A };=0A=0A /*= HS USB Host PHY on PORT 2 */=0A hsusb2_phy: hsusb2_phy {=0A compatible = =3D "usb-nop-xceiv";=0A reset-supply =3D <&hsusb2_reset>;=0A };=0A=0A /* H= S USB Port 3 RESET */=0A hsusb3_reset: hsusb3_reset_reg {=0A compatible = =3D "regulator-fixed";=0A regulator-name =3D "hsusb3_reset";=0A regulator= -min-microvolt =3D <3300000>;=0A regulator-max-microvolt =3D <3300000>;=0A= gpio =3D <&gpio3 15 0>; /* gpio3_79 ETH_NRESET */=0A startup-delay-us = =3D <70000>;=0A enable-active-high;=0A };=0A=0A /* HS USB Host PHY on PORT= 3 */=0A hsusb3_phy: hsusb3_phy {=0A compatible =3D "usb-nop-xceiv";=0A r= eset-supply =3D <&hsusb3_reset>;=0A };=0A=0A /* hsusb2_phy is clocked by FR= EF_CLK1 i.e. auxclk1 */=0A clock_alias {=0A clock-name =3D "auxclk1_ck";= =0A clock-alias =3D "main_clk";=0A device =3D <&hsusb2_phy>;=0A clock-fr= equency =3D <19200000>; /* 19.2 MHz */=0A };=0A};=0A=0A&mmc1 {=0A vmmc-supp= ly =3D <&vmmcsd_fixed>;=0A vmmc-aux-supply =3D <&ldo9_reg>;=0A bus-width = =3D <4>;=0A};=0A=0A&mmc2 {=0A vmmc-supply =3D <&vmmcsd_fixed>;=0A vmmc-aux-= supply =3D <&ldo9_reg>;=0A bus-width =3D <8>;=0A ti,non-removable;=0A};=0A= =0A&mmc3 {=0A bus-width =3D <4>;=0A ti,non-removable;=0A};=0A=0A&mmc4 {=0A = status =3D "disabled";=0A};=0A=0A&mmc5 {=0A status =3D "disabled";=0A};=0A= =0A&i2c1 {=0A clock-frequency =3D <400000>;=0A=0A palmas: palmas@48 {=0A r= eg =3D <0x48>;=0A /* SPI =3D 0, IRQ# =3D 7, 4 =3D active high level-sensit= ive */=0A interrupts =3D <0 7 4>; /* IRQ_SYS_1N cascaded to gic */=0A int= errupt-parent =3D <&gic>;=0A };=0A=0A twl6040: twl@4b {=0A compatible =3D = "ti,twl6040";=0A=0A interrupts =3D <0 119 4>; /* IRQ_SYS_2N cascaded to gi= c */=0A interrupt-parent =3D <&gic>;=0A ti,audpwron-gpio =3D <&gpio5 13 0= >; /* gpio line 141 */=0A=0A vio-supply =3D <&smps7_reg>;=0A v2v1-supply= =3D <&smps9_reg>;=0A enable-active-high;=0A };=0A};=0A=0A=0A&i2c5 {=0A tc= a6424a: tca6424a@22 {=0A compatible =3D "ti,tca6424a";=0A reg =3D <0x22>;= =0A gpio-controller;=0A #gpio-cells =3D <2>;=0A };=0A};=0A=0A&omap5_pmx_c= ore {=0A pinctrl-names =3D "default";=0A pinctrl-0 =3D <=0A &twl6040_pins= =0A &mcpdm_pins=0A &dmic_pins=0A &mcbsp1_pins=0A &mcbsp2_pins=0A = &i2c5_pins=0A &usbhost_pins=0A &dss_hdmi_pins=0A &tpd12s015_pins=0A >= ;=0A=0A twl6040_pins: pinmux_twl6040_pins {=0A pinctrl-single,pins =3D <= =0A 0x17e 0x6 /* mcspi1_somi.gpio5_141 OUTPUT | MODE6 */=0A >;=0A };=0A= =0A mcpdm_pins: pinmux_mcpdm_pins {=0A pinctrl-single,pins =3D <=0A 0x14= 2 0x108 /* abe_clks.abe_clks INPUT PULLDOWN | MODE0 */=0A 0x15c 0x108 /* = abemcpdm_ul_data.abemcpdm_ul_data INPUT PULLDOWN | MODE0 */=0A 0x15e 0x10= 8 /* abemcpdm_dl_data.abemcpdm_dl_data INPUT PULLDOWN | MODE0 */=0A 0x160= 0x118 /* abemcpdm_frame.abemcpdm_frame INPUT PULLUP | MODE0 */=0A 0x162 = 0x108 /* abemcpdm_lb_clk.abemcpdm_lb_clk INPUT PULLDOWN | MODE0 */=0A >;= =0A };=0A=0A dmic_pins: pinmux_dmic_pins {=0A pinctrl-single,pins =3D <=0A= 0x144 0x100 /* abedmic_din1.abedmic_din1 INPUT | MODE0 */=0A 0x146 0x1= 00 /* abedmic_din2.abedmic_din2 INPUT | MODE0 */=0A 0x148 0x100 /* abedmi= c_din3.abedmic_din3 INPUT | MODE0 */=0A 0x14a 0 /* abedmic_clk1.abedmic_= clk1 OUTPUT | MODE0 */=0A >;=0A };=0A=0A mcbsp1_pins: pinmux_mcbsp1_pins {= =0A pinctrl-single,pins =3D <=0A 0x14c 0x101 /* abedmic_clk2.abemcbsp1_f= sx INPUT | MODE1 */=0A 0x14e 0x9 /* abedmic_clk3.abemcbsp1_dx OUTPUT PULL= DOWN | MODE1 */=0A 0x150 0x101 /* abeslimbus1_clock.abemcbsp1_clkx INPUT = | MODE0 */=0A 0x152 0x109 /* abeslimbus1_data.abemcbsp1_dr INPUT PULLDOWN= | MODE1 */=0A >;=0A };=0A=0A mcbsp2_pins: pinmux_mcbsp2_pins {=0A pinctr= l-single,pins =3D <=0A 0x154 0x108 /* abemcbsp2_dr.abemcbsp2_dr INPUT PUL= LDOWN | MODE0 */=0A 0x156 0x8 /* abemcbsp2_dx.abemcbsp2_dx OUTPUT PULLDOW= N | MODE0 */=0A 0x158 0x100 /* abemcbsp2_fsx.abemcbsp2_fsx INPUT | MODE0 = */=0A 0x15a 0x100 /* abemcbsp2_clkx.abemcbsp2_clkx INPUT | MODE0 */=0A >= ;=0A };=0A=0A i2c5_pins: pinmux_i2c5_pins {=0A pinctrl-single,pins =3D <= =0A 0x186 0x100 /* i2c5_scl.i2c5_scl INPUT | MODE0 */=0A 0x188 0x100 /*= i2c5_sda.i2c5_sda INPUT | MODE0 */=0A >;=0A };=0A=0A usbhost_pins: pinmux= _usbhost_pins {=0A pinctrl-single,pins =3D <=0A 0x84 0x100 /* usbb2_hsic= _strobe INPUT | MODE 0 */=0A 0x86 0x100 /* usbb2_hsic_data INPUT | MODE 0= */=0A=0A 0x19e 0x100 /* usbb3_hsic_strobe INPUT | MODE 0 */=0A 0x1a0 0= x100 /* usbb3_hsic_data INPUT | MODE 0 */=0A=0A 0x70 0x6 /* gpio3_80 OUTP= UT | MODE 6 HUB_NRESET */=0A 0x6e 0x6 /* gpio3_79 OUTPUT | MODE 6 ETH_NRE= SET */=0A >;=0A };=0A=0A dss_hdmi_pins: pinmux_dss_hdmi_pins {=0A pinctrl= -single,pins =3D <=0A 0x0fc 0x118 /* hdmi_cec.hdmi_cec INPUT PULLUP | MOD= E 0 */=0A 0x100 0x100 /* hdmi_scl.hdmi_scl INPUT | MODE 0 */=0A 0x102 0= x100 /* hdmi_sda.hdmi_sda INPUT | MODE 0 */=0A >;=0A };=0A=0A tpd12s015_pi= ns: pinmux_tpd12s015_pins {=0A pinctrl-single,pins =3D <=0A 0x0fe 0x116 = /* hdmi_hpd.gpio7_193 INPUT PULLDOWN | MODE6 */=0A >;=0A };=0A};=0A=0A&oma= p5_pmx_wkup {=0A pinctrl-names =3D "default";=0A pinctrl-0 =3D <=0A &usbh= ost_wkup_pins=0A >;=0A=0A usbhost_wkup_pins: pinmux_usbhost_wkup_pins {=0A = pinctrl-single,pins =3D <=0A 0x1A 0x0 /* fref_clk1_out OUTPUT | MODE 7 f= or USB hub clk */=0A >;=0A };=0A};=0A=0A&i2c5 {=0A tca6424a: tca6424a@22 {= =0A compatible =3D "ti,tca6424a";=0A gpio-controller;=0A #gpio-cells =3D= <2>;=0A reg =3D <0x22>;=0A };=0A};=0A=0A&usbhshost {=0A port2-mode =3D "e= hci-hsic";=0A port3-mode =3D "ehci-hsic";=0A};=0A=0A&usbhsehci {=0A phys = =3D <0 &hsusb2_phy &hsusb3_phy>;=0A};=0A=0A&hdmi {=0A tpd12s015: tpd12s015 = {=0A compatible =3D "ti,tpd12s015";=0A=0A gpios =3D <&tca6424a 0 0>, /* T= CA6424A P01, CT_CP_HDP */=0A <&tca6424a 1 0>, /* TCA6424A P00, LS_OE*/=0A= <&gpio7 1 0>; /* 193, HPD */=0A=0A hdmi-monitor {=0A compatible =3D = "ti,hdmi_panel";=0A };=0A=0A };=0A};=0A=0A/include/ "palmas.dtsi"=0A/inclu= de/ "twl6040.dtsi"=0A --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm --J2SCkAp4GZ/dPZZf-- From xen-arm-bounces@lists.xen.org Mon Jul 01 12:48:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:48:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdWy-0004pE-Kd; Mon, 01 Jul 2013 12:48:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdWx-0004p4-IZ; Mon, 01 Jul 2013 12:48:31 +0000 Received: from [85.158.139.211:63843] by server-9.bemta-5.messagelabs.com id 31/E8-26025-C9A71D15; Mon, 01 Jul 2013 12:48:28 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1372682905!18878519!1 X-Originating-IP: [209.85.160.41] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24481 invoked from network); 1 Jul 2013 12:48:27 -0000 Received: from mail-pb0-f41.google.com (HELO mail-pb0-f41.google.com) (209.85.160.41) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:48:27 -0000 Received: by mail-pb0-f41.google.com with SMTP id rp16so4820592pbb.0 for ; Mon, 01 Jul 2013 05:48:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=6BgRm8S0MF0E5AXIlDJUByrIM0A0XX4xFVsi9IT2MHc=; b=uOw6REkJlNlUiobvwgnck42RfivEMmALXpVT6mayoQ46qApNrJocIRfn+PN23p3ztD sItGeCru8ZrWKAOPVKUBNuO8fEFj0Wvrn4g6ofFokk8ir0mDip2TuifS4qONUkGs48hp jVwDLHmRytp1dP3vX+EMQx73+qs4FVGLvN0SD6/DThTQWPZ3oLYeCKey0X1gc7kvmwdk C621mXY333R417gJkqntAkrz62ffAWouGIMFCK0XwCU3SIeQk/kTvZothsEPz4x4UtJY tYR9No8NaEHs4176iNgvlIAPC/tLF2CMKewNlpSKNLixeMq/IZS+Sc9TAfL6uqfWowCu pOoA== X-Received: by 10.68.175.228 with SMTP id cd4mr24026449pbc.40.1372682905273; Mon, 01 Jul 2013 05:48:25 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id hu6sm15968903pbc.28.2013.07.01.05.48.22 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 01 Jul 2013 05:48:24 -0700 (PDT) Date: Mon, 1 Jul 2013 20:43:27 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130701124327.GA25341@cbz-workstation> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: <1372682342.14691.65.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 01, 2013 at 01:39:02PM +0100, Ian Campbell wrote: > On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: > > On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > > > > > On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > > > > > >>> You device has 2GB RAM, what happens if you hack the DTS to say it only > > >>> has 1GB? > > >> > > >> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > > >> > > >> memory { > > >> device_type = "memory" > > >> - reg = <0x80000000 0x80000000>; /* 2 GB */ > > >> + reg = <0x80000000 0x40000000>; /* 1 GB */ > > >> }; > > >> > > >> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > > > > > > Excellent! > > > > > > So I guess if you keep the 2GB but put it at the right address it will > > > also work? > > > > I'm afraid no, :-( > > > > Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): > > > > OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage > > reading xen-uImage > > 902572 bytes read in 59 ms (14.6 MiB/s) > > OMAP5430 EVM # bootm 0x80000000 - > > ## Booting kernel from Legacy Image at 80000000 ... > > Image Name: > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 902508 Bytes = 881.4 KiB > > Load Address: 80200000 > > Entry Point: 80200000 > > Verifying Checksum ... OK > > Loading Kernel Image ... OK > > OK > > > And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both > > cases. It works for 1GB but fails in 2GB case too. > > What is the base address of RAM on the A31 SoC? A31 SoC? I use OMAP5432 ES2.0 uEVM (OMAP5 Panda) board. The attachment is the dts file which the linux kernel uses on this board by default, which the memory line is: reg = <0x80000000 0x80000000>; /* 2 GB */ > I don't have a DTS for > an A31 system but all arch/arm/boot/dts/sun* (which covers A10 and A13 I > think) have it at 0x40000000. Which means that *if* your system has 2GB > then the correct memory line is: > reg = <0x40000000 0x80000000>; /* 2 GB */ > > Ian. > > --J2SCkAp4GZ/dPZZf Content-Type: audio/vnd.dts Content-Disposition: attachment; filename="omap5-panda.dts" Content-Transfer-Encoding: quoted-printable /*=0A * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.c= om/=0A *=0A * This program is free software; you can redistribute it and/or= modify=0A * it under the terms of the GNU General Public License version 2= as=0A * published by the Free Software Foundation.=0A */=0A/dts-v1/;=0A=0A= /include/ "omap5.dtsi"=0A=0A/ {=0A model =3D "TI OMAP5 EVM board";=0A compa= tible =3D "ti,omap5-panda", "ti,omap5";=0A=0A memory {=0A device_type =3D = "memory";=0A reg =3D <0x80000000 0x80000000>; /* 2 GB */=0A };=0A=0A vmmcs= d_fixed: fixedregulator-mmcsd {=0A compatible =3D "regulator-fixed";=0A r= egulator-name =3D "vmmcsd_fixed";=0A regulator-min-microvolt =3D <3000000>= ;=0A regulator-max-microvolt =3D <3000000>;=0A };=0A=0A leds {=0A compati= ble =3D "gpio-leds";=0A usr1 {=0A label =3D "usr1";=0A gpios =3D <&tca= 6424a 2 0>; /* TCA6424A P02, GRN_LED0 */=0A default-state =3D "off";=0A = };=0A usr2 {=0A label =3D "usr2";=0A gpios =3D <&tca6424a 3 0>; /* TCA= 6424A P03, GRN_LED1 */=0A default-state =3D "off";=0A };=0A usr3 {=0A = label =3D "usr3";=0A gpios =3D <&tca6424a 4 0>; /* TCA6424A P04, GRN_LED= 2 */=0A default-state =3D "off";=0A };=0A usr4 {=0A label =3D "usr4";= =0A gpios =3D <&tca6424a 5 0>; /* TCA6424A P05, GRN_LED3 */=0A default-= state =3D "off";=0A };=0A usr5 {=0A label =3D "usr5";=0A gpios =3D <&= tca6424a 6 0>; /* TCA6424A P06, GRN_LED4 */=0A default-state =3D "off";= =0A };=0A tcr {=0A label =3D "tcr";=0A gpios =3D <&tca6424a 17 0>; /*= TCA6424A P21, TC_LED_RED */=0A linux,default-trigger =3D "heartbeat";=0A= };=0A tcg {=0A label =3D "tcg";=0A gpios =3D <&tca6424a 18 0>; /* TC= A6424A P22, TC_LED_GRN */=0A default-state =3D "off";=0A };=0A tcb {=0A= label =3D "tcb";=0A gpios =3D <&tca6424a 19 0>; /* TCA6424A P23, TC_LE= D_BLUE */=0A default-state =3D "off";=0A };=0A };=0A=0A sound {=0A comp= atible =3D "ti,abe-twl6040";=0A ti,model =3D "PandaBoard5";=0A=0A ti,jack= -detection =3D <1>;=0A ti,mclk-freq =3D <19200000>;=0A=0A ti,mcpdm =3D <&= mcpdm>;=0A ti,mcbsp1 =3D <&mcbsp1>;=0A ti,mcbsp2 =3D <&mcbsp2>;=0A ti,ae= ss =3D <&aess>;=0A=0A ti,twl6040 =3D <&twl6040>;=0A=0A /* Audio routing *= /=0A ti,audio-routing =3D=0A "Headset Stereophone", "HSOL",=0A "Headse= t Stereophone", "HSOR",=0A "Line Out", "AUXL",=0A "Line Out", "AUXR",= =0A "HSMIC", "Headset Mic",=0A "Headset Mic", "Headset Mic Bias",=0A = "AFML", "Line In",=0A "AFMR", "Line In",=0A "Headset Playback", "PDM_DL= 1",=0A "PDM_UL1", "Capture",=0A "40122000.mcbsp Playback", "BT_VX_DL",= =0A "BT_VX_UL", "40122000.mcbsp Capture",=0A "40124000.mcbsp Playback",= "MM_EXT_DL",=0A "MM_EXT_UL", "40124000.mcbsp Capture";=0A };=0A=0A sound= _hdmi {=0A compatible =3D "ti,omap-hdmi-tpd12s015-audio";=0A ti,model =3D= "OMAP5HDMI";=0A=0A ti,hdmi_audio =3D <&hdmi>;=0A ti,level_shifter =3D <&= tpd12s015>;=0A };=0A=0A /* HS USB Port 2 RESET */=0A hsusb2_reset: hsusb2_r= eset_reg {=0A compatible =3D "regulator-fixed";=0A regulator-name =3D "hs= usb2_reset";=0A regulator-min-microvolt =3D <3300000>;=0A regulator-max-m= icrovolt =3D <3300000>;=0A gpio =3D <&gpio3 16 0>; /* gpio3_80 HUB_NRESET = */=0A startup-delay-us =3D <70000>;=0A enable-active-high;=0A };=0A=0A /*= HS USB Host PHY on PORT 2 */=0A hsusb2_phy: hsusb2_phy {=0A compatible = =3D "usb-nop-xceiv";=0A reset-supply =3D <&hsusb2_reset>;=0A };=0A=0A /* H= S USB Port 3 RESET */=0A hsusb3_reset: hsusb3_reset_reg {=0A compatible = =3D "regulator-fixed";=0A regulator-name =3D "hsusb3_reset";=0A regulator= -min-microvolt =3D <3300000>;=0A regulator-max-microvolt =3D <3300000>;=0A= gpio =3D <&gpio3 15 0>; /* gpio3_79 ETH_NRESET */=0A startup-delay-us = =3D <70000>;=0A enable-active-high;=0A };=0A=0A /* HS USB Host PHY on PORT= 3 */=0A hsusb3_phy: hsusb3_phy {=0A compatible =3D "usb-nop-xceiv";=0A r= eset-supply =3D <&hsusb3_reset>;=0A };=0A=0A /* hsusb2_phy is clocked by FR= EF_CLK1 i.e. auxclk1 */=0A clock_alias {=0A clock-name =3D "auxclk1_ck";= =0A clock-alias =3D "main_clk";=0A device =3D <&hsusb2_phy>;=0A clock-fr= equency =3D <19200000>; /* 19.2 MHz */=0A };=0A};=0A=0A&mmc1 {=0A vmmc-supp= ly =3D <&vmmcsd_fixed>;=0A vmmc-aux-supply =3D <&ldo9_reg>;=0A bus-width = =3D <4>;=0A};=0A=0A&mmc2 {=0A vmmc-supply =3D <&vmmcsd_fixed>;=0A vmmc-aux-= supply =3D <&ldo9_reg>;=0A bus-width =3D <8>;=0A ti,non-removable;=0A};=0A= =0A&mmc3 {=0A bus-width =3D <4>;=0A ti,non-removable;=0A};=0A=0A&mmc4 {=0A = status =3D "disabled";=0A};=0A=0A&mmc5 {=0A status =3D "disabled";=0A};=0A= =0A&i2c1 {=0A clock-frequency =3D <400000>;=0A=0A palmas: palmas@48 {=0A r= eg =3D <0x48>;=0A /* SPI =3D 0, IRQ# =3D 7, 4 =3D active high level-sensit= ive */=0A interrupts =3D <0 7 4>; /* IRQ_SYS_1N cascaded to gic */=0A int= errupt-parent =3D <&gic>;=0A };=0A=0A twl6040: twl@4b {=0A compatible =3D = "ti,twl6040";=0A=0A interrupts =3D <0 119 4>; /* IRQ_SYS_2N cascaded to gi= c */=0A interrupt-parent =3D <&gic>;=0A ti,audpwron-gpio =3D <&gpio5 13 0= >; /* gpio line 141 */=0A=0A vio-supply =3D <&smps7_reg>;=0A v2v1-supply= =3D <&smps9_reg>;=0A enable-active-high;=0A };=0A};=0A=0A=0A&i2c5 {=0A tc= a6424a: tca6424a@22 {=0A compatible =3D "ti,tca6424a";=0A reg =3D <0x22>;= =0A gpio-controller;=0A #gpio-cells =3D <2>;=0A };=0A};=0A=0A&omap5_pmx_c= ore {=0A pinctrl-names =3D "default";=0A pinctrl-0 =3D <=0A &twl6040_pins= =0A &mcpdm_pins=0A &dmic_pins=0A &mcbsp1_pins=0A &mcbsp2_pins=0A = &i2c5_pins=0A &usbhost_pins=0A &dss_hdmi_pins=0A &tpd12s015_pins=0A >= ;=0A=0A twl6040_pins: pinmux_twl6040_pins {=0A pinctrl-single,pins =3D <= =0A 0x17e 0x6 /* mcspi1_somi.gpio5_141 OUTPUT | MODE6 */=0A >;=0A };=0A= =0A mcpdm_pins: pinmux_mcpdm_pins {=0A pinctrl-single,pins =3D <=0A 0x14= 2 0x108 /* abe_clks.abe_clks INPUT PULLDOWN | MODE0 */=0A 0x15c 0x108 /* = abemcpdm_ul_data.abemcpdm_ul_data INPUT PULLDOWN | MODE0 */=0A 0x15e 0x10= 8 /* abemcpdm_dl_data.abemcpdm_dl_data INPUT PULLDOWN | MODE0 */=0A 0x160= 0x118 /* abemcpdm_frame.abemcpdm_frame INPUT PULLUP | MODE0 */=0A 0x162 = 0x108 /* abemcpdm_lb_clk.abemcpdm_lb_clk INPUT PULLDOWN | MODE0 */=0A >;= =0A };=0A=0A dmic_pins: pinmux_dmic_pins {=0A pinctrl-single,pins =3D <=0A= 0x144 0x100 /* abedmic_din1.abedmic_din1 INPUT | MODE0 */=0A 0x146 0x1= 00 /* abedmic_din2.abedmic_din2 INPUT | MODE0 */=0A 0x148 0x100 /* abedmi= c_din3.abedmic_din3 INPUT | MODE0 */=0A 0x14a 0 /* abedmic_clk1.abedmic_= clk1 OUTPUT | MODE0 */=0A >;=0A };=0A=0A mcbsp1_pins: pinmux_mcbsp1_pins {= =0A pinctrl-single,pins =3D <=0A 0x14c 0x101 /* abedmic_clk2.abemcbsp1_f= sx INPUT | MODE1 */=0A 0x14e 0x9 /* abedmic_clk3.abemcbsp1_dx OUTPUT PULL= DOWN | MODE1 */=0A 0x150 0x101 /* abeslimbus1_clock.abemcbsp1_clkx INPUT = | MODE0 */=0A 0x152 0x109 /* abeslimbus1_data.abemcbsp1_dr INPUT PULLDOWN= | MODE1 */=0A >;=0A };=0A=0A mcbsp2_pins: pinmux_mcbsp2_pins {=0A pinctr= l-single,pins =3D <=0A 0x154 0x108 /* abemcbsp2_dr.abemcbsp2_dr INPUT PUL= LDOWN | MODE0 */=0A 0x156 0x8 /* abemcbsp2_dx.abemcbsp2_dx OUTPUT PULLDOW= N | MODE0 */=0A 0x158 0x100 /* abemcbsp2_fsx.abemcbsp2_fsx INPUT | MODE0 = */=0A 0x15a 0x100 /* abemcbsp2_clkx.abemcbsp2_clkx INPUT | MODE0 */=0A >= ;=0A };=0A=0A i2c5_pins: pinmux_i2c5_pins {=0A pinctrl-single,pins =3D <= =0A 0x186 0x100 /* i2c5_scl.i2c5_scl INPUT | MODE0 */=0A 0x188 0x100 /*= i2c5_sda.i2c5_sda INPUT | MODE0 */=0A >;=0A };=0A=0A usbhost_pins: pinmux= _usbhost_pins {=0A pinctrl-single,pins =3D <=0A 0x84 0x100 /* usbb2_hsic= _strobe INPUT | MODE 0 */=0A 0x86 0x100 /* usbb2_hsic_data INPUT | MODE 0= */=0A=0A 0x19e 0x100 /* usbb3_hsic_strobe INPUT | MODE 0 */=0A 0x1a0 0= x100 /* usbb3_hsic_data INPUT | MODE 0 */=0A=0A 0x70 0x6 /* gpio3_80 OUTP= UT | MODE 6 HUB_NRESET */=0A 0x6e 0x6 /* gpio3_79 OUTPUT | MODE 6 ETH_NRE= SET */=0A >;=0A };=0A=0A dss_hdmi_pins: pinmux_dss_hdmi_pins {=0A pinctrl= -single,pins =3D <=0A 0x0fc 0x118 /* hdmi_cec.hdmi_cec INPUT PULLUP | MOD= E 0 */=0A 0x100 0x100 /* hdmi_scl.hdmi_scl INPUT | MODE 0 */=0A 0x102 0= x100 /* hdmi_sda.hdmi_sda INPUT | MODE 0 */=0A >;=0A };=0A=0A tpd12s015_pi= ns: pinmux_tpd12s015_pins {=0A pinctrl-single,pins =3D <=0A 0x0fe 0x116 = /* hdmi_hpd.gpio7_193 INPUT PULLDOWN | MODE6 */=0A >;=0A };=0A};=0A=0A&oma= p5_pmx_wkup {=0A pinctrl-names =3D "default";=0A pinctrl-0 =3D <=0A &usbh= ost_wkup_pins=0A >;=0A=0A usbhost_wkup_pins: pinmux_usbhost_wkup_pins {=0A = pinctrl-single,pins =3D <=0A 0x1A 0x0 /* fref_clk1_out OUTPUT | MODE 7 f= or USB hub clk */=0A >;=0A };=0A};=0A=0A&i2c5 {=0A tca6424a: tca6424a@22 {= =0A compatible =3D "ti,tca6424a";=0A gpio-controller;=0A #gpio-cells =3D= <2>;=0A reg =3D <0x22>;=0A };=0A};=0A=0A&usbhshost {=0A port2-mode =3D "e= hci-hsic";=0A port3-mode =3D "ehci-hsic";=0A};=0A=0A&usbhsehci {=0A phys = =3D <0 &hsusb2_phy &hsusb3_phy>;=0A};=0A=0A&hdmi {=0A tpd12s015: tpd12s015 = {=0A compatible =3D "ti,tpd12s015";=0A=0A gpios =3D <&tca6424a 0 0>, /* T= CA6424A P01, CT_CP_HDP */=0A <&tca6424a 1 0>, /* TCA6424A P00, LS_OE*/=0A= <&gpio7 1 0>; /* 193, HPD */=0A=0A hdmi-monitor {=0A compatible =3D = "ti,hdmi_panel";=0A };=0A=0A };=0A};=0A=0A/include/ "palmas.dtsi"=0A/inclu= de/ "twl6040.dtsi"=0A --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm --J2SCkAp4GZ/dPZZf-- From xen-arm-bounces@lists.xen.org Mon Jul 01 12:58:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:58:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utdh1-00055s-Jq; Mon, 01 Jul 2013 12:58:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utdgz-00055f-Qw; Mon, 01 Jul 2013 12:58:54 +0000 Received: from [193.109.254.147:9543] by server-1.bemta-14.messagelabs.com id B5/33-20106-D0D71D15; Mon, 01 Jul 2013 12:58:53 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1372683530!9708774!1 X-Originating-IP: [209.85.220.42] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3357 invoked from network); 1 Jul 2013 12:58:51 -0000 Received: from mail-pa0-f42.google.com (HELO mail-pa0-f42.google.com) (209.85.220.42) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:58:51 -0000 Received: by mail-pa0-f42.google.com with SMTP id rl6so5020648pac.1 for ; Mon, 01 Jul 2013 05:58:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=s6IMsLvhDj7Fb56cjePD3XzXJgwVvGIJtds32ti5fhw=; b=0gz1hu0w4+Jfw5NfC7ZUp2BAqP5RMVLTxYuZWm4/WilLM3icShoItnD5ZASBn/xwUI WnEHGnLvu8RCadH/ghJIqdXAemaIvl5pawvZvvNXib6Eb85CJWwq5nT2sgtrZhTBpHS5 SF2yWluqEPdNyET3Cx0P0cLcT0k+bDynW5pBFViFHtjucMONzECIRn3la+osYXR9H3Nk nC6QDy4qei5WAeejvWrmRu38/LxtTH3YNAakkgAZf3ZfR1Q+jtVJxJQ59e9Vuvrp02nD cwww0vxoVhgW0e61nJ2EL5pYwCauTetfaEMNqdyfbogp1P8KAIpxvl5Js6FLHxuMFnMI RKRg== X-Received: by 10.68.175.228 with SMTP id cd4mr24067549pbc.40.1372683529817; Mon, 01 Jul 2013 05:58:49 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id ue9sm23876626pab.7.2013.07.01.05.58.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 05:58:49 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <20130701124327.GA25341@cbz-workstation> Date: Mon, 1 Jul 2013 20:58:41 +0800 Message-Id: <66BD0E7A-C989-4DA2-98F0-7F0435E0ECEF@gmail.com> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> <20130701124327.GA25341@cbz-workstation> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 8:43 PM, Chen Baozi wrote: > On Mon, Jul 01, 2013 at 01:39:02PM +0100, Ian Campbell wrote: >> On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: >>> On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: >>> >>>> On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: >>>> >>>>>> You device has 2GB RAM, what happens if you hack the DTS to say it only >>>>>> has 1GB? >>>>> >>>>> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: >>>>> >>>>> memory { >>>>> device_type = "memory" >>>>> - reg = <0x80000000 0x80000000>; /* 2 GB */ >>>>> + reg = <0x80000000 0x40000000>; /* 1 GB */ >>>>> }; >>>>> >>>>> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". >>>> >>>> Excellent! >>>> >>>> So I guess if you keep the 2GB but put it at the right address it will >>>> also work? >>> >>> I'm afraid no, :-( >>> >>> Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): >>> >>> OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage >>> reading xen-uImage >>> 902572 bytes read in 59 ms (14.6 MiB/s) >>> OMAP5430 EVM # bootm 0x80000000 - >>> ## Booting kernel from Legacy Image at 80000000 ... >>> Image Name: >>> Image Type: ARM Linux Kernel Image (uncompressed) >>> Data Size: 902508 Bytes = 881.4 KiB >>> Load Address: 80200000 >>> Entry Point: 80200000 >>> Verifying Checksum ... OK >>> Loading Kernel Image ... OK >>> OK >> >>> And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both >>> cases. It works for 1GB but fails in 2GB case too. >> >> What is the base address of RAM on the A31 SoC? > > A31 SoC? I use OMAP5432 ES2.0 uEVM (OMAP5 Panda) board. > > The attachment is the dts file which the linux kernel uses on this board by > default, which the memory line is: > > reg = <0x80000000 0x80000000>; /* 2 GB */ > However, interestingly, in omap5-evm.dts, it writes: reg = <0x80000000 0x7F000000>; /* 2032 MB */ And if I use this line, it works! So I think this might be the point. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 12:58:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 12:58:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utdh1-00055s-Jq; Mon, 01 Jul 2013 12:58:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utdgz-00055f-Qw; Mon, 01 Jul 2013 12:58:54 +0000 Received: from [193.109.254.147:9543] by server-1.bemta-14.messagelabs.com id B5/33-20106-D0D71D15; Mon, 01 Jul 2013 12:58:53 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1372683530!9708774!1 X-Originating-IP: [209.85.220.42] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3357 invoked from network); 1 Jul 2013 12:58:51 -0000 Received: from mail-pa0-f42.google.com (HELO mail-pa0-f42.google.com) (209.85.220.42) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 12:58:51 -0000 Received: by mail-pa0-f42.google.com with SMTP id rl6so5020648pac.1 for ; Mon, 01 Jul 2013 05:58:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=s6IMsLvhDj7Fb56cjePD3XzXJgwVvGIJtds32ti5fhw=; b=0gz1hu0w4+Jfw5NfC7ZUp2BAqP5RMVLTxYuZWm4/WilLM3icShoItnD5ZASBn/xwUI WnEHGnLvu8RCadH/ghJIqdXAemaIvl5pawvZvvNXib6Eb85CJWwq5nT2sgtrZhTBpHS5 SF2yWluqEPdNyET3Cx0P0cLcT0k+bDynW5pBFViFHtjucMONzECIRn3la+osYXR9H3Nk nC6QDy4qei5WAeejvWrmRu38/LxtTH3YNAakkgAZf3ZfR1Q+jtVJxJQ59e9Vuvrp02nD cwww0vxoVhgW0e61nJ2EL5pYwCauTetfaEMNqdyfbogp1P8KAIpxvl5Js6FLHxuMFnMI RKRg== X-Received: by 10.68.175.228 with SMTP id cd4mr24067549pbc.40.1372683529817; Mon, 01 Jul 2013 05:58:49 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id ue9sm23876626pab.7.2013.07.01.05.58.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 05:58:49 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <20130701124327.GA25341@cbz-workstation> Date: Mon, 1 Jul 2013 20:58:41 +0800 Message-Id: <66BD0E7A-C989-4DA2-98F0-7F0435E0ECEF@gmail.com> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> <20130701124327.GA25341@cbz-workstation> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 8:43 PM, Chen Baozi wrote: > On Mon, Jul 01, 2013 at 01:39:02PM +0100, Ian Campbell wrote: >> On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: >>> On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: >>> >>>> On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: >>>> >>>>>> You device has 2GB RAM, what happens if you hack the DTS to say it only >>>>>> has 1GB? >>>>> >>>>> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: >>>>> >>>>> memory { >>>>> device_type = "memory" >>>>> - reg = <0x80000000 0x80000000>; /* 2 GB */ >>>>> + reg = <0x80000000 0x40000000>; /* 1 GB */ >>>>> }; >>>>> >>>>> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". >>>> >>>> Excellent! >>>> >>>> So I guess if you keep the 2GB but put it at the right address it will >>>> also work? >>> >>> I'm afraid no, :-( >>> >>> Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): >>> >>> OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage >>> reading xen-uImage >>> 902572 bytes read in 59 ms (14.6 MiB/s) >>> OMAP5430 EVM # bootm 0x80000000 - >>> ## Booting kernel from Legacy Image at 80000000 ... >>> Image Name: >>> Image Type: ARM Linux Kernel Image (uncompressed) >>> Data Size: 902508 Bytes = 881.4 KiB >>> Load Address: 80200000 >>> Entry Point: 80200000 >>> Verifying Checksum ... OK >>> Loading Kernel Image ... OK >>> OK >> >>> And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both >>> cases. It works for 1GB but fails in 2GB case too. >> >> What is the base address of RAM on the A31 SoC? > > A31 SoC? I use OMAP5432 ES2.0 uEVM (OMAP5 Panda) board. > > The attachment is the dts file which the linux kernel uses on this board by > default, which the memory line is: > > reg = <0x80000000 0x80000000>; /* 2 GB */ > However, interestingly, in omap5-evm.dts, it writes: reg = <0x80000000 0x7F000000>; /* 2032 MB */ And if I use this line, it works! So I think this might be the point. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 13:02:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 13:02:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utdjx-0005P0-Vo; Mon, 01 Jul 2013 13:01:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utdjw-0005Oi-Mb; Mon, 01 Jul 2013 13:01:56 +0000 Received: from [85.158.136.67:19338] by server-9.bemta-5.messagelabs.com id A9/CF-26025-3CD71D15; Mon, 01 Jul 2013 13:01:55 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-207.messagelabs.com!1372683715!19345870!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16736 invoked from network); 1 Jul 2013 13:01:55 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-207.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 13:01:55 -0000 X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="6247902" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 13:01:54 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 14:01:54 +0100 Message-ID: <1372683713.14691.73.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 14:01:53 +0100 In-Reply-To: <20130701124327.GA25341@cbz-workstation> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> <20130701124327.GA25341@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 20:43 +0800, Chen Baozi wrote: > On Mon, Jul 01, 2013 at 01:39:02PM +0100, Ian Campbell wrote: > > On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: > > > On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > > > > > > > On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > > > > > > > >>> You device has 2GB RAM, what happens if you hack the DTS to say it only > > > >>> has 1GB? > > > >> > > > >> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > > > >> > > > >> memory { > > > >> device_type = "memory" > > > >> - reg = <0x80000000 0x80000000>; /* 2 GB */ > > > >> + reg = <0x80000000 0x40000000>; /* 1 GB */ > > > >> }; > > > >> > > > >> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > > > > > > > > Excellent! > > > > > > > > So I guess if you keep the 2GB but put it at the right address it will > > > > also work? > > > > > > I'm afraid no, :-( > > > > > > Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): > > > > > > OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage > > > reading xen-uImage > > > 902572 bytes read in 59 ms (14.6 MiB/s) > > > OMAP5430 EVM # bootm 0x80000000 - > > > ## Booting kernel from Legacy Image at 80000000 ... > > > Image Name: > > > Image Type: ARM Linux Kernel Image (uncompressed) > > > Data Size: 902508 Bytes = 881.4 KiB > > > Load Address: 80200000 > > > Entry Point: 80200000 > > > Verifying Checksum ... OK > > > Loading Kernel Image ... OK > > > OK > > > > > And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both > > > cases. It works for 1GB but fails in 2GB case too. > > > > What is the base address of RAM on the A31 SoC? > > A31 SoC? I use OMAP5432 ES2.0 uEVM (OMAP5 Panda) board. Oh, sorry, I conflated your and Bamvor's systems in my mind after discussing combining the serial drivers last week. His is an A31 thing. > The attachment is the dts file which the linux kernel uses on this board by > default, which the memory line is: > > reg = <0x80000000 0x80000000>; /* 2 GB */ OK. So I wonder why that doesn't work for us then. Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 13:02:00 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 13:02:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utdjx-0005P0-Vo; Mon, 01 Jul 2013 13:01:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Utdjw-0005Oi-Mb; Mon, 01 Jul 2013 13:01:56 +0000 Received: from [85.158.136.67:19338] by server-9.bemta-5.messagelabs.com id A9/CF-26025-3CD71D15; Mon, 01 Jul 2013 13:01:55 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-207.messagelabs.com!1372683715!19345870!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16736 invoked from network); 1 Jul 2013 13:01:55 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-207.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 13:01:55 -0000 X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="6247902" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 13:01:54 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 14:01:54 +0100 Message-ID: <1372683713.14691.73.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 14:01:53 +0100 In-Reply-To: <20130701124327.GA25341@cbz-workstation> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> <20130701124327.GA25341@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 20:43 +0800, Chen Baozi wrote: > On Mon, Jul 01, 2013 at 01:39:02PM +0100, Ian Campbell wrote: > > On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: > > > On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > > > > > > > On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > > > > > > > >>> You device has 2GB RAM, what happens if you hack the DTS to say it only > > > >>> has 1GB? > > > >> > > > >> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > > > >> > > > >> memory { > > > >> device_type = "memory" > > > >> - reg = <0x80000000 0x80000000>; /* 2 GB */ > > > >> + reg = <0x80000000 0x40000000>; /* 1 GB */ > > > >> }; > > > >> > > > >> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > > > > > > > > Excellent! > > > > > > > > So I guess if you keep the 2GB but put it at the right address it will > > > > also work? > > > > > > I'm afraid no, :-( > > > > > > Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): > > > > > > OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage > > > reading xen-uImage > > > 902572 bytes read in 59 ms (14.6 MiB/s) > > > OMAP5430 EVM # bootm 0x80000000 - > > > ## Booting kernel from Legacy Image at 80000000 ... > > > Image Name: > > > Image Type: ARM Linux Kernel Image (uncompressed) > > > Data Size: 902508 Bytes = 881.4 KiB > > > Load Address: 80200000 > > > Entry Point: 80200000 > > > Verifying Checksum ... OK > > > Loading Kernel Image ... OK > > > OK > > > > > And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both > > > cases. It works for 1GB but fails in 2GB case too. > > > > What is the base address of RAM on the A31 SoC? > > A31 SoC? I use OMAP5432 ES2.0 uEVM (OMAP5 Panda) board. Oh, sorry, I conflated your and Bamvor's systems in my mind after discussing combining the serial drivers last week. His is an A31 thing. > The attachment is the dts file which the linux kernel uses on this board by > default, which the memory line is: > > reg = <0x80000000 0x80000000>; /* 2 GB */ OK. So I wonder why that doesn't work for us then. Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 13:03:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 13:03:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdlT-0005aO-Jn; Mon, 01 Jul 2013 13:03:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdlS-0005aC-AM; Mon, 01 Jul 2013 13:03:30 +0000 Received: from [85.158.139.211:32678] by server-13.bemta-5.messagelabs.com id 58/7D-11519-12E71D15; Mon, 01 Jul 2013 13:03:29 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1372683808!19778126!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13904 invoked from network); 1 Jul 2013 13:03:28 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 13:03:28 -0000 X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="6247997" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 13:03:28 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 14:03:27 +0100 Message-ID: <1372683806.14691.75.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 14:03:26 +0100 In-Reply-To: <66BD0E7A-C989-4DA2-98F0-7F0435E0ECEF@gmail.com> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> <20130701124327.GA25341@cbz-workstation> <66BD0E7A-C989-4DA2-98F0-7F0435E0ECEF@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 20:58 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 8:43 PM, Chen Baozi wrote: > > > On Mon, Jul 01, 2013 at 01:39:02PM +0100, Ian Campbell wrote: > >> On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: > >>> On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > >>> > >>>> On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > >>>> > >>>>>> You device has 2GB RAM, what happens if you hack the DTS to say it only > >>>>>> has 1GB? > >>>>> > >>>>> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > >>>>> > >>>>> memory { > >>>>> device_type = "memory" > >>>>> - reg = <0x80000000 0x80000000>; /* 2 GB */ > >>>>> + reg = <0x80000000 0x40000000>; /* 1 GB */ > >>>>> }; > >>>>> > >>>>> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > >>>> > >>>> Excellent! > >>>> > >>>> So I guess if you keep the 2GB but put it at the right address it will > >>>> also work? > >>> > >>> I'm afraid no, :-( > >>> > >>> Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): > >>> > >>> OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage > >>> reading xen-uImage > >>> 902572 bytes read in 59 ms (14.6 MiB/s) > >>> OMAP5430 EVM # bootm 0x80000000 - > >>> ## Booting kernel from Legacy Image at 80000000 ... > >>> Image Name: > >>> Image Type: ARM Linux Kernel Image (uncompressed) > >>> Data Size: 902508 Bytes = 881.4 KiB > >>> Load Address: 80200000 > >>> Entry Point: 80200000 > >>> Verifying Checksum ... OK > >>> Loading Kernel Image ... OK > >>> OK > >> > >>> And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both > >>> cases. It works for 1GB but fails in 2GB case too. > >> > >> What is the base address of RAM on the A31 SoC? > > > > A31 SoC? I use OMAP5432 ES2.0 uEVM (OMAP5 Panda) board. > > > > The attachment is the dts file which the linux kernel uses on this board by > > default, which the memory line is: > > > > reg = <0x80000000 0x80000000>; /* 2 GB */ > > > However, interestingly, in omap5-evm.dts, it writes: > > reg = <0x80000000 0x7F000000>; /* 2032 MB */ > > And if I use this line, it works! > > So I think this might be the point. Huzzah! It certainly is important to use a DTB which accurately describes the exact hardware. I bet some RAM is carved out for video RAM or secure world use or something... Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 13:03:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 13:03:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdlT-0005aO-Jn; Mon, 01 Jul 2013 13:03:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UtdlS-0005aC-AM; Mon, 01 Jul 2013 13:03:30 +0000 Received: from [85.158.139.211:32678] by server-13.bemta-5.messagelabs.com id 58/7D-11519-12E71D15; Mon, 01 Jul 2013 13:03:29 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1372683808!19778126!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13904 invoked from network); 1 Jul 2013 13:03:28 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 13:03:28 -0000 X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="6247997" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 01 Jul 2013 13:03:28 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Mon, 1 Jul 2013 14:03:27 +0100 Message-ID: <1372683806.14691.75.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 1 Jul 2013 14:03:26 +0100 In-Reply-To: <66BD0E7A-C989-4DA2-98F0-7F0435E0ECEF@gmail.com> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> <20130701124327.GA25341@cbz-workstation> <66BD0E7A-C989-4DA2-98F0-7F0435E0ECEF@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 2013-07-01 at 20:58 +0800, Chen Baozi wrote: > On Jul 1, 2013, at 8:43 PM, Chen Baozi wrote: > > > On Mon, Jul 01, 2013 at 01:39:02PM +0100, Ian Campbell wrote: > >> On Mon, 2013-07-01 at 20:32 +0800, Chen Baozi wrote: > >>> On Jul 1, 2013, at 8:06 PM, Ian Campbell wrote: > >>> > >>>> On Mon, 2013-07-01 at 20:00 +0800, Chen Baozi wrote: > >>>> > >>>>>> You device has 2GB RAM, what happens if you hack the DTS to say it only > >>>>>> has 1GB? > >>>>> > >>>>> Bingo! Compared to Arndale board, OMAP5432 uEVM's RAM is not yet 0x40000000~0xbfffffff, but 0x80000000~0xffffffff. After make the following change to DTS: > >>>>> > >>>>> memory { > >>>>> device_type = "memory" > >>>>> - reg = <0x80000000 0x80000000>; /* 2 GB */ > >>>>> + reg = <0x80000000 0x40000000>; /* 1 GB */ > >>>>> }; > >>>>> > >>>>> I can reach the output "Xen heap: 131072 pages Dom heap: 131072 pages". > >>>> > >>>> Excellent! > >>>> > >>>> So I guess if you keep the 2GB but put it at the right address it will > >>>> also work? > >>> > >>> I'm afraid no, :-( > >>> > >>> Here is how I load and boot the image both in 1GB case and 2G case (from u-boot): > >>> > >>> OMAP5430 EVM # fatload mmc 0 0x80000000 xen-uImage > >>> reading xen-uImage > >>> 902572 bytes read in 59 ms (14.6 MiB/s) > >>> OMAP5430 EVM # bootm 0x80000000 - > >>> ## Booting kernel from Legacy Image at 80000000 ... > >>> Image Name: > >>> Image Type: ARM Linux Kernel Image (uncompressed) > >>> Data Size: 902508 Bytes = 881.4 KiB > >>> Load Address: 80200000 > >>> Entry Point: 80200000 > >>> Verifying Checksum ... OK > >>> Loading Kernel Image ... OK > >>> OK > >> > >>> And I've also tried "fat load mmc 0 0x90000000 xen-uImage" in both > >>> cases. It works for 1GB but fails in 2GB case too. > >> > >> What is the base address of RAM on the A31 SoC? > > > > A31 SoC? I use OMAP5432 ES2.0 uEVM (OMAP5 Panda) board. > > > > The attachment is the dts file which the linux kernel uses on this board by > > default, which the memory line is: > > > > reg = <0x80000000 0x80000000>; /* 2 GB */ > > > However, interestingly, in omap5-evm.dts, it writes: > > reg = <0x80000000 0x7F000000>; /* 2032 MB */ > > And if I use this line, it works! > > So I think this might be the point. Huzzah! It certainly is important to use a DTB which accurately describes the exact hardware. I bet some RAM is carved out for video RAM or secure world use or something... Ian. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 13:44:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 13:44:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UteOz-0006xl-3y; Mon, 01 Jul 2013 13:44:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UteOx-0006xd-OO; Mon, 01 Jul 2013 13:44:19 +0000 Received: from [85.158.139.211:46795] by server-12.bemta-5.messagelabs.com id F0/42-22750-2B781D15; Mon, 01 Jul 2013 13:44:18 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1372686253!17560009!1 X-Originating-IP: [209.85.160.49] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20144 invoked from network); 1 Jul 2013 13:44:15 -0000 Received: from mail-pb0-f49.google.com (HELO mail-pb0-f49.google.com) (209.85.160.49) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 13:44:15 -0000 Received: by mail-pb0-f49.google.com with SMTP id jt11so4797696pbb.36 for ; Mon, 01 Jul 2013 06:44:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=IBlXsMPPSF1/clx18UcZIKcArbSl09rBQksaUF23AXI=; b=nxXI4rs620EyHoG1xBDDAbp8qjulPiExPWbwLARebcXN2XvMe43a6PxjCtH24pXMFY Tn2VLcrKUlOOXnPBfZhUgv70vA7RUxiNqoi51WdNYxM/dJC+Panjug2VhvI0ywE7sEOK BCPWCjChAIiRC5JBRwzLDTLeBm4QLeoFmWC8khGKbtYEwh/36hXffEXgdelVGlEEQH4/ vQOLvAn9jSNpujoeRMK/FGoxxwXnyJdhNmmXP82cpo9FMCtB8zC4Lk0LsEpjjAnawFaY h5aVud2bSO3dFrc0oIFhhgY1htKhX1OwtkuJlx5MdDfFwr8AJv6gbaglLMJIzwtcCPM5 h+SA== X-Received: by 10.66.157.68 with SMTP id wk4mr24299888pab.17.1372686252945; Mon, 01 Jul 2013 06:44:12 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id jf4sm22399863pbb.19.2013.07.01.06.43.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 06:44:12 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372683806.14691.75.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 21:43:42 +0800 Message-Id: <0F3409E3-8FB3-4599-817E-1799A53AF5FA@gmail.com> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> <20130701124327.GA25341@cbz-workstation> <66BD0E7A-C989-4DA2-98F0-7F0435E0ECEF@gmail.com> <1372683806.14691.75.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 9:03 PM, Ian Campbell wrote: > Huzzah! > > It certainly is important to use a DTB which accurately describes the > exact hardware. > > I bet some RAM is carved out for video RAM or secure world use or > something... Aha, I've found the commit log of omap5-evm.dts's memory line: ARM: dts: omap5-evm: Update available memory to 2032 MB On OMAP5 to detect invalid/bad memory accesses, 16MB of DDR is used as a trap. Hence available memory for linux OS is 2032 MB on boards populated with 2 GB memory. So I think we've finally got the cause. Cheers, Baozi. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Mon Jul 01 13:44:24 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 01 Jul 2013 13:44:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UteOz-0006xl-3y; Mon, 01 Jul 2013 13:44:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UteOx-0006xd-OO; Mon, 01 Jul 2013 13:44:19 +0000 Received: from [85.158.139.211:46795] by server-12.bemta-5.messagelabs.com id F0/42-22750-2B781D15; Mon, 01 Jul 2013 13:44:18 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1372686253!17560009!1 X-Originating-IP: [209.85.160.49] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20144 invoked from network); 1 Jul 2013 13:44:15 -0000 Received: from mail-pb0-f49.google.com (HELO mail-pb0-f49.google.com) (209.85.160.49) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Jul 2013 13:44:15 -0000 Received: by mail-pb0-f49.google.com with SMTP id jt11so4797696pbb.36 for ; Mon, 01 Jul 2013 06:44:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=IBlXsMPPSF1/clx18UcZIKcArbSl09rBQksaUF23AXI=; b=nxXI4rs620EyHoG1xBDDAbp8qjulPiExPWbwLARebcXN2XvMe43a6PxjCtH24pXMFY Tn2VLcrKUlOOXnPBfZhUgv70vA7RUxiNqoi51WdNYxM/dJC+Panjug2VhvI0ywE7sEOK BCPWCjChAIiRC5JBRwzLDTLeBm4QLeoFmWC8khGKbtYEwh/36hXffEXgdelVGlEEQH4/ vQOLvAn9jSNpujoeRMK/FGoxxwXnyJdhNmmXP82cpo9FMCtB8zC4Lk0LsEpjjAnawFaY h5aVud2bSO3dFrc0oIFhhgY1htKhX1OwtkuJlx5MdDfFwr8AJv6gbaglLMJIzwtcCPM5 h+SA== X-Received: by 10.66.157.68 with SMTP id wk4mr24299888pab.17.1372686252945; Mon, 01 Jul 2013 06:44:12 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id jf4sm22399863pbb.19.2013.07.01.06.43.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 06:44:12 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Chen Baozi In-Reply-To: <1372683806.14691.75.camel@zakaz.uk.xensource.com> Date: Mon, 1 Jul 2013 21:43:42 +0800 Message-Id: <0F3409E3-8FB3-4599-817E-1799A53AF5FA@gmail.com> References: <4A3B65D6-D82D-44AB-8135-4F86A189ECA2@gmail.com> <1372671036.14691.49.camel@zakaz.uk.xensource.com> <1372672679.14691.50.camel@zakaz.uk.xensource.com> <92525597-A6A4-4B90-B497-18BD40A875D3@gmail.com> <1372678297.14691.61.camel@zakaz.uk.xensource.com> <46544C0F-F507-4DF3-8182-427D6A54687C@gmail.com> <1372680387.14691.62.camel@zakaz.uk.xensource.com> <1372682342.14691.65.camel@zakaz.uk.xensource.com> <20130701124327.GA25341@cbz-workstation> <66BD0E7A-C989-4DA2-98F0-7F0435E0ECEF@gmail.com> <1372683806.14691.75.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1508) Cc: xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] Problems when booting on OMAP5432 devboard X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Jul 1, 2013, at 9:03 PM, Ian Campbell wrote: > Huzzah! > > It certainly is important to use a DTB which accurately describes the > exact hardware. > > I bet some RAM is carved out for video RAM or secure world use or > something... Aha, I've found the commit log of omap5-evm.dts's memory line: ARM: dts: omap5-evm: Update available memory to 2032 MB On OMAP5 to detect invalid/bad memory accesses, 16MB of DDR is used as a trap. Hence available memory for linux OS is 2032 MB on boards populated with 2 GB memory. So I think we've finally got the cause. Cheers, Baozi. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Tue Jul 02 16:49:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 02 Jul 2013 16:49:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uu3lt-0002lN-32; Tue, 02 Jul 2013 16:49:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uu3lr-0002lI-Sz for xen-arm@lists.xen.org; Tue, 02 Jul 2013 16:49:40 +0000 Received: from [85.158.143.99:42971] by server-3.bemta-4.messagelabs.com id 5C/4B-29480-3A403D15; Tue, 02 Jul 2013 16:49:39 +0000 X-Env-Sender: rajeshpaul@hotmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1372783777!28780915!1 X-Originating-IP: [65.55.116.42] X-SpamReason: No, hits=0.4 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_60_70, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_2,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10769 invoked from network); 2 Jul 2013 16:49:37 -0000 Received: from blu0-omc1-s31.blu0.hotmail.com (HELO blu0-omc1-s31.blu0.hotmail.com) (65.55.116.42) by server-13.tower-216.messagelabs.com with SMTP; 2 Jul 2013 16:49:37 -0000 Received: from BLU177-W34 ([65.55.116.9]) by blu0-omc1-s31.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 2 Jul 2013 09:49:37 -0700 X-TMN: [BfTo7pJxS4EKn5k3k4QY0jT/gH1UKjFT] X-Originating-Email: [rajeshpaul@hotmail.com] Message-ID: From: Rajesh Paul To: Krishna Pavan Date: Tue, 2 Jul 2013 22:19:36 +0530 Importance: Normal In-Reply-To: References: , , , MIME-Version: 1.0 X-OriginalArrivalTime: 02 Jul 2013 16:49:37.0092 (UTC) FILETIME=[231D3040:01CE7744] Cc: "xen-arm@lists.xen.org" Subject: Re: [XenARM] Xen ARM support for Tegra3 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3950937736593556461==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3950937736593556461== Content-Type: multipart/alternative; boundary="_99bcb131-87cb-469a-9e7b-544e2e368e69_" --_99bcb131-87cb-469a-9e7b-544e2e368e69_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgS3Jpc2huYSwgDQpJIGFtIGxvb2tpbmcgZm9yIHRoZSBsYXN0IHJlbGVhc2VkL2xhdGVzdCBz b3VyY2Ugb2YgWGVuLUFSTShQVikgcG9ydCBmb3IgVGVncmEgMiBIYXJtb255IGJvYXJkLg0KVGhl IHdpa2kgbGVkIG1lIHRvIGh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcvZXh0L2FybS94ZW4tdW5zdGFi bGUuaGcvZmlsZS8yMTdkMTMwMDMwMDAveGVuL2J1dCBhbSBub3Qgc3VyZSBpZiB0aGlzIGlzIHRo ZSBsYXRlc3Qgb25lLg0Kd291bGQgaGVscCBpZiB5b3UgY2FuIHByb3ZpZGUgcG9pbnRlcnMvbGlu a3MgdG8gdGhlIGxhdGVzdCBzb3VyY2UgYXJjaGl2ZXMuLi4NClRoYW5rcyxSYWplc2ggIA0KRGF0 ZTogVGh1LCAyNyBKdW4gMjAxMyAwOTo0OTo1OCArMDUzMA0KU3ViamVjdDogUmU6IFtYZW5BUk1d IFhlbiBBUk0gc3VwcG9ydCBmb3IgVGVncmEzDQpGcm9tOiBwb3N0NHBhdmFuQGdtYWlsLmNvbQ0K VG86IHJhamVzaHBhdWxAaG90bWFpbC5jb20NCkNDOiB4ZW4tYXJtQGxpc3RzLnhlbi5vcmcNCg0K SGkgUmFqZXNoLAogCgoKCgogSGFzIHRoZXJlIGJlZW4gYW4gZWZmb3J0IHRvIHBvcnQgdG8gVGVn cmEgMyA/CkkgZG8gbm90IGtub3cgYW55dGhpbmcgYWJvdXQgVGVncmEgMyBwb3J0LCBhbmQgdGhh dCB0b28gd2l0aCBQVi4KIAoKCgpBbHNvLCBpcyB0aGVyZSBhIGxpbmsgdG8gYSBzdGFibGUgcmVs ZWFzZSBmb3IgVGVncmEgMi4KVGhlcmUgYXJlIHNldmVyYWwgcG9zdHMgcmVsYXRlZCB0byBwb3J0 IG9mIFRlZ3JhMiB3aXRoaW4gWGVuLUFSTSBhcmNoaXZlcywgd2hlcmUgeW91IG1heSBmaW5kLiBJ IGRpZCBub3QgdW5kZXJzdGFuZCB0aGUgd29yZCAnc3RhYmxlJyBob3dldmVyLgoKCgoNCgpSZWdh cmRzLApSYWplc2ggCg0KCgoKRGF0ZTogV2VkLCAyNiBKdW4gMjAxMyAxNTowMjoxMyArMDUzMA0K U3ViamVjdDogUmU6IFtYZW5BUk1dIFhlbiBBUk0gc3VwcG9ydCBmb3IgVGVncmEzDQpGcm9tOiBw b3N0NHBhdmFuQGdtYWlsLmNvbQ0KVG86IHJhamVzaHBhdWxAaG90bWFpbC5jb20NCgpDQzogeGVu LWFybUBsaXN0cy54ZW4ub3JnDQoNCgoKCgpIaSwNCiANCkZvciBUZWdyYTIgaXQncyBhdmFpbGFi bGUuIEkgaGF2ZW4ndCBjb21lIGFjcm9zcyBUZWdyYTMgbmV3cy4NCgogCiAKIAoNCiAKT24gVHVl LCBKdW4gMjUsIDIwMTMgYXQgMTE6MzMgUE0sIFJhamVzaCBQYXVsIDxyYWplc2hwYXVsQGhvdG1h aWwuY29tPiB3cm90ZToNCgoKCkhpIEFsbCwgICAKDQoKT25lIG9mIG15IHByb2plY3QgcmVxdWly ZW1lbnRzIG5lZWQgYm9vdGluZyB0d28gVWJ1bnR1IExpbnV4IGluc3RhbmNlcyBvbiBhIFRlZ3Jh IDMgQm9hcmQoUXVhZC1jb3JlIEFSTSBDb3J0ZXggQTkgTVBDb3JlIHByb2Nlc3NvcikuIEFuZCBJ IHBsYW4gdG8gaG9zdCB0aGVtIG9uIGEgWGVuIEFSTSBiYXNlZCBIeXBlcnZpc29yLiAKDQoKbXkg cXVlcnk6Cg0KCklzIHRoZXJlIGEgc3BlY2lmaWMgc3VwcG9ydCBhdmFpbGFibGUgZm9yIFhlbiAo QVJNIFBWKSBmb3IgQ29ydGV4IEE5IGJhc2VkIHByb2Nlc3NvcnMuIEkgc2VlIHN1cHBvcnQgZm9y IENvcnRleCBBNywgQTE1ICh3aXRoIGgvdyB2aXJ0dWFsaXphdGlvbiBleHRlbnNpb25zKSBpbiBt YW55IHBsYWNlcywgYnV0IGRpZG4ndCBmaW5kIGFueSBwb2ludGVycy9saW5rcyB0byBDb3J0ZXgg QTkuIAoKDQoKQW55IGluZm9ybWF0aW9uIG9uIHRoaXMgdG9waWMgc2hhbGwgYmUgZ3JlYXRseSBo ZWxwZnVsLgoNCgpNYW55IFRoYW5rcywKUmFqZXNoDQpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXw0KWGVuLWFybSBtYWlsaW5nIGxpc3QNClhlbi1hcm1AbGlz dHMueGVuLm9yZw0KaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZv L3hlbi1hcm0NCgoNCg0KDQotLSANCgrinIkgUmVnYXJkcyA6OiBLcmlzaG5hIFBhdmFuIOKcjQoN Cg0KLS0gDQoKIFJlZ2FyZHMgOjogS3Jpc2huYSBQYXZhbiDinI0KIAkJIAkgICAJCSAg --_99bcb131-87cb-469a-9e7b-544e2e368e69_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxzdHlsZT48IS0tDQouaG1tZXNzYWdlIFANCnsNCm1hcmdpbjowcHg7 DQpwYWRkaW5nOjBweA0KfQ0KYm9keS5obW1lc3NhZ2UNCnsNCmZvbnQtc2l6ZTogMTJwdDsNCmZv bnQtZmFtaWx5OkNhbGlicmkNCn0NCi0tPjwvc3R5bGU+PC9oZWFkPg0KPGJvZHkgY2xhc3M9J2ht bWVzc2FnZSc+PGRpdiBkaXI9J2x0cic+SGkgS3Jpc2huYSwmbmJzcDs8ZGl2Pjxicj48L2Rpdj48 ZGl2PkkgYW0gbG9va2luZyBmb3IgdGhlIGxhc3QgcmVsZWFzZWQvbGF0ZXN0IHNvdXJjZSBvZiBY ZW4tQVJNKFBWKSBwb3J0IGZvciBUZWdyYSAyIEhhcm1vbnkgYm9hcmQuPC9kaXY+PGRpdj48c3Bh biBzdHlsZT0iZm9udC1zaXplOiAxMnB0OyI+PGJyPjwvc3Bhbj48L2Rpdj48ZGl2PjxzcGFuIHN0 eWxlPSJmb250LXNpemU6IDEycHQ7Ij5UaGUgd2lraSBsZWQgbWUgdG8mbmJzcDs8L3NwYW4+PGEg aHJlZj0iaHR0cDovL3hlbmJpdHMueGVuLm9yZy9leHQvYXJtL3hlbi11bnN0YWJsZS5oZy9maWxl LzIxN2QxMzAwMzAwMC94ZW4vIiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImZvbnQtc2l6ZTogMTJw dDsiPmh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcvZXh0L2FybS94ZW4tdW5zdGFibGUuaGcvZmlsZS8y MTdkMTMwMDMwMDAveGVuLzwvYT48L2Rpdj48ZGl2PmJ1dCBhbSBub3Qgc3VyZSBpZiB0aGlzIGlz IHRoZSBsYXRlc3Qgb25lLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+PHNwYW4gc3R5bGU9ImZv bnQtc2l6ZTogMTJwdDsiPndvdWxkIGhlbHAgaWYgeW91IGNhbiBwcm92aWRlIHBvaW50ZXJzL2xp bmtzIHRvIHRoZSBsYXRlc3Qgc291cmNlIGFyY2hpdmVzLi4uPC9zcGFuPjwvZGl2PjxkaXY+PGJy PjwvZGl2PjxkaXY+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTJwdDsiPlRoYW5rcyw8L3NwYW4+ PC9kaXY+PGRpdj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMnB0OyI+UmFqZXNoICZuYnNwOzwv c3Bhbj48L2Rpdj48ZGl2Pjxicj48ZGl2PjxociBpZD0ic3RvcFNwZWxsaW5nIj5EYXRlOiBUaHUs IDI3IEp1biAyMDEzIDA5OjQ5OjU4ICswNTMwPGJyPlN1YmplY3Q6IFJlOiBbWGVuQVJNXSBYZW4g QVJNIHN1cHBvcnQgZm9yIFRlZ3JhMzxicj5Gcm9tOiBwb3N0NHBhdmFuQGdtYWlsLmNvbTxicj5U bzogcmFqZXNocGF1bEBob3RtYWlsLmNvbTxicj5DQzogeGVuLWFybUBsaXN0cy54ZW4ub3JnPGJy Pjxicj48ZGl2IGRpcj0ibHRyIj48ZGl2Pjxmb250IGNvbG9yPSIjOTkzMzk5Ij5IaSBSYWplc2gs PC9mb250PjwvZGl2Pgo8ZGl2PiZuYnNwOzwvZGl2Pgo8ZGl2IGNsYXNzPSJlY3hnbWFpbF9xdW90 ZSI+CjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojY2NjIDFweCBzb2xpZDtNQVJHSU46 MHB4IDBweCAwcHggMC44ZXg7UEFERElORy1MRUZUOjFleDsiIGNsYXNzPSJlY3hnbWFpbF9xdW90 ZSI+CjxkaXY+CjxkaXYgZGlyPSJsdHIiPgo8ZGl2PiZuYnNwO0g8c3Bhbj5hcyB0aGVyZSBiZWVu IGFuIGVmZm9ydCB0byBwb3J0IHRvIFRlZ3JhIDMgPzwvc3Bhbj48L2Rpdj48L2Rpdj48L2Rpdj48 L2Jsb2NrcXVvdGU+CjxkaXY+PGZvbnQgY29sb3I9IiM5OTMzOTkiPkkgZG8gbm90IGtub3cgYW55 dGhpbmcgYWJvdXQgVGVncmEgMyBwb3J0LCBhbmQgdGhhdCB0b28gd2l0aCBQVi48L2ZvbnQ+PC9k aXY+CjxkaXY+Jm5ic3A7PC9kaXY+CjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojY2Nj IDFweCBzb2xpZDtNQVJHSU46MHB4IDBweCAwcHggMC44ZXg7UEFERElORy1MRUZUOjFleDsiIGNs YXNzPSJlY3hnbWFpbF9xdW90ZSI+CjxkaXY+CjxkaXYgZGlyPSJsdHIiPgo8ZGl2PjxzcGFuPkFs c28sIGlzIHRoZXJlIGEgbGluayB0byBhIHN0YWJsZSByZWxlYXNlIGZvciBUZWdyYSAyLjwvc3Bh bj48L2Rpdj48L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+CjxkaXY+PGZvbnQgY29sb3I9IiM5OTMz OTkiPlRoZXJlIGFyZSBzZXZlcmFsIHBvc3RzIHJlbGF0ZWQgdG8gcG9ydCBvZiBUZWdyYTIgd2l0 aGluIFhlbi1BUk0gYXJjaGl2ZXMsIHdoZXJlIHlvdSBtYXkgZmluZC4gSSBkaWQgbm90IHVuZGVy c3RhbmQgdGhlIHdvcmQgJ3N0YWJsZScgaG93ZXZlci48L2ZvbnQ+PC9kaXY+CjxibG9ja3F1b3Rl IHN0eWxlPSJCT1JERVItTEVGVDojY2NjIDFweCBzb2xpZDtNQVJHSU46MHB4IDBweCAwcHggMC44 ZXg7UEFERElORy1MRUZUOjFleDsiIGNsYXNzPSJlY3hnbWFpbF9xdW90ZSI+CjxkaXY+CjxkaXYg ZGlyPSJsdHIiPgo8ZGl2PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+UmVnYXJk cyw8L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+UmFqZXNoJm5ic3A7PC9zcGFuPjwvZGl2Pgo8ZGl2 Pjxicj4KPGRpdj4KPGhyPgpEYXRlOiBXZWQsIDI2IEp1biAyMDEzIDE1OjAyOjEzICswNTMwPGJy PlN1YmplY3Q6IFJlOiBbWGVuQVJNXSBYZW4gQVJNIHN1cHBvcnQgZm9yIFRlZ3JhMzxicj5Gcm9t OiA8YSBocmVmPSJtYWlsdG86cG9zdDRwYXZhbkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5w b3N0NHBhdmFuQGdtYWlsLmNvbTwvYT48YnI+VG86IDxhIGhyZWY9Im1haWx0bzpyYWplc2hwYXVs QGhvdG1haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+cmFqZXNocGF1bEBob3RtYWlsLmNvbTwvYT48 YnI+CkNDOiA8YSBocmVmPSJtYWlsdG86eGVuLWFybUBsaXN0cy54ZW4ub3JnIiB0YXJnZXQ9Il9i bGFuayI+eGVuLWFybUBsaXN0cy54ZW4ub3JnPC9hPjxicj48YnI+CjxkaXYgZGlyPSJsdHIiPgo8 ZGl2Pgo8ZGl2IGNsYXNzPSJoNSI+CjxkaXY+PGZvbnQgY29sb3I9IiM5OTMzOTkiPkhpLDxicj4m bmJzcDs8YnI+Rm9yIFRlZ3JhMiBpdCdzIGF2YWlsYWJsZS4gSSBoYXZlbid0IGNvbWUgYWNyb3Nz IFRlZ3JhMyBuZXdzLjxicj48L2ZvbnQ+PC9kaXY+CjxkaXY+Jm5ic3A7PC9kaXY+CjxkaXY+Jm5i c3A7PC9kaXY+CjxkaXY+Jm5ic3A7PC9kaXY+CjxkaXY+PGJyPiZuYnNwOzwvZGl2Pgo8ZGl2Pk9u IFR1ZSwgSnVuIDI1LCAyMDEzIGF0IDExOjMzIFBNLCBSYWplc2ggUGF1bCA8c3BhbiBkaXI9Imx0 ciI+Jmx0OzxhIGhyZWY9Im1haWx0bzpyYWplc2hwYXVsQGhvdG1haWwuY29tIiB0YXJnZXQ9Il9i bGFuayI+cmFqZXNocGF1bEBob3RtYWlsLmNvbTwvYT4mZ3Q7PC9zcGFuPiB3cm90ZTo8YnI+Cjxi bG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojY2NjIDFweCBzb2xpZDtNQVJHSU46MHB4IDBw eCAwcHggMC44ZXg7UEFERElORy1MRUZUOjFleDsiPgo8ZGl2Pgo8ZGl2IGRpcj0ibHRyIj5IaSBB bGwsICZuYnNwOyAKPGRpdj48YnI+PC9kaXY+CjxkaXY+T25lIG9mIG15IHByb2plY3QgcmVxdWly ZW1lbnRzIG5lZWQgYm9vdGluZyB0d28gVWJ1bnR1IExpbnV4IGluc3RhbmNlcyBvbiBhIFRlZ3Jh IDMgQm9hcmQoUXVhZC1jb3JlIEFSTSBDb3J0ZXggQTkgTVBDb3JlIHByb2Nlc3NvcikuIEFuZCBJ IHBsYW4gdG8gaG9zdCB0aGVtIG9uIGEgWGVuIEFSTSBiYXNlZCBIeXBlcnZpc29yLiZuYnNwOzwv ZGl2Pgo8ZGl2PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+bXkgcXVlcnk6PC9z cGFuPjwvZGl2Pgo8ZGl2PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+SXMgdGhl cmUgYSBzcGVjaWZpYyBzdXBwb3J0IGF2YWlsYWJsZSBmb3ImbmJzcDs8L3NwYW4+PGIgc3R5bGU9 IkxJTkUtSEVJR0hUOjE4cHg7Rk9OVC1GQU1JTFk6QXJpYWwsc2Fucy1zZXJpZjtDT0xPUjpyZ2Io NTEsNTEsNTEpOyI+WGVuIChBUk0gUFYpPC9iPjxzcGFuPiZuYnNwO2ZvciBDb3J0ZXggQTkgYmFz ZWQgcHJvY2Vzc29ycy4gSSBzZWUgc3VwcG9ydCBmb3IgQ29ydGV4IEE3LCBBMTUgKHdpdGggaC93 IHZpcnR1YWxpemF0aW9uIGV4dGVuc2lvbnMpIGluIG1hbnkgcGxhY2VzLCBidXQgZGlkbid0IGZp bmQgYW55IHBvaW50ZXJzL2xpbmtzIHRvIENvcnRleCBBOS4mbmJzcDs8L3NwYW4+PC9kaXY+Cgo8 ZGl2PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+QW55IGluZm9ybWF0aW9uIG9u IHRoaXMgdG9waWMgc2hhbGwgYmUgZ3JlYXRseSBoZWxwZnVsLjwvc3Bhbj48L2Rpdj4KPGRpdj48 c3Bhbj48YnI+PC9zcGFuPjwvZGl2Pgo8ZGl2PjxzcGFuPk1hbnkgVGhhbmtzLDwvc3Bhbj48L2Rp dj4KPGRpdj48c3Bhbj5SYWplc2g8L3NwYW4+PC9kaXY+PC9kaXY+PC9kaXY+PGJyPl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPlhlbi1hcm0gbWFpbGlu ZyBsaXN0PGJyPjxhIGhyZWY9Im1haWx0bzpYZW4tYXJtQGxpc3RzLnhlbi5vcmciIHRhcmdldD0i X2JsYW5rIj5YZW4tYXJtQGxpc3RzLnhlbi5vcmc8L2E+PGJyPjxhIGhyZWY9Imh0dHA6Ly9saXN0 cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXJtIiB0YXJnZXQ9Il9ibGFu ayI+aHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcm08 L2E+PGJyPgo8YnI+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48YnIgY2xlYXI9ImFsbCI+PGJyPi0t IDxicj48L2Rpdj48L2Rpdj4KPGRpdiBkaXI9Imx0ciI+PGZvbnQgc3R5bGU9IkNPTE9SOnJnYigw LDAsMTAyKTsiPjxpbWcgdGl0bGU9IkVudmVsb3BlIiBhbHQ9IkVudmVsb3BlIiBzcmM9Imh0dHBz Oi8vYS5nZngubXMvZW1vamlfMDI3MDkucG5nIj48L2ZvbnQ+PGZvbnQgc3R5bGU9IkNPTE9SOnJn YigwLDAsMTAyKTsiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTpjb21pYyBzYW5zIG1zLHNhbnMt c2VyaWY7Ij4gUmVnYXJkcyA6OiBLcmlzaG5hIFBhdmFuPC9zcGFuPjwvZm9udD4gPHNwYW4gc3R5 bGU9IkNPTE9SOnJnYigwLDAsMTAyKTsiPuKcjTwvc3Bhbj48L2Rpdj4KPC9kaXY+PC9kaXY+PC9k aXY+PC9kaXY+PC9kaXY+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48YnIgY2xlYXI9ImFsbCI+PGJy Pi0tIDxicj4KPGRpdiBkaXI9Imx0ciI+PGZvbnQgc3R5bGU9IkNPTE9SOnJnYigwLDAsMTAyKTsi PjxpbWcgc3JjPSJodHRwczovL2EuZ2Z4Lm1zL2Vtb2ppXzAyNzA5LnBuZyIgY2xhc3M9IkVtb2pp JDAyNzA5JEFDNCBSZW5kZXJlZEVtb2ppIiB0aXRsZT0iRW52ZWxvcGUiIGFsdD0iRW52ZWxvcGUi PjwvZm9udD48Zm9udCBzdHlsZT0iQ09MT1I6cmdiKDAsMCwxMDIpOyI+PHNwYW4gc3R5bGU9IkZP TlQtRkFNSUxZOmNvbWljIHNhbnMgbXMsc2Fucy1zZXJpZjsiPiBSZWdhcmRzIDo6IEtyaXNobmEg UGF2YW48L3NwYW4+PC9mb250PiA8c3BhbiBzdHlsZT0iQ09MT1I6cmdiKDAsMCwxMDIpOyI+4pyN PC9zcGFuPjwvZGl2Pgo8L2Rpdj48L2Rpdj48L2Rpdj4gCQkgCSAgIAkJICA8L2Rpdj48L2JvZHk+ DQo8L2h0bWw+ --_99bcb131-87cb-469a-9e7b-544e2e368e69_-- --===============3950937736593556461== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm --===============3950937736593556461==-- From xen-arm-bounces@lists.xen.org Tue Jul 02 16:49:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 02 Jul 2013 16:49:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uu3lt-0002lN-32; Tue, 02 Jul 2013 16:49:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uu3lr-0002lI-Sz for xen-arm@lists.xen.org; Tue, 02 Jul 2013 16:49:40 +0000 Received: from [85.158.143.99:42971] by server-3.bemta-4.messagelabs.com id 5C/4B-29480-3A403D15; Tue, 02 Jul 2013 16:49:39 +0000 X-Env-Sender: rajeshpaul@hotmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1372783777!28780915!1 X-Originating-IP: [65.55.116.42] X-SpamReason: No, hits=0.4 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_60_70, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_2,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10769 invoked from network); 2 Jul 2013 16:49:37 -0000 Received: from blu0-omc1-s31.blu0.hotmail.com (HELO blu0-omc1-s31.blu0.hotmail.com) (65.55.116.42) by server-13.tower-216.messagelabs.com with SMTP; 2 Jul 2013 16:49:37 -0000 Received: from BLU177-W34 ([65.55.116.9]) by blu0-omc1-s31.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 2 Jul 2013 09:49:37 -0700 X-TMN: [BfTo7pJxS4EKn5k3k4QY0jT/gH1UKjFT] X-Originating-Email: [rajeshpaul@hotmail.com] Message-ID: From: Rajesh Paul To: Krishna Pavan Date: Tue, 2 Jul 2013 22:19:36 +0530 Importance: Normal In-Reply-To: References: , , , MIME-Version: 1.0 X-OriginalArrivalTime: 02 Jul 2013 16:49:37.0092 (UTC) FILETIME=[231D3040:01CE7744] Cc: "xen-arm@lists.xen.org" Subject: Re: [XenARM] Xen ARM support for Tegra3 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3950937736593556461==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3950937736593556461== Content-Type: multipart/alternative; boundary="_99bcb131-87cb-469a-9e7b-544e2e368e69_" --_99bcb131-87cb-469a-9e7b-544e2e368e69_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgS3Jpc2huYSwgDQpJIGFtIGxvb2tpbmcgZm9yIHRoZSBsYXN0IHJlbGVhc2VkL2xhdGVzdCBz b3VyY2Ugb2YgWGVuLUFSTShQVikgcG9ydCBmb3IgVGVncmEgMiBIYXJtb255IGJvYXJkLg0KVGhl IHdpa2kgbGVkIG1lIHRvIGh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcvZXh0L2FybS94ZW4tdW5zdGFi bGUuaGcvZmlsZS8yMTdkMTMwMDMwMDAveGVuL2J1dCBhbSBub3Qgc3VyZSBpZiB0aGlzIGlzIHRo ZSBsYXRlc3Qgb25lLg0Kd291bGQgaGVscCBpZiB5b3UgY2FuIHByb3ZpZGUgcG9pbnRlcnMvbGlu a3MgdG8gdGhlIGxhdGVzdCBzb3VyY2UgYXJjaGl2ZXMuLi4NClRoYW5rcyxSYWplc2ggIA0KRGF0 ZTogVGh1LCAyNyBKdW4gMjAxMyAwOTo0OTo1OCArMDUzMA0KU3ViamVjdDogUmU6IFtYZW5BUk1d IFhlbiBBUk0gc3VwcG9ydCBmb3IgVGVncmEzDQpGcm9tOiBwb3N0NHBhdmFuQGdtYWlsLmNvbQ0K VG86IHJhamVzaHBhdWxAaG90bWFpbC5jb20NCkNDOiB4ZW4tYXJtQGxpc3RzLnhlbi5vcmcNCg0K SGkgUmFqZXNoLAogCgoKCgogSGFzIHRoZXJlIGJlZW4gYW4gZWZmb3J0IHRvIHBvcnQgdG8gVGVn cmEgMyA/CkkgZG8gbm90IGtub3cgYW55dGhpbmcgYWJvdXQgVGVncmEgMyBwb3J0LCBhbmQgdGhh dCB0b28gd2l0aCBQVi4KIAoKCgpBbHNvLCBpcyB0aGVyZSBhIGxpbmsgdG8gYSBzdGFibGUgcmVs ZWFzZSBmb3IgVGVncmEgMi4KVGhlcmUgYXJlIHNldmVyYWwgcG9zdHMgcmVsYXRlZCB0byBwb3J0 IG9mIFRlZ3JhMiB3aXRoaW4gWGVuLUFSTSBhcmNoaXZlcywgd2hlcmUgeW91IG1heSBmaW5kLiBJ IGRpZCBub3QgdW5kZXJzdGFuZCB0aGUgd29yZCAnc3RhYmxlJyBob3dldmVyLgoKCgoNCgpSZWdh cmRzLApSYWplc2ggCg0KCgoKRGF0ZTogV2VkLCAyNiBKdW4gMjAxMyAxNTowMjoxMyArMDUzMA0K U3ViamVjdDogUmU6IFtYZW5BUk1dIFhlbiBBUk0gc3VwcG9ydCBmb3IgVGVncmEzDQpGcm9tOiBw b3N0NHBhdmFuQGdtYWlsLmNvbQ0KVG86IHJhamVzaHBhdWxAaG90bWFpbC5jb20NCgpDQzogeGVu LWFybUBsaXN0cy54ZW4ub3JnDQoNCgoKCgpIaSwNCiANCkZvciBUZWdyYTIgaXQncyBhdmFpbGFi bGUuIEkgaGF2ZW4ndCBjb21lIGFjcm9zcyBUZWdyYTMgbmV3cy4NCgogCiAKIAoNCiAKT24gVHVl LCBKdW4gMjUsIDIwMTMgYXQgMTE6MzMgUE0sIFJhamVzaCBQYXVsIDxyYWplc2hwYXVsQGhvdG1h aWwuY29tPiB3cm90ZToNCgoKCkhpIEFsbCwgICAKDQoKT25lIG9mIG15IHByb2plY3QgcmVxdWly ZW1lbnRzIG5lZWQgYm9vdGluZyB0d28gVWJ1bnR1IExpbnV4IGluc3RhbmNlcyBvbiBhIFRlZ3Jh IDMgQm9hcmQoUXVhZC1jb3JlIEFSTSBDb3J0ZXggQTkgTVBDb3JlIHByb2Nlc3NvcikuIEFuZCBJ IHBsYW4gdG8gaG9zdCB0aGVtIG9uIGEgWGVuIEFSTSBiYXNlZCBIeXBlcnZpc29yLiAKDQoKbXkg cXVlcnk6Cg0KCklzIHRoZXJlIGEgc3BlY2lmaWMgc3VwcG9ydCBhdmFpbGFibGUgZm9yIFhlbiAo QVJNIFBWKSBmb3IgQ29ydGV4IEE5IGJhc2VkIHByb2Nlc3NvcnMuIEkgc2VlIHN1cHBvcnQgZm9y IENvcnRleCBBNywgQTE1ICh3aXRoIGgvdyB2aXJ0dWFsaXphdGlvbiBleHRlbnNpb25zKSBpbiBt YW55IHBsYWNlcywgYnV0IGRpZG4ndCBmaW5kIGFueSBwb2ludGVycy9saW5rcyB0byBDb3J0ZXgg QTkuIAoKDQoKQW55IGluZm9ybWF0aW9uIG9uIHRoaXMgdG9waWMgc2hhbGwgYmUgZ3JlYXRseSBo ZWxwZnVsLgoNCgpNYW55IFRoYW5rcywKUmFqZXNoDQpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXw0KWGVuLWFybSBtYWlsaW5nIGxpc3QNClhlbi1hcm1AbGlz dHMueGVuLm9yZw0KaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZv L3hlbi1hcm0NCgoNCg0KDQotLSANCgrinIkgUmVnYXJkcyA6OiBLcmlzaG5hIFBhdmFuIOKcjQoN Cg0KLS0gDQoKIFJlZ2FyZHMgOjogS3Jpc2huYSBQYXZhbiDinI0KIAkJIAkgICAJCSAg --_99bcb131-87cb-469a-9e7b-544e2e368e69_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxzdHlsZT48IS0tDQouaG1tZXNzYWdlIFANCnsNCm1hcmdpbjowcHg7 DQpwYWRkaW5nOjBweA0KfQ0KYm9keS5obW1lc3NhZ2UNCnsNCmZvbnQtc2l6ZTogMTJwdDsNCmZv bnQtZmFtaWx5OkNhbGlicmkNCn0NCi0tPjwvc3R5bGU+PC9oZWFkPg0KPGJvZHkgY2xhc3M9J2ht bWVzc2FnZSc+PGRpdiBkaXI9J2x0cic+SGkgS3Jpc2huYSwmbmJzcDs8ZGl2Pjxicj48L2Rpdj48 ZGl2PkkgYW0gbG9va2luZyBmb3IgdGhlIGxhc3QgcmVsZWFzZWQvbGF0ZXN0IHNvdXJjZSBvZiBY ZW4tQVJNKFBWKSBwb3J0IGZvciBUZWdyYSAyIEhhcm1vbnkgYm9hcmQuPC9kaXY+PGRpdj48c3Bh biBzdHlsZT0iZm9udC1zaXplOiAxMnB0OyI+PGJyPjwvc3Bhbj48L2Rpdj48ZGl2PjxzcGFuIHN0 eWxlPSJmb250LXNpemU6IDEycHQ7Ij5UaGUgd2lraSBsZWQgbWUgdG8mbmJzcDs8L3NwYW4+PGEg aHJlZj0iaHR0cDovL3hlbmJpdHMueGVuLm9yZy9leHQvYXJtL3hlbi11bnN0YWJsZS5oZy9maWxl LzIxN2QxMzAwMzAwMC94ZW4vIiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImZvbnQtc2l6ZTogMTJw dDsiPmh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcvZXh0L2FybS94ZW4tdW5zdGFibGUuaGcvZmlsZS8y MTdkMTMwMDMwMDAveGVuLzwvYT48L2Rpdj48ZGl2PmJ1dCBhbSBub3Qgc3VyZSBpZiB0aGlzIGlz IHRoZSBsYXRlc3Qgb25lLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+PHNwYW4gc3R5bGU9ImZv bnQtc2l6ZTogMTJwdDsiPndvdWxkIGhlbHAgaWYgeW91IGNhbiBwcm92aWRlIHBvaW50ZXJzL2xp bmtzIHRvIHRoZSBsYXRlc3Qgc291cmNlIGFyY2hpdmVzLi4uPC9zcGFuPjwvZGl2PjxkaXY+PGJy PjwvZGl2PjxkaXY+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTJwdDsiPlRoYW5rcyw8L3NwYW4+ PC9kaXY+PGRpdj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMnB0OyI+UmFqZXNoICZuYnNwOzwv c3Bhbj48L2Rpdj48ZGl2Pjxicj48ZGl2PjxociBpZD0ic3RvcFNwZWxsaW5nIj5EYXRlOiBUaHUs IDI3IEp1biAyMDEzIDA5OjQ5OjU4ICswNTMwPGJyPlN1YmplY3Q6IFJlOiBbWGVuQVJNXSBYZW4g QVJNIHN1cHBvcnQgZm9yIFRlZ3JhMzxicj5Gcm9tOiBwb3N0NHBhdmFuQGdtYWlsLmNvbTxicj5U bzogcmFqZXNocGF1bEBob3RtYWlsLmNvbTxicj5DQzogeGVuLWFybUBsaXN0cy54ZW4ub3JnPGJy Pjxicj48ZGl2IGRpcj0ibHRyIj48ZGl2Pjxmb250IGNvbG9yPSIjOTkzMzk5Ij5IaSBSYWplc2gs PC9mb250PjwvZGl2Pgo8ZGl2PiZuYnNwOzwvZGl2Pgo8ZGl2IGNsYXNzPSJlY3hnbWFpbF9xdW90 ZSI+CjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojY2NjIDFweCBzb2xpZDtNQVJHSU46 MHB4IDBweCAwcHggMC44ZXg7UEFERElORy1MRUZUOjFleDsiIGNsYXNzPSJlY3hnbWFpbF9xdW90 ZSI+CjxkaXY+CjxkaXYgZGlyPSJsdHIiPgo8ZGl2PiZuYnNwO0g8c3Bhbj5hcyB0aGVyZSBiZWVu IGFuIGVmZm9ydCB0byBwb3J0IHRvIFRlZ3JhIDMgPzwvc3Bhbj48L2Rpdj48L2Rpdj48L2Rpdj48 L2Jsb2NrcXVvdGU+CjxkaXY+PGZvbnQgY29sb3I9IiM5OTMzOTkiPkkgZG8gbm90IGtub3cgYW55 dGhpbmcgYWJvdXQgVGVncmEgMyBwb3J0LCBhbmQgdGhhdCB0b28gd2l0aCBQVi48L2ZvbnQ+PC9k aXY+CjxkaXY+Jm5ic3A7PC9kaXY+CjxibG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojY2Nj IDFweCBzb2xpZDtNQVJHSU46MHB4IDBweCAwcHggMC44ZXg7UEFERElORy1MRUZUOjFleDsiIGNs YXNzPSJlY3hnbWFpbF9xdW90ZSI+CjxkaXY+CjxkaXYgZGlyPSJsdHIiPgo8ZGl2PjxzcGFuPkFs c28sIGlzIHRoZXJlIGEgbGluayB0byBhIHN0YWJsZSByZWxlYXNlIGZvciBUZWdyYSAyLjwvc3Bh bj48L2Rpdj48L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+CjxkaXY+PGZvbnQgY29sb3I9IiM5OTMz OTkiPlRoZXJlIGFyZSBzZXZlcmFsIHBvc3RzIHJlbGF0ZWQgdG8gcG9ydCBvZiBUZWdyYTIgd2l0 aGluIFhlbi1BUk0gYXJjaGl2ZXMsIHdoZXJlIHlvdSBtYXkgZmluZC4gSSBkaWQgbm90IHVuZGVy c3RhbmQgdGhlIHdvcmQgJ3N0YWJsZScgaG93ZXZlci48L2ZvbnQ+PC9kaXY+CjxibG9ja3F1b3Rl IHN0eWxlPSJCT1JERVItTEVGVDojY2NjIDFweCBzb2xpZDtNQVJHSU46MHB4IDBweCAwcHggMC44 ZXg7UEFERElORy1MRUZUOjFleDsiIGNsYXNzPSJlY3hnbWFpbF9xdW90ZSI+CjxkaXY+CjxkaXYg ZGlyPSJsdHIiPgo8ZGl2PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+UmVnYXJk cyw8L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+UmFqZXNoJm5ic3A7PC9zcGFuPjwvZGl2Pgo8ZGl2 Pjxicj4KPGRpdj4KPGhyPgpEYXRlOiBXZWQsIDI2IEp1biAyMDEzIDE1OjAyOjEzICswNTMwPGJy PlN1YmplY3Q6IFJlOiBbWGVuQVJNXSBYZW4gQVJNIHN1cHBvcnQgZm9yIFRlZ3JhMzxicj5Gcm9t OiA8YSBocmVmPSJtYWlsdG86cG9zdDRwYXZhbkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5w b3N0NHBhdmFuQGdtYWlsLmNvbTwvYT48YnI+VG86IDxhIGhyZWY9Im1haWx0bzpyYWplc2hwYXVs QGhvdG1haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+cmFqZXNocGF1bEBob3RtYWlsLmNvbTwvYT48 YnI+CkNDOiA8YSBocmVmPSJtYWlsdG86eGVuLWFybUBsaXN0cy54ZW4ub3JnIiB0YXJnZXQ9Il9i bGFuayI+eGVuLWFybUBsaXN0cy54ZW4ub3JnPC9hPjxicj48YnI+CjxkaXYgZGlyPSJsdHIiPgo8 ZGl2Pgo8ZGl2IGNsYXNzPSJoNSI+CjxkaXY+PGZvbnQgY29sb3I9IiM5OTMzOTkiPkhpLDxicj4m bmJzcDs8YnI+Rm9yIFRlZ3JhMiBpdCdzIGF2YWlsYWJsZS4gSSBoYXZlbid0IGNvbWUgYWNyb3Nz IFRlZ3JhMyBuZXdzLjxicj48L2ZvbnQ+PC9kaXY+CjxkaXY+Jm5ic3A7PC9kaXY+CjxkaXY+Jm5i c3A7PC9kaXY+CjxkaXY+Jm5ic3A7PC9kaXY+CjxkaXY+PGJyPiZuYnNwOzwvZGl2Pgo8ZGl2Pk9u IFR1ZSwgSnVuIDI1LCAyMDEzIGF0IDExOjMzIFBNLCBSYWplc2ggUGF1bCA8c3BhbiBkaXI9Imx0 ciI+Jmx0OzxhIGhyZWY9Im1haWx0bzpyYWplc2hwYXVsQGhvdG1haWwuY29tIiB0YXJnZXQ9Il9i bGFuayI+cmFqZXNocGF1bEBob3RtYWlsLmNvbTwvYT4mZ3Q7PC9zcGFuPiB3cm90ZTo8YnI+Cjxi bG9ja3F1b3RlIHN0eWxlPSJCT1JERVItTEVGVDojY2NjIDFweCBzb2xpZDtNQVJHSU46MHB4IDBw eCAwcHggMC44ZXg7UEFERElORy1MRUZUOjFleDsiPgo8ZGl2Pgo8ZGl2IGRpcj0ibHRyIj5IaSBB bGwsICZuYnNwOyAKPGRpdj48YnI+PC9kaXY+CjxkaXY+T25lIG9mIG15IHByb2plY3QgcmVxdWly ZW1lbnRzIG5lZWQgYm9vdGluZyB0d28gVWJ1bnR1IExpbnV4IGluc3RhbmNlcyBvbiBhIFRlZ3Jh IDMgQm9hcmQoUXVhZC1jb3JlIEFSTSBDb3J0ZXggQTkgTVBDb3JlIHByb2Nlc3NvcikuIEFuZCBJ IHBsYW4gdG8gaG9zdCB0aGVtIG9uIGEgWGVuIEFSTSBiYXNlZCBIeXBlcnZpc29yLiZuYnNwOzwv ZGl2Pgo8ZGl2PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+bXkgcXVlcnk6PC9z cGFuPjwvZGl2Pgo8ZGl2PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+SXMgdGhl cmUgYSBzcGVjaWZpYyBzdXBwb3J0IGF2YWlsYWJsZSBmb3ImbmJzcDs8L3NwYW4+PGIgc3R5bGU9 IkxJTkUtSEVJR0hUOjE4cHg7Rk9OVC1GQU1JTFk6QXJpYWwsc2Fucy1zZXJpZjtDT0xPUjpyZ2Io NTEsNTEsNTEpOyI+WGVuIChBUk0gUFYpPC9iPjxzcGFuPiZuYnNwO2ZvciBDb3J0ZXggQTkgYmFz ZWQgcHJvY2Vzc29ycy4gSSBzZWUgc3VwcG9ydCBmb3IgQ29ydGV4IEE3LCBBMTUgKHdpdGggaC93 IHZpcnR1YWxpemF0aW9uIGV4dGVuc2lvbnMpIGluIG1hbnkgcGxhY2VzLCBidXQgZGlkbid0IGZp bmQgYW55IHBvaW50ZXJzL2xpbmtzIHRvIENvcnRleCBBOS4mbmJzcDs8L3NwYW4+PC9kaXY+Cgo8 ZGl2PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+PHNwYW4+QW55IGluZm9ybWF0aW9uIG9u IHRoaXMgdG9waWMgc2hhbGwgYmUgZ3JlYXRseSBoZWxwZnVsLjwvc3Bhbj48L2Rpdj4KPGRpdj48 c3Bhbj48YnI+PC9zcGFuPjwvZGl2Pgo8ZGl2PjxzcGFuPk1hbnkgVGhhbmtzLDwvc3Bhbj48L2Rp dj4KPGRpdj48c3Bhbj5SYWplc2g8L3NwYW4+PC9kaXY+PC9kaXY+PC9kaXY+PGJyPl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPlhlbi1hcm0gbWFpbGlu ZyBsaXN0PGJyPjxhIGhyZWY9Im1haWx0bzpYZW4tYXJtQGxpc3RzLnhlbi5vcmciIHRhcmdldD0i X2JsYW5rIj5YZW4tYXJtQGxpc3RzLnhlbi5vcmc8L2E+PGJyPjxhIGhyZWY9Imh0dHA6Ly9saXN0 cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXJtIiB0YXJnZXQ9Il9ibGFu ayI+aHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcm08 L2E+PGJyPgo8YnI+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48YnIgY2xlYXI9ImFsbCI+PGJyPi0t IDxicj48L2Rpdj48L2Rpdj4KPGRpdiBkaXI9Imx0ciI+PGZvbnQgc3R5bGU9IkNPTE9SOnJnYigw LDAsMTAyKTsiPjxpbWcgdGl0bGU9IkVudmVsb3BlIiBhbHQ9IkVudmVsb3BlIiBzcmM9Imh0dHBz Oi8vYS5nZngubXMvZW1vamlfMDI3MDkucG5nIj48L2ZvbnQ+PGZvbnQgc3R5bGU9IkNPTE9SOnJn YigwLDAsMTAyKTsiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTpjb21pYyBzYW5zIG1zLHNhbnMt c2VyaWY7Ij4gUmVnYXJkcyA6OiBLcmlzaG5hIFBhdmFuPC9zcGFuPjwvZm9udD4gPHNwYW4gc3R5 bGU9IkNPTE9SOnJnYigwLDAsMTAyKTsiPuKcjTwvc3Bhbj48L2Rpdj4KPC9kaXY+PC9kaXY+PC9k aXY+PC9kaXY+PC9kaXY+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48YnIgY2xlYXI9ImFsbCI+PGJy Pi0tIDxicj4KPGRpdiBkaXI9Imx0ciI+PGZvbnQgc3R5bGU9IkNPTE9SOnJnYigwLDAsMTAyKTsi PjxpbWcgc3JjPSJodHRwczovL2EuZ2Z4Lm1zL2Vtb2ppXzAyNzA5LnBuZyIgY2xhc3M9IkVtb2pp JDAyNzA5JEFDNCBSZW5kZXJlZEVtb2ppIiB0aXRsZT0iRW52ZWxvcGUiIGFsdD0iRW52ZWxvcGUi PjwvZm9udD48Zm9udCBzdHlsZT0iQ09MT1I6cmdiKDAsMCwxMDIpOyI+PHNwYW4gc3R5bGU9IkZP TlQtRkFNSUxZOmNvbWljIHNhbnMgbXMsc2Fucy1zZXJpZjsiPiBSZWdhcmRzIDo6IEtyaXNobmEg UGF2YW48L3NwYW4+PC9mb250PiA8c3BhbiBzdHlsZT0iQ09MT1I6cmdiKDAsMCwxMDIpOyI+4pyN PC9zcGFuPjwvZGl2Pgo8L2Rpdj48L2Rpdj48L2Rpdj4gCQkgCSAgIAkJICA8L2Rpdj48L2JvZHk+ DQo8L2h0bWw+ --_99bcb131-87cb-469a-9e7b-544e2e368e69_-- --===============3950937736593556461== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm --===============3950937736593556461==-- From xen-arm-bounces@lists.xen.org Fri Jul 12 11:29:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 11:29:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxbXW-0001zH-CQ; Fri, 12 Jul 2013 11:29:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ulfzr-0000cL-9V; Sun, 09 Jun 2013 13:49:27 +0000 Received: from [85.158.139.83:58601] by server-12.bemta-5.messagelabs.com id AE/D1-16465-6E784B15; Sun, 09 Jun 2013 13:49:26 +0000 X-Env-Sender: julien.grall@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1370785764!31166032!1 X-Originating-IP: [209.85.214.181] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8897 invoked from network); 9 Jun 2013 13:49:25 -0000 Received: from mail-ob0-f181.google.com (HELO mail-ob0-f181.google.com) (209.85.214.181) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jun 2013 13:49:25 -0000 Received: by mail-ob0-f181.google.com with SMTP id 16so8811359obc.26 for ; Sun, 09 Jun 2013 06:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5Ik4++QlFyASpRKmzwCK/4e3+SxwV9lQs5BzL3RlzA8=; b=hK3TbKHd8h2eZAks2COQvrK7kSW2Lx1GlyXd7vA1nJCbu5k31snhR7bM88UAs1j/NJ yu9Pq1+hh5kUF6agrNiH1qw7osm5GaopxmiDfIJo9HprEGBUd0h+F4hSESQg3GHwuujH 9EG7BQ51xQ+Ti2blWdoY/ph8GCgTh+lPENzbxubxXVK5h4iZBKZT1NfSzkDS50plzqbK iNwhRNptqv/mRKJbWCzb5GcHUK+Dr3KqzF0Wh9Mj5LNS0wcwHKW0l7X2kuxMEC2iFRPp q/4OsxTAXghGpD/5LJq5Qi+1GzU4K2TzhFessuBHTX0QAqU9YJQ0QOhbd+anRMJ8ju03 7hjw== X-Received: by 10.182.24.131 with SMTP id u3mr4992408obf.29.1370785763804; Sun, 09 Jun 2013 06:49:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.102.13 with HTTP; Sun, 9 Jun 2013 06:48:42 -0700 (PDT) In-Reply-To: <20130609124213.GA19123@cbz-workstation> References: <20130609124213.GA19123@cbz-workstation> From: Julien Grall Date: Sun, 9 Jun 2013 14:48:42 +0100 Message-ID: To: Chen Baozi X-Mailman-Approved-At: Fri, 12 Jul 2013 11:29:29 +0000 Cc: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Linking errors of Mini-OS for ARM32 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Sun, Jun 9, 2013 at 1:42 PM, Chen Baozi wrote: > Since finishing the very beginning setup assembly, I was turning to adding > necessary headers and empty functions to build the binary. After introducing > those bit operations, spinlocks etc., I thought I have a basic framework to > pass the first build. However, when comming to the final linking stage, > there are errors: > > arm-linux-gnueabihf-ld -T arch/arm/minios-arm32.lds > /home/cbz/src/xen/extras/mini-os/mini-os.o -o > //home/cbz/src/xen/extras/mini-os/mini-os > /home/cbz/src/xen/extras/mini-os/mini-os.o: In function `init_blkfront': > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/mini-os.o:/home/cbz/src/xen/extras/mini-os/blkfront.c:122: more undefined references to `__aeabi_uldivmod' follow > /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' > /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x50): undefined reference to `__aeabi_unwind_cpp_pr0' > make: *** [/home/cbz/src/xen/extras/mini-os/mini-os] Error 1 > > I googled that error message. Some has mentioned that add "-fno-exceptions > -fno-unwind tables" could sovle the problem. I tried, but got the same > errors. > > Any ideas? You need to provide an implementation for __aeabi_uldivmod. For this purpose, you can re-use xen/arch/arm/arm32/lib/lib1func.S -- Grall Julien _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Fri Jul 12 11:29:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 11:29:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxbXW-0001zH-CQ; Fri, 12 Jul 2013 11:29:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ulfzr-0000cL-9V; Sun, 09 Jun 2013 13:49:27 +0000 Received: from [85.158.139.83:58601] by server-12.bemta-5.messagelabs.com id AE/D1-16465-6E784B15; Sun, 09 Jun 2013 13:49:26 +0000 X-Env-Sender: julien.grall@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1370785764!31166032!1 X-Originating-IP: [209.85.214.181] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8897 invoked from network); 9 Jun 2013 13:49:25 -0000 Received: from mail-ob0-f181.google.com (HELO mail-ob0-f181.google.com) (209.85.214.181) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jun 2013 13:49:25 -0000 Received: by mail-ob0-f181.google.com with SMTP id 16so8811359obc.26 for ; Sun, 09 Jun 2013 06:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5Ik4++QlFyASpRKmzwCK/4e3+SxwV9lQs5BzL3RlzA8=; b=hK3TbKHd8h2eZAks2COQvrK7kSW2Lx1GlyXd7vA1nJCbu5k31snhR7bM88UAs1j/NJ yu9Pq1+hh5kUF6agrNiH1qw7osm5GaopxmiDfIJo9HprEGBUd0h+F4hSESQg3GHwuujH 9EG7BQ51xQ+Ti2blWdoY/ph8GCgTh+lPENzbxubxXVK5h4iZBKZT1NfSzkDS50plzqbK iNwhRNptqv/mRKJbWCzb5GcHUK+Dr3KqzF0Wh9Mj5LNS0wcwHKW0l7X2kuxMEC2iFRPp q/4OsxTAXghGpD/5LJq5Qi+1GzU4K2TzhFessuBHTX0QAqU9YJQ0QOhbd+anRMJ8ju03 7hjw== X-Received: by 10.182.24.131 with SMTP id u3mr4992408obf.29.1370785763804; Sun, 09 Jun 2013 06:49:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.102.13 with HTTP; Sun, 9 Jun 2013 06:48:42 -0700 (PDT) In-Reply-To: <20130609124213.GA19123@cbz-workstation> References: <20130609124213.GA19123@cbz-workstation> From: Julien Grall Date: Sun, 9 Jun 2013 14:48:42 +0100 Message-ID: To: Chen Baozi X-Mailman-Approved-At: Fri, 12 Jul 2013 11:29:29 +0000 Cc: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Linking errors of Mini-OS for ARM32 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Sun, Jun 9, 2013 at 1:42 PM, Chen Baozi wrote: > Since finishing the very beginning setup assembly, I was turning to adding > necessary headers and empty functions to build the binary. After introducing > those bit operations, spinlocks etc., I thought I have a basic framework to > pass the first build. However, when comming to the final linking stage, > there are errors: > > arm-linux-gnueabihf-ld -T arch/arm/minios-arm32.lds > /home/cbz/src/xen/extras/mini-os/mini-os.o -o > //home/cbz/src/xen/extras/mini-os/mini-os > /home/cbz/src/xen/extras/mini-os/mini-os.o: In function `init_blkfront': > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > /home/cbz/src/xen/extras/mini-os/mini-os.o:/home/cbz/src/xen/extras/mini-os/blkfront.c:122: more undefined references to `__aeabi_uldivmod' follow > /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' > /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x50): undefined reference to `__aeabi_unwind_cpp_pr0' > make: *** [/home/cbz/src/xen/extras/mini-os/mini-os] Error 1 > > I googled that error message. Some has mentioned that add "-fno-exceptions > -fno-unwind tables" could sovle the problem. I tried, but got the same > errors. > > Any ideas? You need to provide an implementation for __aeabi_uldivmod. For this purpose, you can re-use xen/arch/arm/arm32/lib/lib1func.S -- Grall Julien _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Fri Jul 12 11:29:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 11:29:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxbXW-0001zN-G1; Fri, 12 Jul 2013 11:29:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ulyzs-0002h0-2M for xen-arm@lists.xen.org; Mon, 10 Jun 2013 10:06:44 +0000 Received: from [85.158.139.211:26253] by server-16.bemta-5.messagelabs.com id 37/60-31493-335A5B15; Mon, 10 Jun 2013 10:06:43 +0000 X-Env-Sender: julien.grall@linaro.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1370858801!18070499!1 X-Originating-IP: [209.85.214.43] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5245 invoked from network); 10 Jun 2013 10:06:41 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2013 10:06:41 -0000 Received: by mail-bk0-f43.google.com with SMTP id jm2so1948564bkc.30 for ; Mon, 10 Jun 2013 03:06:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=jG+mLbppMZ8bZ8WYa/9t+0+CkxFUnZPmZMm5Zmnw4s8=; b=eWH1eSgUqnzW4ScQqeM0d2m2ycD6QZ5p9ZJ0A+YoqM+o02LNJ4w5pwy4jfgbNJ1DrF 8abXtatefi9QhLe+GegXKu9MNuEzLC3lb3YC26njiiEmV2Obck5rOJ6LlIMYUMPgWjzH 6miIjduOh6Zj2RCvZqio6UTXViu+aCioZkBzD3Dx50Pyn14XqnNH9F6Hk+AdtNwl0fCP yxU99hm1Fk6LWIuSLcP7UUNGJ7eMq4mftM6IWM8jizwbKsEDsfsDyStTliD7v+Kqw7+i Zqqug6XJJQCJ7F/Fl67++vn1NxZAfMQTISVln8h+lgpHqZeK2RtXHA2QTnuYqvApdUAe 42Sg== X-Received: by 10.204.240.15 with SMTP id ky15mr1372157bkb.144.1370858800884; Mon, 10 Jun 2013 03:06:40 -0700 (PDT) Received: from [10.80.2.139] (firewall.ctxuk.citrix.com. [46.33.159.2]) by mx.google.com with ESMTPSA id np10sm3380824bkb.10.2013.06.10.03.06.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Jun 2013 03:06:39 -0700 (PDT) Message-ID: <51B5A52D.7050709@linaro.org> Date: Mon, 10 Jun 2013 11:06:37 +0100 From: Julien Grall User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Chen Baozi References: <20130609124213.GA19123@cbz-workstation> <20130610001315.GA1714@cbz-workstation> In-Reply-To: <20130610001315.GA1714@cbz-workstation> X-Gm-Message-State: ALoCoQk7aU++GeNUSxpUyrmh/6S0glZRq6PXutvBYV/sN9ZYIw2eHkCJ/QaYZcKyW2YIvmp6S5iX X-Mailman-Approved-At: Fri, 12 Jul 2013 11:29:29 +0000 Cc: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Linking errors of Mini-OS for ARM32 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On 06/10/2013 01:13 AM, Chen Baozi wrote: > On Sun, Jun 09, 2013 at 02:48:42PM +0100, Julien Grall wrote: >> On Sun, Jun 9, 2013 at 1:42 PM, Chen Baozi wrote: >>> Since finishing the very beginning setup assembly, I was turning to adding >>> necessary headers and empty functions to build the binary. After introducing >>> those bit operations, spinlocks etc., I thought I have a basic framework to >>> pass the first build. However, when comming to the final linking stage, >>> there are errors: >>> >>> arm-linux-gnueabihf-ld -T arch/arm/minios-arm32.lds >>> /home/cbz/src/xen/extras/mini-os/mini-os.o -o >>> //home/cbz/src/xen/extras/mini-os/mini-os >>> /home/cbz/src/xen/extras/mini-os/mini-os.o: In function `init_blkfront': >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:/home/cbz/src/xen/extras/mini-os/blkfront.c:122: more undefined references to `__aeabi_uldivmod' follow >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x50): undefined reference to `__aeabi_unwind_cpp_pr0' >>> make: *** [/home/cbz/src/xen/extras/mini-os/mini-os] Error 1 >>> >>> I googled that error message. Some has mentioned that add "-fno-exceptions >>> -fno-unwind tables" could sovle the problem. I tried, but got the same >>> errors. >>> >>> Any ideas? >> >> You need to provide an implementation for __aeabi_uldivmod. >> For this purpose, you can re-use xen/arch/arm/arm32/lib/lib1func.S > > Thanks a lot. > > A further question. I'm a litte curious that whether __aeabi_uldivmod is missing > because of a toolchain bug or some other reasons? __aeabi_uldivmod and co. are provided by libgcc.{so,a}. Mini-OS is not linked against this library. -- Julien _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Fri Jul 12 11:29:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 11:29:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxbXW-0001zN-G1; Fri, 12 Jul 2013 11:29:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ulyzs-0002h0-2M for xen-arm@lists.xen.org; Mon, 10 Jun 2013 10:06:44 +0000 Received: from [85.158.139.211:26253] by server-16.bemta-5.messagelabs.com id 37/60-31493-335A5B15; Mon, 10 Jun 2013 10:06:43 +0000 X-Env-Sender: julien.grall@linaro.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1370858801!18070499!1 X-Originating-IP: [209.85.214.43] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5245 invoked from network); 10 Jun 2013 10:06:41 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jun 2013 10:06:41 -0000 Received: by mail-bk0-f43.google.com with SMTP id jm2so1948564bkc.30 for ; Mon, 10 Jun 2013 03:06:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=jG+mLbppMZ8bZ8WYa/9t+0+CkxFUnZPmZMm5Zmnw4s8=; b=eWH1eSgUqnzW4ScQqeM0d2m2ycD6QZ5p9ZJ0A+YoqM+o02LNJ4w5pwy4jfgbNJ1DrF 8abXtatefi9QhLe+GegXKu9MNuEzLC3lb3YC26njiiEmV2Obck5rOJ6LlIMYUMPgWjzH 6miIjduOh6Zj2RCvZqio6UTXViu+aCioZkBzD3Dx50Pyn14XqnNH9F6Hk+AdtNwl0fCP yxU99hm1Fk6LWIuSLcP7UUNGJ7eMq4mftM6IWM8jizwbKsEDsfsDyStTliD7v+Kqw7+i Zqqug6XJJQCJ7F/Fl67++vn1NxZAfMQTISVln8h+lgpHqZeK2RtXHA2QTnuYqvApdUAe 42Sg== X-Received: by 10.204.240.15 with SMTP id ky15mr1372157bkb.144.1370858800884; Mon, 10 Jun 2013 03:06:40 -0700 (PDT) Received: from [10.80.2.139] (firewall.ctxuk.citrix.com. [46.33.159.2]) by mx.google.com with ESMTPSA id np10sm3380824bkb.10.2013.06.10.03.06.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Jun 2013 03:06:39 -0700 (PDT) Message-ID: <51B5A52D.7050709@linaro.org> Date: Mon, 10 Jun 2013 11:06:37 +0100 From: Julien Grall User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Chen Baozi References: <20130609124213.GA19123@cbz-workstation> <20130610001315.GA1714@cbz-workstation> In-Reply-To: <20130610001315.GA1714@cbz-workstation> X-Gm-Message-State: ALoCoQk7aU++GeNUSxpUyrmh/6S0glZRq6PXutvBYV/sN9ZYIw2eHkCJ/QaYZcKyW2YIvmp6S5iX X-Mailman-Approved-At: Fri, 12 Jul 2013 11:29:29 +0000 Cc: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Linking errors of Mini-OS for ARM32 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On 06/10/2013 01:13 AM, Chen Baozi wrote: > On Sun, Jun 09, 2013 at 02:48:42PM +0100, Julien Grall wrote: >> On Sun, Jun 9, 2013 at 1:42 PM, Chen Baozi wrote: >>> Since finishing the very beginning setup assembly, I was turning to adding >>> necessary headers and empty functions to build the binary. After introducing >>> those bit operations, spinlocks etc., I thought I have a basic framework to >>> pass the first build. However, when comming to the final linking stage, >>> there are errors: >>> >>> arm-linux-gnueabihf-ld -T arch/arm/minios-arm32.lds >>> /home/cbz/src/xen/extras/mini-os/mini-os.o -o >>> //home/cbz/src/xen/extras/mini-os/mini-os >>> /home/cbz/src/xen/extras/mini-os/mini-os.o: In function `init_blkfront': >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:/home/cbz/src/xen/extras/mini-os/blkfront.c:122: more undefined references to `__aeabi_uldivmod' follow >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x50): undefined reference to `__aeabi_unwind_cpp_pr0' >>> make: *** [/home/cbz/src/xen/extras/mini-os/mini-os] Error 1 >>> >>> I googled that error message. Some has mentioned that add "-fno-exceptions >>> -fno-unwind tables" could sovle the problem. I tried, but got the same >>> errors. >>> >>> Any ideas? >> >> You need to provide an implementation for __aeabi_uldivmod. >> For this purpose, you can re-use xen/arch/arm/arm32/lib/lib1func.S > > Thanks a lot. > > A further question. I'm a litte curious that whether __aeabi_uldivmod is missing > because of a toolchain bug or some other reasons? __aeabi_uldivmod and co. are provided by libgcc.{so,a}. Mini-OS is not linked against this library. -- Julien _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Fri Jul 12 11:29:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 11:29:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxbXW-0001zS-JM; Fri, 12 Jul 2013 11:29:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Urljq-0007rs-Kv for xen-arm@lists.xen.org; Wed, 26 Jun 2013 09:10:06 +0000 Received: from [85.158.137.99:17131] by server-16.bemta-3.messagelabs.com id 67/68-15362-DEFAAC15; Wed, 26 Jun 2013 09:10:05 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1372237804!14708166!2 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17131 invoked from network); 26 Jun 2013 09:10:05 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Jun 2013 09:10:05 -0000 X-IronPort-AV: E=Sophos;i="4.87,943,1363132800"; d="scan'208";a="6065723" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 26 Jun 2013 09:10:04 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Wed, 26 Jun 2013 10:10:03 +0100 Message-ID: <1372237802.18901.115.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Eric Trudeau Date: Wed, 26 Jun 2013 10:10:02 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] X-Mailman-Approved-At: Fri, 12 Jul 2013 11:29:29 +0000 Cc: xen-devel Subject: Re: [XenARM] XEN tools for ARM with Virtualization Extensions X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org KG1vdmluZyB0byB4ZW4tZGV2ZWwsIHhlbi1hcm0gaXMgZm9yIHRoZSBvbGRlciBQViBBUk0gcG9y dCkKCk9uIFR1ZSwgMjAxMy0wNi0yNSBhdCAyMzo1OSArMDAwMCwgRXJpYyBUcnVkZWF1IHdyb3Rl Ogo+IEhpLCBJIGFtIHRyeWluZyB0byBidWlsZCB0aGUgWEVOIHRvb2xzIGZvciBvdXIgcG9ydCBv ZiBYRU4gdG8gb3VyCj4gQ29ydGV4IEExNS1iYXNlZCBwbGF0Zm9ybS4KPiAKPiBJIGFtIHVzaW5n IHRoZSByZXBvIGF0IGdpdDovL3hlbmJpdHMueGVucHJvamVjdC5vcmcveGVuLmdpdCB0bwo+IGNy b3NzLWNvbXBpbGUgdGhlIHRvb2xzIGludG8gb3VyIHJvb3Rmcy4KCldoaWNoIGJyYW5jaC9jaGFu Z2VzZXQgYXJlIHlvdSB1c2luZz8KCkkndmUgaGVhcmQgdGhhdCB0aGUgcmVjZW50IFhTQS01NSBm aXhlcyBoYXZlIGJyb2tlbiBndWVzdCBsb2FkaW5nIG9uCkFSTSwgYnV0IHlvdXIgcHJvYmxlbXMg ZG8gbm90IHNlZW0gdG8gYmUgcmVsYXRlZCB0byB0aGF0IChJIG1lbnRpb24gaXQKYmVjYXVzZSBp dCBtaWdodCBiZSBzb21ldGhpbmcgeW91IGhpdCBhZnRlciB3ZSB3b3JrIHRocm91Z2ggeW91ciBj dXJyZW50Cmlzc3VlcykKCj4gVGhpcyByZXBvIGlzIHdoYXQgd2UgYXJlIHVzaW5nIGZvciBvdXIg SHlwZXJ2aXNvciBkZXZlbG9wbWVudCBhbHNvLgo+IAo+IFdoZW4gYnVpbGRpbmcgdGhlIHRvb2xz LCBJIGZvdW5kIHRoYXQgbGliYWlvIGRvZXMgbm90IGJ1aWxkIGZvciBBUk0KPiBzaW5jZSBpdCB3 YXMgbWlzc2luZyB0b29scy9saWJhaW8vc3JjL3N5c2NhbGwtYXJtLmguCj4gCj4gSSBmb3VuZCBh IHZlcnNpb24gb24gdGhlIHdlYiBzbyB0aGF0IEkgY291bGQgY29udGludWUuCgpBcmUgeW91IHBp Y2tpbmcgdXAgdGhlIGxpYmFpbyBpbiB0b29scy9saWJhaW8/IFRoYXQgaXMgYW4gYW5jaWVudApz bmFwc2hvdCB1c2VkIHRvIHN1cHBvcnQgb2xkZXIgZGlzdHJvcyB3aGljaCBkb24ndCBzaGlwIGxp YmFpbwp0aGVtc2VsdmVzLiBJdCByZWFsbHkgc2hvdWxkbid0IGV2ZW4gYmUgY29uc2lkZXJlZCBm b3IgQVJNICh0aGlzIGlzIGEKYnVnIGluIG91ciBidWlsZCBzeXN0ZW0gSU1ITykuIElmIHlvdSBp bnN0YWxsIHRoZSBsaWJhaW8gKGFuZCBoZWFkZXJzCmV0YykgZnJvbSB5b3VyIGRpc3RybyB0aGVu IGNvbmZpZ3VyZSB3aWxsIGRldGVjdCB0aGlzIGFuZCBub3QgdXNlIHRoZQplbWJlZGRlZCBjb3B5 LiAoVGhlIGVtYmVkZGVkIGNvcHkgaXMgb24gbXkgaGl0bGlzdCBmb3IgY3J1ZnQgcmVtb3ZhbCBm b3IKNC40LCBidXQgd2UgYXJlIGZyb3plbiBmb3IgNC4zIHJpZ2h0IG5vdyBzbyBJIGNhbid0IHRv dWNoIGl0KQoKRldJVyBJIHdyb3RlIHVwIHNvbWUgZGV0YWlscyBvZiBob3cgSSBjcm9zcyBjb21w aWxlIHdpdGggRGViaWFuL1VidW50dQphdApodHRwOi8vd2lraS54ZW4ub3JnL3dpa2kvWGVuX0FS TV93aXRoX1ZpcnR1YWxpemF0aW9uX0V4dGVuc2lvbnMvQ3Jvc3NDb21waWxpbmcgd2hpY2ggaW5j bHVkZXMgbGlzdHMgb2YgcGFja2FnZXMgdG8gaW5zdGFsbCBldGMuCgo+IEkgYWxzbyBmb3VuZCB0 aGF0IHhjX2RvbV9lbGZsb2FkZXIuY+KAmXMgZnVuY3Rpb24sIHhjX2RvbV9ndWVzdF90eXBlKCks Cj4gZGlkIG5vdCBrbm93IGFib3V0IHRoZSBFTV9BUk0gbWFjaGluZSB0eXBlLgoKWW91IHNob3Vs ZG4ndCBiZSBoaXR0aW5nIHRoZSBlbGYgbG9hZGVyIHBhdGhzLCB5b3Ugc2hvdWxkIGluc3RlYWQg dXNlCnRoZSB6SW1hZ2UgdmVyc2lvbiBvZiB0aGUga2VybmVsIHdoaWNoIHdpbGwgaGl0IHRoZQp4 Y19kb21fYXJtemltYWdlbG9hZGVyLmMgY29kZSBwYXRocy4KCldlIGRpZCBhdCBvbmUgcG9pbnQg aW4gdGhlIHZlcnkgZWFybHkgZGF5cyBvZiB0aGUgcG9ydCBzdXBwb3J0IGxvYWRpbmcKRUxGIGZp bGVzIHZpYSBhIHF1aWNrIGhhY2sgb2YgYSB0b29sICgieGNidWlsZCIpIGJ1dCB0aGF0IGhhcyBi ZWVuCnN1cGVyY2VkZWQgYnkgdGhlIHByb3BlciB0b29sc3RhY2sgc3VwcG9ydCBhbmQgdGhlIHVz ZSBvZiB6SW1hZ2UuCgo+IEFtIEkgdXNpbmcgdGhlIHdyb25nIHJlcG8gZm9yIGRldmVsb3BtZW50 IG9mIHRoZSB0b29scyBmb3IgQVJNPwoKCj4gCj4gSWYgbm90LCB0aGUgdHdpa2kgc2VlbXMgdG8g aW5kaWNhdGUgdGhhdCB4bCBpcyB3b3JraW5nIG9uIEFSTSB0bwo+IGNyZWF0ZSBndWVzdCBtYWNo aW5lcy4KCk1vZHVsbyBhbnkgYnVncyBpbnRyb2R1Y2VkIGJ5IFhTQS01NSB3ZSBiZWxpZXZlIGl0 IGlzLgoKSWFuLgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXwpYZW4tYXJtIG1haWxpbmcgbGlzdApYZW4tYXJtQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xp c3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcm0K From xen-arm-bounces@lists.xen.org Fri Jul 12 11:29:33 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 11:29:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxbXW-0001zS-JM; Fri, 12 Jul 2013 11:29:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Urljq-0007rs-Kv for xen-arm@lists.xen.org; Wed, 26 Jun 2013 09:10:06 +0000 Received: from [85.158.137.99:17131] by server-16.bemta-3.messagelabs.com id 67/68-15362-DEFAAC15; Wed, 26 Jun 2013 09:10:05 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1372237804!14708166!2 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.9; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17131 invoked from network); 26 Jun 2013 09:10:05 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Jun 2013 09:10:05 -0000 X-IronPort-AV: E=Sophos;i="4.87,943,1363132800"; d="scan'208";a="6065723" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 26 Jun 2013 09:10:04 +0000 Received: from [10.80.2.42] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.4; Wed, 26 Jun 2013 10:10:03 +0100 Message-ID: <1372237802.18901.115.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Eric Trudeau Date: Wed, 26 Jun 2013 10:10:02 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 X-Originating-IP: [10.30.203.1] X-Mailman-Approved-At: Fri, 12 Jul 2013 11:29:29 +0000 Cc: xen-devel Subject: Re: [XenARM] XEN tools for ARM with Virtualization Extensions X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org KG1vdmluZyB0byB4ZW4tZGV2ZWwsIHhlbi1hcm0gaXMgZm9yIHRoZSBvbGRlciBQViBBUk0gcG9y dCkKCk9uIFR1ZSwgMjAxMy0wNi0yNSBhdCAyMzo1OSArMDAwMCwgRXJpYyBUcnVkZWF1IHdyb3Rl Ogo+IEhpLCBJIGFtIHRyeWluZyB0byBidWlsZCB0aGUgWEVOIHRvb2xzIGZvciBvdXIgcG9ydCBv ZiBYRU4gdG8gb3VyCj4gQ29ydGV4IEExNS1iYXNlZCBwbGF0Zm9ybS4KPiAKPiBJIGFtIHVzaW5n IHRoZSByZXBvIGF0IGdpdDovL3hlbmJpdHMueGVucHJvamVjdC5vcmcveGVuLmdpdCB0bwo+IGNy b3NzLWNvbXBpbGUgdGhlIHRvb2xzIGludG8gb3VyIHJvb3Rmcy4KCldoaWNoIGJyYW5jaC9jaGFu Z2VzZXQgYXJlIHlvdSB1c2luZz8KCkkndmUgaGVhcmQgdGhhdCB0aGUgcmVjZW50IFhTQS01NSBm aXhlcyBoYXZlIGJyb2tlbiBndWVzdCBsb2FkaW5nIG9uCkFSTSwgYnV0IHlvdXIgcHJvYmxlbXMg ZG8gbm90IHNlZW0gdG8gYmUgcmVsYXRlZCB0byB0aGF0IChJIG1lbnRpb24gaXQKYmVjYXVzZSBp dCBtaWdodCBiZSBzb21ldGhpbmcgeW91IGhpdCBhZnRlciB3ZSB3b3JrIHRocm91Z2ggeW91ciBj dXJyZW50Cmlzc3VlcykKCj4gVGhpcyByZXBvIGlzIHdoYXQgd2UgYXJlIHVzaW5nIGZvciBvdXIg SHlwZXJ2aXNvciBkZXZlbG9wbWVudCBhbHNvLgo+IAo+IFdoZW4gYnVpbGRpbmcgdGhlIHRvb2xz LCBJIGZvdW5kIHRoYXQgbGliYWlvIGRvZXMgbm90IGJ1aWxkIGZvciBBUk0KPiBzaW5jZSBpdCB3 YXMgbWlzc2luZyB0b29scy9saWJhaW8vc3JjL3N5c2NhbGwtYXJtLmguCj4gCj4gSSBmb3VuZCBh IHZlcnNpb24gb24gdGhlIHdlYiBzbyB0aGF0IEkgY291bGQgY29udGludWUuCgpBcmUgeW91IHBp Y2tpbmcgdXAgdGhlIGxpYmFpbyBpbiB0b29scy9saWJhaW8/IFRoYXQgaXMgYW4gYW5jaWVudApz bmFwc2hvdCB1c2VkIHRvIHN1cHBvcnQgb2xkZXIgZGlzdHJvcyB3aGljaCBkb24ndCBzaGlwIGxp YmFpbwp0aGVtc2VsdmVzLiBJdCByZWFsbHkgc2hvdWxkbid0IGV2ZW4gYmUgY29uc2lkZXJlZCBm b3IgQVJNICh0aGlzIGlzIGEKYnVnIGluIG91ciBidWlsZCBzeXN0ZW0gSU1ITykuIElmIHlvdSBp bnN0YWxsIHRoZSBsaWJhaW8gKGFuZCBoZWFkZXJzCmV0YykgZnJvbSB5b3VyIGRpc3RybyB0aGVu IGNvbmZpZ3VyZSB3aWxsIGRldGVjdCB0aGlzIGFuZCBub3QgdXNlIHRoZQplbWJlZGRlZCBjb3B5 LiAoVGhlIGVtYmVkZGVkIGNvcHkgaXMgb24gbXkgaGl0bGlzdCBmb3IgY3J1ZnQgcmVtb3ZhbCBm b3IKNC40LCBidXQgd2UgYXJlIGZyb3plbiBmb3IgNC4zIHJpZ2h0IG5vdyBzbyBJIGNhbid0IHRv dWNoIGl0KQoKRldJVyBJIHdyb3RlIHVwIHNvbWUgZGV0YWlscyBvZiBob3cgSSBjcm9zcyBjb21w aWxlIHdpdGggRGViaWFuL1VidW50dQphdApodHRwOi8vd2lraS54ZW4ub3JnL3dpa2kvWGVuX0FS TV93aXRoX1ZpcnR1YWxpemF0aW9uX0V4dGVuc2lvbnMvQ3Jvc3NDb21waWxpbmcgd2hpY2ggaW5j bHVkZXMgbGlzdHMgb2YgcGFja2FnZXMgdG8gaW5zdGFsbCBldGMuCgo+IEkgYWxzbyBmb3VuZCB0 aGF0IHhjX2RvbV9lbGZsb2FkZXIuY+KAmXMgZnVuY3Rpb24sIHhjX2RvbV9ndWVzdF90eXBlKCks Cj4gZGlkIG5vdCBrbm93IGFib3V0IHRoZSBFTV9BUk0gbWFjaGluZSB0eXBlLgoKWW91IHNob3Vs ZG4ndCBiZSBoaXR0aW5nIHRoZSBlbGYgbG9hZGVyIHBhdGhzLCB5b3Ugc2hvdWxkIGluc3RlYWQg dXNlCnRoZSB6SW1hZ2UgdmVyc2lvbiBvZiB0aGUga2VybmVsIHdoaWNoIHdpbGwgaGl0IHRoZQp4 Y19kb21fYXJtemltYWdlbG9hZGVyLmMgY29kZSBwYXRocy4KCldlIGRpZCBhdCBvbmUgcG9pbnQg aW4gdGhlIHZlcnkgZWFybHkgZGF5cyBvZiB0aGUgcG9ydCBzdXBwb3J0IGxvYWRpbmcKRUxGIGZp bGVzIHZpYSBhIHF1aWNrIGhhY2sgb2YgYSB0b29sICgieGNidWlsZCIpIGJ1dCB0aGF0IGhhcyBi ZWVuCnN1cGVyY2VkZWQgYnkgdGhlIHByb3BlciB0b29sc3RhY2sgc3VwcG9ydCBhbmQgdGhlIHVz ZSBvZiB6SW1hZ2UuCgo+IEFtIEkgdXNpbmcgdGhlIHdyb25nIHJlcG8gZm9yIGRldmVsb3BtZW50 IG9mIHRoZSB0b29scyBmb3IgQVJNPwoKCj4gCj4gSWYgbm90LCB0aGUgdHdpa2kgc2VlbXMgdG8g aW5kaWNhdGUgdGhhdCB4bCBpcyB3b3JraW5nIG9uIEFSTSB0bwo+IGNyZWF0ZSBndWVzdCBtYWNo aW5lcy4KCk1vZHVsbyBhbnkgYnVncyBpbnRyb2R1Y2VkIGJ5IFhTQS01NSB3ZSBiZWxpZXZlIGl0 IGlzLgoKSWFuLgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXwpYZW4tYXJtIG1haWxpbmcgbGlzdApYZW4tYXJtQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xp c3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcm0K From xen-arm-bounces@lists.xen.org Fri Jul 12 11:32:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 11:32:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uxba1-00025w-SN; Fri, 12 Jul 2013 11:32:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uxba1-00025r-33 for xen-arm@lists.xen.org; Fri, 12 Jul 2013 11:32:05 +0000 Received: from [85.158.139.83:50087] by server-14.bemta-5.messagelabs.com id 85/AC-11419-439EFD15; Fri, 12 Jul 2013 11:32:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1373628723!23488328!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5811 invoked from network); 12 Jul 2013 11:32:03 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jul 2013 11:32:03 -0000 Received: by mail-wi0-f169.google.com with SMTP id c10so586179wiw.0 for ; Fri, 12 Jul 2013 04:32:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=kAagwGrJEPKfjZqS1Gm/UjxGGwEYVltOMh387KhuEzc=; b=yxSo8yYdls75wCPRMPrAQaiLxMtSvRG2Uxf1At80IGd9DdsdezbdO4ebsMhUgu/7nZ HkNQobbSXhuLhoaeeBy+TyjqZujs+G2ZHPRbbkA2JO3f+wzKndmdd07TRy95m6uxYhQq 0ZChqYyf0eWuR1yFJmH1gG7VwYp4CILKX11kLjvnCPJPA+dPuJPW8Xzj9K+16AmfQG2k 3bZbTGjPF8N0O7lSzTqfoqkljiRGhDSOXePzqfq1HURuMIIDnQ/s2ZrBI6u7Otjym2NO xosSrY2lPlrrjbMddAVhs3z2a7PasWt5mjMsDt/xPPXqKWUzlwuJYlafRWnkwFuGv8Jz pvOA== X-Received: by 10.180.187.235 with SMTP id fv11mr1328882wic.65.1373628723636; Fri, 12 Jul 2013 04:32:03 -0700 (PDT) Received: from [172.16.26.11] (054181f9.skybroadband.com. [5.65.129.249]) by mx.google.com with ESMTPSA id x2sm2820583wif.3.2013.07.12.04.32.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Jul 2013 04:32:02 -0700 (PDT) Message-ID: <51DFE930.2090305@xen.org> Date: Fri, 12 Jul 2013 12:32:00 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: "xen-arm@lists.xen.org" Subject: [XenARM] Trouble with list moderation X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org Hi, just to let you know that I have had some trouble with the list moderation: some messages were stuck in the moderation queue for a few weeks. I approved them, and a week later there again (and had not been sent). I think I managed to resolve this now, but you probably saw an influx of older messages. Lars _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Fri Jul 12 11:32:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 11:32:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uxba1-00025w-SN; Fri, 12 Jul 2013 11:32:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uxba1-00025r-33 for xen-arm@lists.xen.org; Fri, 12 Jul 2013 11:32:05 +0000 Received: from [85.158.139.83:50087] by server-14.bemta-5.messagelabs.com id 85/AC-11419-439EFD15; Fri, 12 Jul 2013 11:32:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1373628723!23488328!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5811 invoked from network); 12 Jul 2013 11:32:03 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jul 2013 11:32:03 -0000 Received: by mail-wi0-f169.google.com with SMTP id c10so586179wiw.0 for ; Fri, 12 Jul 2013 04:32:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=kAagwGrJEPKfjZqS1Gm/UjxGGwEYVltOMh387KhuEzc=; b=yxSo8yYdls75wCPRMPrAQaiLxMtSvRG2Uxf1At80IGd9DdsdezbdO4ebsMhUgu/7nZ HkNQobbSXhuLhoaeeBy+TyjqZujs+G2ZHPRbbkA2JO3f+wzKndmdd07TRy95m6uxYhQq 0ZChqYyf0eWuR1yFJmH1gG7VwYp4CILKX11kLjvnCPJPA+dPuJPW8Xzj9K+16AmfQG2k 3bZbTGjPF8N0O7lSzTqfoqkljiRGhDSOXePzqfq1HURuMIIDnQ/s2ZrBI6u7Otjym2NO xosSrY2lPlrrjbMddAVhs3z2a7PasWt5mjMsDt/xPPXqKWUzlwuJYlafRWnkwFuGv8Jz pvOA== X-Received: by 10.180.187.235 with SMTP id fv11mr1328882wic.65.1373628723636; Fri, 12 Jul 2013 04:32:03 -0700 (PDT) Received: from [172.16.26.11] (054181f9.skybroadband.com. [5.65.129.249]) by mx.google.com with ESMTPSA id x2sm2820583wif.3.2013.07.12.04.32.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Jul 2013 04:32:02 -0700 (PDT) Message-ID: <51DFE930.2090305@xen.org> Date: Fri, 12 Jul 2013 12:32:00 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: "xen-arm@lists.xen.org" Subject: [XenARM] Trouble with list moderation X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org Hi, just to let you know that I have had some trouble with the list moderation: some messages were stuck in the moderation queue for a few weeks. I approved them, and a week later there again (and had not been sent). I think I managed to resolve this now, but you probably saw an influx of older messages. Lars _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Fri Jul 12 13:14:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 13:14:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxdBR-0005Lq-08; Fri, 12 Jul 2013 13:14:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxdBP-0005LY-CM; Fri, 12 Jul 2013 13:14:47 +0000 Received: from [85.158.139.83:30309] by server-2.bemta-5.messagelabs.com id 71/F9-23285-64100E15; Fri, 12 Jul 2013 13:14:46 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1373634884!27376298!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16736 invoked from network); 12 Jul 2013 13:14:45 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jul 2013 13:14:45 -0000 X-IronPort-AV: E=Sophos;i="4.89,653,1367971200"; d="scan'208";a="34883396" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 12 Jul 2013 13:14:43 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Fri, 12 Jul 2013 09:14:42 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UxdBK-0001G3-Lc; Fri, 12 Jul 2013 14:14:42 +0100 Date: Fri, 12 Jul 2013 14:14:36 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Julien Grall In-Reply-To: <51B5A52D.7050709@linaro.org> Message-ID: References: <20130609124213.GA19123@cbz-workstation> <20130610001315.GA1714@cbz-workstation> <51B5A52D.7050709@linaro.org> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Linking errors of Mini-OS for ARM32 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 10 Jun 2013, Julien Grall wrote: > On 06/10/2013 01:13 AM, Chen Baozi wrote: > > > On Sun, Jun 09, 2013 at 02:48:42PM +0100, Julien Grall wrote: > >> On Sun, Jun 9, 2013 at 1:42 PM, Chen Baozi wrote: > >>> Since finishing the very beginning setup assembly, I was turning to adding > >>> necessary headers and empty functions to build the binary. After introducing > >>> those bit operations, spinlocks etc., I thought I have a basic framework to > >>> pass the first build. However, when comming to the final linking stage, > >>> there are errors: > >>> > >>> arm-linux-gnueabihf-ld -T arch/arm/minios-arm32.lds > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o -o > >>> //home/cbz/src/xen/extras/mini-os/mini-os > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o: In function `init_blkfront': > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:/home/cbz/src/xen/extras/mini-os/blkfront.c:122: more undefined references to `__aeabi_uldivmod' follow > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x50): undefined reference to `__aeabi_unwind_cpp_pr0' > >>> make: *** [/home/cbz/src/xen/extras/mini-os/mini-os] Error 1 > >>> > >>> I googled that error message. Some has mentioned that add "-fno-exceptions > >>> -fno-unwind tables" could sovle the problem. I tried, but got the same > >>> errors. > >>> > >>> Any ideas? > >> > >> You need to provide an implementation for __aeabi_uldivmod. > >> For this purpose, you can re-use xen/arch/arm/arm32/lib/lib1func.S > > > > Thanks a lot. > > > > A further question. I'm a litte curious that whether __aeabi_uldivmod is missing > > because of a toolchain bug or some other reasons? > > __aeabi_uldivmod and co. are provided by libgcc.{so,a}. Mini-OS is not > linked against this library. Actually the implementation of __aeabi_uldivmod in xen/arch/arm/arm32/lib/lib1funcs.S is GPLv2. You cannot use it in Mini-OS that is BSD licensed. You need to find a BSD implementation of that function. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Fri Jul 12 13:14:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 12 Jul 2013 13:14:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxdBR-0005Lq-08; Fri, 12 Jul 2013 13:14:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UxdBP-0005LY-CM; Fri, 12 Jul 2013 13:14:47 +0000 Received: from [85.158.139.83:30309] by server-2.bemta-5.messagelabs.com id 71/F9-23285-64100E15; Fri, 12 Jul 2013 13:14:46 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1373634884!27376298!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16736 invoked from network); 12 Jul 2013 13:14:45 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Jul 2013 13:14:45 -0000 X-IronPort-AV: E=Sophos;i="4.89,653,1367971200"; d="scan'208";a="34883396" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 12 Jul 2013 13:14:43 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Fri, 12 Jul 2013 09:14:42 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UxdBK-0001G3-Lc; Fri, 12 Jul 2013 14:14:42 +0100 Date: Fri, 12 Jul 2013 14:14:36 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Julien Grall In-Reply-To: <51B5A52D.7050709@linaro.org> Message-ID: References: <20130609124213.GA19123@cbz-workstation> <20130610001315.GA1714@cbz-workstation> <51B5A52D.7050709@linaro.org> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Linking errors of Mini-OS for ARM32 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On Mon, 10 Jun 2013, Julien Grall wrote: > On 06/10/2013 01:13 AM, Chen Baozi wrote: > > > On Sun, Jun 09, 2013 at 02:48:42PM +0100, Julien Grall wrote: > >> On Sun, Jun 9, 2013 at 1:42 PM, Chen Baozi wrote: > >>> Since finishing the very beginning setup assembly, I was turning to adding > >>> necessary headers and empty functions to build the binary. After introducing > >>> those bit operations, spinlocks etc., I thought I have a basic framework to > >>> pass the first build. However, when comming to the final linking stage, > >>> there are errors: > >>> > >>> arm-linux-gnueabihf-ld -T arch/arm/minios-arm32.lds > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o -o > >>> //home/cbz/src/xen/extras/mini-os/mini-os > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o: In function `init_blkfront': > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/blkfront.c:122: undefined reference to `__aeabi_uldivmod' > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:/home/cbz/src/xen/extras/mini-os/blkfront.c:122: more undefined references to `__aeabi_uldivmod' follow > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' > >>> /home/cbz/src/xen/extras/mini-os/mini-os.o:(.ARM.exidx+0x50): undefined reference to `__aeabi_unwind_cpp_pr0' > >>> make: *** [/home/cbz/src/xen/extras/mini-os/mini-os] Error 1 > >>> > >>> I googled that error message. Some has mentioned that add "-fno-exceptions > >>> -fno-unwind tables" could sovle the problem. I tried, but got the same > >>> errors. > >>> > >>> Any ideas? > >> > >> You need to provide an implementation for __aeabi_uldivmod. > >> For this purpose, you can re-use xen/arch/arm/arm32/lib/lib1func.S > > > > Thanks a lot. > > > > A further question. I'm a litte curious that whether __aeabi_uldivmod is missing > > because of a toolchain bug or some other reasons? > > __aeabi_uldivmod and co. are provided by libgcc.{so,a}. Mini-OS is not > linked against this library. Actually the implementation of __aeabi_uldivmod in xen/arch/arm/arm32/lib/lib1funcs.S is GPLv2. You cannot use it in Mini-OS that is BSD licensed. You need to find a BSD implementation of that function. _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Tue Jul 16 06:33:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 16 Jul 2013 06:33:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UyypG-0001cJ-Ht; Tue, 16 Jul 2013 06:33:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UyypE-0001c9-VY for xen-arm@lists.xen.org; Tue, 16 Jul 2013 06:33:29 +0000 Received: from [85.158.143.35:22652] by server-2.bemta-4.messagelabs.com id 5F/1A-09492-839E4E15; Tue, 16 Jul 2013 06:33:28 +0000 X-Env-Sender: giridhar.maruthy@linaro.org X-Msg-Ref: server-15.tower-21.messagelabs.com!1373956407!338279!1 X-Originating-IP: [74.125.83.52] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28473 invoked from network); 16 Jul 2013 06:33:27 -0000 Received: from mail-ee0-f52.google.com (HELO mail-ee0-f52.google.com) (74.125.83.52) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jul 2013 06:33:27 -0000 Received: by mail-ee0-f52.google.com with SMTP id c50so133651eek.39 for ; Mon, 15 Jul 2013 23:33:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=OIsludAbug6d8Gx3QJdI6hZkKAn9YArT+nm4hCHPSIs=; b=UP5onfnI+R9tdHts2o10r3LnqUHaCBzPBhhGfHsKdXcsUunFBdzUyktdJEvtLCS1zj X+0mZW3gU9qdP3WY7hYF5Ch+fdBU5pGeENbvcDt8nT+GSl7VHvfwaxrwtXx+xd61DzuF Ea5yy2hiuJJ1Fjo0eBTRFmatgURCD+ZEBYKpuDbgJVBbmxo+IbygxEx5TUumhIrx0/PK U/b5tB+nofQH8kSgQBEO4MB3/KH2USvEpgzl4q3SnXkKDqc6YRpixCsg/leXUBeDRI8u bPRuyKuBbl/1cUV+Z6vlQ7dAa8MXFqhjEDZg76FVfLG1xqHWcowSgW1yEIq8G/Z/75rf Frrg== MIME-Version: 1.0 X-Received: by 10.14.203.8 with SMTP id e8mr61367047eeo.96.1373956406856; Mon, 15 Jul 2013 23:33:26 -0700 (PDT) Received: by 10.223.39.20 with HTTP; Mon, 15 Jul 2013 23:33:26 -0700 (PDT) In-Reply-To: <5151F707.8080704@citrix.com> References: <5151C711.5090604@citrix.com> <5151F707.8080704@citrix.com> Date: Tue, 16 Jul 2013 12:03:26 +0530 Message-ID: From: Giridhar Maruthy To: Julien Grall X-Gm-Message-State: ALoCoQlJO8XBDOFyk3UDklgreQhMaBLfvdc2VjfUXAvBo6L81HrPFz4svwoIo72eU2jcrQKKCNTP Cc: Anthony PERARD , "xen-arm@lists.xen.org" , Xen Devel Subject: Re: [XenARM] [Xen-devel] Testing xen-arm on Arndale X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org Hi Julien, I am trying to use Xen on Arndale board with instrunction on page http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale I am also facing a problem similar to the one that you debugged before. Translation fault is happening at level3. The fault happens when 0x12c20008 is accessed. This location happens to be a register of UART2 port on Arndale. A part of the log is below. Any idea what caused access to UART to fail? (XEN) Device-tree contains "xen,xen" node. Ignoring. (XEN) Populate P2M 0x50000000->0x60000000 (1:1 mapping for dom0) (XEN) Loading kernel from boot module 1 (XEN) Loading zImage from 0000000060000000 to 0000000050008000-00000000503b6858 (XEN) Loading dom0 DTB to 0x000000005fe00000-0x000000005fe04442 (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) ********************************************** (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS (XEN) ******* This option is intended to aid debugging of Xen by ensuring (XEN) ******* that all output is synchronously delivered on the serial line. (XEN) ******* However it can introduce SIGNIFICANT latencies and affect (XEN) ******* timekeeping. It is NOT recommended for production use! (XEN) ********************************************** (XEN) 3... 2... 1... (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 220kB init memory. (XEN) Guest data abort: Translation fault at level 3 (XEN) gva=f7020008 (XEN) gpa=0000000012c20008 (XEN) size=2 sign=0 write=0 reg=2 (XEN) eat=0 cm=0 s1ptw=0 dfsc=7 (XEN) dom0 IPA 0x0000000012c20008 (XEN) P2M @ 02ffbf80 mfn:0xbfdfc (XEN) 1ST[0x0] = 0x00000000bfdfe6ff (XEN) 2ND[0x96] = 0x00000000bfd776ff (XEN) 3RD[0x20] = 0x0000000000000000 Thanks, Giridhar On 27 March 2013 00:59, Julien Grall wrote: > On 03/26/2013 04:04 PM, Anthony PERARD wrote: > >> CC'ing xen-devel, where the ARMv7+ port of Xen is happening. >> >> On 25/03/13 09:46, Sengul Thomas wrote: >>> Hello Anthony, >>> I'm hoping your are the right person to ask about xen-arm on Arndale. >>> >>> I've tried the following wiki to run xen-arm on Arndale and it crashes while booting dom0. >>> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale >>> >>> Here goes some part of log (attached the full log): >>> >>> (XEN) Guest data abort: Translation fault at level 2 >>> (XEN) gva=23c1901c >>> (XEN) gpa=0000000023c1901c >>> (XEN) size=2 sign=0 write=1 reg=0 >>> (XEN) eat=0 cm=0 s1ptw=0 dfsc=6 >>> (XEN) dom0 IPA 0x0000000023c1901c >>> (XEN) P2M @ 02ffbfc0 mfn:0xbfdfe >>> (XEN) 1ST[0x0] = 0x00000000bfdfd6ff >>> (XEN) 2ND[0x11e] = 0x0000000000000000 >>> (XEN) ----[ Xen-4.3-unstable arm32 debug=y Tainted: C ]---- >>> (XEN) CPU: 0 >>> (XEN) PC: 4000893c >>> >>> Looks like dom0 tried to access at 23c1901c and page fault happens. >>> I've got no idea how to figure out what is going on. >>> Could you tell me any helpful tips to move on further? > > It's seems the kernel is unable to start when the zImage is loaded at > 0x40007000. If you change this address, both in U-Boot and the DTS, by > 0x60000000 the kernel is able to start. > > I updated wiki page with the new instructions and the new device tree. > > Cheers, > > Julien > > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Tue Jul 16 06:33:35 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 16 Jul 2013 06:33:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UyypG-0001cJ-Ht; Tue, 16 Jul 2013 06:33:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UyypE-0001c9-VY for xen-arm@lists.xen.org; Tue, 16 Jul 2013 06:33:29 +0000 Received: from [85.158.143.35:22652] by server-2.bemta-4.messagelabs.com id 5F/1A-09492-839E4E15; Tue, 16 Jul 2013 06:33:28 +0000 X-Env-Sender: giridhar.maruthy@linaro.org X-Msg-Ref: server-15.tower-21.messagelabs.com!1373956407!338279!1 X-Originating-IP: [74.125.83.52] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28473 invoked from network); 16 Jul 2013 06:33:27 -0000 Received: from mail-ee0-f52.google.com (HELO mail-ee0-f52.google.com) (74.125.83.52) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jul 2013 06:33:27 -0000 Received: by mail-ee0-f52.google.com with SMTP id c50so133651eek.39 for ; Mon, 15 Jul 2013 23:33:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=OIsludAbug6d8Gx3QJdI6hZkKAn9YArT+nm4hCHPSIs=; b=UP5onfnI+R9tdHts2o10r3LnqUHaCBzPBhhGfHsKdXcsUunFBdzUyktdJEvtLCS1zj X+0mZW3gU9qdP3WY7hYF5Ch+fdBU5pGeENbvcDt8nT+GSl7VHvfwaxrwtXx+xd61DzuF Ea5yy2hiuJJ1Fjo0eBTRFmatgURCD+ZEBYKpuDbgJVBbmxo+IbygxEx5TUumhIrx0/PK U/b5tB+nofQH8kSgQBEO4MB3/KH2USvEpgzl4q3SnXkKDqc6YRpixCsg/leXUBeDRI8u bPRuyKuBbl/1cUV+Z6vlQ7dAa8MXFqhjEDZg76FVfLG1xqHWcowSgW1yEIq8G/Z/75rf Frrg== MIME-Version: 1.0 X-Received: by 10.14.203.8 with SMTP id e8mr61367047eeo.96.1373956406856; Mon, 15 Jul 2013 23:33:26 -0700 (PDT) Received: by 10.223.39.20 with HTTP; Mon, 15 Jul 2013 23:33:26 -0700 (PDT) In-Reply-To: <5151F707.8080704@citrix.com> References: <5151C711.5090604@citrix.com> <5151F707.8080704@citrix.com> Date: Tue, 16 Jul 2013 12:03:26 +0530 Message-ID: From: Giridhar Maruthy To: Julien Grall X-Gm-Message-State: ALoCoQlJO8XBDOFyk3UDklgreQhMaBLfvdc2VjfUXAvBo6L81HrPFz4svwoIo72eU2jcrQKKCNTP Cc: Anthony PERARD , "xen-arm@lists.xen.org" , Xen Devel Subject: Re: [XenARM] [Xen-devel] Testing xen-arm on Arndale X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org Hi Julien, I am trying to use Xen on Arndale board with instrunction on page http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale I am also facing a problem similar to the one that you debugged before. Translation fault is happening at level3. The fault happens when 0x12c20008 is accessed. This location happens to be a register of UART2 port on Arndale. A part of the log is below. Any idea what caused access to UART to fail? (XEN) Device-tree contains "xen,xen" node. Ignoring. (XEN) Populate P2M 0x50000000->0x60000000 (1:1 mapping for dom0) (XEN) Loading kernel from boot module 1 (XEN) Loading zImage from 0000000060000000 to 0000000050008000-00000000503b6858 (XEN) Loading dom0 DTB to 0x000000005fe00000-0x000000005fe04442 (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) ********************************************** (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS (XEN) ******* This option is intended to aid debugging of Xen by ensuring (XEN) ******* that all output is synchronously delivered on the serial line. (XEN) ******* However it can introduce SIGNIFICANT latencies and affect (XEN) ******* timekeeping. It is NOT recommended for production use! (XEN) ********************************************** (XEN) 3... 2... 1... (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 220kB init memory. (XEN) Guest data abort: Translation fault at level 3 (XEN) gva=f7020008 (XEN) gpa=0000000012c20008 (XEN) size=2 sign=0 write=0 reg=2 (XEN) eat=0 cm=0 s1ptw=0 dfsc=7 (XEN) dom0 IPA 0x0000000012c20008 (XEN) P2M @ 02ffbf80 mfn:0xbfdfc (XEN) 1ST[0x0] = 0x00000000bfdfe6ff (XEN) 2ND[0x96] = 0x00000000bfd776ff (XEN) 3RD[0x20] = 0x0000000000000000 Thanks, Giridhar On 27 March 2013 00:59, Julien Grall wrote: > On 03/26/2013 04:04 PM, Anthony PERARD wrote: > >> CC'ing xen-devel, where the ARMv7+ port of Xen is happening. >> >> On 25/03/13 09:46, Sengul Thomas wrote: >>> Hello Anthony, >>> I'm hoping your are the right person to ask about xen-arm on Arndale. >>> >>> I've tried the following wiki to run xen-arm on Arndale and it crashes while booting dom0. >>> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale >>> >>> Here goes some part of log (attached the full log): >>> >>> (XEN) Guest data abort: Translation fault at level 2 >>> (XEN) gva=23c1901c >>> (XEN) gpa=0000000023c1901c >>> (XEN) size=2 sign=0 write=1 reg=0 >>> (XEN) eat=0 cm=0 s1ptw=0 dfsc=6 >>> (XEN) dom0 IPA 0x0000000023c1901c >>> (XEN) P2M @ 02ffbfc0 mfn:0xbfdfe >>> (XEN) 1ST[0x0] = 0x00000000bfdfd6ff >>> (XEN) 2ND[0x11e] = 0x0000000000000000 >>> (XEN) ----[ Xen-4.3-unstable arm32 debug=y Tainted: C ]---- >>> (XEN) CPU: 0 >>> (XEN) PC: 4000893c >>> >>> Looks like dom0 tried to access at 23c1901c and page fault happens. >>> I've got no idea how to figure out what is going on. >>> Could you tell me any helpful tips to move on further? > > It's seems the kernel is unable to start when the zImage is loaded at > 0x40007000. If you change this address, both in U-Boot and the DTS, by > 0x60000000 the kernel is able to start. > > I updated wiki page with the new instructions and the new device tree. > > Cheers, > > Julien > > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Thu Jul 18 16:24:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 18 Jul 2013 16:24:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uzqzw-0005l4-KM; Thu, 18 Jul 2013 16:24:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uzqzv-0005ky-1o for xen-arm@lists.xen.org; Thu, 18 Jul 2013 16:24:07 +0000 Received: from [85.158.138.51:18309] by server-6.bemta-3.messagelabs.com id 48/A0-00484-5A618E15; Thu, 18 Jul 2013 16:24:05 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1374164645!28118717!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15384 invoked from network); 18 Jul 2013 16:24:05 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jul 2013 16:24:05 -0000 Received: by mail-lb0-f180.google.com with SMTP id o10so2707901lbi.39 for ; Thu, 18 Jul 2013 09:24:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=oQnIIM5INpsKl5VyL5OSFBBrrqcyPZE1Xb2om9zWfRo=; b=O7Tp9coNYOFpXB+WNdG5yqmlGkVVS5vhDGbGEt7hr8RwmQ27SUznU4QLxhSiopqJyw QzDtnUxAr4+MjXp4JzrAoAd3kmBRyv9NKJiOX1BFrP3yiqUQiT8Wxzl0ZZ+7TftYKj03 wGNqzMWWeWYChvc1sJZi3ZhmbOCiF92OFROrDzjFoqP0e7HazGGH2dBYEGs7oWe6PFSI 1A4u2e/QazPbdP6pbzWWLgqkyZ2kDAOcEQzMhBxFmZEoUQqjxYooQ3uDX7aga5d1JMr6 wHThSj6QuCwQt8TFyOKhu6s3cW5uJvPnjCF3VANCOkBabHKggelscZI853NiPQRIgKjj ltLg== MIME-Version: 1.0 X-Received: by 10.112.5.199 with SMTP id u7mr5758920lbu.67.1374164644359; Thu, 18 Jul 2013 09:24:04 -0700 (PDT) Received: by 10.112.130.135 with HTTP; Thu, 18 Jul 2013 09:24:04 -0700 (PDT) Date: Thu, 18 Jul 2013 12:24:04 -0400 X-Google-Sender-Auth: Recyl2MACVUWW9x4X6Bqf_tMnqg Message-ID: From: Russ Pavlicek To: xen-arm@lists.xen.org Subject: [XenARM] Xen Project User Summit looking for Xen/ARM talk X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org Greetings, I'd really like to see someone talk about Xen on ARM at the Xen Project User Summit in New Orleans in September. Unfortunately, I still haven't seen a submission on that subject come in yet. This is your golden opportunity to talk about Xen on ARM: futures, features, uses, etc. The Call for Participation for the Xen Project User Summit closes next week on July 26. If you have a Xen on ARM story to tell, please tell us about it. If you are not sure if it is a story worth telling, contact me directly and I will try to give you some guidance. You can find the CFP information here: http://events.linuxfoundation.org/events/linuxcon-north-america/program/xen-project-user-summit There's only a week left, so please submit soon! Thanks and I hope to see you in New Orleans! Russ Pavlicek Xen Project Evangelist _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Thu Jul 18 16:24:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 18 Jul 2013 16:24:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uzqzw-0005l4-KM; Thu, 18 Jul 2013 16:24:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uzqzv-0005ky-1o for xen-arm@lists.xen.org; Thu, 18 Jul 2013 16:24:07 +0000 Received: from [85.158.138.51:18309] by server-6.bemta-3.messagelabs.com id 48/A0-00484-5A618E15; Thu, 18 Jul 2013 16:24:05 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1374164645!28118717!1 X-Originating-IP: [209.85.217.180] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15384 invoked from network); 18 Jul 2013 16:24:05 -0000 Received: from mail-lb0-f180.google.com (HELO mail-lb0-f180.google.com) (209.85.217.180) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jul 2013 16:24:05 -0000 Received: by mail-lb0-f180.google.com with SMTP id o10so2707901lbi.39 for ; Thu, 18 Jul 2013 09:24:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=oQnIIM5INpsKl5VyL5OSFBBrrqcyPZE1Xb2om9zWfRo=; b=O7Tp9coNYOFpXB+WNdG5yqmlGkVVS5vhDGbGEt7hr8RwmQ27SUznU4QLxhSiopqJyw QzDtnUxAr4+MjXp4JzrAoAd3kmBRyv9NKJiOX1BFrP3yiqUQiT8Wxzl0ZZ+7TftYKj03 wGNqzMWWeWYChvc1sJZi3ZhmbOCiF92OFROrDzjFoqP0e7HazGGH2dBYEGs7oWe6PFSI 1A4u2e/QazPbdP6pbzWWLgqkyZ2kDAOcEQzMhBxFmZEoUQqjxYooQ3uDX7aga5d1JMr6 wHThSj6QuCwQt8TFyOKhu6s3cW5uJvPnjCF3VANCOkBabHKggelscZI853NiPQRIgKjj ltLg== MIME-Version: 1.0 X-Received: by 10.112.5.199 with SMTP id u7mr5758920lbu.67.1374164644359; Thu, 18 Jul 2013 09:24:04 -0700 (PDT) Received: by 10.112.130.135 with HTTP; Thu, 18 Jul 2013 09:24:04 -0700 (PDT) Date: Thu, 18 Jul 2013 12:24:04 -0400 X-Google-Sender-Auth: Recyl2MACVUWW9x4X6Bqf_tMnqg Message-ID: From: Russ Pavlicek To: xen-arm@lists.xen.org Subject: [XenARM] Xen Project User Summit looking for Xen/ARM talk X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org Greetings, I'd really like to see someone talk about Xen on ARM at the Xen Project User Summit in New Orleans in September. Unfortunately, I still haven't seen a submission on that subject come in yet. This is your golden opportunity to talk about Xen on ARM: futures, features, uses, etc. The Call for Participation for the Xen Project User Summit closes next week on July 26. If you have a Xen on ARM story to tell, please tell us about it. If you are not sure if it is a story worth telling, contact me directly and I will try to give you some guidance. You can find the CFP information here: http://events.linuxfoundation.org/events/linuxcon-north-america/program/xen-project-user-summit There's only a week left, so please submit soon! Thanks and I hope to see you in New Orleans! Russ Pavlicek Xen Project Evangelist _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Thu Jul 18 17:29:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 18 Jul 2013 17:29:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uzs1D-0007rc-EG; Thu, 18 Jul 2013 17:29:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uzs1B-0007rB-HN for xen-arm@lists.xen.org; Thu, 18 Jul 2013 17:29:29 +0000 Received: from [85.158.139.83:31306] by server-12.bemta-5.messagelabs.com id 8B/25-22750-8F528E15; Thu, 18 Jul 2013 17:29:28 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1374168565!28258649!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30037 invoked from network); 18 Jul 2013 17:29:28 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jul 2013 17:29:28 -0000 X-IronPort-AV: E=Sophos;i="4.89,695,1367971200"; d="scan'208";a="36044449" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 18 Jul 2013 17:29:25 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Thu, 18 Jul 2013 13:29:24 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1Uzs16-0006Rv-Ok; Thu, 18 Jul 2013 18:29:24 +0100 Date: Thu, 18 Jul 2013 18:29:12 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Russ Pavlicek In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Xen Project User Summit looking for Xen/ARM talk X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org You might want to CC xen-devel too, upstream Xen on ARM with virtualizatuion extensions development is done there. On Thu, 18 Jul 2013, Russ Pavlicek wrote: > Greetings, > > I'd really like to see someone talk about Xen on ARM at the Xen > Project User Summit in New Orleans in September. Unfortunately, I > still haven't seen a submission on that subject come in yet. > > This is your golden opportunity to talk about Xen on ARM: futures, > features, uses, etc. > > The Call for Participation for the Xen Project User Summit closes next > week on July 26. If you have a Xen on ARM story to tell, please tell > us about it. If you are not sure if it is a story worth telling, > contact me directly and I will try to give you some guidance. > > You can find the CFP information here: > > http://events.linuxfoundation.org/events/linuxcon-north-america/program/xen-project-user-summit > > There's only a week left, so please submit soon! > > Thanks and I hope to see you in New Orleans! > > Russ Pavlicek > Xen Project Evangelist > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Thu Jul 18 17:29:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 18 Jul 2013 17:29:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uzs1D-0007rc-EG; Thu, 18 Jul 2013 17:29:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uzs1B-0007rB-HN for xen-arm@lists.xen.org; Thu, 18 Jul 2013 17:29:29 +0000 Received: from [85.158.139.83:31306] by server-12.bemta-5.messagelabs.com id 8B/25-22750-8F528E15; Thu, 18 Jul 2013 17:29:28 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1374168565!28258649!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30037 invoked from network); 18 Jul 2013 17:29:28 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jul 2013 17:29:28 -0000 X-IronPort-AV: E=Sophos;i="4.89,695,1367971200"; d="scan'208";a="36044449" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 18 Jul 2013 17:29:25 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Thu, 18 Jul 2013 13:29:24 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1Uzs16-0006Rv-Ok; Thu, 18 Jul 2013 18:29:24 +0100 Date: Thu, 18 Jul 2013 18:29:12 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Russ Pavlicek In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Xen Project User Summit looking for Xen/ARM talk X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org You might want to CC xen-devel too, upstream Xen on ARM with virtualizatuion extensions development is done there. On Thu, 18 Jul 2013, Russ Pavlicek wrote: > Greetings, > > I'd really like to see someone talk about Xen on ARM at the Xen > Project User Summit in New Orleans in September. Unfortunately, I > still haven't seen a submission on that subject come in yet. > > This is your golden opportunity to talk about Xen on ARM: futures, > features, uses, etc. > > The Call for Participation for the Xen Project User Summit closes next > week on July 26. If you have a Xen on ARM story to tell, please tell > us about it. If you are not sure if it is a story worth telling, > contact me directly and I will try to give you some guidance. > > You can find the CFP information here: > > http://events.linuxfoundation.org/events/linuxcon-north-america/program/xen-project-user-summit > > There's only a week left, so please submit soon! > > Thanks and I hope to see you in New Orleans! > > Russ Pavlicek > Xen Project Evangelist > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm > _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Sat Jul 27 04:23:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 27 Jul 2013 04:23:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1V2w1y-0008RO-Oo; Sat, 27 Jul 2013 04:22:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1V2w1w-0008R5-Q2; Sat, 27 Jul 2013 04:22:57 +0000 Received: from [85.158.137.99:14180] by server-1.bemta-3.messagelabs.com id 4B/C6-01921-F1B43F15; Sat, 27 Jul 2013 04:22:55 +0000 X-Env-Sender: russell.pavlicek@citrix.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1374898972!18234248!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16554 invoked from network); 27 Jul 2013 04:22:54 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jul 2013 04:22:54 -0000 X-IronPort-AV: E=Sophos;i="4.89,755,1367971200"; d="scan'208";a="39676469" Received: from sjcpex01cl02.citrite.net ([10.216.14.144]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 27 Jul 2013 04:22:51 +0000 Received: from SJCPEX01CL03.citrite.net ([169.254.3.42]) by SJCPEX01CL02.citrite.net ([10.216.14.144]) with mapi id 14.02.0342.004; Fri, 26 Jul 2013 21:22:50 -0700 From: Russell Pavlicek To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-publicity@lists.xen.org" , "xen-api@lists.xen.org" Thread-Topic: [Xen-users] Xen Project User Summit Call for Participation Closes July 26 Thread-Index: Ac6KgN64cj/x3Xu8TGOIHsn8yDSOhg== Date: Sat, 27 Jul 2013 04:22:49 +0000 Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA203D004@SJCPEX01CL03.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.2.168] MIME-Version: 1.0 Subject: Re: [XenARM] [Xen-users] Xen Project User Summit Call for Participation Closes July 26 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org We've extended the deadline to July 31. If you've been meaning to submit a talk proposal, now is the time! Russ Pavlicek Xen Project Evangelist -----Original Message----- From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Russ Pavlicek Sent: Thursday, July 11, 2013 2:39 PM To: xen-users@lists.xen.org Subject: [Xen-users] Xen Project User Summit Call for Participation Closes July 26 Just a reminder that the Call For Participation for the Xen Project User Summit in New Orleans on September 18 is still open for another two weeks. We want to hear from members of the user community about their experiences with Xen. It might be about a case studie, Xen-based clouds, Xen-related projects, security, best practices, or just about anything else related to Xen. If you have a story to tell, submit it and you may find yourself with an opportunity to speak to your peers about it, Just about everything you should need to know can be found here: http://events.linuxfoundation.org/events/linuxcon-north-america/program/xen-project-user-summit Remember to submit your talk proposal by July 26. If you have vacation time planned in the near future, consider submitting your proposal now so you don't forget. If you have any questions, let me know and I will do my best to get you answers. Hope to see (and hear) you at the Xen Project User Summit on September 18! Sincerely, Russell Pavlicek Xen Project Evangelist _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm From xen-arm-bounces@lists.xen.org Sat Jul 27 04:23:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 27 Jul 2013 04:23:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1V2w1y-0008RO-Oo; Sat, 27 Jul 2013 04:22:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1V2w1w-0008R5-Q2; Sat, 27 Jul 2013 04:22:57 +0000 Received: from [85.158.137.99:14180] by server-1.bemta-3.messagelabs.com id 4B/C6-01921-F1B43F15; Sat, 27 Jul 2013 04:22:55 +0000 X-Env-Sender: russell.pavlicek@citrix.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1374898972!18234248!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16554 invoked from network); 27 Jul 2013 04:22:54 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jul 2013 04:22:54 -0000 X-IronPort-AV: E=Sophos;i="4.89,755,1367971200"; d="scan'208";a="39676469" Received: from sjcpex01cl02.citrite.net ([10.216.14.144]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 27 Jul 2013 04:22:51 +0000 Received: from SJCPEX01CL03.citrite.net ([169.254.3.42]) by SJCPEX01CL02.citrite.net ([10.216.14.144]) with mapi id 14.02.0342.004; Fri, 26 Jul 2013 21:22:50 -0700 From: Russell Pavlicek To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-publicity@lists.xen.org" , "xen-api@lists.xen.org" Thread-Topic: [Xen-users] Xen Project User Summit Call for Participation Closes July 26 Thread-Index: Ac6KgN64cj/x3Xu8TGOIHsn8yDSOhg== Date: Sat, 27 Jul 2013 04:22:49 +0000 Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA203D004@SJCPEX01CL03.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.2.168] MIME-Version: 1.0 Subject: Re: [XenARM] [Xen-users] Xen Project User Summit Call for Participation Closes July 26 X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org We've extended the deadline to July 31. If you've been meaning to submit a talk proposal, now is the time! Russ Pavlicek Xen Project Evangelist -----Original Message----- From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Russ Pavlicek Sent: Thursday, July 11, 2013 2:39 PM To: xen-users@lists.xen.org Subject: [Xen-users] Xen Project User Summit Call for Participation Closes July 26 Just a reminder that the Call For Participation for the Xen Project User Summit in New Orleans on September 18 is still open for another two weeks. We want to hear from members of the user community about their experiences with Xen. It might be about a case studie, Xen-based clouds, Xen-related projects, security, best practices, or just about anything else related to Xen. If you have a story to tell, submit it and you may find yourself with an opportunity to speak to your peers about it, Just about everything you should need to know can be found here: http://events.linuxfoundation.org/events/linuxcon-north-america/program/xen-project-user-summit Remember to submit your talk proposal by July 26. If you have vacation time planned in the near future, consider submitting your proposal now so you don't forget. If you have any questions, let me know and I will do my best to get you answers. Hope to see (and hear) you at the Xen Project User Summit on September 18! Sincerely, Russell Pavlicek Xen Project Evangelist _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users _______________________________________________ Xen-arm mailing list Xen-arm@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm