From xen-arm-bounces@lists.xen.org Fri May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCW-00068E-Cc; Fri, 03 May 2013 12:35:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Szi1w-0005yq-8a for xen-arm@lists.xensource.com; Fri, 10 Aug 2012 05:45:04 +0000 Received: from [85.158.138.51:32191] by server-10.bemta-3.messagelabs.com id 00/D9-07905-FDF94205; Fri, 10 Aug 2012 05:45:03 +0000 X-Env-Sender: maheen_butt26@yahoo.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1344577501!8851318!1 X-Originating-IP: [98.138.91.43] X-SpamReason: No, hits=0.7 required=7.0 tests=FROM_HAS_ULINE_NUMS, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10667 invoked from network); 10 Aug 2012 05:45:02 -0000 Received: from nm29-vm0.bullet.mail.ne1.yahoo.com (HELO nm29-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.43) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Aug 2012 05:45:02 -0000 Received: from [98.138.90.48] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 05:45:00 -0000 Received: from [98.138.88.235] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 05:45:00 -0000 Received: from [127.0.0.1] by omp1035.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 05:45:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 496782.94234.bm@omp1035.mail.ne1.yahoo.com Received: (qmail 78992 invoked by uid 60001); 10 Aug 2012 05:45:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1344577500; bh=oTlcfSkjalOgdVeIJPHD4JkBvtRE89Np8TvCgyMw9nk=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=myHyh+sJMmyau7t+d7DwqnDyl9RA9eLw9zHTHdinWotroaiaPyjxdYilZKD1fO0F6OEE0FrRo0smL0QmRHabsoTAb5IuGvUZmxbO7bIoZjUalpViU1cjo+KMJ914LzIrAT0gUGCYW5PTT7RYxti851WKTInznRG/MFRtC2rjc88= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=VynNME7JCbO+QJxWGzbQpLXuzSoSqtHzaq9tR2RxWchqvdwcODxF5qERrLUJOzgWC8fW376ViJb0czRHs74RIALoOoooj1Sx4l9kAKwUl7fOcP2FuzwIbOkdruSdzn7glIhlddjolmZLCcSgt3OynZ0ODxAZYSsJx2oug3ZIOwE=; X-YMail-OSG: NbZ5N34VM1n_vIyuKil_L.L2iVck1z6qFNsg1SptcH49tXQ nblt6oFClHjT0sqdgPorB3UfDS.KLvj46hlKrraGvcpsz4WENa01gDxO1Iob F30dlvIZff1l68gOSwoeLfWTi2Kq5rj5pkpSzgVlJghkfNhcnSrgaIksLWQL nrIa1lRbDhzoFSpBJKhCBsi.wSdn_aWl4e.kqBSQmai9lqQsusdJ4mY38ux2 Fd3.e2xTHTafmcqcKMdV9OQKhVqyNI86QKlD87XXr9p5XDBMo5PdkMN1XnKC RePlz1KnQmZVAZu3HPLV_uh8mZVgxrpnGJPPTCZidd8cmqBFtE.eqlDbhXWB bwgo7mS6ZhDTH.JfRzxYZMZACxFrtFfPWVK49axo3sKeNBFkAzKA_LhVZoOC 1xyIkoVAKzwKiGayG4Mc5GPiWFdT_57wVodk0mVG.nn8EX2G7jOyVu6UHZbE GWGNAEol8Pznc.u6X_CWQfhNpoOUmkjrcwUa3yj3hNmaqwwOCcdcfDvMD972 zX5VqytzNj_6x4hpYnGddf5.NKqpLcL2gUnT7pTOL1JZXdmBoLl53Nh66Srp CNDmDIIvUMi0tJMKj7hK_pM620_dVp2OTIi866WtjGln596M_0r3MrbkI.6j Y_3A7PnQfIw-- Received: from [58.27.199.186] by web126003.mail.ne1.yahoo.com via HTTP; Thu, 09 Aug 2012 22:45:00 PDT X-Mailer: YahooMailWebService/0.8.120.356233 Message-ID: <1344577500.65644.YahooMailNeo@web126003.mail.ne1.yahoo.com> Date: Thu, 9 Aug 2012 22:45:00 -0700 (PDT) From: maheen butt To: "xen-arm@lists.xensource.com" , "sbuk.suh@samsung.com" , "keir@xen.org" , "community.manager@xen.org" MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Subject: [XenARM] Xen-ARM and paravirt_ops? X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: maheen butt List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3096104876794683830==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3096104876794683830== Content-Type: multipart/alternative; boundary="-1134493521-1584150673-1344577500=:65644" ---1134493521-1584150673-1344577500=:65644 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi,=0AI came to know from Xen-ARM wiki and other related pages that ARM =A0= port is based on=A0=0Axen-unstable and it can boot a Linux 3.0 based virtua= l machine (dom 0). for reference=0Ahttps://lkml.org/lkml/2011/11/29/265=0A= =0A=0AAs Xen-ARM can boot Linux 3.0, it means that this hypervisor is using= =A0=0Aparavirt_ops infrastructure of kernel. I want to know that did you ex= plicitly=A0=0Aadd paravirt_ops support in kernel for ARM?=0AAs far as I kno= w paravirt_ops is an infrastructure given by Linux kernel to support=A0=0Ah= ypervisor. and=A0http://wiki.xensource.com/xenwiki/XenParavirtOps=A0tells t= hat=0Aat present paravirt_ops is available for x86_32, x86_64 and ia64 arch= itectures.=0A=0AIf this the case that you have add support of paravirt_ops = in Linux kernel for ARM=0Aarchitecture then what is the level of complexity= for adding this kind of support?=0A=0AThanks ---1134493521-1584150673-1344577500=:65644 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
I came to know from Xen-ARM wiki and other related pages that A= RM  port is based on 

As Xen-ARM can boot Linux 3.0, it means tha= t this hypervisor is using 
paravirt_ops infrastruct= ure of kernel. I want to know that did you explicitly 
As far = as I know paravirt_ops is an infrastructure given by Linux kernel to suppor= t 
at present paravirt_ops is available for x86_32, x86_6= 4 and ia64 architectures.
If this the case that you ha= ve add support of paravirt_ops in Linux kernel for ARM
architecture then what is the level of compl= exity for adding this kind of support?

Thanks=
---1134493521-1584150673-1344577500=:65644-- --===============3096104876794683830== 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 --===============3096104876794683830==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCW-00068E-Cc; Fri, 03 May 2013 12:35:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Szi1w-0005yq-8a for xen-arm@lists.xensource.com; Fri, 10 Aug 2012 05:45:04 +0000 Received: from [85.158.138.51:32191] by server-10.bemta-3.messagelabs.com id 00/D9-07905-FDF94205; Fri, 10 Aug 2012 05:45:03 +0000 X-Env-Sender: maheen_butt26@yahoo.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1344577501!8851318!1 X-Originating-IP: [98.138.91.43] X-SpamReason: No, hits=0.7 required=7.0 tests=FROM_HAS_ULINE_NUMS, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10667 invoked from network); 10 Aug 2012 05:45:02 -0000 Received: from nm29-vm0.bullet.mail.ne1.yahoo.com (HELO nm29-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.43) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Aug 2012 05:45:02 -0000 Received: from [98.138.90.48] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 05:45:00 -0000 Received: from [98.138.88.235] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 05:45:00 -0000 Received: from [127.0.0.1] by omp1035.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 05:45:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 496782.94234.bm@omp1035.mail.ne1.yahoo.com Received: (qmail 78992 invoked by uid 60001); 10 Aug 2012 05:45:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1344577500; bh=oTlcfSkjalOgdVeIJPHD4JkBvtRE89Np8TvCgyMw9nk=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=myHyh+sJMmyau7t+d7DwqnDyl9RA9eLw9zHTHdinWotroaiaPyjxdYilZKD1fO0F6OEE0FrRo0smL0QmRHabsoTAb5IuGvUZmxbO7bIoZjUalpViU1cjo+KMJ914LzIrAT0gUGCYW5PTT7RYxti851WKTInznRG/MFRtC2rjc88= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=VynNME7JCbO+QJxWGzbQpLXuzSoSqtHzaq9tR2RxWchqvdwcODxF5qERrLUJOzgWC8fW376ViJb0czRHs74RIALoOoooj1Sx4l9kAKwUl7fOcP2FuzwIbOkdruSdzn7glIhlddjolmZLCcSgt3OynZ0ODxAZYSsJx2oug3ZIOwE=; X-YMail-OSG: NbZ5N34VM1n_vIyuKil_L.L2iVck1z6qFNsg1SptcH49tXQ nblt6oFClHjT0sqdgPorB3UfDS.KLvj46hlKrraGvcpsz4WENa01gDxO1Iob F30dlvIZff1l68gOSwoeLfWTi2Kq5rj5pkpSzgVlJghkfNhcnSrgaIksLWQL nrIa1lRbDhzoFSpBJKhCBsi.wSdn_aWl4e.kqBSQmai9lqQsusdJ4mY38ux2 Fd3.e2xTHTafmcqcKMdV9OQKhVqyNI86QKlD87XXr9p5XDBMo5PdkMN1XnKC RePlz1KnQmZVAZu3HPLV_uh8mZVgxrpnGJPPTCZidd8cmqBFtE.eqlDbhXWB bwgo7mS6ZhDTH.JfRzxYZMZACxFrtFfPWVK49axo3sKeNBFkAzKA_LhVZoOC 1xyIkoVAKzwKiGayG4Mc5GPiWFdT_57wVodk0mVG.nn8EX2G7jOyVu6UHZbE GWGNAEol8Pznc.u6X_CWQfhNpoOUmkjrcwUa3yj3hNmaqwwOCcdcfDvMD972 zX5VqytzNj_6x4hpYnGddf5.NKqpLcL2gUnT7pTOL1JZXdmBoLl53Nh66Srp CNDmDIIvUMi0tJMKj7hK_pM620_dVp2OTIi866WtjGln596M_0r3MrbkI.6j Y_3A7PnQfIw-- Received: from [58.27.199.186] by web126003.mail.ne1.yahoo.com via HTTP; Thu, 09 Aug 2012 22:45:00 PDT X-Mailer: YahooMailWebService/0.8.120.356233 Message-ID: <1344577500.65644.YahooMailNeo@web126003.mail.ne1.yahoo.com> Date: Thu, 9 Aug 2012 22:45:00 -0700 (PDT) From: maheen butt To: "xen-arm@lists.xensource.com" , "sbuk.suh@samsung.com" , "keir@xen.org" , "community.manager@xen.org" MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Subject: [XenARM] Xen-ARM and paravirt_ops? X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: maheen butt List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3096104876794683830==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3096104876794683830== Content-Type: multipart/alternative; boundary="-1134493521-1584150673-1344577500=:65644" ---1134493521-1584150673-1344577500=:65644 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi,=0AI came to know from Xen-ARM wiki and other related pages that ARM =A0= port is based on=A0=0Axen-unstable and it can boot a Linux 3.0 based virtua= l machine (dom 0). for reference=0Ahttps://lkml.org/lkml/2011/11/29/265=0A= =0A=0AAs Xen-ARM can boot Linux 3.0, it means that this hypervisor is using= =A0=0Aparavirt_ops infrastructure of kernel. I want to know that did you ex= plicitly=A0=0Aadd paravirt_ops support in kernel for ARM?=0AAs far as I kno= w paravirt_ops is an infrastructure given by Linux kernel to support=A0=0Ah= ypervisor. and=A0http://wiki.xensource.com/xenwiki/XenParavirtOps=A0tells t= hat=0Aat present paravirt_ops is available for x86_32, x86_64 and ia64 arch= itectures.=0A=0AIf this the case that you have add support of paravirt_ops = in Linux kernel for ARM=0Aarchitecture then what is the level of complexity= for adding this kind of support?=0A=0AThanks ---1134493521-1584150673-1344577500=:65644 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
I came to know from Xen-ARM wiki and other related pages that A= RM  port is based on 

As Xen-ARM can boot Linux 3.0, it means tha= t this hypervisor is using 
paravirt_ops infrastruct= ure of kernel. I want to know that did you explicitly 
As far = as I know paravirt_ops is an infrastructure given by Linux kernel to suppor= t 
at present paravirt_ops is available for x86_32, x86_6= 4 and ia64 architectures.
If this the case that you ha= ve add support of paravirt_ops in Linux kernel for ARM
architecture then what is the level of compl= exity for adding this kind of support?

Thanks=
---1134493521-1584150673-1344577500=:65644-- --===============3096104876794683830== 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 --===============3096104876794683830==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-000690-PR; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfrdc-0007x8-6P for xen-arm@lists.xen.org; Tue, 04 Dec 2012 12:30:12 +0000 Received: from [193.109.254.147:47587] by server-15.bemta-14.messagelabs.com id CF/E1-12105-3DCEDB05; Tue, 04 Dec 2012 12:30:11 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1354624208!8778584!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20511 invoked from network); 4 Dec 2012 12:30:08 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-8.tower-27.messagelabs.com with SMTP; 4 Dec 2012 12:30:08 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4CU2UO006009; Tue, 4 Dec 2012 12:30:02 GMT Date: Tue, 4 Dec 2012 12:30:01 +0000 From: Will Deacon To: Rob Herring Message-ID: <20121204123001.GL23368@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50BD1F81.9080304@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Marc Zyngier , "xen-arm@lists.xen.org" , Mark Rutland , "arnd@arndb.de" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Rob, [fixing Arnd's address, as I apparently can't spell] On Mon, Dec 03, 2012 at 09:54:09PM +0000, Rob Herring wrote: > On 12/03/2012 11:52 AM, Will Deacon wrote: > > When running Linux on a para-virtualised platform (that is, one where > > the guest is aware that it is dealing with virtual devices sitting on > > things like virtio or xenbus) we require very little in the way of > > platform code and piggy-backing on top of an existing platform can > > require a lot of device emulation for very little gain. > > > > These two patches introduce mach-virt: a very simple, DT-based machine > > which can be used with kvmtool in conjunction with virtio-based devices. > > It's not hard to imagine the same machine being targetted by Xen, which > > currently emulates a minimal variant of the vexpress platform. > > > > Note that this patch series depends on the timer rework from Mark > > Rutland, posted on Friday: > > > > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/135651.html > > > > All feedback welcome. We suspect that most controversy will be around > > the name of the thing :) > > We've discussed this before at conferences. I don't know that we > concluded this wasn't needed, but it certainly leaned that direction. I too leaned that direction before I started looking at kvm in detail and, since then, I've changed my mind when it comes to para-virtualisation. The reason for this is that there is absolutely no reason to emulate some components of a real platform and then bolt virtual devices onto it once you've got enough to get it going. It leads to a right royal mess in userspace, where you have to write a load of non-reusable emulation code and it leads to churn in the kernel because you're constantly at odds with people trying to develop the platform code based on the actual hardware they have. With a virtualisation-capable ARMv7 system, all you *need* to boot SMP Debian is: - A v7 CPU with virt extensions - vGIC - architected timers *everything* else can be described using virtio devices in the device-tree, essentially allowing you to generate platforms based on the above and boot the same kernel on them. > So what has changed? You're not going to save code space because we're > building multiple platforms together. You'll save some boot time, but a > stripped down dtb with only the minimal peripherals would probably save > nearly as much time. It's really got nothing to do with code space or boot speed. What it *is* about is avoiding the tight coupling with a real platform and suffering as a result. Yes, you can strip down the DT for a real platform but you'll likely still have to emulate things like the SP804 in order to boot. That's not to mention any platform-specific system register interfaces which are required early on. We can't even re-use the socfpga code (which is incredibly minimal) without emulating the dw_apb_timer. > However, I do have concerns with using VExpress as > the guest. For example, you can't support a non-PAE guest with 4GB of > RAM on VExpress (maybe if the vexpress code gets all memory map info > from DT). Yes, vexpress is even less suitable for this. > Is this really complete? Will we need reset, poweroff, hotplug, and > suspend/resume support for example? Unlike most initial platform > submissions which are minimal, I think seeing full support would be > useful here. Then we can better gauge how much we are really saving. The code is complete in the sense that you can boot an SMP guest running Debian with console, network, block etc. etc. but you're right to point out the absence of power-management support. However, power-management in KVM guests is a *much* larger problem and not one that has been solved adequately as of yet. There are suggestions that it should be handled entirely in firmware, with the guest making smc calls to request power-management operations but this is yet to materialise and, as such, we can't yet use it here. We could look at building a virtio-based power controller but that's going to come up too late for SMP booting (although will give us hotplug, reset etc). Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCX-00068T-Ej; Fri, 03 May 2013 12:35:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfaCK-000418-UG for xen-arm@lists.xen.org; Mon, 03 Dec 2012 17:52:53 +0000 Received: from [85.158.143.99:18619] by server-2.bemta-4.messagelabs.com id 04/3C-28922-4F6ECB05; Mon, 03 Dec 2012 17:52:52 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1354557171!18244075!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15847 invoked from network); 3 Dec 2012 17:52:51 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-14.tower-216.messagelabs.com with SMTP; 3 Dec 2012 17:52:51 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB3Hqh53002347; Mon, 3 Dec 2012 17:52:43 GMT Received: by mudshark.cambridge.arm.com (Postfix, from userid 1000) id 45D2BC0336; Mon, 3 Dec 2012 17:52:42 +0000 (GMT) From: Will Deacon To: linux-arm-kernel@lists.infradead.org Date: Mon, 3 Dec 2012 17:52:39 +0000 Message-Id: <1354557160-20144-2-git-send-email-will.deacon@arm.com> X-Mailer: git-send-email 1.8.0 In-Reply-To: <1354557160-20144-1-git-send-email-will.deacon@arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, Will Deacon , arnd@arnd.de Subject: [XenARM] [RFC PATCH 1/2] ARM: Dummy Virtual Machine platform support 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: , MIME-Version: 1.0 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 From: Marc Zyngier Add support for the smallest, dumbest possible platform, to be used as a guest for KVM or other hypervisors. It only mandates a GIC and architected timers. Fits nicely with a multiplatform zImage. Uses very little silicon area. Signed-off-by: Marc Zyngier Signed-off-by: Will Deacon --- arch/arm/Kconfig | 2 ++ arch/arm/Makefile | 1 + arch/arm/mach-virt/Kconfig | 9 +++++++ arch/arm/mach-virt/Makefile | 5 ++++ arch/arm/mach-virt/virt.c | 65 +++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 82 insertions(+) create mode 100644 arch/arm/mach-virt/Kconfig create mode 100644 arch/arm/mach-virt/Makefile create mode 100644 arch/arm/mach-virt/virt.c diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig index 781725e..ba0dca7 100644 --- a/arch/arm/Kconfig +++ b/arch/arm/Kconfig @@ -1126,6 +1126,8 @@ source "arch/arm/mach-versatile/Kconfig" source "arch/arm/mach-vexpress/Kconfig" source "arch/arm/plat-versatile/Kconfig" +source "arch/arm/mach-virt/Kconfig" + source "arch/arm/mach-w90x900/Kconfig" # Definitions to make life easier diff --git a/arch/arm/Makefile b/arch/arm/Makefile index 5f914fc..e8232ad 100644 --- a/arch/arm/Makefile +++ b/arch/arm/Makefile @@ -192,6 +192,7 @@ machine-$(CONFIG_ARCH_SOCFPGA) += socfpga machine-$(CONFIG_ARCH_SPEAR13XX) += spear13xx machine-$(CONFIG_ARCH_SPEAR3XX) += spear3xx machine-$(CONFIG_MACH_SPEAR600) += spear6xx +machine-$(CONFIG_ARCH_VIRT) += virt machine-$(CONFIG_ARCH_ZYNQ) += zynq # Platform directory name. This list is sorted alphanumerically diff --git a/arch/arm/mach-virt/Kconfig b/arch/arm/mach-virt/Kconfig new file mode 100644 index 0000000..a568a2a --- /dev/null +++ b/arch/arm/mach-virt/Kconfig @@ -0,0 +1,9 @@ +config ARCH_VIRT + bool "Dummy Virtual Machine" if ARCH_MULTI_V7 + select ARCH_WANT_OPTIONAL_GPIOLIB + select ARM_GIC + select ARM_ARCH_TIMER + select HAVE_SMP + select CPU_V7 + select SPARSE_IRQ + select USE_OF diff --git a/arch/arm/mach-virt/Makefile b/arch/arm/mach-virt/Makefile new file mode 100644 index 0000000..7ddbfa6 --- /dev/null +++ b/arch/arm/mach-virt/Makefile @@ -0,0 +1,5 @@ +# +# Makefile for the linux kernel. +# + +obj-y := virt.o diff --git a/arch/arm/mach-virt/virt.c b/arch/arm/mach-virt/virt.c new file mode 100644 index 0000000..174b9da --- /dev/null +++ b/arch/arm/mach-virt/virt.c @@ -0,0 +1,65 @@ +/* + * Dummy Virtual Machine - does what it says on the tin. + * + * Copyright (C) 2012 ARM Ltd + * Authors: Will Deacon , + * Marc Zyngier + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program. If not, see . + */ + +#include +#include + +#include +#include +#include +#include + +const static struct of_device_id irq_match[] = { + { .compatible = "arm,cortex-a15-gic", .data = gic_of_init, }, + {} +}; + +static void __init gic_init_irq(void) +{ + of_irq_init(irq_match); +} + +static void __init virt_init(void) +{ + of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL); +} + +static void __init virt_timer_init(void) +{ + WARN_ON(arch_timer_of_register() != 0); + WARN_ON(arch_timer_sched_clock_init() != 0); +} + +static const char *virt_dt_match[] = { + "linux,dummy-virt", + NULL +}; + +static struct sys_timer virt_timer = { + .init = virt_timer_init, +}; + +DT_MACHINE_START(VIRT, "Dummy Virtual Machine") + .init_irq = gic_init_irq, + .handle_irq = gic_handle_irq, + .timer = &virt_timer, + .init_machine = virt_init, + .dt_compat = virt_dt_match, +MACHINE_END -- 1.8.0 _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006EM-Ob; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGZz-0005Ej-QQ for xen-arm@lists.xen.org; Wed, 05 Dec 2012 15:08:08 +0000 Received: from [85.158.139.211:15888] by server-9.bemta-5.messagelabs.com id 82/95-29295-6536FB05; Wed, 05 Dec 2012 15:08:06 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1354720066!19148548!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32337 invoked from network); 5 Dec 2012 15:07:48 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-14.tower-206.messagelabs.com with SMTP; 5 Dec 2012 15:07:48 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB5F7XUO006188; Wed, 5 Dec 2012 15:07:33 GMT Date: Wed, 5 Dec 2012 15:07:32 +0000 From: Will Deacon To: Catalin Marinas Message-ID: <20121205150732.GJ22385@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Nicolas Pitre , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Wed, Dec 05, 2012 at 02:52:57PM +0000, Catalin Marinas wrote: > On 4 December 2012 18:14, Will Deacon wrote: > > Well, this depends on the guest taking an undefined instruction exception on > > the smc, then deciding to issue an hvc instead and *then* having the > > hypervisor somehow translate that into a PSCI invocation. It could work, but > > it sounds easy to mess up and relies on the PSCI firmware co-existing with > > things like kvm. > > We can have enable-method DT entries independent of the SoC and one of > them can be psci-hvc. As soon as the support is there in the upper layers, we can do that. > Just for clarification, AArch32 with virtualisation mandates the > security extensions, so the SMC can be trapped. On AArch64 it is a bit > tricky since the presence of EL3 is not mandate, in which case SMC > would undef (don't as why ;). That's where we can have different > enable methods specified via the DT. Not entirely true: only ARMv7 mandates the security extensions in this manner. You can still have ARMv8 CPUs running AArch32 code without the security extensions. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069e-DP; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfvdG-0006ht-Fu for xen-arm@lists.xen.org; Tue, 04 Dec 2012 16:46:06 +0000 Received: from [193.109.254.147:53682] by server-3.bemta-14.messagelabs.com id 09/BC-01317-DC82EB05; Tue, 04 Dec 2012 16:46:05 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1354639563!1722852!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=2.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1459 invoked from network); 4 Dec 2012 16:46:04 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2012 16:46:04 -0000 Received: by mail-ob0-f173.google.com with SMTP id xn12so4732940obc.32 for ; Tue, 04 Dec 2012 08:46:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=GbHENo4n6omIyynTU/ssEIwJtCrZnw653XDus6kx1/Y=; b=kEuR6PqIUNAIQUicWHHT/DwNsNvnC+iF7cWhMGPnVlxt1WEhI5dKDCjJRoncarOyMy iW/+m+Rmqe4k172W6Gy4u3lRapW4SRLpbIU5lyniM4+nEalaxgsP/9UWvIqrmlPQX5HM WCjr9MW7vcFf6605S/2Jk3xpq1sFB0O9QGwHO3/0JLH8Kvhvtuy/9C1fS3FW1TCfMcOn BEdPajG0ru4h9upIhPxotCMMJxwRQdI/em8+2sUnWlVqypHfBjSpL3dzvHo9dIS1tSpB rEUG+keU01w4p2iNTQ891tgKsM8vqYgxmLa8aoagLdtPDPZXpCMUXafoWMhqow/mQWUW Vt1A== Received: by 10.60.31.68 with SMTP id y4mr12232592oeh.121.1354639563415; Tue, 04 Dec 2012 08:46:03 -0800 (PST) Received: from [10.10.10.90] ([173.226.190.126]) by mx.google.com with ESMTPS id hg8sm1165756obb.19.2012.12.04.08.45.59 (version=SSLv3 cipher=OTHER); Tue, 04 Dec 2012 08:46:02 -0800 (PST) Message-ID: <50BE28C6.2010403@gmail.com> Date: Tue, 04 Dec 2012 10:45:58 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> In-Reply-To: <20121204161113.GT23368@mudshark.cambridge.arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 12/04/2012 10:11 AM, Will Deacon wrote: > On Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: >> On Tue, Dec 04, 2012 at 01:40:10PM +0000, Will Deacon wrote: >>> On Tue, Dec 04, 2012 at 01:33:26PM +0000, Russell King - ARM Linux wrote: >>>> The memory that these 'offline' CPUs is executing then gets overwritten, >>>> and that's game over for those CPUs. >>> >>> That's not strictly true. The device-tree passed to the kernel should have a >>> /memreserve/ entry for the SMP pen to avoid exactly this scenario. In real >>> hardware, this still sucks because you have spinning CPUs burning up power >>> but that's not such a problem with a virtual platform. >> >> Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec >> into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which >> will be located at 32K into the RAM. The v3.7 kernel will also want to >> occupy the same place. At some point you have to overwrite the v3.6 >> kernel with the v3.7 kernel image. > > If the 3.6 kernel didn't bring those CPUs online, they will sit in the > bootloader pen (out of the way of the kernel image) rather than the kernel > pen so I don't think there will be a problem. > > The problem you're describing actually happens when the 3.6 kernel onlines > all of the CPUs, because now it has no way to hotplug them off safely. This > is also an issue with non-virtualised hardware but we could solve it for the > virtual platform by having a para-virtualised device for doing CPU hotplug. > >> That happens _before_ the DT has been parsed, so any memreserve stuff >> will be ignored. And it's at that point that your "offline" secondary >> CPUs will have their instructions overwritten. >> >> That's fine if the pen ends up being at the same place but that's not >> something we guarantee. > > Having CPUs in limbo between the bootloader the being online in the kernel > is something we should just avoid. Isn't that pen __init anyway? Aren't we mixing 2 pens here? You must have some simple bootloader containing vector table and a pen that the dtb points to, right? The pen you have in the kernel is only needed when hotplug only does a wfi. As you don't yet support hotplug, then you can drop all the kernel pen code. If there is no way to reset the core, then couldn't the hotplug code tear down the cpu setup and just jump back to 0x0 which then returns to the bootloader's pen? Rob _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006BC-Ch; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfwp2-0001y0-QE for xen-arm@lists.xen.org; Tue, 04 Dec 2012 18:02:21 +0000 Received: from [85.158.137.99:55843] by server-11.bemta-3.messagelabs.com id 5E/D9-19361-7AA3EB05; Tue, 04 Dec 2012 18:02:15 +0000 X-Env-Sender: nico@fluxnic.net X-Msg-Ref: server-13.tower-217.messagelabs.com!1354644134!17924200!1 X-Originating-IP: [24.201.245.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n,sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9733 invoked from network); 4 Dec 2012 18:02:14 -0000 Received: from relais.videotron.ca (HELO relais.videotron.ca) (24.201.245.36) by server-13.tower-217.messagelabs.com with SMTP; 4 Dec 2012 18:02:14 -0000 MIME-version: 1.0 Received: from xanadu.home ([24.202.213.203]) by VL-VM-MR004.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MEI003MPQ3PRZN0@VL-VM-MR004.ip.videotron.ca> for xen-arm@lists.xen.org; Tue, 04 Dec 2012 13:02:14 -0500 (EST) Date: Tue, 04 Dec 2012 13:02:13 -0500 (EST) From: Nicolas Pitre To: Will Deacon In-reply-to: <20121204171129.GE5314@mudshark.cambridge.arm.com> Message-id: References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Tue, 4 Dec 2012, Will Deacon wrote: > Hi Nicolas, > > On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: > > on the topic of a para-virtualised machine, I think that it should > > simply implement the PSCI calls to bring up CPUs _without_ any holding > > pen nor spinning tables. You issue the appropriate PSCI call with the > > physical address for secondary_startup() as argument and you're done. > > The host intercepts that call and free a new CPU instance in response. > > That's all. > > I'd be happy to go with this suggestion if it wasn't for one thing: > platforms that do not implement a secure mode. For these platforms, smc will > be an undefined instruction at the exception level where it is executed and > therefore cannot be trapped by the hypervisor. Really? I thought the hypervisor could virtualize SMC calls. Or is that considered a security hazard? I don't remember all the PSCI spec details, but I think there was some provision for this case i.e. the SMC call could be a HYP call instead. And if that's not in the spec, then it probably should be added and implemented as if it was. > If that situation requires a pen, I see no benefit from having two boot > schemes where one of them would work in every case. We always have the choice between several schemes in device drivers for example, depending on the hardware generation. Yet we always implement the better scheme for the newest hardware for performance reasons, even if an older one could work in all cases. A holding pen is a rather stupid scheme. Please let's try to do without it if possible. Nicolas _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069j-Hw; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfvr0-0007FF-S1 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:00:19 +0000 Received: from [85.158.137.99:48418] by server-13.bemta-3.messagelabs.com id AC/25-24887-D1C2EB05; Tue, 04 Dec 2012 17:00:13 +0000 X-Env-Sender: nico@fluxnic.net X-Msg-Ref: server-10.tower-217.messagelabs.com!1354640408!17242129!1 X-Originating-IP: [24.201.245.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n,sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30785 invoked from network); 4 Dec 2012 17:00:09 -0000 Received: from relais.videotron.ca (HELO relais.videotron.ca) (24.201.245.36) by server-10.tower-217.messagelabs.com with SMTP; 4 Dec 2012 17:00:09 -0000 MIME-version: 1.0 Received: from xanadu.home ([24.202.213.203]) by VL-VM-MR003.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MEI00G1LN87DIL0@VL-VM-MR003.ip.videotron.ca> for xen-arm@lists.xen.org; Tue, 04 Dec 2012 12:00:08 -0500 (EST) Date: Tue, 04 Dec 2012 12:00:07 -0500 (EST) From: Nicolas Pitre To: Rob Herring In-reply-to: <50BE04C6.4070602@gmail.com> Message-id: References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Will Deacon , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Tue, 4 Dec 2012, Rob Herring wrote: > That to me is highlighting where we need to do more work on DT driving > the initialization. The platforms are still aware of what kind of timers > and interrupt controllers are present. They should not be. There's work > in progress for both of those. > > Lorenzo's DT MPIDR patches should trim down smp code some. The DT spin > table code could probably be common. I think I could use it on highbank > as well. If we decide the pen code stays, then it should be common > rather than creating yet another copy. I don't want to rain on the "everything should be common" parade here. However, for the best part of last year I've been working on kernel support for big.LITTLE systems, and the handling of CPU hotplug (including SMP secondary boot) is far from being a trivial task. Managing the simple bringing up or down of a CPU in such an environment required hundreds of new lines of code. That is far from a simple holding pen or spinning table to say the least. [ For the curious, I'll post this code here soon for review. ] So my point of view is: if you do not need a holding pen because you can hold individual CPUs in reset, then don't. Many platforms with support in the kernel can do that, yet they copied the holding pen code just because it is there. And that is total crap. on the topic of a para-virtualised machine, I think that it should simply implement the PSCI calls to bring up CPUs _without_ any holding pen nor spinning tables. You issue the appropriate PSCI call with the physical address for secondary_startup() as argument and you're done. The host intercepts that call and free a new CPU instance in response. That's all. Nicolas _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006Ef-S8; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGcT-0005FZ-1K for xen-arm@lists.xen.org; Wed, 05 Dec 2012 15:10:41 +0000 Received: from [85.158.143.35:59213] by server-3.bemta-4.messagelabs.com id 1A/02-06841-0F36FB05; Wed, 05 Dec 2012 15:10:40 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1354720239!16204881!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29819 invoked from network); 5 Dec 2012 15:10:39 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-6.tower-21.messagelabs.com with SMTP; 5 Dec 2012 15:10:39 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB5FAUUO006221; Wed, 5 Dec 2012 15:10:30 GMT Date: Wed, 5 Dec 2012 15:10:29 +0000 From: Will Deacon To: Nicolas Pitre Message-ID: <20121205151029.GK22385@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Catalin Marinas , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Wed, Dec 05, 2012 at 03:07:05PM +0000, Nicolas Pitre wrote: > On Wed, 5 Dec 2012, Catalin Marinas wrote: > > On 4 December 2012 18:14, Will Deacon wrote: > > > Well, this depends on the guest taking an undefined instruction exception on > > > the smc, then deciding to issue an hvc instead and *then* having the > > > hypervisor somehow translate that into a PSCI invocation. It could work, but > > > it sounds easy to mess up and relies on the PSCI firmware co-existing with > > > things like kvm. > > > > We can have enable-method DT entries independent of the SoC and one of > > them can be psci-hvc. > > > > Just for clarification, AArch32 with virtualisation mandates the > > security extensions, so the SMC can be trapped. > > Good. Therefore this one is settled. Looks we replied at the same time! Please see my other mail... Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006B1-93; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfwKm-0008Q7-U6 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:31:05 +0000 Received: from [193.109.254.147:40090] by server-12.bemta-14.messagelabs.com id EF/5E-00510-8533EB05; Tue, 04 Dec 2012 17:31:04 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1354642257!8925636!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 489 invoked from network); 4 Dec 2012 17:30:57 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-2.tower-27.messagelabs.com with SMTP; 4 Dec 2012 17:30:57 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4HUkUO012225; Tue, 4 Dec 2012 17:30:46 GMT Date: Tue, 4 Dec 2012 17:30:45 +0000 From: Will Deacon To: Marc Zyngier Message-ID: <20121204173045.GI5314@mudshark.cambridge.arm.com> References: <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> <20121204171628.GF5314@mudshark.cambridge.arm.com> <50BE31E9.3040404@arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50BE31E9.3040404@arm.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 05:24:57PM +0000, Marc Zyngier wrote: > On 04/12/12 17:16, Will Deacon wrote: > > On Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: > >> Aren't we mixing 2 pens here? You must have some simple bootloader > >> containing vector table and a pen that the dtb points to, right? The pen > >> you have in the kernel is only needed when hotplug only does a wfi. As > >> you don't yet support hotplug, then you can drop all the kernel pen code. > > > > Yes, both qemu and kvmtool have bootloader pens outside of the kernel but > > since wfi is not trapped by kvm, the secondaries can be released early due > > to a spurious wakeup so we need the second pen. > > Actually, KVM traps WFI and puts the vcpu thread on a wait queue (we are > actually giving more guaranties than the architecture offers here). Ok, if we can rely on this behaviour in the future this sounds promising. Can somebody comment from the Xen side of things please? > We should be able to remove the loop and rely on WFI. Yes, we should be able to remove the kernel-side loop. We still won't have hotplug and friends, but that can come later because there's a discussion around PSCI vs virtual power controller to be had there. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-00068v-M5; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfdzJ-0002Yo-TL for xen-arm@lists.xen.org; Mon, 03 Dec 2012 21:55:42 +0000 Received: from [85.158.143.99:3894] by server-2.bemta-4.messagelabs.com id A1/76-28922-DDF1DB05; Mon, 03 Dec 2012 21:55:41 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1354571738!18130805!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=2.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3576 invoked from network); 3 Dec 2012 21:55:39 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Dec 2012 21:55:39 -0000 Received: by mail-oa0-f45.google.com with SMTP id i18so3890308oag.32 for ; Mon, 03 Dec 2012 13:55:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=vVB3e0BZ6VCSeV7RRR6+t4jY7LgV0BoytZ0Kr7VY8Nw=; b=lPmaOL4YzoQp80gN/HspDc3nzhbQYf9t7mSLe5tftEUX2dPiAciybkPV1g7n5Kx8Hf 2fsRWyFCkufWlCNKBKDLHLaJ79/2oeM25h/TNj+USoR8IvwA4noGiBYZQH4x5QRUmYe0 HvPHzt1FMDi2RW8TM/xOqRgY33+c0VHiZAmOTM6dkJLaLFyytzubm0Pri7kuUJ2yMYqi dad3F2eI4ZxXBKMKdiObLpUtpocAykmOKOl7YQeZJ36B4hMbOI88kHYxTkXM6pvmZMu8 h2+5S1PrWwA6aFn8sB8RFx50f9AG2gtAaFtFJbWPK91MqTrKxBtJzdtrHaV3eS9Dco7+ 40nA== Received: by 10.182.18.196 with SMTP id y4mr5784627obd.52.1354571738361; Mon, 03 Dec 2012 13:55:38 -0800 (PST) Received: from [10.10.10.90] ([173.226.190.126]) by mx.google.com with ESMTPS id f7sm13037305oef.8.2012.12.03.13.55.36 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 13:55:36 -0800 (PST) Message-ID: <50BD1FD7.9040000@gmail.com> Date: Mon, 03 Dec 2012 15:55:35 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> In-Reply-To: <1354557160-20144-3-git-send-email-will.deacon@arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, arnd@arnd.de, linux-arm-kernel@lists.infradead.org Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 12/03/2012 11:52 AM, Will Deacon wrote: > From: Marc Zyngier > > This patch adds support for SMP to mach-virt. > > Signed-off-by: Marc Zyngier > Signed-off-by: Will Deacon > --- > arch/arm/mach-virt/Makefile | 1 + > arch/arm/mach-virt/headsmp.S | 38 ++++++++ > arch/arm/mach-virt/platsmp.c | 205 +++++++++++++++++++++++++++++++++++++++++++ > arch/arm/mach-virt/virt.c | 6 ++ > 4 files changed, 250 insertions(+) > create mode 100644 arch/arm/mach-virt/headsmp.S > create mode 100644 arch/arm/mach-virt/platsmp.c > > diff --git a/arch/arm/mach-virt/Makefile b/arch/arm/mach-virt/Makefile > index 7ddbfa6..9ce8a28 100644 > --- a/arch/arm/mach-virt/Makefile > +++ b/arch/arm/mach-virt/Makefile > @@ -3,3 +3,4 @@ > # > > obj-y := virt.o > +obj-$(CONFIG_SMP) += platsmp.o headsmp.o > diff --git a/arch/arm/mach-virt/headsmp.S b/arch/arm/mach-virt/headsmp.S > new file mode 100644 > index 0000000..e27afb0 > --- /dev/null > +++ b/arch/arm/mach-virt/headsmp.S > @@ -0,0 +1,38 @@ > +/* > + * Copyright (c) 2012 ARM Limited > + * All Rights Reserved > + * > + * This program is free software; you can redistribute it and/or modify > + * it under the terms of the GNU General Public License version 2 as > + * published by the Free Software Foundation. > + */ > +#include > +#include > + > + __INIT > + > +/* > + * This provides a "holding pen" into which all secondary cores are held > + * until we're ready for them to initialise. > + */ > +ENTRY(virt_secondary_startup) > + mrc p15, 0, r0, c0, c0, 5 > + and r0, r0, #15 > + adr r4, 1f > + ldmia r4, {r5, r6} > + sub r4, r4, r5 > + add r6, r6, r4 > +pen: ldr r7, [r6] > + cmp r7, r0 > + bne pen Why is the pen is needed? It should only be needed for hotplug on systems that can't reset their cores. I'd hope you could design good virtual h/w. > + > + /* > + * we've been released from the holding pen: secondary_stack > + * should now contain the SVC stack for this core > + */ > + b secondary_startup > + > + .align > +1: .long . > + .long pen_release > +ENDPROC(virt_secondary_startup) > diff --git a/arch/arm/mach-virt/platsmp.c b/arch/arm/mach-virt/platsmp.c > new file mode 100644 > index 0000000..fe02f51 > --- /dev/null > +++ b/arch/arm/mach-virt/platsmp.c > @@ -0,0 +1,205 @@ > +/* > + * Dummy Virtual Machine - does what it says on the tin. > + * > + * SMP operations, shamelessly stolen from: > + * arch/arm64/kernel/smp.c > + * > + * Copyright (C) 2012 ARM Ltd > + * Author: Catalin Marinas > + * Author: Will Deacon > + * Author: Marc Zyngier > + * > + * This program is free software; you can redistribute it and/or modify > + * it under the terms of the GNU General Public License version 2 as > + * published by the Free Software Foundation. > + * > + * This program is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > + * GNU General Public License for more details. > + * > + * You should have received a copy of the GNU General Public License > + * along with this program. If not, see . > + */ > + > +#include > +#include > +#include > +#include > +#include > +#include > + > +#include > +#include > +#include > + > +extern void virt_secondary_startup(void); > + > +static DEFINE_RAW_SPINLOCK(boot_lock); > +static phys_addr_t cpu_release_addr[NR_CPUS]; > + > +/* > + * Write secondary_holding_pen_release in a way that is guaranteed to be > + * visible to all observers, irrespective of whether they're taking part > + * in coherency or not. This is necessary for the hotplug code to work > + * reliably. > + */ > +static void __cpuinit write_pen_release(int val) > +{ > + void *start = (void *)&pen_release; > + unsigned long size = sizeof(pen_release); > + > + pen_release = val; > + smp_wmb(); > + __cpuc_flush_dcache_area(start, size); > + outer_clean_range(__pa(&pen_release), __pa(&pen_release + 1)); > +} > + > +/* > + * Enumerate the possible CPU set from the device tree. > + */ > +static void __init virt_smp_init_cpus(void) > +{ > + const char *enable_method; > + struct device_node *dn = NULL; > + int cpu = 0; > + u32 release_addr; > + > + while ((dn = of_find_node_by_type(dn, "cpu"))) { > + if (cpu >= NR_CPUS) > + goto next; > + > + /* > + * We currently support only the "spin-table" enable-method. > + */ > + enable_method = of_get_property(dn, "enable-method", NULL); > + if (!enable_method || strcmp(enable_method, "spin-table")) { Are these documented? > + pr_err("CPU %d: missing or invalid enable-method property: %s\n", > + cpu, enable_method); > + goto next; > + } > + > + /* > + * Determine the address from which the CPU is polling. > + */ > + if (of_property_read_u32(dn, "cpu-release-addr", &release_addr)) { > + pr_err("CPU %d: missing or invalid cpu-release-addr property\n", > + cpu); > + goto next; > + } > + > + cpu_release_addr[cpu] = release_addr; > + set_cpu_possible(cpu, true); > +next: > + cpu++; > + } > + > + /* sanity check */ > + if (cpu > NR_CPUS) > + pr_warning("no. of cores (%d) greater than configured maximum of %d - clipping\n", > + cpu, NR_CPUS); > + > + set_smp_cross_call(gic_raise_softirq); > +} > + > +static void __init virt_smp_prepare_cpus(unsigned int max_cpus) > +{ > + int cpu; > + void **release_addr; > + unsigned int ncores = num_possible_cpus(); > + > + /* > + * are we trying to boot more cores than exist? > + */ > + if (max_cpus > ncores) > + max_cpus = ncores; > + > + /* > + * Initialise the present map (which describes the set of CPUs > + * actually populated at the present time) and release the > + * secondaries from the bootloader. > + */ > + for_each_possible_cpu(cpu) { > + if (max_cpus == 0) > + break; > + > + if (!cpu_release_addr[cpu]) > + continue; > + > + release_addr = __va(cpu_release_addr[cpu]); > + release_addr[0] = (void *)__pa(virt_secondary_startup); > + smp_wmb(); > + __cpuc_flush_dcache_area(release_addr, sizeof(release_addr[0])); > + outer_clean_range(__pa(release_addr), __pa(release_addr+1)); > + > + set_cpu_present(cpu, true); > + max_cpus--; > + } > +} > + > +static int __cpuinit virt_boot_secondary(unsigned int cpu, > + struct task_struct *idle) > +{ > + unsigned long timeout; > + > + /* > + * Set synchronisation state between this boot processor > + * and the secondary one > + */ > + raw_spin_lock(&boot_lock); > + > + /* > + * Update the pen release flag. > + */ > + write_pen_release(cpu); > + > + /* > + * Send the secondary CPU a soft interrupt, causing the > + * secondaries to read pen_release. > + */ > + gic_raise_softirq(cpumask_of(cpu), 0); > + > + timeout = jiffies + (1 * HZ); > + while (time_before(jiffies, timeout)) { > + if (pen_release == -1UL) > + break; > + udelay(10); > + } > + > + /* > + * Now the secondary core is starting up let it run its > + * calibrations, then wait for it to finish > + */ > + raw_spin_unlock(&boot_lock); > + > + return pen_release != -1 ? -ENOSYS : 0; > +} > + > +static void __cpuinit virt_secondary_init(unsigned int cpu) > +{ > + /* > + * if any interrupts are already enabled for the primary > + * core (e.g. timer irq), then they will not have been enabled > + * for us: do so > + */ > + gic_secondary_init(0); > + > + /* > + * let the primary processor know we're out of the > + * pen, then head off into the C entry point > + */ > + write_pen_release(-1); > + > + /* > + * Synchronise with the boot thread. > + */ > + raw_spin_lock(&boot_lock); > + raw_spin_unlock(&boot_lock); > +} > + > +struct smp_operations __initdata virt_smp_ops = { > + .smp_init_cpus = virt_smp_init_cpus, > + .smp_prepare_cpus = virt_smp_prepare_cpus, > + .smp_secondary_init = virt_secondary_init, > + .smp_boot_secondary = virt_boot_secondary, > +}; > diff --git a/arch/arm/mach-virt/virt.c b/arch/arm/mach-virt/virt.c > index 174b9da..d764835 100644 > --- a/arch/arm/mach-virt/virt.c > +++ b/arch/arm/mach-virt/virt.c > @@ -20,6 +20,7 @@ > > #include > #include > +#include > > #include > #include > @@ -56,10 +57,15 @@ static struct sys_timer virt_timer = { > .init = virt_timer_init, > }; > > +#ifdef CONFIG_SMP > +extern struct smp_operations virt_smp_ops; > +#endif > + > DT_MACHINE_START(VIRT, "Dummy Virtual Machine") > .init_irq = gic_init_irq, > .handle_irq = gic_handle_irq, > .timer = &virt_timer, > .init_machine = virt_init, > + .smp = smp_ops(virt_smp_ops), > .dt_compat = virt_dt_match, > MACHINE_END > _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-00068k-FL; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfaCS-00046O-1C for xen-arm@lists.xen.org; Mon, 03 Dec 2012 17:53:00 +0000 Received: from [85.158.137.99:31724] by server-11.bemta-3.messagelabs.com id E1/81-19361-BF6ECB05; Mon, 03 Dec 2012 17:52:59 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1354557175!17417955!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22108 invoked from network); 3 Dec 2012 17:52:55 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-2.tower-217.messagelabs.com with SMTP; 3 Dec 2012 17:52:55 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB3Hqh53002348; Mon, 3 Dec 2012 17:52:43 GMT Received: by mudshark.cambridge.arm.com (Postfix, from userid 1000) id 77ABDC2A9C; Mon, 3 Dec 2012 17:52:42 +0000 (GMT) From: Will Deacon To: linux-arm-kernel@lists.infradead.org Date: Mon, 3 Dec 2012 17:52:40 +0000 Message-Id: <1354557160-20144-3-git-send-email-will.deacon@arm.com> X-Mailer: git-send-email 1.8.0 In-Reply-To: <1354557160-20144-1-git-send-email-will.deacon@arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, Will Deacon , arnd@arnd.de Subject: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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: , MIME-Version: 1.0 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 From: Marc Zyngier This patch adds support for SMP to mach-virt. Signed-off-by: Marc Zyngier Signed-off-by: Will Deacon --- arch/arm/mach-virt/Makefile | 1 + arch/arm/mach-virt/headsmp.S | 38 ++++++++ arch/arm/mach-virt/platsmp.c | 205 +++++++++++++++++++++++++++++++++++++++++++ arch/arm/mach-virt/virt.c | 6 ++ 4 files changed, 250 insertions(+) create mode 100644 arch/arm/mach-virt/headsmp.S create mode 100644 arch/arm/mach-virt/platsmp.c diff --git a/arch/arm/mach-virt/Makefile b/arch/arm/mach-virt/Makefile index 7ddbfa6..9ce8a28 100644 --- a/arch/arm/mach-virt/Makefile +++ b/arch/arm/mach-virt/Makefile @@ -3,3 +3,4 @@ # obj-y := virt.o +obj-$(CONFIG_SMP) += platsmp.o headsmp.o diff --git a/arch/arm/mach-virt/headsmp.S b/arch/arm/mach-virt/headsmp.S new file mode 100644 index 0000000..e27afb0 --- /dev/null +++ b/arch/arm/mach-virt/headsmp.S @@ -0,0 +1,38 @@ +/* + * Copyright (c) 2012 ARM Limited + * All Rights Reserved + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ +#include +#include + + __INIT + +/* + * This provides a "holding pen" into which all secondary cores are held + * until we're ready for them to initialise. + */ +ENTRY(virt_secondary_startup) + mrc p15, 0, r0, c0, c0, 5 + and r0, r0, #15 + adr r4, 1f + ldmia r4, {r5, r6} + sub r4, r4, r5 + add r6, r6, r4 +pen: ldr r7, [r6] + cmp r7, r0 + bne pen + + /* + * we've been released from the holding pen: secondary_stack + * should now contain the SVC stack for this core + */ + b secondary_startup + + .align +1: .long . + .long pen_release +ENDPROC(virt_secondary_startup) diff --git a/arch/arm/mach-virt/platsmp.c b/arch/arm/mach-virt/platsmp.c new file mode 100644 index 0000000..fe02f51 --- /dev/null +++ b/arch/arm/mach-virt/platsmp.c @@ -0,0 +1,205 @@ +/* + * Dummy Virtual Machine - does what it says on the tin. + * + * SMP operations, shamelessly stolen from: + * arch/arm64/kernel/smp.c + * + * Copyright (C) 2012 ARM Ltd + * Author: Catalin Marinas + * Author: Will Deacon + * Author: Marc Zyngier + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program. If not, see . + */ + +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +extern void virt_secondary_startup(void); + +static DEFINE_RAW_SPINLOCK(boot_lock); +static phys_addr_t cpu_release_addr[NR_CPUS]; + +/* + * Write secondary_holding_pen_release in a way that is guaranteed to be + * visible to all observers, irrespective of whether they're taking part + * in coherency or not. This is necessary for the hotplug code to work + * reliably. + */ +static void __cpuinit write_pen_release(int val) +{ + void *start = (void *)&pen_release; + unsigned long size = sizeof(pen_release); + + pen_release = val; + smp_wmb(); + __cpuc_flush_dcache_area(start, size); + outer_clean_range(__pa(&pen_release), __pa(&pen_release + 1)); +} + +/* + * Enumerate the possible CPU set from the device tree. + */ +static void __init virt_smp_init_cpus(void) +{ + const char *enable_method; + struct device_node *dn = NULL; + int cpu = 0; + u32 release_addr; + + while ((dn = of_find_node_by_type(dn, "cpu"))) { + if (cpu >= NR_CPUS) + goto next; + + /* + * We currently support only the "spin-table" enable-method. + */ + enable_method = of_get_property(dn, "enable-method", NULL); + if (!enable_method || strcmp(enable_method, "spin-table")) { + pr_err("CPU %d: missing or invalid enable-method property: %s\n", + cpu, enable_method); + goto next; + } + + /* + * Determine the address from which the CPU is polling. + */ + if (of_property_read_u32(dn, "cpu-release-addr", &release_addr)) { + pr_err("CPU %d: missing or invalid cpu-release-addr property\n", + cpu); + goto next; + } + + cpu_release_addr[cpu] = release_addr; + set_cpu_possible(cpu, true); +next: + cpu++; + } + + /* sanity check */ + if (cpu > NR_CPUS) + pr_warning("no. of cores (%d) greater than configured maximum of %d - clipping\n", + cpu, NR_CPUS); + + set_smp_cross_call(gic_raise_softirq); +} + +static void __init virt_smp_prepare_cpus(unsigned int max_cpus) +{ + int cpu; + void **release_addr; + unsigned int ncores = num_possible_cpus(); + + /* + * are we trying to boot more cores than exist? + */ + if (max_cpus > ncores) + max_cpus = ncores; + + /* + * Initialise the present map (which describes the set of CPUs + * actually populated at the present time) and release the + * secondaries from the bootloader. + */ + for_each_possible_cpu(cpu) { + if (max_cpus == 0) + break; + + if (!cpu_release_addr[cpu]) + continue; + + release_addr = __va(cpu_release_addr[cpu]); + release_addr[0] = (void *)__pa(virt_secondary_startup); + smp_wmb(); + __cpuc_flush_dcache_area(release_addr, sizeof(release_addr[0])); + outer_clean_range(__pa(release_addr), __pa(release_addr+1)); + + set_cpu_present(cpu, true); + max_cpus--; + } +} + +static int __cpuinit virt_boot_secondary(unsigned int cpu, + struct task_struct *idle) +{ + unsigned long timeout; + + /* + * Set synchronisation state between this boot processor + * and the secondary one + */ + raw_spin_lock(&boot_lock); + + /* + * Update the pen release flag. + */ + write_pen_release(cpu); + + /* + * Send the secondary CPU a soft interrupt, causing the + * secondaries to read pen_release. + */ + gic_raise_softirq(cpumask_of(cpu), 0); + + timeout = jiffies + (1 * HZ); + while (time_before(jiffies, timeout)) { + if (pen_release == -1UL) + break; + udelay(10); + } + + /* + * Now the secondary core is starting up let it run its + * calibrations, then wait for it to finish + */ + raw_spin_unlock(&boot_lock); + + return pen_release != -1 ? -ENOSYS : 0; +} + +static void __cpuinit virt_secondary_init(unsigned int cpu) +{ + /* + * if any interrupts are already enabled for the primary + * core (e.g. timer irq), then they will not have been enabled + * for us: do so + */ + gic_secondary_init(0); + + /* + * let the primary processor know we're out of the + * pen, then head off into the C entry point + */ + write_pen_release(-1); + + /* + * Synchronise with the boot thread. + */ + raw_spin_lock(&boot_lock); + raw_spin_unlock(&boot_lock); +} + +struct smp_operations __initdata virt_smp_ops = { + .smp_init_cpus = virt_smp_init_cpus, + .smp_prepare_cpus = virt_smp_prepare_cpus, + .smp_secondary_init = virt_secondary_init, + .smp_boot_secondary = virt_boot_secondary, +}; diff --git a/arch/arm/mach-virt/virt.c b/arch/arm/mach-virt/virt.c index 174b9da..d764835 100644 --- a/arch/arm/mach-virt/virt.c +++ b/arch/arm/mach-virt/virt.c @@ -20,6 +20,7 @@ #include #include +#include #include #include @@ -56,10 +57,15 @@ static struct sys_timer virt_timer = { .init = virt_timer_init, }; +#ifdef CONFIG_SMP +extern struct smp_operations virt_smp_ops; +#endif + DT_MACHINE_START(VIRT, "Dummy Virtual Machine") .init_irq = gic_init_irq, .handle_irq = gic_handle_irq, .timer = &virt_timer, .init_machine = virt_init, + .smp = smp_ops(virt_smp_ops), .dt_compat = virt_dt_match, MACHINE_END -- 1.8.0 _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-000698-VT; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfro2-0008Cb-LG for xen-arm@lists.xen.org; Tue, 04 Dec 2012 12:40:59 +0000 Received: from [85.158.139.83:52943] by server-1.bemta-5.messagelabs.com id E2/82-09311-95FEDB05; Tue, 04 Dec 2012 12:40:57 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1354624856!28338104!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14430 invoked from network); 4 Dec 2012 12:40:56 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-3.tower-182.messagelabs.com with SMTP; 4 Dec 2012 12:40:56 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4CemUO006233; Tue, 4 Dec 2012 12:40:48 GMT Date: Tue, 4 Dec 2012 12:40:47 +0000 From: Will Deacon To: Rob Herring Message-ID: <20121204124047.GM23368@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50BD1FD7.9040000@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Marc Zyngier , "xen-arm@lists.xen.org" , Mark Rutland , "arnd@arndb.de" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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, Dec 03, 2012 at 09:55:35PM +0000, Rob Herring wrote: > On 12/03/2012 11:52 AM, Will Deacon wrote: > > From: Marc Zyngier > > > > This patch adds support for SMP to mach-virt. > > > > Signed-off-by: Marc Zyngier > > Signed-off-by: Will Deacon > > [...] > > +/* > > + * This provides a "holding pen" into which all secondary cores are held > > + * until we're ready for them to initialise. > > + */ > > +ENTRY(virt_secondary_startup) > > + mrc p15, 0, r0, c0, c0, 5 > > + and r0, r0, #15 > > + adr r4, 1f > > + ldmia r4, {r5, r6} > > + sub r4, r4, r5 > > + add r6, r6, r4 > > +pen: ldr r7, [r6] > > + cmp r7, r0 > > + bne pen > > Why is the pen is needed? It should only be needed for hotplug on > systems that can't reset their cores. I'd hope you could design good > virtual h/w. It's not so much about designing good virtual h/w as it is avoiding tying the platform to it. What we don't want is to mandate that in order to boot this machine, you *must* implement an emulation of some virtual power-controller or SMP booting device. If we go down that route, there's less advantage from having the virtual platform in the first place. There's also less of a problem with the pen approach to booting because ultimately the virtual CPUs executing there are just pthreads and will be scheduled appropriately by the hypervisor (in contrast to a real system where there may be concerns about power consumption and memory bandwidth). For hotplug, sure, we could have an *optional* virtio-based device for dealing with that if we want to. We could even have some early probing code for it and use it for SMP boot if we find a matching DT node, but we'd still need to keep the pen code lying around as a fallback. > > +/* > > + * Enumerate the possible CPU set from the device tree. > > + */ > > +static void __init virt_smp_init_cpus(void) > > +{ > > + const char *enable_method; > > + struct device_node *dn = NULL; > > + int cpu = 0; > > + u32 release_addr; > > + > > + while ((dn = of_find_node_by_type(dn, "cpu"))) { > > + if (cpu >= NR_CPUS) > > + goto next; > > + > > + /* > > + * We currently support only the "spin-table" enable-method. > > + */ > > + enable_method = of_get_property(dn, "enable-method", NULL); > > + if (!enable_method || strcmp(enable_method, "spin-table")) { > > Are these documented? It's part of the EPAPR spec iirc and follows the booting protocol used by arm64. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069J-3B; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfsjZ-0002FF-Ku for xen-arm@lists.xen.org; Tue, 04 Dec 2012 13:40:25 +0000 Received: from [85.158.143.99:23899] by server-3.bemta-4.messagelabs.com id F4/49-06841-84DFDB05; Tue, 04 Dec 2012 13:40:24 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1354628423!22713930!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14761 invoked from network); 4 Dec 2012 13:40:23 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-4.tower-216.messagelabs.com with SMTP; 4 Dec 2012 13:40:23 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4DeBUO007433; Tue, 4 Dec 2012 13:40:11 GMT Date: Tue, 4 Dec 2012 13:40:10 +0000 From: Will Deacon To: Russell King - ARM Linux Message-ID: <20121204134010.GP23368@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20121204133326.GE14363@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 01:33:26PM +0000, Russell King - ARM Linux wrote: > On Tue, Dec 04, 2012 at 12:40:47PM +0000, Will Deacon wrote: > > On Mon, Dec 03, 2012 at 09:55:35PM +0000, Rob Herring wrote: > > > Why is the pen is needed? It should only be needed for hotplug on > > > systems that can't reset their cores. I'd hope you could design good > > > virtual h/w. > > > > It's not so much about designing good virtual h/w as it is avoiding tying > > the platform to it. What we don't want is to mandate that in order to boot > > this machine, you *must* implement an emulation of some virtual > > power-controller or SMP booting device. If we go down that route, there's > > less advantage from having the virtual platform in the first place. > > There is actually a bigger problem here. Let's say that you have a > quad SMP platform. You've arranged for your kernel to boot and only > bring one of those cores online. > > You then kexec() or reboot. As far as the kernel is concerned, those > other two CPUs are not online and are not running any kernel code; > however in reality they could be sitting in this 'pen'. > > The memory that these 'offline' CPUs is executing then gets overwritten, > and that's game over for those CPUs. That's not strictly true. The device-tree passed to the kernel should have a /memreserve/ entry for the SMP pen to avoid exactly this scenario. In real hardware, this still sucks because you have spinning CPUs burning up power but that's not such a problem with a virtual platform. > So, the 'pen' approach in the kernel is fragile, I'd much rather not > have it. It was fine in the beginning for the initial ARM Ltd SMP > platforms but in this modern age it has no place in real platforms where > there is proper control of the secondary CPUs. We could have an (optional) virtual device for booting secondary CPUs but I think the pen should still be there as a default method. Otherwise, we're forcing a component of the platform to be emulated unnecessarily (the CPU, vGIC and timers all have hardware-assisted virtualisation and require no emulation). Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069J-3B; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfsjZ-0002FF-Ku for xen-arm@lists.xen.org; Tue, 04 Dec 2012 13:40:25 +0000 Received: from [85.158.143.99:23899] by server-3.bemta-4.messagelabs.com id F4/49-06841-84DFDB05; Tue, 04 Dec 2012 13:40:24 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1354628423!22713930!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14761 invoked from network); 4 Dec 2012 13:40:23 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-4.tower-216.messagelabs.com with SMTP; 4 Dec 2012 13:40:23 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4DeBUO007433; Tue, 4 Dec 2012 13:40:11 GMT Date: Tue, 4 Dec 2012 13:40:10 +0000 From: Will Deacon To: Russell King - ARM Linux Message-ID: <20121204134010.GP23368@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20121204133326.GE14363@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 01:33:26PM +0000, Russell King - ARM Linux wrote: > On Tue, Dec 04, 2012 at 12:40:47PM +0000, Will Deacon wrote: > > On Mon, Dec 03, 2012 at 09:55:35PM +0000, Rob Herring wrote: > > > Why is the pen is needed? It should only be needed for hotplug on > > > systems that can't reset their cores. I'd hope you could design good > > > virtual h/w. > > > > It's not so much about designing good virtual h/w as it is avoiding tying > > the platform to it. What we don't want is to mandate that in order to boot > > this machine, you *must* implement an emulation of some virtual > > power-controller or SMP booting device. If we go down that route, there's > > less advantage from having the virtual platform in the first place. > > There is actually a bigger problem here. Let's say that you have a > quad SMP platform. You've arranged for your kernel to boot and only > bring one of those cores online. > > You then kexec() or reboot. As far as the kernel is concerned, those > other two CPUs are not online and are not running any kernel code; > however in reality they could be sitting in this 'pen'. > > The memory that these 'offline' CPUs is executing then gets overwritten, > and that's game over for those CPUs. That's not strictly true. The device-tree passed to the kernel should have a /memreserve/ entry for the SMP pen to avoid exactly this scenario. In real hardware, this still sucks because you have spinning CPUs burning up power but that's not such a problem with a virtual platform. > So, the 'pen' approach in the kernel is fragile, I'd much rather not > have it. It was fine in the beginning for the initial ARM Ltd SMP > platforms but in this modern age it has no place in real platforms where > there is proper control of the secondary CPUs. We could have an (optional) virtual device for booting secondary CPUs but I think the pen should still be there as a default method. Otherwise, we're forcing a component of the platform to be emulated unnecessarily (the CPU, vGIC and timers all have hardware-assisted virtualisation and require no emulation). Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-00068k-FL; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfaCS-00046O-1C for xen-arm@lists.xen.org; Mon, 03 Dec 2012 17:53:00 +0000 Received: from [85.158.137.99:31724] by server-11.bemta-3.messagelabs.com id E1/81-19361-BF6ECB05; Mon, 03 Dec 2012 17:52:59 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1354557175!17417955!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22108 invoked from network); 3 Dec 2012 17:52:55 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-2.tower-217.messagelabs.com with SMTP; 3 Dec 2012 17:52:55 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB3Hqh53002348; Mon, 3 Dec 2012 17:52:43 GMT Received: by mudshark.cambridge.arm.com (Postfix, from userid 1000) id 77ABDC2A9C; Mon, 3 Dec 2012 17:52:42 +0000 (GMT) From: Will Deacon To: linux-arm-kernel@lists.infradead.org Date: Mon, 3 Dec 2012 17:52:40 +0000 Message-Id: <1354557160-20144-3-git-send-email-will.deacon@arm.com> X-Mailer: git-send-email 1.8.0 In-Reply-To: <1354557160-20144-1-git-send-email-will.deacon@arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, Will Deacon , arnd@arnd.de Subject: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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: , MIME-Version: 1.0 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 From: Marc Zyngier This patch adds support for SMP to mach-virt. Signed-off-by: Marc Zyngier Signed-off-by: Will Deacon --- arch/arm/mach-virt/Makefile | 1 + arch/arm/mach-virt/headsmp.S | 38 ++++++++ arch/arm/mach-virt/platsmp.c | 205 +++++++++++++++++++++++++++++++++++++++++++ arch/arm/mach-virt/virt.c | 6 ++ 4 files changed, 250 insertions(+) create mode 100644 arch/arm/mach-virt/headsmp.S create mode 100644 arch/arm/mach-virt/platsmp.c diff --git a/arch/arm/mach-virt/Makefile b/arch/arm/mach-virt/Makefile index 7ddbfa6..9ce8a28 100644 --- a/arch/arm/mach-virt/Makefile +++ b/arch/arm/mach-virt/Makefile @@ -3,3 +3,4 @@ # obj-y := virt.o +obj-$(CONFIG_SMP) += platsmp.o headsmp.o diff --git a/arch/arm/mach-virt/headsmp.S b/arch/arm/mach-virt/headsmp.S new file mode 100644 index 0000000..e27afb0 --- /dev/null +++ b/arch/arm/mach-virt/headsmp.S @@ -0,0 +1,38 @@ +/* + * Copyright (c) 2012 ARM Limited + * All Rights Reserved + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ +#include +#include + + __INIT + +/* + * This provides a "holding pen" into which all secondary cores are held + * until we're ready for them to initialise. + */ +ENTRY(virt_secondary_startup) + mrc p15, 0, r0, c0, c0, 5 + and r0, r0, #15 + adr r4, 1f + ldmia r4, {r5, r6} + sub r4, r4, r5 + add r6, r6, r4 +pen: ldr r7, [r6] + cmp r7, r0 + bne pen + + /* + * we've been released from the holding pen: secondary_stack + * should now contain the SVC stack for this core + */ + b secondary_startup + + .align +1: .long . + .long pen_release +ENDPROC(virt_secondary_startup) diff --git a/arch/arm/mach-virt/platsmp.c b/arch/arm/mach-virt/platsmp.c new file mode 100644 index 0000000..fe02f51 --- /dev/null +++ b/arch/arm/mach-virt/platsmp.c @@ -0,0 +1,205 @@ +/* + * Dummy Virtual Machine - does what it says on the tin. + * + * SMP operations, shamelessly stolen from: + * arch/arm64/kernel/smp.c + * + * Copyright (C) 2012 ARM Ltd + * Author: Catalin Marinas + * Author: Will Deacon + * Author: Marc Zyngier + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program. If not, see . + */ + +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +extern void virt_secondary_startup(void); + +static DEFINE_RAW_SPINLOCK(boot_lock); +static phys_addr_t cpu_release_addr[NR_CPUS]; + +/* + * Write secondary_holding_pen_release in a way that is guaranteed to be + * visible to all observers, irrespective of whether they're taking part + * in coherency or not. This is necessary for the hotplug code to work + * reliably. + */ +static void __cpuinit write_pen_release(int val) +{ + void *start = (void *)&pen_release; + unsigned long size = sizeof(pen_release); + + pen_release = val; + smp_wmb(); + __cpuc_flush_dcache_area(start, size); + outer_clean_range(__pa(&pen_release), __pa(&pen_release + 1)); +} + +/* + * Enumerate the possible CPU set from the device tree. + */ +static void __init virt_smp_init_cpus(void) +{ + const char *enable_method; + struct device_node *dn = NULL; + int cpu = 0; + u32 release_addr; + + while ((dn = of_find_node_by_type(dn, "cpu"))) { + if (cpu >= NR_CPUS) + goto next; + + /* + * We currently support only the "spin-table" enable-method. + */ + enable_method = of_get_property(dn, "enable-method", NULL); + if (!enable_method || strcmp(enable_method, "spin-table")) { + pr_err("CPU %d: missing or invalid enable-method property: %s\n", + cpu, enable_method); + goto next; + } + + /* + * Determine the address from which the CPU is polling. + */ + if (of_property_read_u32(dn, "cpu-release-addr", &release_addr)) { + pr_err("CPU %d: missing or invalid cpu-release-addr property\n", + cpu); + goto next; + } + + cpu_release_addr[cpu] = release_addr; + set_cpu_possible(cpu, true); +next: + cpu++; + } + + /* sanity check */ + if (cpu > NR_CPUS) + pr_warning("no. of cores (%d) greater than configured maximum of %d - clipping\n", + cpu, NR_CPUS); + + set_smp_cross_call(gic_raise_softirq); +} + +static void __init virt_smp_prepare_cpus(unsigned int max_cpus) +{ + int cpu; + void **release_addr; + unsigned int ncores = num_possible_cpus(); + + /* + * are we trying to boot more cores than exist? + */ + if (max_cpus > ncores) + max_cpus = ncores; + + /* + * Initialise the present map (which describes the set of CPUs + * actually populated at the present time) and release the + * secondaries from the bootloader. + */ + for_each_possible_cpu(cpu) { + if (max_cpus == 0) + break; + + if (!cpu_release_addr[cpu]) + continue; + + release_addr = __va(cpu_release_addr[cpu]); + release_addr[0] = (void *)__pa(virt_secondary_startup); + smp_wmb(); + __cpuc_flush_dcache_area(release_addr, sizeof(release_addr[0])); + outer_clean_range(__pa(release_addr), __pa(release_addr+1)); + + set_cpu_present(cpu, true); + max_cpus--; + } +} + +static int __cpuinit virt_boot_secondary(unsigned int cpu, + struct task_struct *idle) +{ + unsigned long timeout; + + /* + * Set synchronisation state between this boot processor + * and the secondary one + */ + raw_spin_lock(&boot_lock); + + /* + * Update the pen release flag. + */ + write_pen_release(cpu); + + /* + * Send the secondary CPU a soft interrupt, causing the + * secondaries to read pen_release. + */ + gic_raise_softirq(cpumask_of(cpu), 0); + + timeout = jiffies + (1 * HZ); + while (time_before(jiffies, timeout)) { + if (pen_release == -1UL) + break; + udelay(10); + } + + /* + * Now the secondary core is starting up let it run its + * calibrations, then wait for it to finish + */ + raw_spin_unlock(&boot_lock); + + return pen_release != -1 ? -ENOSYS : 0; +} + +static void __cpuinit virt_secondary_init(unsigned int cpu) +{ + /* + * if any interrupts are already enabled for the primary + * core (e.g. timer irq), then they will not have been enabled + * for us: do so + */ + gic_secondary_init(0); + + /* + * let the primary processor know we're out of the + * pen, then head off into the C entry point + */ + write_pen_release(-1); + + /* + * Synchronise with the boot thread. + */ + raw_spin_lock(&boot_lock); + raw_spin_unlock(&boot_lock); +} + +struct smp_operations __initdata virt_smp_ops = { + .smp_init_cpus = virt_smp_init_cpus, + .smp_prepare_cpus = virt_smp_prepare_cpus, + .smp_secondary_init = virt_secondary_init, + .smp_boot_secondary = virt_boot_secondary, +}; diff --git a/arch/arm/mach-virt/virt.c b/arch/arm/mach-virt/virt.c index 174b9da..d764835 100644 --- a/arch/arm/mach-virt/virt.c +++ b/arch/arm/mach-virt/virt.c @@ -20,6 +20,7 @@ #include #include +#include #include #include @@ -56,10 +57,15 @@ static struct sys_timer virt_timer = { .init = virt_timer_init, }; +#ifdef CONFIG_SMP +extern struct smp_operations virt_smp_ops; +#endif + DT_MACHINE_START(VIRT, "Dummy Virtual Machine") .init_irq = gic_init_irq, .handle_irq = gic_handle_irq, .timer = &virt_timer, .init_machine = virt_init, + .smp = smp_ops(virt_smp_ops), .dt_compat = virt_dt_match, MACHINE_END -- 1.8.0 _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069V-AA; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfv5l-0004VH-Qb for xen-arm@lists.xen.org; Tue, 04 Dec 2012 16:11:30 +0000 Received: from [85.158.137.99:9570] by server-6.bemta-3.messagelabs.com id 86/A9-28265-0B02EB05; Tue, 04 Dec 2012 16:11:28 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1354637487!17903399!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31658 invoked from network); 4 Dec 2012 16:11:28 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-4.tower-217.messagelabs.com with SMTP; 4 Dec 2012 16:11:28 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4GBEUO010544; Tue, 4 Dec 2012 16:11:14 GMT Date: Tue, 4 Dec 2012 16:11:13 +0000 From: Will Deacon To: Russell King - ARM Linux Message-ID: <20121204161113.GT23368@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20121204143724.GF14363@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: > On Tue, Dec 04, 2012 at 01:40:10PM +0000, Will Deacon wrote: > > On Tue, Dec 04, 2012 at 01:33:26PM +0000, Russell King - ARM Linux wrote: > > > The memory that these 'offline' CPUs is executing then gets overwritten, > > > and that's game over for those CPUs. > > > > That's not strictly true. The device-tree passed to the kernel should have a > > /memreserve/ entry for the SMP pen to avoid exactly this scenario. In real > > hardware, this still sucks because you have spinning CPUs burning up power > > but that's not such a problem with a virtual platform. > > Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec > into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which > will be located at 32K into the RAM. The v3.7 kernel will also want to > occupy the same place. At some point you have to overwrite the v3.6 > kernel with the v3.7 kernel image. If the 3.6 kernel didn't bring those CPUs online, they will sit in the bootloader pen (out of the way of the kernel image) rather than the kernel pen so I don't think there will be a problem. The problem you're describing actually happens when the 3.6 kernel onlines all of the CPUs, because now it has no way to hotplug them off safely. This is also an issue with non-virtualised hardware but we could solve it for the virtual platform by having a para-virtualised device for doing CPU hotplug. > That happens _before_ the DT has been parsed, so any memreserve stuff > will be ignored. And it's at that point that your "offline" secondary > CPUs will have their instructions overwritten. > > That's fine if the pen ends up being at the same place but that's not > something we guarantee. Having CPUs in limbo between the bootloader the being online in the kernel is something we should just avoid. Isn't that pen __init anyway? Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069s-LA; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfw23-0007Wb-Us for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:11:44 +0000 Received: from [85.158.138.51:28138] by server-3.bemta-3.messagelabs.com id A1/46-31566-ECE2EB05; Tue, 04 Dec 2012 17:11:42 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1354641101!27526669!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32575 invoked from network); 4 Dec 2012 17:11:42 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-5.tower-174.messagelabs.com with SMTP; 4 Dec 2012 17:11:42 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4HBUUO011957; Tue, 4 Dec 2012 17:11:30 GMT Date: Tue, 4 Dec 2012 17:11:29 +0000 From: Will Deacon To: Nicolas Pitre Message-ID: <20121204171129.GE5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Nicolas, On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: > On Tue, 4 Dec 2012, Rob Herring wrote: > > > That to me is highlighting where we need to do more work on DT driving > > the initialization. The platforms are still aware of what kind of timers > > and interrupt controllers are present. They should not be. There's work > > in progress for both of those. > > > > Lorenzo's DT MPIDR patches should trim down smp code some. The DT spin > > table code could probably be common. I think I could use it on highbank > > as well. If we decide the pen code stays, then it should be common > > rather than creating yet another copy. > > I don't want to rain on the "everything should be common" parade here. > However, for the best part of last year I've been working on kernel > support for big.LITTLE systems, and the handling of CPU hotplug > (including SMP secondary boot) is far from being a trivial task. > Managing the simple bringing up or down of a CPU in such an environment > required hundreds of new lines of code. That is far from a simple > holding pen or spinning table to say the least. > > [ For the curious, I'll post this code here soon for review. ] > > So my point of view is: if you do not need a holding pen because you can > hold individual CPUs in reset, then don't. Many platforms with support > in the kernel can do that, yet they copied the holding pen code just > because it is there. And that is total crap. Agreed, but it's also total crap forcing emulation of a made-up power controller on the host in the case of a virtual platform. > on the topic of a para-virtualised machine, I think that it should > simply implement the PSCI calls to bring up CPUs _without_ any holding > pen nor spinning tables. You issue the appropriate PSCI call with the > physical address for secondary_startup() as argument and you're done. > The host intercepts that call and free a new CPU instance in response. > That's all. I'd be happy to go with this suggestion if it wasn't for one thing: platforms that do not implement a secure mode. For these platforms, smc will be an undefined instruction at the exception level where it is executed and therefore cannot be trapped by the hypervisor. If that situation requires a pen, I see no benefit from having two boot schemes where one of them would work in every case. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-00068q-Ij; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfdxu-0002YU-T6 for xen-arm@lists.xen.org; Mon, 03 Dec 2012 21:54:15 +0000 Received: from [85.158.139.83:36358] by server-9.bemta-5.messagelabs.com id C1/74-29295-68F1DB05; Mon, 03 Dec 2012 21:54:14 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1354571652!28264666!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=2.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18388 invoked from network); 3 Dec 2012 21:54:13 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Dec 2012 21:54:13 -0000 Received: by mail-ob0-f173.google.com with SMTP id xn12so3653012obc.32 for ; Mon, 03 Dec 2012 13:54:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=o4Z91y7vpWdaPMY95MbHHdrPxCZ6NyrgHN78QsPT0NA=; b=KKu3LMszDV5G5/LjRHaRAbg8dcUEkH/dWbIS/Zq5p9A/v/2lEf0DKb9e9MK0ot7rlh fuOHh0yVMc6vwRGGTbDlffW087RFwTLNBqiSih6puDQppeYnC1C9yur5CHhSpSaxHxmI sd6LS8JSrT6uCfU1tPvbcm6xDrBqys5eXBofyrp6288yC4KzSNvjooSmx5GbOUICIyHY zRV+FLK3BgPTabjpqBbSczgWZSF5MLb4PFIMslkdwNzB0TZLqXltFMwVmvnhN51JN221 R8U9ZJLTiHOqisWqZYKbEddPC8imUgUCGzj1Ndi/hRqHYpW8hmdYp0Hs30bRzC9Hw4Ve UvVA== Received: by 10.182.152.4 with SMTP id uu4mr5641362obb.85.1354571651668; Mon, 03 Dec 2012 13:54:11 -0800 (PST) Received: from [10.10.10.90] ([173.226.190.126]) by mx.google.com with ESMTPS id c18sm14857097obc.17.2012.12.03.13.54.10 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 13:54:10 -0800 (PST) Message-ID: <50BD1F81.9080304@gmail.com> Date: Mon, 03 Dec 2012 15:54:09 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> In-Reply-To: <1354557160-20144-1-git-send-email-will.deacon@arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, arnd@arnd.de, linux-arm-kernel@lists.infradead.org Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 12/03/2012 11:52 AM, Will Deacon wrote: > Hello, > > When running Linux on a para-virtualised platform (that is, one where > the guest is aware that it is dealing with virtual devices sitting on > things like virtio or xenbus) we require very little in the way of > platform code and piggy-backing on top of an existing platform can > require a lot of device emulation for very little gain. > > These two patches introduce mach-virt: a very simple, DT-based machine > which can be used with kvmtool in conjunction with virtio-based devices. > It's not hard to imagine the same machine being targetted by Xen, which > currently emulates a minimal variant of the vexpress platform. > > Note that this patch series depends on the timer rework from Mark > Rutland, posted on Friday: > > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/135651.html > > All feedback welcome. We suspect that most controversy will be around > the name of the thing :) We've discussed this before at conferences. I don't know that we concluded this wasn't needed, but it certainly leaned that direction. So what has changed? You're not going to save code space because we're building multiple platforms together. You'll save some boot time, but a stripped down dtb with only the minimal peripherals would probably save nearly as much time. However, I do have concerns with using VExpress as the guest. For example, you can't support a non-PAE guest with 4GB of RAM on VExpress (maybe if the vexpress code gets all memory map info from DT). Is this really complete? Will we need reset, poweroff, hotplug, and suspend/resume support for example? Unlike most initial platform submissions which are minimal, I think seeing full support would be useful here. Then we can better gauge how much we are really saving. Rob > > Will > > > Marc Zyngier (2): > ARM: Dummy Virtual Machine platform support > ARM: SMP support for mach-virt > > arch/arm/Kconfig | 2 + > arch/arm/Makefile | 1 + > arch/arm/mach-virt/Kconfig | 9 ++ > arch/arm/mach-virt/Makefile | 6 ++ > arch/arm/mach-virt/headsmp.S | 38 ++++++++ > arch/arm/mach-virt/platsmp.c | 205 +++++++++++++++++++++++++++++++++++++++++++ > arch/arm/mach-virt/virt.c | 71 +++++++++++++++ > 7 files changed, 332 insertions(+) > create mode 100644 arch/arm/mach-virt/Kconfig > create mode 100644 arch/arm/mach-virt/Makefile > create mode 100644 arch/arm/mach-virt/headsmp.S > create mode 100644 arch/arm/mach-virt/platsmp.c > create mode 100644 arch/arm/mach-virt/virt.c > _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069j-Hw; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfvr0-0007FF-S1 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:00:19 +0000 Received: from [85.158.137.99:48418] by server-13.bemta-3.messagelabs.com id AC/25-24887-D1C2EB05; Tue, 04 Dec 2012 17:00:13 +0000 X-Env-Sender: nico@fluxnic.net X-Msg-Ref: server-10.tower-217.messagelabs.com!1354640408!17242129!1 X-Originating-IP: [24.201.245.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n,sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30785 invoked from network); 4 Dec 2012 17:00:09 -0000 Received: from relais.videotron.ca (HELO relais.videotron.ca) (24.201.245.36) by server-10.tower-217.messagelabs.com with SMTP; 4 Dec 2012 17:00:09 -0000 MIME-version: 1.0 Received: from xanadu.home ([24.202.213.203]) by VL-VM-MR003.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MEI00G1LN87DIL0@VL-VM-MR003.ip.videotron.ca> for xen-arm@lists.xen.org; Tue, 04 Dec 2012 12:00:08 -0500 (EST) Date: Tue, 04 Dec 2012 12:00:07 -0500 (EST) From: Nicolas Pitre To: Rob Herring In-reply-to: <50BE04C6.4070602@gmail.com> Message-id: References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Will Deacon , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Tue, 4 Dec 2012, Rob Herring wrote: > That to me is highlighting where we need to do more work on DT driving > the initialization. The platforms are still aware of what kind of timers > and interrupt controllers are present. They should not be. There's work > in progress for both of those. > > Lorenzo's DT MPIDR patches should trim down smp code some. The DT spin > table code could probably be common. I think I could use it on highbank > as well. If we decide the pen code stays, then it should be common > rather than creating yet another copy. I don't want to rain on the "everything should be common" parade here. However, for the best part of last year I've been working on kernel support for big.LITTLE systems, and the handling of CPU hotplug (including SMP secondary boot) is far from being a trivial task. Managing the simple bringing up or down of a CPU in such an environment required hundreds of new lines of code. That is far from a simple holding pen or spinning table to say the least. [ For the curious, I'll post this code here soon for review. ] So my point of view is: if you do not need a holding pen because you can hold individual CPUs in reset, then don't. Many platforms with support in the kernel can do that, yet they copied the holding pen code just because it is there. And that is total crap. on the topic of a para-virtualised machine, I think that it should simply implement the PSCI calls to bring up CPUs _without_ any holding pen nor spinning tables. You issue the appropriate PSCI call with the physical address for secondary_startup() as argument and you're done. The host intercepts that call and free a new CPU instance in response. That's all. Nicolas _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-0006AE-TO; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfwEU-0008G3-38 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:24:34 +0000 Received: from [85.158.143.99:8839] by server-3.bemta-4.messagelabs.com id A6/FD-06841-1D13EB05; Tue, 04 Dec 2012 17:24:33 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1354641872!28023425!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27522 invoked from network); 4 Dec 2012 17:24:32 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-15.tower-216.messagelabs.com with SMTP; 4 Dec 2012 17:24:32 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4HOPUO012122; Tue, 4 Dec 2012 17:24:25 GMT Date: Tue, 4 Dec 2012 17:24:24 +0000 From: Will Deacon To: Russell King - ARM Linux Message-ID: <20121204172424.GG5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <20121204163555.GH14363@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20121204163555.GH14363@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 04:35:55PM +0000, Russell King - ARM Linux wrote: > On Tue, Dec 04, 2012 at 04:11:13PM +0000, Will Deacon wrote: > > The problem you're describing actually happens when the 3.6 kernel onlines > > all of the CPUs, because now it has no way to hotplug them off safely. This > > is also an issue with non-virtualised hardware but we could solve it for the > > virtual platform by having a para-virtualised device for doing CPU hotplug. > > That situation exists on ARM Ltd platforms where there's no way to > properly return them back to the boot loader. We should not be forcing > this ARM Ltd platform deficiency onto other platforms as part of a > "design", even virtual platforms. > > Most other real-world platforms out there have a way to power off the > unused secondary CPUs - Tegra and OMAP both do. If a virtual machine powers off a virtual CPU, I doubt we want to power of its corresponding CPU -- that logic can remain in the host. All we need to do is kill the virtual CPU thread, which we can do easily enough. Booting is the more difficult problem because we introduce a reliance on a virtual device being ready incredibly early, essentially hardcoding part of the virtual machine. > As far as virtual platforms go, how secondary CPUs are dealt with should > already have been solved; I really can't imagine that KVM and XEN on > other architectures end up with CPUs spinning in a loop inside the guest > kernel waiting for the guest OS to ask them to boot. Neither can I imagine > that KVM and XEN end up with CPUs spinning in the guest OS when CPUs are > asked to be hot-unplugged. So neither kvmtool or qemu currently support hotplug for kvm guests on any architectures from what I can tell. Furthermore, kvmtool on ppc (at least) uses a secondary spinning loop at a fixed offset into the kernel image. I don't think we should really pay much attention to those other architectures in this regard! > > > That happens _before_ the DT has been parsed, so any memreserve stuff > > > will be ignored. And it's at that point that your "offline" secondary > > > CPUs will have their instructions overwritten. > > > > > > That's fine if the pen ends up being at the same place but that's not > > > something we guarantee. > > > > Having CPUs in limbo between the bootloader the being online in the kernel > > is something we should just avoid. Isn't that pen __init anyway? > > If you have hotplug enabled, all the secondary bringup code should be > in the __cpuinit and __cpuinitdata sections. Right, but if booting a !HOTPLUG kernel via kexec, surely we'd have to clear that pen of CPUs? Will _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006Ef-S8; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGcT-0005FZ-1K for xen-arm@lists.xen.org; Wed, 05 Dec 2012 15:10:41 +0000 Received: from [85.158.143.35:59213] by server-3.bemta-4.messagelabs.com id 1A/02-06841-0F36FB05; Wed, 05 Dec 2012 15:10:40 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1354720239!16204881!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29819 invoked from network); 5 Dec 2012 15:10:39 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-6.tower-21.messagelabs.com with SMTP; 5 Dec 2012 15:10:39 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB5FAUUO006221; Wed, 5 Dec 2012 15:10:30 GMT Date: Wed, 5 Dec 2012 15:10:29 +0000 From: Will Deacon To: Nicolas Pitre Message-ID: <20121205151029.GK22385@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Catalin Marinas , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Wed, Dec 05, 2012 at 03:07:05PM +0000, Nicolas Pitre wrote: > On Wed, 5 Dec 2012, Catalin Marinas wrote: > > On 4 December 2012 18:14, Will Deacon wrote: > > > Well, this depends on the guest taking an undefined instruction exception on > > > the smc, then deciding to issue an hvc instead and *then* having the > > > hypervisor somehow translate that into a PSCI invocation. It could work, but > > > it sounds easy to mess up and relies on the PSCI firmware co-existing with > > > things like kvm. > > > > We can have enable-method DT entries independent of the SoC and one of > > them can be psci-hvc. > > > > Just for clarification, AArch32 with virtualisation mandates the > > security extensions, so the SMC can be trapped. > > Good. Therefore this one is settled. Looks we replied at the same time! Please see my other mail... Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCW-00068O-Ls; Fri, 03 May 2013 12:35:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG3hQ-0007A6-6q for xen-arm@lists.xen.org; Mon, 24 Sep 2012 08:07:28 +0000 Received: from [85.158.143.99:60970] by server-3.bemta-4.messagelabs.com id E0/17-10986-FB410605; Mon, 24 Sep 2012 08:07:27 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1348474046!23368681!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5160 invoked from network); 24 Sep 2012 08:07:26 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:07:26 -0000 Received: by lbbgm13 with SMTP id gm13so7838046lbb.32 for ; Mon, 24 Sep 2012 01:07:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VQM2rVud5klBfZBJsYP4BZ05g1BoP8iFuZY4r7QOYIY=; b=gYnaJjsP+4u7B2DkjMucZjh96UMsiaqNVhgAcf/Fq1I3raUMz9qpkDylqAXNut51Qe 4eIomwWYOAESOgG0E1h+E27W4wXp4AhOX8TwGbG3YcXijTsJMVLPBc8HrVFSyxJqPeVy uqcAi0V7BSP3EKK8/PRjBtxkKYk9LjczmWiUhK5wVMaTuq5kefsOkGCU6VtiZDahZZg7 XmQ5MZu7i6R/toiLcQUa4jIKpZBIAwnTM+deNCFTTkak898O69KnYQCHs3ByrORMN5YN 3T8IdlWNnz6faDLPYnUTaPC4zUtGF/rjgpxcOkRCOoCnmqgtKKgEZTlKUrOKDZGxpjP6 prRw== MIME-Version: 1.0 Received: by 10.112.26.135 with SMTP id l7mr567705lbg.84.1348474045943; Mon, 24 Sep 2012 01:07:25 -0700 (PDT) Received: by 10.112.120.138 with HTTP; Mon, 24 Sep 2012 01:07:25 -0700 (PDT) Date: Mon, 24 Sep 2012 09:07:25 +0100 Message-ID: From: Lars Kurth To: xen-devel@lists.xen.org, xen-users@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] [Reminder] Xen Document Day on IRC freenode #xendocs today 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="===============2042890039193443060==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============2042890039193443060== Content-Type: multipart/alternative; boundary=bcaec554d4247f4f0204ca6e143b --bcaec554d4247f4f0204ca6e143b Content-Type: text/plain; charset=ISO-8859-1 Good Morning, we have another document day today! More information about docs day at http://wiki.xen.org/wiki/Xen_Document_Days The TODO list is at http://wiki.xen.org/wiki/Xen_Document_Days/TODO Regards Lars --bcaec554d4247f4f0204ca6e143b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Good Morning,
we have another document day today! More information about= docs day at http://= wiki.xen.org/wiki/Xen_Document_Days
The TODO list is at http://wiki.xen.org/wiki/Xe= n_Document_Days/TODO
Regards
Lars
--bcaec554d4247f4f0204ca6e143b-- --===============2042890039193443060== 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 --===============2042890039193443060==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-0006A3-ON; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfw6y-0007r5-T2 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:16:49 +0000 Received: from [85.158.143.99:24305] by server-3.bemta-4.messagelabs.com id D3/16-06841-0003EB05; Tue, 04 Dec 2012 17:16:48 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1354641404!27451723!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2882 invoked from network); 4 Dec 2012 17:16:44 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-3.tower-216.messagelabs.com with SMTP; 4 Dec 2012 17:16:44 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4HGTUO012032; Tue, 4 Dec 2012 17:16:29 GMT Date: Tue, 4 Dec 2012 17:16:28 +0000 From: Will Deacon To: Rob Herring Message-ID: <20121204171628.GF5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50BE28C6.2010403@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: > On 12/04/2012 10:11 AM, Will Deacon wrote: > > On Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: > >> Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec > >> into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which > >> will be located at 32K into the RAM. The v3.7 kernel will also want to > >> occupy the same place. At some point you have to overwrite the v3.6 > >> kernel with the v3.7 kernel image. > > > > If the 3.6 kernel didn't bring those CPUs online, they will sit in the > > bootloader pen (out of the way of the kernel image) rather than the kernel > > pen so I don't think there will be a problem. > > > > The problem you're describing actually happens when the 3.6 kernel onlines > > all of the CPUs, because now it has no way to hotplug them off safely. This > > is also an issue with non-virtualised hardware but we could solve it for the > > virtual platform by having a para-virtualised device for doing CPU hotplug. > > > >> That happens _before_ the DT has been parsed, so any memreserve stuff > >> will be ignored. And it's at that point that your "offline" secondary > >> CPUs will have their instructions overwritten. > >> > >> That's fine if the pen ends up being at the same place but that's not > >> something we guarantee. > > > > Having CPUs in limbo between the bootloader the being online in the kernel > > is something we should just avoid. Isn't that pen __init anyway? > > Aren't we mixing 2 pens here? You must have some simple bootloader > containing vector table and a pen that the dtb points to, right? The pen > you have in the kernel is only needed when hotplug only does a wfi. As > you don't yet support hotplug, then you can drop all the kernel pen code. Yes, both qemu and kvmtool have bootloader pens outside of the kernel but since wfi is not trapped by kvm, the secondaries can be released early due to a spurious wakeup so we need the second pen. > If there is no way to reset the core, then couldn't the hotplug code > tear down the cpu setup and just jump back to 0x0 which then returns to > the bootloader's pen? I think hotplug really should be implemented with a virtio device. We just trap back to the emulation and kill the vcpu thread. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCW-00068O-Ls; Fri, 03 May 2013 12:35:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG3hQ-0007A6-6q for xen-arm@lists.xen.org; Mon, 24 Sep 2012 08:07:28 +0000 Received: from [85.158.143.99:60970] by server-3.bemta-4.messagelabs.com id E0/17-10986-FB410605; Mon, 24 Sep 2012 08:07:27 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1348474046!23368681!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5160 invoked from network); 24 Sep 2012 08:07:26 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:07:26 -0000 Received: by lbbgm13 with SMTP id gm13so7838046lbb.32 for ; Mon, 24 Sep 2012 01:07:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VQM2rVud5klBfZBJsYP4BZ05g1BoP8iFuZY4r7QOYIY=; b=gYnaJjsP+4u7B2DkjMucZjh96UMsiaqNVhgAcf/Fq1I3raUMz9qpkDylqAXNut51Qe 4eIomwWYOAESOgG0E1h+E27W4wXp4AhOX8TwGbG3YcXijTsJMVLPBc8HrVFSyxJqPeVy uqcAi0V7BSP3EKK8/PRjBtxkKYk9LjczmWiUhK5wVMaTuq5kefsOkGCU6VtiZDahZZg7 XmQ5MZu7i6R/toiLcQUa4jIKpZBIAwnTM+deNCFTTkak898O69KnYQCHs3ByrORMN5YN 3T8IdlWNnz6faDLPYnUTaPC4zUtGF/rjgpxcOkRCOoCnmqgtKKgEZTlKUrOKDZGxpjP6 prRw== MIME-Version: 1.0 Received: by 10.112.26.135 with SMTP id l7mr567705lbg.84.1348474045943; Mon, 24 Sep 2012 01:07:25 -0700 (PDT) Received: by 10.112.120.138 with HTTP; Mon, 24 Sep 2012 01:07:25 -0700 (PDT) Date: Mon, 24 Sep 2012 09:07:25 +0100 Message-ID: From: Lars Kurth To: xen-devel@lists.xen.org, xen-users@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] [Reminder] Xen Document Day on IRC freenode #xendocs today 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="===============2042890039193443060==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============2042890039193443060== Content-Type: multipart/alternative; boundary=bcaec554d4247f4f0204ca6e143b --bcaec554d4247f4f0204ca6e143b Content-Type: text/plain; charset=ISO-8859-1 Good Morning, we have another document day today! More information about docs day at http://wiki.xen.org/wiki/Xen_Document_Days The TODO list is at http://wiki.xen.org/wiki/Xen_Document_Days/TODO Regards Lars --bcaec554d4247f4f0204ca6e143b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Good Morning,
we have another document day today! More information about= docs day at http://= wiki.xen.org/wiki/Xen_Document_Days
The TODO list is at http://wiki.xen.org/wiki/Xe= n_Document_Days/TODO
Regards
Lars
--bcaec554d4247f4f0204ca6e143b-- --===============2042890039193443060== 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 --===============2042890039193443060==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006AW-4y; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfwEw-0008MR-Bl for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:25:02 +0000 Received: from [85.158.143.35:61261] by server-2.bemta-4.messagelabs.com id 0D/32-28922-DE13EB05; Tue, 04 Dec 2012 17:25:01 +0000 X-Env-Sender: marc.zyngier@arm.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1354641901!10575705!1 X-Originating-IP: [91.220.42.44] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogOTEuMjIwLjQyLjQ0ID0+IDM0MDY4OA==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3873 invoked from network); 4 Dec 2012 17:25:01 -0000 Received: from service87.mimecast.com (HELO service87.mimecast.com) (91.220.42.44) by server-10.tower-21.messagelabs.com with SMTP; 4 Dec 2012 17:25:01 -0000 Received: from cam-owa1.Emea.Arm.com (fw-tnat.cambridge.arm.com [217.140.96.21]) by service87.mimecast.com; Tue, 04 Dec 2012 17:25:00 +0000 Received: from [10.1.70.21] ([10.1.255.212]) by cam-owa1.Emea.Arm.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 4 Dec 2012 17:24:58 +0000 Message-ID: <50BE31E9.3040404@arm.com> Date: Tue, 04 Dec 2012 17:24:57 +0000 From: Marc Zyngier User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> <20121204171628.GF5314@mudshark.cambridge.arm.com> In-Reply-To: <20121204171628.GF5314@mudshark.cambridge.arm.com> X-Enigmail-Version: 1.4.6 X-OriginalArrivalTime: 04 Dec 2012 17:24:58.0593 (UTC) FILETIME=[48E10D10:01CDD244] X-MC-Unique: 112120417250010401 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 04/12/12 17:16, Will Deacon wrote: > On Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: >> On 12/04/2012 10:11 AM, Will Deacon wrote: >>> On Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: >>>> Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec >>>> into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which >>>> will be located at 32K into the RAM. The v3.7 kernel will also want to >>>> occupy the same place. At some point you have to overwrite the v3.6 >>>> kernel with the v3.7 kernel image. >>> >>> If the 3.6 kernel didn't bring those CPUs online, they will sit in the >>> bootloader pen (out of the way of the kernel image) rather than the kernel >>> pen so I don't think there will be a problem. >>> >>> The problem you're describing actually happens when the 3.6 kernel onlines >>> all of the CPUs, because now it has no way to hotplug them off safely. This >>> is also an issue with non-virtualised hardware but we could solve it for the >>> virtual platform by having a para-virtualised device for doing CPU hotplug. >>> >>>> That happens _before_ the DT has been parsed, so any memreserve stuff >>>> will be ignored. And it's at that point that your "offline" secondary >>>> CPUs will have their instructions overwritten. >>>> >>>> That's fine if the pen ends up being at the same place but that's not >>>> something we guarantee. >>> >>> Having CPUs in limbo between the bootloader the being online in the kernel >>> is something we should just avoid. Isn't that pen __init anyway? >> >> Aren't we mixing 2 pens here? You must have some simple bootloader >> containing vector table and a pen that the dtb points to, right? The pen >> you have in the kernel is only needed when hotplug only does a wfi. As >> you don't yet support hotplug, then you can drop all the kernel pen code. > > Yes, both qemu and kvmtool have bootloader pens outside of the kernel but > since wfi is not trapped by kvm, the secondaries can be released early due > to a spurious wakeup so we need the second pen. Actually, KVM traps WFI and puts the vcpu thread on a wait queue (we are actually giving more guaranties than the architecture offers here). We should be able to remove the loop and rely on WFI. M. -- Jazz is not dead. It just smells funny... _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069O-6a; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TftF3-0004F9-RS for xen-arm@lists.xen.org; Tue, 04 Dec 2012 14:12:58 +0000 Received: from [193.109.254.147:23675] by server-1.bemta-14.messagelabs.com id 49/05-25314-9E40EB05; Tue, 04 Dec 2012 14:12:57 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1354630346!8650563!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=2.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7348 invoked from network); 4 Dec 2012 14:12:28 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2012 14:12:28 -0000 Received: by mail-oa0-f45.google.com with SMTP id i18so4713956oag.32 for ; Tue, 04 Dec 2012 06:12:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Ypd2kU+KEfGTg+IlRTM13tdni0pWw4IQjIPXHn4pjcE=; b=m2YtgSuxaoRS4RFAa5xA7lBqwH9VnJ2kf4FzUeJtEo728XXE/NcaxnUM9Vu7ewXNRp ICC1aoupByAnkgDuG1f9gFpIhiAqz3hrQojXP5DtePrenAxFVSRz+sYVyuXBjtQWlGsI T0IKEU/frfA6+FXsiGReEklec8xawx3qFy0O6Jw+fKKd3VlIKtzt03zZHzOyDJkVLBkc 2+6BWVj50CwtpYLwxi8+sjUeyovntEMlMqsrPCyyl1eTX3D2I9SzHPyslbZoDHSptZJC Z/sXtIppIa3DYeAJVVcuNGWbIVfqhCrPFdtu24m8srsxkEsgI4kXEHPOAJR1K6iEZ6Hb sKAw== Received: by 10.60.13.198 with SMTP id j6mr11439492oec.51.1354630346441; Tue, 04 Dec 2012 06:12:26 -0800 (PST) Received: from [192.168.1.103] (65-36-73-129.dyn.grandenetworks.net. [65.36.73.129]) by mx.google.com with ESMTPS id hz6sm853132obb.1.2012.12.04.06.12.23 (version=SSLv3 cipher=OTHER); Tue, 04 Dec 2012 06:12:25 -0800 (PST) Message-ID: <50BE04C6.4070602@gmail.com> Date: Tue, 04 Dec 2012 08:12:22 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> In-Reply-To: <20121204123001.GL23368@mudshark.cambridge.arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Marc Zyngier , "xen-arm@lists.xen.org" , Mark Rutland , "arnd@arndb.de" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 12/04/2012 06:30 AM, Will Deacon wrote: > Hi Rob, > > [fixing Arnd's address, as I apparently can't spell] > > On Mon, Dec 03, 2012 at 09:54:09PM +0000, Rob Herring wrote: >> On 12/03/2012 11:52 AM, Will Deacon wrote: >>> When running Linux on a para-virtualised platform (that is, one where >>> the guest is aware that it is dealing with virtual devices sitting on >>> things like virtio or xenbus) we require very little in the way of >>> platform code and piggy-backing on top of an existing platform can >>> require a lot of device emulation for very little gain. >>> >>> These two patches introduce mach-virt: a very simple, DT-based machine >>> which can be used with kvmtool in conjunction with virtio-based devices. >>> It's not hard to imagine the same machine being targetted by Xen, which >>> currently emulates a minimal variant of the vexpress platform. >>> >>> Note that this patch series depends on the timer rework from Mark >>> Rutland, posted on Friday: >>> >>> http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/135651.html >>> >>> All feedback welcome. We suspect that most controversy will be around >>> the name of the thing :) >> >> We've discussed this before at conferences. I don't know that we >> concluded this wasn't needed, but it certainly leaned that direction. > > I too leaned that direction before I started looking at kvm in detail and, > since then, I've changed my mind when it comes to para-virtualisation. > > The reason for this is that there is absolutely no reason to emulate some > components of a real platform and then bolt virtual devices onto it once > you've got enough to get it going. It leads to a right royal mess in > userspace, where you have to write a load of non-reusable emulation code and > it leads to churn in the kernel because you're constantly at odds with > people trying to develop the platform code based on the actual hardware > they have. > > With a virtualisation-capable ARMv7 system, all you *need* to boot SMP > Debian is: > > - A v7 CPU with virt extensions > - vGIC > - architected timers > > *everything* else can be described using virtio devices in the device-tree, > essentially allowing you to generate platforms based on the above and boot > the same kernel on them. > >> So what has changed? You're not going to save code space because we're >> building multiple platforms together. You'll save some boot time, but a >> stripped down dtb with only the minimal peripherals would probably save >> nearly as much time. > > It's really got nothing to do with code space or boot speed. What it *is* > about is avoiding the tight coupling with a real platform and suffering as a > result. Yes, you can strip down the DT for a real platform but you'll likely > still have to emulate things like the SP804 in order to boot. That's not to > mention any platform-specific system register interfaces which are required > early on. > > We can't even re-use the socfpga code (which is incredibly minimal) without > emulating the dw_apb_timer. That to me is highlighting where we need to do more work on DT driving the initialization. The platforms are still aware of what kind of timers and interrupt controllers are present. They should not be. There's work in progress for both of those. Lorenzo's DT MPIDR patches should trim down smp code some. The DT spin table code could probably be common. I think I could use it on highbank as well. If we decide the pen code stays, then it should be common rather than creating yet another copy. Rob _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-000690-PR; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfrdc-0007x8-6P for xen-arm@lists.xen.org; Tue, 04 Dec 2012 12:30:12 +0000 Received: from [193.109.254.147:47587] by server-15.bemta-14.messagelabs.com id CF/E1-12105-3DCEDB05; Tue, 04 Dec 2012 12:30:11 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1354624208!8778584!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20511 invoked from network); 4 Dec 2012 12:30:08 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-8.tower-27.messagelabs.com with SMTP; 4 Dec 2012 12:30:08 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4CU2UO006009; Tue, 4 Dec 2012 12:30:02 GMT Date: Tue, 4 Dec 2012 12:30:01 +0000 From: Will Deacon To: Rob Herring Message-ID: <20121204123001.GL23368@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50BD1F81.9080304@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Marc Zyngier , "xen-arm@lists.xen.org" , Mark Rutland , "arnd@arndb.de" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Rob, [fixing Arnd's address, as I apparently can't spell] On Mon, Dec 03, 2012 at 09:54:09PM +0000, Rob Herring wrote: > On 12/03/2012 11:52 AM, Will Deacon wrote: > > When running Linux on a para-virtualised platform (that is, one where > > the guest is aware that it is dealing with virtual devices sitting on > > things like virtio or xenbus) we require very little in the way of > > platform code and piggy-backing on top of an existing platform can > > require a lot of device emulation for very little gain. > > > > These two patches introduce mach-virt: a very simple, DT-based machine > > which can be used with kvmtool in conjunction with virtio-based devices. > > It's not hard to imagine the same machine being targetted by Xen, which > > currently emulates a minimal variant of the vexpress platform. > > > > Note that this patch series depends on the timer rework from Mark > > Rutland, posted on Friday: > > > > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/135651.html > > > > All feedback welcome. We suspect that most controversy will be around > > the name of the thing :) > > We've discussed this before at conferences. I don't know that we > concluded this wasn't needed, but it certainly leaned that direction. I too leaned that direction before I started looking at kvm in detail and, since then, I've changed my mind when it comes to para-virtualisation. The reason for this is that there is absolutely no reason to emulate some components of a real platform and then bolt virtual devices onto it once you've got enough to get it going. It leads to a right royal mess in userspace, where you have to write a load of non-reusable emulation code and it leads to churn in the kernel because you're constantly at odds with people trying to develop the platform code based on the actual hardware they have. With a virtualisation-capable ARMv7 system, all you *need* to boot SMP Debian is: - A v7 CPU with virt extensions - vGIC - architected timers *everything* else can be described using virtio devices in the device-tree, essentially allowing you to generate platforms based on the above and boot the same kernel on them. > So what has changed? You're not going to save code space because we're > building multiple platforms together. You'll save some boot time, but a > stripped down dtb with only the minimal peripherals would probably save > nearly as much time. It's really got nothing to do with code space or boot speed. What it *is* about is avoiding the tight coupling with a real platform and suffering as a result. Yes, you can strip down the DT for a real platform but you'll likely still have to emulate things like the SP804 in order to boot. That's not to mention any platform-specific system register interfaces which are required early on. We can't even re-use the socfpga code (which is incredibly minimal) without emulating the dw_apb_timer. > However, I do have concerns with using VExpress as > the guest. For example, you can't support a non-PAE guest with 4GB of > RAM on VExpress (maybe if the vexpress code gets all memory map info > from DT). Yes, vexpress is even less suitable for this. > Is this really complete? Will we need reset, poweroff, hotplug, and > suspend/resume support for example? Unlike most initial platform > submissions which are minimal, I think seeing full support would be > useful here. Then we can better gauge how much we are really saving. The code is complete in the sense that you can boot an SMP guest running Debian with console, network, block etc. etc. but you're right to point out the absence of power-management support. However, power-management in KVM guests is a *much* larger problem and not one that has been solved adequately as of yet. There are suggestions that it should be handled entirely in firmware, with the guest making smc calls to request power-management operations but this is yet to materialise and, as such, we can't yet use it here. We could look at building a virtio-based power controller but that's going to come up too late for SMP booting (although will give us hotplug, reset etc). Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069s-LA; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfw23-0007Wb-Us for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:11:44 +0000 Received: from [85.158.138.51:28138] by server-3.bemta-3.messagelabs.com id A1/46-31566-ECE2EB05; Tue, 04 Dec 2012 17:11:42 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1354641101!27526669!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32575 invoked from network); 4 Dec 2012 17:11:42 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-5.tower-174.messagelabs.com with SMTP; 4 Dec 2012 17:11:42 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4HBUUO011957; Tue, 4 Dec 2012 17:11:30 GMT Date: Tue, 4 Dec 2012 17:11:29 +0000 From: Will Deacon To: Nicolas Pitre Message-ID: <20121204171129.GE5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Nicolas, On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: > On Tue, 4 Dec 2012, Rob Herring wrote: > > > That to me is highlighting where we need to do more work on DT driving > > the initialization. The platforms are still aware of what kind of timers > > and interrupt controllers are present. They should not be. There's work > > in progress for both of those. > > > > Lorenzo's DT MPIDR patches should trim down smp code some. The DT spin > > table code could probably be common. I think I could use it on highbank > > as well. If we decide the pen code stays, then it should be common > > rather than creating yet another copy. > > I don't want to rain on the "everything should be common" parade here. > However, for the best part of last year I've been working on kernel > support for big.LITTLE systems, and the handling of CPU hotplug > (including SMP secondary boot) is far from being a trivial task. > Managing the simple bringing up or down of a CPU in such an environment > required hundreds of new lines of code. That is far from a simple > holding pen or spinning table to say the least. > > [ For the curious, I'll post this code here soon for review. ] > > So my point of view is: if you do not need a holding pen because you can > hold individual CPUs in reset, then don't. Many platforms with support > in the kernel can do that, yet they copied the holding pen code just > because it is there. And that is total crap. Agreed, but it's also total crap forcing emulation of a made-up power controller on the host in the case of a virtual platform. > on the topic of a para-virtualised machine, I think that it should > simply implement the PSCI calls to bring up CPUs _without_ any holding > pen nor spinning tables. You issue the appropriate PSCI call with the > physical address for secondary_startup() as argument and you're done. > The host intercepts that call and free a new CPU instance in response. > That's all. I'd be happy to go with this suggestion if it wasn't for one thing: platforms that do not implement a secure mode. For these platforms, smc will be an undefined instruction at the exception level where it is executed and therefore cannot be trapped by the hypervisor. If that situation requires a pen, I see no benefit from having two boot schemes where one of them would work in every case. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006C4-GW; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfx1G-0003RQ-72 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 18:14:58 +0000 Received: from [85.158.138.51:52675] by server-7.bemta-3.messagelabs.com id 15/51-01713-1AD3EB05; Tue, 04 Dec 2012 18:14:57 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1354644896!27361066!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5053 invoked from network); 4 Dec 2012 18:14:56 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-16.tower-174.messagelabs.com with SMTP; 4 Dec 2012 18:14:56 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4IElUO013015; Tue, 4 Dec 2012 18:14:47 GMT Date: Tue, 4 Dec 2012 18:14:46 +0000 From: Will Deacon To: Nicolas Pitre Message-ID: <20121204181446.GJ5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Tue, Dec 04, 2012 at 06:02:13PM +0000, Nicolas Pitre wrote: > On Tue, 4 Dec 2012, Will Deacon wrote: > > > Hi Nicolas, > > > > On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: > > > on the topic of a para-virtualised machine, I think that it should > > > simply implement the PSCI calls to bring up CPUs _without_ any holding > > > pen nor spinning tables. You issue the appropriate PSCI call with the > > > physical address for secondary_startup() as argument and you're done. > > > The host intercepts that call and free a new CPU instance in response. > > > That's all. > > > > I'd be happy to go with this suggestion if it wasn't for one thing: > > platforms that do not implement a secure mode. For these platforms, smc will > > be an undefined instruction at the exception level where it is executed and > > therefore cannot be trapped by the hypervisor. > > Really? I thought the hypervisor could virtualize SMC calls. Or is > that considered a security hazard? If the security extensions aren't implemented, the hypervisor can't trap the smc instruction. > I don't remember all the PSCI spec details, but I think there was some > provision for this case i.e. the SMC call could be a HYP call instead. > And if that's not in the spec, then it probably should be added and > implemented as if it was. Well, this depends on the guest taking an undefined instruction exception on the smc, then deciding to issue an hvc instead and *then* having the hypervisor somehow translate that into a PSCI invocation. It could work, but it sounds easy to mess up and relies on the PSCI firmware co-existing with things like kvm. > > If that situation requires a pen, I see no benefit from having two boot > > schemes where one of them would work in every case. > > We always have the choice between several schemes in device drivers for > example, depending on the hardware generation. Yet we always implement > the better scheme for the newest hardware for performance reasons, even > if an older one could work in all cases. Again, I totally agree when it comes to things like poweroff and hotplug but for booting I don't think we gain much from having multiple implementations for a single platform. Hopefully this is moot -- see below. > A holding pen is a rather stupid scheme. Please let's try to do without > it if possible. I've just hacked up Rob's suggestion and it seems to be working, so I'll post a pen-less v2 tomorrow. The hotplug/reboot code can come later when we have something host-side that we can use (could be PSCI). Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCW-00068J-Ij; Fri, 03 May 2013 12:35:00 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T06ti-0001i9-2L for xen-arm@lists.xensource.com; Sat, 11 Aug 2012 08:18:14 +0000 X-Env-Sender: maheen_butt26@yahoo.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1344673086!8714448!1 X-Originating-IP: [98.138.91.48] X-SpamReason: No, hits=0.7 required=7.0 tests=FROM_HAS_ULINE_NUMS, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17647 invoked from network); 11 Aug 2012 08:18:07 -0000 Received: from nm13-vm0.bullet.mail.ne1.yahoo.com (HELO nm13-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.48) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Aug 2012 08:18:07 -0000 Received: from [98.138.90.57] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 11 Aug 2012 08:18:05 -0000 Received: from [98.138.226.165] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 11 Aug 2012 08:18:05 -0000 Received: from [127.0.0.1] by omp1066.mail.ne1.yahoo.com with NNFMP; 11 Aug 2012 08:18:05 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 712341.25560.bm@omp1066.mail.ne1.yahoo.com Received: (qmail 40619 invoked by uid 60001); 11 Aug 2012 08:18:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1344673085; bh=G8QAFl16s6JvcvE1hR0PLoEy7fOm5RA2c1lBiRseBm8=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ARA0DRjq5yarF0eNCWCRblLvG/4588/llRsUm8kM5U7TgFaeoQ2tMoKzOeC9pkAQ01o8FWVmA2dqr6rEZPc4vITIOdizLoNlPMu4NB9d+Mpz2FZwp4OGtMyA9Eg+G/RVEGgDNhABikdg9obXp4W3CkBAK/TEEbj+82n/NyvHNYA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=f0NFTr6rBqU6pgSEaB0MPjbW04kgThToTt81VMoy11ZsnHIuLZwnCq5j742iM+bwtfNQUUYWLmEIg8k9lsRv9T3noKrrddDt3eSc1xwZDRHy0XMHNjHD07o+mgpRVXt3hQOr/Vze7Oo7rPQ7H7nLZiiNkEn4lJIqLcg7qwQTALg=; X-YMail-OSG: Brqd9icVM1ka3kWsYwF_SUrI44wlJsvgz.BtL7.MHn7Zeg. B6ypOGhA3EZV8wE_JCafxjucRwFpDlpXp_pQvabIrzKjYlpAYVZwlCfZYYnM kah55aoStXu6pXOBsIJVpvSHD4wiBFzDZTxM8yryVnJTMPjJn2XqTAIsGUNV 1tKRv_nrx0XotnMw86cUv7qHc.YpAlGPsJyRjxrJ2qI4cT0hvFYPTCcLWrGn uvx.t4wcdNy2pY7eQPGCXu4XjhkAlN2uwrNb50gHp4MJei7KD8HjchFkCi_r KS3UIw8XGhIoJW6FskdgllMFa1UUtyEJeIt1v3fM7TW3A3p4mAHC85B7HVSO KWcGOn4KXBij3tl1y6VLX1sUiZluTaRCRqYrnccG9SqkK4jcDsfwqz8yric3 LxkKRDIJADw18jp9fxZy7uEVTS18.DtOP8OKO0DtTuH1cHcLeukbotpvMT97 Kk5azYT_vhkwQG3KtSpWEK4_9jZhSLQlKDKycUGZoosz0HMHOe98LTp.7tK1 XrOF45Hlb9mclrDJI9tK1g__HjLHWa5rC05WnwluSEF9JA8.QAQXswqwA6V7 mZPAr Received: from [58.27.199.186] by web126005.mail.ne1.yahoo.com via HTTP; Sat, 11 Aug 2012 01:18:05 PDT X-Mailer: YahooMailWebService/0.8.120.356233 References: <1344577500.65644.YahooMailNeo@web126003.mail.ne1.yahoo.com> <5024D27C.4080107@xen.org> Message-ID: <1344673085.39641.YahooMailNeo@web126005.mail.ne1.yahoo.com> Date: Sat, 11 Aug 2012 01:18:05 -0700 (PDT) From: maheen butt To: Stefano Stabellini In-Reply-To: MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: "xen-arm@lists.xensource.com" , "keir@xen.org" , "community.manager@xen.org" Subject: Re: [XenARM] Xen-ARM and paravirt_ops? X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: maheen butt List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org ________________________________ From: Stefano Stabellini To: maheen_butt26@yahoo.com = Cc: Stefano Stabellini ; xen-arm@lists.xe= nsource.com; sbuk.suh@samsung.com; keir@xen.org; community.manager@xen.org = Sent: Friday, August 10, 2012 2:59 PM Subject: Re: Xen-ARM and paravirt_ops? On Fri, 10 Aug 2012, maheen butt wrote: > Hi, > I came to know from Xen-ARM wiki and other related pages that ARM =A0port= is based on=A0 > xen-unstable and it can boot a Linux 3.0 based virtual machine (dom 0). f= or reference > https://lkml.org/lkml/2011/11/29/265 > = > As Xen-ARM can boot Linux 3.0, it means that this hypervisor is using=A0 > paravirt_ops infrastructure of kernel. I want to know that did you explic= itly=A0 > add paravirt_ops support in kernel for ARM? The xen-unstable based ARM port uses the new virtualization extensions introduced recently by ARM. Therefore it requires a Cortex-A15 processor or newer in order to work. On the other hand no paravirt_ops support is necessary in the kernel, as we are using nested paging in hardware. What is the relationship between nested paging and paravirt_ops? paravirt_o= ps is=A0 =A0hypervisor-agnostic interface between the hypervisor and guest kernels w= here as=A0 nested paging increase the performance of hardware virtualization by provid= ing hardware=A0 support for page-table virtualization. Its hard for me to understand relati= onship between two. (the relationship is that if one is present other can be ignored) will you please explain it. > As far as I know paravirt_ops is an infrastructure given by Linux kernel = to support=A0 > hypervisor. and=A0http://wiki.xensource.com/xenwiki/XenParavirtOps=A0tell= s that > at present paravirt_ops is available for x86_32, x86_64 and ia64 architec= tures. > If this the case that you have add support of paravirt_ops in Linux kerne= l for ARM > architecture then what is the level of complexity for adding this kind of= support? The level of complexity is non-trivial, fortunately we managed to avoid it. _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006BC-Ch; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfwp2-0001y0-QE for xen-arm@lists.xen.org; Tue, 04 Dec 2012 18:02:21 +0000 Received: from [85.158.137.99:55843] by server-11.bemta-3.messagelabs.com id 5E/D9-19361-7AA3EB05; Tue, 04 Dec 2012 18:02:15 +0000 X-Env-Sender: nico@fluxnic.net X-Msg-Ref: server-13.tower-217.messagelabs.com!1354644134!17924200!1 X-Originating-IP: [24.201.245.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n,sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9733 invoked from network); 4 Dec 2012 18:02:14 -0000 Received: from relais.videotron.ca (HELO relais.videotron.ca) (24.201.245.36) by server-13.tower-217.messagelabs.com with SMTP; 4 Dec 2012 18:02:14 -0000 MIME-version: 1.0 Received: from xanadu.home ([24.202.213.203]) by VL-VM-MR004.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MEI003MPQ3PRZN0@VL-VM-MR004.ip.videotron.ca> for xen-arm@lists.xen.org; Tue, 04 Dec 2012 13:02:14 -0500 (EST) Date: Tue, 04 Dec 2012 13:02:13 -0500 (EST) From: Nicolas Pitre To: Will Deacon In-reply-to: <20121204171129.GE5314@mudshark.cambridge.arm.com> Message-id: References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Tue, 4 Dec 2012, Will Deacon wrote: > Hi Nicolas, > > On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: > > on the topic of a para-virtualised machine, I think that it should > > simply implement the PSCI calls to bring up CPUs _without_ any holding > > pen nor spinning tables. You issue the appropriate PSCI call with the > > physical address for secondary_startup() as argument and you're done. > > The host intercepts that call and free a new CPU instance in response. > > That's all. > > I'd be happy to go with this suggestion if it wasn't for one thing: > platforms that do not implement a secure mode. For these platforms, smc will > be an undefined instruction at the exception level where it is executed and > therefore cannot be trapped by the hypervisor. Really? I thought the hypervisor could virtualize SMC calls. Or is that considered a security hazard? I don't remember all the PSCI spec details, but I think there was some provision for this case i.e. the SMC call could be a HYP call instead. And if that's not in the spec, then it probably should be added and implemented as if it was. > If that situation requires a pen, I see no benefit from having two boot > schemes where one of them would work in every case. We always have the choice between several schemes in device drivers for example, depending on the hardware generation. Yet we always implement the better scheme for the newest hardware for performance reasons, even if an older one could work in all cases. A holding pen is a rather stupid scheme. Please let's try to do without it if possible. Nicolas _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006C4-GW; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfx1G-0003RQ-72 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 18:14:58 +0000 Received: from [85.158.138.51:52675] by server-7.bemta-3.messagelabs.com id 15/51-01713-1AD3EB05; Tue, 04 Dec 2012 18:14:57 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1354644896!27361066!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5053 invoked from network); 4 Dec 2012 18:14:56 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-16.tower-174.messagelabs.com with SMTP; 4 Dec 2012 18:14:56 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4IElUO013015; Tue, 4 Dec 2012 18:14:47 GMT Date: Tue, 4 Dec 2012 18:14:46 +0000 From: Will Deacon To: Nicolas Pitre Message-ID: <20121204181446.GJ5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Tue, Dec 04, 2012 at 06:02:13PM +0000, Nicolas Pitre wrote: > On Tue, 4 Dec 2012, Will Deacon wrote: > > > Hi Nicolas, > > > > On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: > > > on the topic of a para-virtualised machine, I think that it should > > > simply implement the PSCI calls to bring up CPUs _without_ any holding > > > pen nor spinning tables. You issue the appropriate PSCI call with the > > > physical address for secondary_startup() as argument and you're done. > > > The host intercepts that call and free a new CPU instance in response. > > > That's all. > > > > I'd be happy to go with this suggestion if it wasn't for one thing: > > platforms that do not implement a secure mode. For these platforms, smc will > > be an undefined instruction at the exception level where it is executed and > > therefore cannot be trapped by the hypervisor. > > Really? I thought the hypervisor could virtualize SMC calls. Or is > that considered a security hazard? If the security extensions aren't implemented, the hypervisor can't trap the smc instruction. > I don't remember all the PSCI spec details, but I think there was some > provision for this case i.e. the SMC call could be a HYP call instead. > And if that's not in the spec, then it probably should be added and > implemented as if it was. Well, this depends on the guest taking an undefined instruction exception on the smc, then deciding to issue an hvc instead and *then* having the hypervisor somehow translate that into a PSCI invocation. It could work, but it sounds easy to mess up and relies on the PSCI firmware co-existing with things like kvm. > > If that situation requires a pen, I see no benefit from having two boot > > schemes where one of them would work in every case. > > We always have the choice between several schemes in device drivers for > example, depending on the hardware generation. Yet we always implement > the better scheme for the newest hardware for performance reasons, even > if an older one could work in all cases. Again, I totally agree when it comes to things like poweroff and hotplug but for booting I don't think we gain much from having multiple implementations for a single platform. Hopefully this is moot -- see below. > A holding pen is a rather stupid scheme. Please let's try to do without > it if possible. I've just hacked up Rob's suggestion and it seems to be working, so I'll post a pen-less v2 tomorrow. The hotplug/reboot code can come later when we have something host-side that we can use (could be PSCI). Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-00068b-C8; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfaCN-00043K-Ul for xen-arm@lists.xen.org; Mon, 03 Dec 2012 17:52:56 +0000 Received: from [193.109.254.147:12159] by server-5.bemta-14.messagelabs.com id C9/D2-10257-7F6ECB05; Mon, 03 Dec 2012 17:52:55 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1354557174!8826700!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1219 invoked from network); 3 Dec 2012 17:52:54 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-13.tower-27.messagelabs.com with SMTP; 3 Dec 2012 17:52:54 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB3Hqh53002346; Mon, 3 Dec 2012 17:52:43 GMT Received: by mudshark.cambridge.arm.com (Postfix, from userid 1000) id 18F56C2A9E; Mon, 3 Dec 2012 17:52:41 +0000 (GMT) From: Will Deacon To: linux-arm-kernel@lists.infradead.org Date: Mon, 3 Dec 2012 17:52:38 +0000 Message-Id: <1354557160-20144-1-git-send-email-will.deacon@arm.com> X-Mailer: git-send-email 1.8.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, Will Deacon , arnd@arnd.de Subject: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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: , MIME-Version: 1.0 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 Hello, When running Linux on a para-virtualised platform (that is, one where the guest is aware that it is dealing with virtual devices sitting on things like virtio or xenbus) we require very little in the way of platform code and piggy-backing on top of an existing platform can require a lot of device emulation for very little gain. These two patches introduce mach-virt: a very simple, DT-based machine which can be used with kvmtool in conjunction with virtio-based devices. It's not hard to imagine the same machine being targetted by Xen, which currently emulates a minimal variant of the vexpress platform. Note that this patch series depends on the timer rework from Mark Rutland, posted on Friday: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/135651.html All feedback welcome. We suspect that most controversy will be around the name of the thing :) Will Marc Zyngier (2): ARM: Dummy Virtual Machine platform support ARM: SMP support for mach-virt arch/arm/Kconfig | 2 + arch/arm/Makefile | 1 + arch/arm/mach-virt/Kconfig | 9 ++ arch/arm/mach-virt/Makefile | 6 ++ arch/arm/mach-virt/headsmp.S | 38 ++++++++ arch/arm/mach-virt/platsmp.c | 205 +++++++++++++++++++++++++++++++++++++++++++ arch/arm/mach-virt/virt.c | 71 +++++++++++++++ 7 files changed, 332 insertions(+) create mode 100644 arch/arm/mach-virt/Kconfig create mode 100644 arch/arm/mach-virt/Makefile create mode 100644 arch/arm/mach-virt/headsmp.S create mode 100644 arch/arm/mach-virt/platsmp.c create mode 100644 arch/arm/mach-virt/virt.c -- 1.8.0 _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069O-6a; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TftF3-0004F9-RS for xen-arm@lists.xen.org; Tue, 04 Dec 2012 14:12:58 +0000 Received: from [193.109.254.147:23675] by server-1.bemta-14.messagelabs.com id 49/05-25314-9E40EB05; Tue, 04 Dec 2012 14:12:57 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1354630346!8650563!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=2.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7348 invoked from network); 4 Dec 2012 14:12:28 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2012 14:12:28 -0000 Received: by mail-oa0-f45.google.com with SMTP id i18so4713956oag.32 for ; Tue, 04 Dec 2012 06:12:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Ypd2kU+KEfGTg+IlRTM13tdni0pWw4IQjIPXHn4pjcE=; b=m2YtgSuxaoRS4RFAa5xA7lBqwH9VnJ2kf4FzUeJtEo728XXE/NcaxnUM9Vu7ewXNRp ICC1aoupByAnkgDuG1f9gFpIhiAqz3hrQojXP5DtePrenAxFVSRz+sYVyuXBjtQWlGsI T0IKEU/frfA6+FXsiGReEklec8xawx3qFy0O6Jw+fKKd3VlIKtzt03zZHzOyDJkVLBkc 2+6BWVj50CwtpYLwxi8+sjUeyovntEMlMqsrPCyyl1eTX3D2I9SzHPyslbZoDHSptZJC Z/sXtIppIa3DYeAJVVcuNGWbIVfqhCrPFdtu24m8srsxkEsgI4kXEHPOAJR1K6iEZ6Hb sKAw== Received: by 10.60.13.198 with SMTP id j6mr11439492oec.51.1354630346441; Tue, 04 Dec 2012 06:12:26 -0800 (PST) Received: from [192.168.1.103] (65-36-73-129.dyn.grandenetworks.net. [65.36.73.129]) by mx.google.com with ESMTPS id hz6sm853132obb.1.2012.12.04.06.12.23 (version=SSLv3 cipher=OTHER); Tue, 04 Dec 2012 06:12:25 -0800 (PST) Message-ID: <50BE04C6.4070602@gmail.com> Date: Tue, 04 Dec 2012 08:12:22 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> In-Reply-To: <20121204123001.GL23368@mudshark.cambridge.arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Marc Zyngier , "xen-arm@lists.xen.org" , Mark Rutland , "arnd@arndb.de" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 12/04/2012 06:30 AM, Will Deacon wrote: > Hi Rob, > > [fixing Arnd's address, as I apparently can't spell] > > On Mon, Dec 03, 2012 at 09:54:09PM +0000, Rob Herring wrote: >> On 12/03/2012 11:52 AM, Will Deacon wrote: >>> When running Linux on a para-virtualised platform (that is, one where >>> the guest is aware that it is dealing with virtual devices sitting on >>> things like virtio or xenbus) we require very little in the way of >>> platform code and piggy-backing on top of an existing platform can >>> require a lot of device emulation for very little gain. >>> >>> These two patches introduce mach-virt: a very simple, DT-based machine >>> which can be used with kvmtool in conjunction with virtio-based devices. >>> It's not hard to imagine the same machine being targetted by Xen, which >>> currently emulates a minimal variant of the vexpress platform. >>> >>> Note that this patch series depends on the timer rework from Mark >>> Rutland, posted on Friday: >>> >>> http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/135651.html >>> >>> All feedback welcome. We suspect that most controversy will be around >>> the name of the thing :) >> >> We've discussed this before at conferences. I don't know that we >> concluded this wasn't needed, but it certainly leaned that direction. > > I too leaned that direction before I started looking at kvm in detail and, > since then, I've changed my mind when it comes to para-virtualisation. > > The reason for this is that there is absolutely no reason to emulate some > components of a real platform and then bolt virtual devices onto it once > you've got enough to get it going. It leads to a right royal mess in > userspace, where you have to write a load of non-reusable emulation code and > it leads to churn in the kernel because you're constantly at odds with > people trying to develop the platform code based on the actual hardware > they have. > > With a virtualisation-capable ARMv7 system, all you *need* to boot SMP > Debian is: > > - A v7 CPU with virt extensions > - vGIC > - architected timers > > *everything* else can be described using virtio devices in the device-tree, > essentially allowing you to generate platforms based on the above and boot > the same kernel on them. > >> So what has changed? You're not going to save code space because we're >> building multiple platforms together. You'll save some boot time, but a >> stripped down dtb with only the minimal peripherals would probably save >> nearly as much time. > > It's really got nothing to do with code space or boot speed. What it *is* > about is avoiding the tight coupling with a real platform and suffering as a > result. Yes, you can strip down the DT for a real platform but you'll likely > still have to emulate things like the SP804 in order to boot. That's not to > mention any platform-specific system register interfaces which are required > early on. > > We can't even re-use the socfpga code (which is incredibly minimal) without > emulating the dw_apb_timer. That to me is highlighting where we need to do more work on DT driving the initialization. The platforms are still aware of what kind of timers and interrupt controllers are present. They should not be. There's work in progress for both of those. Lorenzo's DT MPIDR patches should trim down smp code some. The DT spin table code could probably be common. I think I could use it on highbank as well. If we decide the pen code stays, then it should be common rather than creating yet another copy. Rob _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-0006AE-TO; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfwEU-0008G3-38 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:24:34 +0000 Received: from [85.158.143.99:8839] by server-3.bemta-4.messagelabs.com id A6/FD-06841-1D13EB05; Tue, 04 Dec 2012 17:24:33 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1354641872!28023425!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27522 invoked from network); 4 Dec 2012 17:24:32 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-15.tower-216.messagelabs.com with SMTP; 4 Dec 2012 17:24:32 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4HOPUO012122; Tue, 4 Dec 2012 17:24:25 GMT Date: Tue, 4 Dec 2012 17:24:24 +0000 From: Will Deacon To: Russell King - ARM Linux Message-ID: <20121204172424.GG5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <20121204163555.GH14363@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20121204163555.GH14363@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 04:35:55PM +0000, Russell King - ARM Linux wrote: > On Tue, Dec 04, 2012 at 04:11:13PM +0000, Will Deacon wrote: > > The problem you're describing actually happens when the 3.6 kernel onlines > > all of the CPUs, because now it has no way to hotplug them off safely. This > > is also an issue with non-virtualised hardware but we could solve it for the > > virtual platform by having a para-virtualised device for doing CPU hotplug. > > That situation exists on ARM Ltd platforms where there's no way to > properly return them back to the boot loader. We should not be forcing > this ARM Ltd platform deficiency onto other platforms as part of a > "design", even virtual platforms. > > Most other real-world platforms out there have a way to power off the > unused secondary CPUs - Tegra and OMAP both do. If a virtual machine powers off a virtual CPU, I doubt we want to power of its corresponding CPU -- that logic can remain in the host. All we need to do is kill the virtual CPU thread, which we can do easily enough. Booting is the more difficult problem because we introduce a reliance on a virtual device being ready incredibly early, essentially hardcoding part of the virtual machine. > As far as virtual platforms go, how secondary CPUs are dealt with should > already have been solved; I really can't imagine that KVM and XEN on > other architectures end up with CPUs spinning in a loop inside the guest > kernel waiting for the guest OS to ask them to boot. Neither can I imagine > that KVM and XEN end up with CPUs spinning in the guest OS when CPUs are > asked to be hot-unplugged. So neither kvmtool or qemu currently support hotplug for kvm guests on any architectures from what I can tell. Furthermore, kvmtool on ppc (at least) uses a secondary spinning loop at a fixed offset into the kernel image. I don't think we should really pay much attention to those other architectures in this regard! > > > That happens _before_ the DT has been parsed, so any memreserve stuff > > > will be ignored. And it's at that point that your "offline" secondary > > > CPUs will have their instructions overwritten. > > > > > > That's fine if the pen ends up being at the same place but that's not > > > something we guarantee. > > > > Having CPUs in limbo between the bootloader the being online in the kernel > > is something we should just avoid. Isn't that pen __init anyway? > > If you have hotplug enabled, all the secondary bringup code should be > in the __cpuinit and __cpuinitdata sections. Right, but if booting a !HOTPLUG kernel via kexec, surely we'd have to clear that pen of CPUs? Will _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006EM-Ob; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGZz-0005Ej-QQ for xen-arm@lists.xen.org; Wed, 05 Dec 2012 15:08:08 +0000 Received: from [85.158.139.211:15888] by server-9.bemta-5.messagelabs.com id 82/95-29295-6536FB05; Wed, 05 Dec 2012 15:08:06 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1354720066!19148548!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32337 invoked from network); 5 Dec 2012 15:07:48 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-14.tower-206.messagelabs.com with SMTP; 5 Dec 2012 15:07:48 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB5F7XUO006188; Wed, 5 Dec 2012 15:07:33 GMT Date: Wed, 5 Dec 2012 15:07:32 +0000 From: Will Deacon To: Catalin Marinas Message-ID: <20121205150732.GJ22385@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Nicolas Pitre , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Wed, Dec 05, 2012 at 02:52:57PM +0000, Catalin Marinas wrote: > On 4 December 2012 18:14, Will Deacon wrote: > > Well, this depends on the guest taking an undefined instruction exception on > > the smc, then deciding to issue an hvc instead and *then* having the > > hypervisor somehow translate that into a PSCI invocation. It could work, but > > it sounds easy to mess up and relies on the PSCI firmware co-existing with > > things like kvm. > > We can have enable-method DT entries independent of the SoC and one of > them can be psci-hvc. As soon as the support is there in the upper layers, we can do that. > Just for clarification, AArch32 with virtualisation mandates the > security extensions, so the SMC can be trapped. On AArch64 it is a bit > tricky since the presence of EL3 is not mandate, in which case SMC > would undef (don't as why ;). That's where we can have different > enable methods specified via the DT. Not entirely true: only ARMv7 mandates the security extensions in this manner. You can still have ARMv8 CPUs running AArch32 code without the security extensions. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069V-AA; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfv5l-0004VH-Qb for xen-arm@lists.xen.org; Tue, 04 Dec 2012 16:11:30 +0000 Received: from [85.158.137.99:9570] by server-6.bemta-3.messagelabs.com id 86/A9-28265-0B02EB05; Tue, 04 Dec 2012 16:11:28 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1354637487!17903399!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31658 invoked from network); 4 Dec 2012 16:11:28 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-4.tower-217.messagelabs.com with SMTP; 4 Dec 2012 16:11:28 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4GBEUO010544; Tue, 4 Dec 2012 16:11:14 GMT Date: Tue, 4 Dec 2012 16:11:13 +0000 From: Will Deacon To: Russell King - ARM Linux Message-ID: <20121204161113.GT23368@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20121204143724.GF14363@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: > On Tue, Dec 04, 2012 at 01:40:10PM +0000, Will Deacon wrote: > > On Tue, Dec 04, 2012 at 01:33:26PM +0000, Russell King - ARM Linux wrote: > > > The memory that these 'offline' CPUs is executing then gets overwritten, > > > and that's game over for those CPUs. > > > > That's not strictly true. The device-tree passed to the kernel should have a > > /memreserve/ entry for the SMP pen to avoid exactly this scenario. In real > > hardware, this still sucks because you have spinning CPUs burning up power > > but that's not such a problem with a virtual platform. > > Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec > into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which > will be located at 32K into the RAM. The v3.7 kernel will also want to > occupy the same place. At some point you have to overwrite the v3.6 > kernel with the v3.7 kernel image. If the 3.6 kernel didn't bring those CPUs online, they will sit in the bootloader pen (out of the way of the kernel image) rather than the kernel pen so I don't think there will be a problem. The problem you're describing actually happens when the 3.6 kernel onlines all of the CPUs, because now it has no way to hotplug them off safely. This is also an issue with non-virtualised hardware but we could solve it for the virtual platform by having a para-virtualised device for doing CPU hotplug. > That happens _before_ the DT has been parsed, so any memreserve stuff > will be ignored. And it's at that point that your "offline" secondary > CPUs will have their instructions overwritten. > > That's fine if the pen ends up being at the same place but that's not > something we guarantee. Having CPUs in limbo between the bootloader the being online in the kernel is something we should just avoid. Isn't that pen __init anyway? Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-00068b-C8; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfaCN-00043K-Ul for xen-arm@lists.xen.org; Mon, 03 Dec 2012 17:52:56 +0000 Received: from [193.109.254.147:12159] by server-5.bemta-14.messagelabs.com id C9/D2-10257-7F6ECB05; Mon, 03 Dec 2012 17:52:55 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1354557174!8826700!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1219 invoked from network); 3 Dec 2012 17:52:54 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-13.tower-27.messagelabs.com with SMTP; 3 Dec 2012 17:52:54 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB3Hqh53002346; Mon, 3 Dec 2012 17:52:43 GMT Received: by mudshark.cambridge.arm.com (Postfix, from userid 1000) id 18F56C2A9E; Mon, 3 Dec 2012 17:52:41 +0000 (GMT) From: Will Deacon To: linux-arm-kernel@lists.infradead.org Date: Mon, 3 Dec 2012 17:52:38 +0000 Message-Id: <1354557160-20144-1-git-send-email-will.deacon@arm.com> X-Mailer: git-send-email 1.8.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, Will Deacon , arnd@arnd.de Subject: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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: , MIME-Version: 1.0 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 Hello, When running Linux on a para-virtualised platform (that is, one where the guest is aware that it is dealing with virtual devices sitting on things like virtio or xenbus) we require very little in the way of platform code and piggy-backing on top of an existing platform can require a lot of device emulation for very little gain. These two patches introduce mach-virt: a very simple, DT-based machine which can be used with kvmtool in conjunction with virtio-based devices. It's not hard to imagine the same machine being targetted by Xen, which currently emulates a minimal variant of the vexpress platform. Note that this patch series depends on the timer rework from Mark Rutland, posted on Friday: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/135651.html All feedback welcome. We suspect that most controversy will be around the name of the thing :) Will Marc Zyngier (2): ARM: Dummy Virtual Machine platform support ARM: SMP support for mach-virt arch/arm/Kconfig | 2 + arch/arm/Makefile | 1 + arch/arm/mach-virt/Kconfig | 9 ++ arch/arm/mach-virt/Makefile | 6 ++ arch/arm/mach-virt/headsmp.S | 38 ++++++++ arch/arm/mach-virt/platsmp.c | 205 +++++++++++++++++++++++++++++++++++++++++++ arch/arm/mach-virt/virt.c | 71 +++++++++++++++ 7 files changed, 332 insertions(+) create mode 100644 arch/arm/mach-virt/Kconfig create mode 100644 arch/arm/mach-virt/Makefile create mode 100644 arch/arm/mach-virt/headsmp.S create mode 100644 arch/arm/mach-virt/platsmp.c create mode 100644 arch/arm/mach-virt/virt.c -- 1.8.0 _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCW-00068J-Ij; Fri, 03 May 2013 12:35:00 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T06ti-0001i9-2L for xen-arm@lists.xensource.com; Sat, 11 Aug 2012 08:18:14 +0000 X-Env-Sender: maheen_butt26@yahoo.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1344673086!8714448!1 X-Originating-IP: [98.138.91.48] X-SpamReason: No, hits=0.7 required=7.0 tests=FROM_HAS_ULINE_NUMS, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17647 invoked from network); 11 Aug 2012 08:18:07 -0000 Received: from nm13-vm0.bullet.mail.ne1.yahoo.com (HELO nm13-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.48) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Aug 2012 08:18:07 -0000 Received: from [98.138.90.57] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 11 Aug 2012 08:18:05 -0000 Received: from [98.138.226.165] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 11 Aug 2012 08:18:05 -0000 Received: from [127.0.0.1] by omp1066.mail.ne1.yahoo.com with NNFMP; 11 Aug 2012 08:18:05 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 712341.25560.bm@omp1066.mail.ne1.yahoo.com Received: (qmail 40619 invoked by uid 60001); 11 Aug 2012 08:18:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1344673085; bh=G8QAFl16s6JvcvE1hR0PLoEy7fOm5RA2c1lBiRseBm8=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ARA0DRjq5yarF0eNCWCRblLvG/4588/llRsUm8kM5U7TgFaeoQ2tMoKzOeC9pkAQ01o8FWVmA2dqr6rEZPc4vITIOdizLoNlPMu4NB9d+Mpz2FZwp4OGtMyA9Eg+G/RVEGgDNhABikdg9obXp4W3CkBAK/TEEbj+82n/NyvHNYA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=f0NFTr6rBqU6pgSEaB0MPjbW04kgThToTt81VMoy11ZsnHIuLZwnCq5j742iM+bwtfNQUUYWLmEIg8k9lsRv9T3noKrrddDt3eSc1xwZDRHy0XMHNjHD07o+mgpRVXt3hQOr/Vze7Oo7rPQ7H7nLZiiNkEn4lJIqLcg7qwQTALg=; X-YMail-OSG: Brqd9icVM1ka3kWsYwF_SUrI44wlJsvgz.BtL7.MHn7Zeg. B6ypOGhA3EZV8wE_JCafxjucRwFpDlpXp_pQvabIrzKjYlpAYVZwlCfZYYnM kah55aoStXu6pXOBsIJVpvSHD4wiBFzDZTxM8yryVnJTMPjJn2XqTAIsGUNV 1tKRv_nrx0XotnMw86cUv7qHc.YpAlGPsJyRjxrJ2qI4cT0hvFYPTCcLWrGn uvx.t4wcdNy2pY7eQPGCXu4XjhkAlN2uwrNb50gHp4MJei7KD8HjchFkCi_r KS3UIw8XGhIoJW6FskdgllMFa1UUtyEJeIt1v3fM7TW3A3p4mAHC85B7HVSO KWcGOn4KXBij3tl1y6VLX1sUiZluTaRCRqYrnccG9SqkK4jcDsfwqz8yric3 LxkKRDIJADw18jp9fxZy7uEVTS18.DtOP8OKO0DtTuH1cHcLeukbotpvMT97 Kk5azYT_vhkwQG3KtSpWEK4_9jZhSLQlKDKycUGZoosz0HMHOe98LTp.7tK1 XrOF45Hlb9mclrDJI9tK1g__HjLHWa5rC05WnwluSEF9JA8.QAQXswqwA6V7 mZPAr Received: from [58.27.199.186] by web126005.mail.ne1.yahoo.com via HTTP; Sat, 11 Aug 2012 01:18:05 PDT X-Mailer: YahooMailWebService/0.8.120.356233 References: <1344577500.65644.YahooMailNeo@web126003.mail.ne1.yahoo.com> <5024D27C.4080107@xen.org> Message-ID: <1344673085.39641.YahooMailNeo@web126005.mail.ne1.yahoo.com> Date: Sat, 11 Aug 2012 01:18:05 -0700 (PDT) From: maheen butt To: Stefano Stabellini In-Reply-To: MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: "xen-arm@lists.xensource.com" , "keir@xen.org" , "community.manager@xen.org" Subject: Re: [XenARM] Xen-ARM and paravirt_ops? X-BeenThere: xen-arm@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: maheen butt List-Id: List for Xen ARM developers and users List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org ________________________________ From: Stefano Stabellini To: maheen_butt26@yahoo.com = Cc: Stefano Stabellini ; xen-arm@lists.xe= nsource.com; sbuk.suh@samsung.com; keir@xen.org; community.manager@xen.org = Sent: Friday, August 10, 2012 2:59 PM Subject: Re: Xen-ARM and paravirt_ops? On Fri, 10 Aug 2012, maheen butt wrote: > Hi, > I came to know from Xen-ARM wiki and other related pages that ARM =A0port= is based on=A0 > xen-unstable and it can boot a Linux 3.0 based virtual machine (dom 0). f= or reference > https://lkml.org/lkml/2011/11/29/265 > = > As Xen-ARM can boot Linux 3.0, it means that this hypervisor is using=A0 > paravirt_ops infrastructure of kernel. I want to know that did you explic= itly=A0 > add paravirt_ops support in kernel for ARM? The xen-unstable based ARM port uses the new virtualization extensions introduced recently by ARM. Therefore it requires a Cortex-A15 processor or newer in order to work. On the other hand no paravirt_ops support is necessary in the kernel, as we are using nested paging in hardware. What is the relationship between nested paging and paravirt_ops? paravirt_o= ps is=A0 =A0hypervisor-agnostic interface between the hypervisor and guest kernels w= here as=A0 nested paging increase the performance of hardware virtualization by provid= ing hardware=A0 support for page-table virtualization. Its hard for me to understand relati= onship between two. (the relationship is that if one is present other can be ignored) will you please explain it. > As far as I know paravirt_ops is an infrastructure given by Linux kernel = to support=A0 > hypervisor. and=A0http://wiki.xensource.com/xenwiki/XenParavirtOps=A0tell= s that > at present paravirt_ops is available for x86_32, x86_64 and ia64 architec= tures. > If this the case that you have add support of paravirt_ops in Linux kerne= l for ARM > architecture then what is the level of complexity for adding this kind of= support? The level of complexity is non-trivial, fortunately we managed to avoid it. _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-000698-VT; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfro2-0008Cb-LG for xen-arm@lists.xen.org; Tue, 04 Dec 2012 12:40:59 +0000 Received: from [85.158.139.83:52943] by server-1.bemta-5.messagelabs.com id E2/82-09311-95FEDB05; Tue, 04 Dec 2012 12:40:57 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1354624856!28338104!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14430 invoked from network); 4 Dec 2012 12:40:56 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-3.tower-182.messagelabs.com with SMTP; 4 Dec 2012 12:40:56 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4CemUO006233; Tue, 4 Dec 2012 12:40:48 GMT Date: Tue, 4 Dec 2012 12:40:47 +0000 From: Will Deacon To: Rob Herring Message-ID: <20121204124047.GM23368@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50BD1FD7.9040000@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Marc Zyngier , "xen-arm@lists.xen.org" , Mark Rutland , "arnd@arndb.de" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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, Dec 03, 2012 at 09:55:35PM +0000, Rob Herring wrote: > On 12/03/2012 11:52 AM, Will Deacon wrote: > > From: Marc Zyngier > > > > This patch adds support for SMP to mach-virt. > > > > Signed-off-by: Marc Zyngier > > Signed-off-by: Will Deacon > > [...] > > +/* > > + * This provides a "holding pen" into which all secondary cores are held > > + * until we're ready for them to initialise. > > + */ > > +ENTRY(virt_secondary_startup) > > + mrc p15, 0, r0, c0, c0, 5 > > + and r0, r0, #15 > > + adr r4, 1f > > + ldmia r4, {r5, r6} > > + sub r4, r4, r5 > > + add r6, r6, r4 > > +pen: ldr r7, [r6] > > + cmp r7, r0 > > + bne pen > > Why is the pen is needed? It should only be needed for hotplug on > systems that can't reset their cores. I'd hope you could design good > virtual h/w. It's not so much about designing good virtual h/w as it is avoiding tying the platform to it. What we don't want is to mandate that in order to boot this machine, you *must* implement an emulation of some virtual power-controller or SMP booting device. If we go down that route, there's less advantage from having the virtual platform in the first place. There's also less of a problem with the pen approach to booting because ultimately the virtual CPUs executing there are just pthreads and will be scheduled appropriately by the hypervisor (in contrast to a real system where there may be concerns about power consumption and memory bandwidth). For hotplug, sure, we could have an *optional* virtio-based device for dealing with that if we want to. We could even have some early probing code for it and use it for SMP boot if we find a matching DT node, but we'd still need to keep the pen code lying around as a fallback. > > +/* > > + * Enumerate the possible CPU set from the device tree. > > + */ > > +static void __init virt_smp_init_cpus(void) > > +{ > > + const char *enable_method; > > + struct device_node *dn = NULL; > > + int cpu = 0; > > + u32 release_addr; > > + > > + while ((dn = of_find_node_by_type(dn, "cpu"))) { > > + if (cpu >= NR_CPUS) > > + goto next; > > + > > + /* > > + * We currently support only the "spin-table" enable-method. > > + */ > > + enable_method = of_get_property(dn, "enable-method", NULL); > > + if (!enable_method || strcmp(enable_method, "spin-table")) { > > Are these documented? It's part of the EPAPR spec iirc and follows the booting protocol used by arm64. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-00069e-DP; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfvdG-0006ht-Fu for xen-arm@lists.xen.org; Tue, 04 Dec 2012 16:46:06 +0000 Received: from [193.109.254.147:53682] by server-3.bemta-14.messagelabs.com id 09/BC-01317-DC82EB05; Tue, 04 Dec 2012 16:46:05 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1354639563!1722852!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=2.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1459 invoked from network); 4 Dec 2012 16:46:04 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2012 16:46:04 -0000 Received: by mail-ob0-f173.google.com with SMTP id xn12so4732940obc.32 for ; Tue, 04 Dec 2012 08:46:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=GbHENo4n6omIyynTU/ssEIwJtCrZnw653XDus6kx1/Y=; b=kEuR6PqIUNAIQUicWHHT/DwNsNvnC+iF7cWhMGPnVlxt1WEhI5dKDCjJRoncarOyMy iW/+m+Rmqe4k172W6Gy4u3lRapW4SRLpbIU5lyniM4+nEalaxgsP/9UWvIqrmlPQX5HM WCjr9MW7vcFf6605S/2Jk3xpq1sFB0O9QGwHO3/0JLH8Kvhvtuy/9C1fS3FW1TCfMcOn BEdPajG0ru4h9upIhPxotCMMJxwRQdI/em8+2sUnWlVqypHfBjSpL3dzvHo9dIS1tSpB rEUG+keU01w4p2iNTQ891tgKsM8vqYgxmLa8aoagLdtPDPZXpCMUXafoWMhqow/mQWUW Vt1A== Received: by 10.60.31.68 with SMTP id y4mr12232592oeh.121.1354639563415; Tue, 04 Dec 2012 08:46:03 -0800 (PST) Received: from [10.10.10.90] ([173.226.190.126]) by mx.google.com with ESMTPS id hg8sm1165756obb.19.2012.12.04.08.45.59 (version=SSLv3 cipher=OTHER); Tue, 04 Dec 2012 08:46:02 -0800 (PST) Message-ID: <50BE28C6.2010403@gmail.com> Date: Tue, 04 Dec 2012 10:45:58 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> In-Reply-To: <20121204161113.GT23368@mudshark.cambridge.arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 12/04/2012 10:11 AM, Will Deacon wrote: > On Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: >> On Tue, Dec 04, 2012 at 01:40:10PM +0000, Will Deacon wrote: >>> On Tue, Dec 04, 2012 at 01:33:26PM +0000, Russell King - ARM Linux wrote: >>>> The memory that these 'offline' CPUs is executing then gets overwritten, >>>> and that's game over for those CPUs. >>> >>> That's not strictly true. The device-tree passed to the kernel should have a >>> /memreserve/ entry for the SMP pen to avoid exactly this scenario. In real >>> hardware, this still sucks because you have spinning CPUs burning up power >>> but that's not such a problem with a virtual platform. >> >> Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec >> into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which >> will be located at 32K into the RAM. The v3.7 kernel will also want to >> occupy the same place. At some point you have to overwrite the v3.6 >> kernel with the v3.7 kernel image. > > If the 3.6 kernel didn't bring those CPUs online, they will sit in the > bootloader pen (out of the way of the kernel image) rather than the kernel > pen so I don't think there will be a problem. > > The problem you're describing actually happens when the 3.6 kernel onlines > all of the CPUs, because now it has no way to hotplug them off safely. This > is also an issue with non-virtualised hardware but we could solve it for the > virtual platform by having a para-virtualised device for doing CPU hotplug. > >> That happens _before_ the DT has been parsed, so any memreserve stuff >> will be ignored. And it's at that point that your "offline" secondary >> CPUs will have their instructions overwritten. >> >> That's fine if the pen ends up being at the same place but that's not >> something we guarantee. > > Having CPUs in limbo between the bootloader the being online in the kernel > is something we should just avoid. Isn't that pen __init anyway? Aren't we mixing 2 pens here? You must have some simple bootloader containing vector table and a pen that the dtb points to, right? The pen you have in the kernel is only needed when hotplug only does a wfi. As you don't yet support hotplug, then you can drop all the kernel pen code. If there is no way to reset the core, then couldn't the hotplug code tear down the cpu setup and just jump back to 0x0 which then returns to the bootloader's pen? Rob _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-00068q-Ij; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfdxu-0002YU-T6 for xen-arm@lists.xen.org; Mon, 03 Dec 2012 21:54:15 +0000 Received: from [85.158.139.83:36358] by server-9.bemta-5.messagelabs.com id C1/74-29295-68F1DB05; Mon, 03 Dec 2012 21:54:14 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1354571652!28264666!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=2.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18388 invoked from network); 3 Dec 2012 21:54:13 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Dec 2012 21:54:13 -0000 Received: by mail-ob0-f173.google.com with SMTP id xn12so3653012obc.32 for ; Mon, 03 Dec 2012 13:54:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=o4Z91y7vpWdaPMY95MbHHdrPxCZ6NyrgHN78QsPT0NA=; b=KKu3LMszDV5G5/LjRHaRAbg8dcUEkH/dWbIS/Zq5p9A/v/2lEf0DKb9e9MK0ot7rlh fuOHh0yVMc6vwRGGTbDlffW087RFwTLNBqiSih6puDQppeYnC1C9yur5CHhSpSaxHxmI sd6LS8JSrT6uCfU1tPvbcm6xDrBqys5eXBofyrp6288yC4KzSNvjooSmx5GbOUICIyHY zRV+FLK3BgPTabjpqBbSczgWZSF5MLb4PFIMslkdwNzB0TZLqXltFMwVmvnhN51JN221 R8U9ZJLTiHOqisWqZYKbEddPC8imUgUCGzj1Ndi/hRqHYpW8hmdYp0Hs30bRzC9Hw4Ve UvVA== Received: by 10.182.152.4 with SMTP id uu4mr5641362obb.85.1354571651668; Mon, 03 Dec 2012 13:54:11 -0800 (PST) Received: from [10.10.10.90] ([173.226.190.126]) by mx.google.com with ESMTPS id c18sm14857097obc.17.2012.12.03.13.54.10 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 13:54:10 -0800 (PST) Message-ID: <50BD1F81.9080304@gmail.com> Date: Mon, 03 Dec 2012 15:54:09 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> In-Reply-To: <1354557160-20144-1-git-send-email-will.deacon@arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, arnd@arnd.de, linux-arm-kernel@lists.infradead.org Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 12/03/2012 11:52 AM, Will Deacon wrote: > Hello, > > When running Linux on a para-virtualised platform (that is, one where > the guest is aware that it is dealing with virtual devices sitting on > things like virtio or xenbus) we require very little in the way of > platform code and piggy-backing on top of an existing platform can > require a lot of device emulation for very little gain. > > These two patches introduce mach-virt: a very simple, DT-based machine > which can be used with kvmtool in conjunction with virtio-based devices. > It's not hard to imagine the same machine being targetted by Xen, which > currently emulates a minimal variant of the vexpress platform. > > Note that this patch series depends on the timer rework from Mark > Rutland, posted on Friday: > > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/135651.html > > All feedback welcome. We suspect that most controversy will be around > the name of the thing :) We've discussed this before at conferences. I don't know that we concluded this wasn't needed, but it certainly leaned that direction. So what has changed? You're not going to save code space because we're building multiple platforms together. You'll save some boot time, but a stripped down dtb with only the minimal peripherals would probably save nearly as much time. However, I do have concerns with using VExpress as the guest. For example, you can't support a non-PAE guest with 4GB of RAM on VExpress (maybe if the vexpress code gets all memory map info from DT). Is this really complete? Will we need reset, poweroff, hotplug, and suspend/resume support for example? Unlike most initial platform submissions which are minimal, I think seeing full support would be useful here. Then we can better gauge how much we are really saving. Rob > > Will > > > Marc Zyngier (2): > ARM: Dummy Virtual Machine platform support > ARM: SMP support for mach-virt > > arch/arm/Kconfig | 2 + > arch/arm/Makefile | 1 + > arch/arm/mach-virt/Kconfig | 9 ++ > arch/arm/mach-virt/Makefile | 6 ++ > arch/arm/mach-virt/headsmp.S | 38 ++++++++ > arch/arm/mach-virt/platsmp.c | 205 +++++++++++++++++++++++++++++++++++++++++++ > arch/arm/mach-virt/virt.c | 71 +++++++++++++++ > 7 files changed, 332 insertions(+) > create mode 100644 arch/arm/mach-virt/Kconfig > create mode 100644 arch/arm/mach-virt/Makefile > create mode 100644 arch/arm/mach-virt/headsmp.S > create mode 100644 arch/arm/mach-virt/platsmp.c > create mode 100644 arch/arm/mach-virt/virt.c > _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCY-00068v-M5; Fri, 03 May 2013 12:35:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfdzJ-0002Yo-TL for xen-arm@lists.xen.org; Mon, 03 Dec 2012 21:55:42 +0000 Received: from [85.158.143.99:3894] by server-2.bemta-4.messagelabs.com id A1/76-28922-DDF1DB05; Mon, 03 Dec 2012 21:55:41 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-8.tower-216.messagelabs.com!1354571738!18130805!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=2.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3576 invoked from network); 3 Dec 2012 21:55:39 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-8.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Dec 2012 21:55:39 -0000 Received: by mail-oa0-f45.google.com with SMTP id i18so3890308oag.32 for ; Mon, 03 Dec 2012 13:55:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=vVB3e0BZ6VCSeV7RRR6+t4jY7LgV0BoytZ0Kr7VY8Nw=; b=lPmaOL4YzoQp80gN/HspDc3nzhbQYf9t7mSLe5tftEUX2dPiAciybkPV1g7n5Kx8Hf 2fsRWyFCkufWlCNKBKDLHLaJ79/2oeM25h/TNj+USoR8IvwA4noGiBYZQH4x5QRUmYe0 HvPHzt1FMDi2RW8TM/xOqRgY33+c0VHiZAmOTM6dkJLaLFyytzubm0Pri7kuUJ2yMYqi dad3F2eI4ZxXBKMKdiObLpUtpocAykmOKOl7YQeZJ36B4hMbOI88kHYxTkXM6pvmZMu8 h2+5S1PrWwA6aFn8sB8RFx50f9AG2gtAaFtFJbWPK91MqTrKxBtJzdtrHaV3eS9Dco7+ 40nA== Received: by 10.182.18.196 with SMTP id y4mr5784627obd.52.1354571738361; Mon, 03 Dec 2012 13:55:38 -0800 (PST) Received: from [10.10.10.90] ([173.226.190.126]) by mx.google.com with ESMTPS id f7sm13037305oef.8.2012.12.03.13.55.36 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 13:55:36 -0800 (PST) Message-ID: <50BD1FD7.9040000@gmail.com> Date: Mon, 03 Dec 2012 15:55:35 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> In-Reply-To: <1354557160-20144-3-git-send-email-will.deacon@arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, arnd@arnd.de, linux-arm-kernel@lists.infradead.org Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 12/03/2012 11:52 AM, Will Deacon wrote: > From: Marc Zyngier > > This patch adds support for SMP to mach-virt. > > Signed-off-by: Marc Zyngier > Signed-off-by: Will Deacon > --- > arch/arm/mach-virt/Makefile | 1 + > arch/arm/mach-virt/headsmp.S | 38 ++++++++ > arch/arm/mach-virt/platsmp.c | 205 +++++++++++++++++++++++++++++++++++++++++++ > arch/arm/mach-virt/virt.c | 6 ++ > 4 files changed, 250 insertions(+) > create mode 100644 arch/arm/mach-virt/headsmp.S > create mode 100644 arch/arm/mach-virt/platsmp.c > > diff --git a/arch/arm/mach-virt/Makefile b/arch/arm/mach-virt/Makefile > index 7ddbfa6..9ce8a28 100644 > --- a/arch/arm/mach-virt/Makefile > +++ b/arch/arm/mach-virt/Makefile > @@ -3,3 +3,4 @@ > # > > obj-y := virt.o > +obj-$(CONFIG_SMP) += platsmp.o headsmp.o > diff --git a/arch/arm/mach-virt/headsmp.S b/arch/arm/mach-virt/headsmp.S > new file mode 100644 > index 0000000..e27afb0 > --- /dev/null > +++ b/arch/arm/mach-virt/headsmp.S > @@ -0,0 +1,38 @@ > +/* > + * Copyright (c) 2012 ARM Limited > + * All Rights Reserved > + * > + * This program is free software; you can redistribute it and/or modify > + * it under the terms of the GNU General Public License version 2 as > + * published by the Free Software Foundation. > + */ > +#include > +#include > + > + __INIT > + > +/* > + * This provides a "holding pen" into which all secondary cores are held > + * until we're ready for them to initialise. > + */ > +ENTRY(virt_secondary_startup) > + mrc p15, 0, r0, c0, c0, 5 > + and r0, r0, #15 > + adr r4, 1f > + ldmia r4, {r5, r6} > + sub r4, r4, r5 > + add r6, r6, r4 > +pen: ldr r7, [r6] > + cmp r7, r0 > + bne pen Why is the pen is needed? It should only be needed for hotplug on systems that can't reset their cores. I'd hope you could design good virtual h/w. > + > + /* > + * we've been released from the holding pen: secondary_stack > + * should now contain the SVC stack for this core > + */ > + b secondary_startup > + > + .align > +1: .long . > + .long pen_release > +ENDPROC(virt_secondary_startup) > diff --git a/arch/arm/mach-virt/platsmp.c b/arch/arm/mach-virt/platsmp.c > new file mode 100644 > index 0000000..fe02f51 > --- /dev/null > +++ b/arch/arm/mach-virt/platsmp.c > @@ -0,0 +1,205 @@ > +/* > + * Dummy Virtual Machine - does what it says on the tin. > + * > + * SMP operations, shamelessly stolen from: > + * arch/arm64/kernel/smp.c > + * > + * Copyright (C) 2012 ARM Ltd > + * Author: Catalin Marinas > + * Author: Will Deacon > + * Author: Marc Zyngier > + * > + * This program is free software; you can redistribute it and/or modify > + * it under the terms of the GNU General Public License version 2 as > + * published by the Free Software Foundation. > + * > + * This program is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > + * GNU General Public License for more details. > + * > + * You should have received a copy of the GNU General Public License > + * along with this program. If not, see . > + */ > + > +#include > +#include > +#include > +#include > +#include > +#include > + > +#include > +#include > +#include > + > +extern void virt_secondary_startup(void); > + > +static DEFINE_RAW_SPINLOCK(boot_lock); > +static phys_addr_t cpu_release_addr[NR_CPUS]; > + > +/* > + * Write secondary_holding_pen_release in a way that is guaranteed to be > + * visible to all observers, irrespective of whether they're taking part > + * in coherency or not. This is necessary for the hotplug code to work > + * reliably. > + */ > +static void __cpuinit write_pen_release(int val) > +{ > + void *start = (void *)&pen_release; > + unsigned long size = sizeof(pen_release); > + > + pen_release = val; > + smp_wmb(); > + __cpuc_flush_dcache_area(start, size); > + outer_clean_range(__pa(&pen_release), __pa(&pen_release + 1)); > +} > + > +/* > + * Enumerate the possible CPU set from the device tree. > + */ > +static void __init virt_smp_init_cpus(void) > +{ > + const char *enable_method; > + struct device_node *dn = NULL; > + int cpu = 0; > + u32 release_addr; > + > + while ((dn = of_find_node_by_type(dn, "cpu"))) { > + if (cpu >= NR_CPUS) > + goto next; > + > + /* > + * We currently support only the "spin-table" enable-method. > + */ > + enable_method = of_get_property(dn, "enable-method", NULL); > + if (!enable_method || strcmp(enable_method, "spin-table")) { Are these documented? > + pr_err("CPU %d: missing or invalid enable-method property: %s\n", > + cpu, enable_method); > + goto next; > + } > + > + /* > + * Determine the address from which the CPU is polling. > + */ > + if (of_property_read_u32(dn, "cpu-release-addr", &release_addr)) { > + pr_err("CPU %d: missing or invalid cpu-release-addr property\n", > + cpu); > + goto next; > + } > + > + cpu_release_addr[cpu] = release_addr; > + set_cpu_possible(cpu, true); > +next: > + cpu++; > + } > + > + /* sanity check */ > + if (cpu > NR_CPUS) > + pr_warning("no. of cores (%d) greater than configured maximum of %d - clipping\n", > + cpu, NR_CPUS); > + > + set_smp_cross_call(gic_raise_softirq); > +} > + > +static void __init virt_smp_prepare_cpus(unsigned int max_cpus) > +{ > + int cpu; > + void **release_addr; > + unsigned int ncores = num_possible_cpus(); > + > + /* > + * are we trying to boot more cores than exist? > + */ > + if (max_cpus > ncores) > + max_cpus = ncores; > + > + /* > + * Initialise the present map (which describes the set of CPUs > + * actually populated at the present time) and release the > + * secondaries from the bootloader. > + */ > + for_each_possible_cpu(cpu) { > + if (max_cpus == 0) > + break; > + > + if (!cpu_release_addr[cpu]) > + continue; > + > + release_addr = __va(cpu_release_addr[cpu]); > + release_addr[0] = (void *)__pa(virt_secondary_startup); > + smp_wmb(); > + __cpuc_flush_dcache_area(release_addr, sizeof(release_addr[0])); > + outer_clean_range(__pa(release_addr), __pa(release_addr+1)); > + > + set_cpu_present(cpu, true); > + max_cpus--; > + } > +} > + > +static int __cpuinit virt_boot_secondary(unsigned int cpu, > + struct task_struct *idle) > +{ > + unsigned long timeout; > + > + /* > + * Set synchronisation state between this boot processor > + * and the secondary one > + */ > + raw_spin_lock(&boot_lock); > + > + /* > + * Update the pen release flag. > + */ > + write_pen_release(cpu); > + > + /* > + * Send the secondary CPU a soft interrupt, causing the > + * secondaries to read pen_release. > + */ > + gic_raise_softirq(cpumask_of(cpu), 0); > + > + timeout = jiffies + (1 * HZ); > + while (time_before(jiffies, timeout)) { > + if (pen_release == -1UL) > + break; > + udelay(10); > + } > + > + /* > + * Now the secondary core is starting up let it run its > + * calibrations, then wait for it to finish > + */ > + raw_spin_unlock(&boot_lock); > + > + return pen_release != -1 ? -ENOSYS : 0; > +} > + > +static void __cpuinit virt_secondary_init(unsigned int cpu) > +{ > + /* > + * if any interrupts are already enabled for the primary > + * core (e.g. timer irq), then they will not have been enabled > + * for us: do so > + */ > + gic_secondary_init(0); > + > + /* > + * let the primary processor know we're out of the > + * pen, then head off into the C entry point > + */ > + write_pen_release(-1); > + > + /* > + * Synchronise with the boot thread. > + */ > + raw_spin_lock(&boot_lock); > + raw_spin_unlock(&boot_lock); > +} > + > +struct smp_operations __initdata virt_smp_ops = { > + .smp_init_cpus = virt_smp_init_cpus, > + .smp_prepare_cpus = virt_smp_prepare_cpus, > + .smp_secondary_init = virt_secondary_init, > + .smp_boot_secondary = virt_boot_secondary, > +}; > diff --git a/arch/arm/mach-virt/virt.c b/arch/arm/mach-virt/virt.c > index 174b9da..d764835 100644 > --- a/arch/arm/mach-virt/virt.c > +++ b/arch/arm/mach-virt/virt.c > @@ -20,6 +20,7 @@ > > #include > #include > +#include > > #include > #include > @@ -56,10 +57,15 @@ static struct sys_timer virt_timer = { > .init = virt_timer_init, > }; > > +#ifdef CONFIG_SMP > +extern struct smp_operations virt_smp_ops; > +#endif > + > DT_MACHINE_START(VIRT, "Dummy Virtual Machine") > .init_irq = gic_init_irq, > .handle_irq = gic_handle_irq, > .timer = &virt_timer, > .init_machine = virt_init, > + .smp = smp_ops(virt_smp_ops), > .dt_compat = virt_dt_match, > MACHINE_END > _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006B1-93; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfwKm-0008Q7-U6 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:31:05 +0000 Received: from [193.109.254.147:40090] by server-12.bemta-14.messagelabs.com id EF/5E-00510-8533EB05; Tue, 04 Dec 2012 17:31:04 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1354642257!8925636!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 489 invoked from network); 4 Dec 2012 17:30:57 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-2.tower-27.messagelabs.com with SMTP; 4 Dec 2012 17:30:57 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4HUkUO012225; Tue, 4 Dec 2012 17:30:46 GMT Date: Tue, 4 Dec 2012 17:30:45 +0000 From: Will Deacon To: Marc Zyngier Message-ID: <20121204173045.GI5314@mudshark.cambridge.arm.com> References: <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> <20121204171628.GF5314@mudshark.cambridge.arm.com> <50BE31E9.3040404@arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50BE31E9.3040404@arm.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 05:24:57PM +0000, Marc Zyngier wrote: > On 04/12/12 17:16, Will Deacon wrote: > > On Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: > >> Aren't we mixing 2 pens here? You must have some simple bootloader > >> containing vector table and a pen that the dtb points to, right? The pen > >> you have in the kernel is only needed when hotplug only does a wfi. As > >> you don't yet support hotplug, then you can drop all the kernel pen code. > > > > Yes, both qemu and kvmtool have bootloader pens outside of the kernel but > > since wfi is not trapped by kvm, the secondaries can be released early due > > to a spurious wakeup so we need the second pen. > > Actually, KVM traps WFI and puts the vcpu thread on a wait queue (we are > actually giving more guaranties than the architecture offers here). Ok, if we can rely on this behaviour in the future this sounds promising. Can somebody comment from the Xen side of things please? > We should be able to remove the loop and rely on WFI. Yes, we should be able to remove the kernel-side loop. We still won't have hotplug and friends, but that can come later because there's a discussion around PSCI vs virtual power controller to be had there. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006AW-4y; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfwEw-0008MR-Bl for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:25:02 +0000 Received: from [85.158.143.35:61261] by server-2.bemta-4.messagelabs.com id 0D/32-28922-DE13EB05; Tue, 04 Dec 2012 17:25:01 +0000 X-Env-Sender: marc.zyngier@arm.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1354641901!10575705!1 X-Originating-IP: [91.220.42.44] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogOTEuMjIwLjQyLjQ0ID0+IDM0MDY4OA==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3873 invoked from network); 4 Dec 2012 17:25:01 -0000 Received: from service87.mimecast.com (HELO service87.mimecast.com) (91.220.42.44) by server-10.tower-21.messagelabs.com with SMTP; 4 Dec 2012 17:25:01 -0000 Received: from cam-owa1.Emea.Arm.com (fw-tnat.cambridge.arm.com [217.140.96.21]) by service87.mimecast.com; Tue, 04 Dec 2012 17:25:00 +0000 Received: from [10.1.70.21] ([10.1.255.212]) by cam-owa1.Emea.Arm.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 4 Dec 2012 17:24:58 +0000 Message-ID: <50BE31E9.3040404@arm.com> Date: Tue, 04 Dec 2012 17:24:57 +0000 From: Marc Zyngier User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> <20121204171628.GF5314@mudshark.cambridge.arm.com> In-Reply-To: <20121204171628.GF5314@mudshark.cambridge.arm.com> X-Enigmail-Version: 1.4.6 X-OriginalArrivalTime: 04 Dec 2012 17:24:58.0593 (UTC) FILETIME=[48E10D10:01CDD244] X-MC-Unique: 112120417250010401 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 04/12/12 17:16, Will Deacon wrote: > On Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: >> On 12/04/2012 10:11 AM, Will Deacon wrote: >>> On Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: >>>> Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec >>>> into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which >>>> will be located at 32K into the RAM. The v3.7 kernel will also want to >>>> occupy the same place. At some point you have to overwrite the v3.6 >>>> kernel with the v3.7 kernel image. >>> >>> If the 3.6 kernel didn't bring those CPUs online, they will sit in the >>> bootloader pen (out of the way of the kernel image) rather than the kernel >>> pen so I don't think there will be a problem. >>> >>> The problem you're describing actually happens when the 3.6 kernel onlines >>> all of the CPUs, because now it has no way to hotplug them off safely. This >>> is also an issue with non-virtualised hardware but we could solve it for the >>> virtual platform by having a para-virtualised device for doing CPU hotplug. >>> >>>> That happens _before_ the DT has been parsed, so any memreserve stuff >>>> will be ignored. And it's at that point that your "offline" secondary >>>> CPUs will have their instructions overwritten. >>>> >>>> That's fine if the pen ends up being at the same place but that's not >>>> something we guarantee. >>> >>> Having CPUs in limbo between the bootloader the being online in the kernel >>> is something we should just avoid. Isn't that pen __init anyway? >> >> Aren't we mixing 2 pens here? You must have some simple bootloader >> containing vector table and a pen that the dtb points to, right? The pen >> you have in the kernel is only needed when hotplug only does a wfi. As >> you don't yet support hotplug, then you can drop all the kernel pen code. > > Yes, both qemu and kvmtool have bootloader pens outside of the kernel but > since wfi is not trapped by kvm, the secondaries can be released early due > to a spurious wakeup so we need the second pen. Actually, KVM traps WFI and puts the vcpu thread on a wait queue (we are actually giving more guaranties than the architecture offers here). We should be able to remove the loop and rely on WFI. M. -- Jazz is not dead. It just smells funny... _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCZ-0006A3-ON; Fri, 03 May 2013 12:35:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfw6y-0007r5-T2 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:16:49 +0000 Received: from [85.158.143.99:24305] by server-3.bemta-4.messagelabs.com id D3/16-06841-0003EB05; Tue, 04 Dec 2012 17:16:48 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1354641404!27451723!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2882 invoked from network); 4 Dec 2012 17:16:44 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-3.tower-216.messagelabs.com with SMTP; 4 Dec 2012 17:16:44 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB4HGTUO012032; Tue, 4 Dec 2012 17:16:29 GMT Date: Tue, 4 Dec 2012 17:16:28 +0000 From: Will Deacon To: Rob Herring Message-ID: <20121204171628.GF5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50BE28C6.2010403@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: > On 12/04/2012 10:11 AM, Will Deacon wrote: > > On Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: > >> Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec > >> into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which > >> will be located at 32K into the RAM. The v3.7 kernel will also want to > >> occupy the same place. At some point you have to overwrite the v3.6 > >> kernel with the v3.7 kernel image. > > > > If the 3.6 kernel didn't bring those CPUs online, they will sit in the > > bootloader pen (out of the way of the kernel image) rather than the kernel > > pen so I don't think there will be a problem. > > > > The problem you're describing actually happens when the 3.6 kernel onlines > > all of the CPUs, because now it has no way to hotplug them off safely. This > > is also an issue with non-virtualised hardware but we could solve it for the > > virtual platform by having a para-virtualised device for doing CPU hotplug. > > > >> That happens _before_ the DT has been parsed, so any memreserve stuff > >> will be ignored. And it's at that point that your "offline" secondary > >> CPUs will have their instructions overwritten. > >> > >> That's fine if the pen ends up being at the same place but that's not > >> something we guarantee. > > > > Having CPUs in limbo between the bootloader the being online in the kernel > > is something we should just avoid. Isn't that pen __init anyway? > > Aren't we mixing 2 pens here? You must have some simple bootloader > containing vector table and a pen that the dtb points to, right? The pen > you have in the kernel is only needed when hotplug only does a wfi. As > you don't yet support hotplug, then you can drop all the kernel pen code. Yes, both qemu and kvmtool have bootloader pens outside of the kernel but since wfi is not trapped by kvm, the secondaries can be released early due to a spurious wakeup so we need the second pen. > If there is no way to reset the core, then couldn't the hotplug code > tear down the cpu setup and just jump back to 0x0 which then returns to > the bootloader's pen? I think hotplug really should be implemented with a virtio device. We just trap back to the emulation and kill the vcpu thread. Will _______________________________________________ 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 May 03 12:35:04 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCX-00068T-Ej; Fri, 03 May 2013 12:35:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfaCK-000418-UG for xen-arm@lists.xen.org; Mon, 03 Dec 2012 17:52:53 +0000 Received: from [85.158.143.99:18619] by server-2.bemta-4.messagelabs.com id 04/3C-28922-4F6ECB05; Mon, 03 Dec 2012 17:52:52 +0000 X-Env-Sender: will.deacon@arm.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1354557171!18244075!1 X-Originating-IP: [217.140.96.50] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15847 invoked from network); 3 Dec 2012 17:52:51 -0000 Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by server-14.tower-216.messagelabs.com with SMTP; 3 Dec 2012 17:52:51 -0000 Received: from mudshark.cambridge.arm.com (mudshark.cambridge.arm.com [10.1.79.58]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id qB3Hqh53002347; Mon, 3 Dec 2012 17:52:43 GMT Received: by mudshark.cambridge.arm.com (Postfix, from userid 1000) id 45D2BC0336; Mon, 3 Dec 2012 17:52:42 +0000 (GMT) From: Will Deacon To: linux-arm-kernel@lists.infradead.org Date: Mon, 3 Dec 2012 17:52:39 +0000 Message-Id: <1354557160-20144-2-git-send-email-will.deacon@arm.com> X-Mailer: git-send-email 1.8.0 In-Reply-To: <1354557160-20144-1-git-send-email-will.deacon@arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: marc.zyngier@arm.com, xen-arm@lists.xen.org, mark.rutland@arm.com, Will Deacon , arnd@arnd.de Subject: [XenARM] [RFC PATCH 1/2] ARM: Dummy Virtual Machine platform support 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: , MIME-Version: 1.0 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 From: Marc Zyngier Add support for the smallest, dumbest possible platform, to be used as a guest for KVM or other hypervisors. It only mandates a GIC and architected timers. Fits nicely with a multiplatform zImage. Uses very little silicon area. Signed-off-by: Marc Zyngier Signed-off-by: Will Deacon --- arch/arm/Kconfig | 2 ++ arch/arm/Makefile | 1 + arch/arm/mach-virt/Kconfig | 9 +++++++ arch/arm/mach-virt/Makefile | 5 ++++ arch/arm/mach-virt/virt.c | 65 +++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 82 insertions(+) create mode 100644 arch/arm/mach-virt/Kconfig create mode 100644 arch/arm/mach-virt/Makefile create mode 100644 arch/arm/mach-virt/virt.c diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig index 781725e..ba0dca7 100644 --- a/arch/arm/Kconfig +++ b/arch/arm/Kconfig @@ -1126,6 +1126,8 @@ source "arch/arm/mach-versatile/Kconfig" source "arch/arm/mach-vexpress/Kconfig" source "arch/arm/plat-versatile/Kconfig" +source "arch/arm/mach-virt/Kconfig" + source "arch/arm/mach-w90x900/Kconfig" # Definitions to make life easier diff --git a/arch/arm/Makefile b/arch/arm/Makefile index 5f914fc..e8232ad 100644 --- a/arch/arm/Makefile +++ b/arch/arm/Makefile @@ -192,6 +192,7 @@ machine-$(CONFIG_ARCH_SOCFPGA) += socfpga machine-$(CONFIG_ARCH_SPEAR13XX) += spear13xx machine-$(CONFIG_ARCH_SPEAR3XX) += spear3xx machine-$(CONFIG_MACH_SPEAR600) += spear6xx +machine-$(CONFIG_ARCH_VIRT) += virt machine-$(CONFIG_ARCH_ZYNQ) += zynq # Platform directory name. This list is sorted alphanumerically diff --git a/arch/arm/mach-virt/Kconfig b/arch/arm/mach-virt/Kconfig new file mode 100644 index 0000000..a568a2a --- /dev/null +++ b/arch/arm/mach-virt/Kconfig @@ -0,0 +1,9 @@ +config ARCH_VIRT + bool "Dummy Virtual Machine" if ARCH_MULTI_V7 + select ARCH_WANT_OPTIONAL_GPIOLIB + select ARM_GIC + select ARM_ARCH_TIMER + select HAVE_SMP + select CPU_V7 + select SPARSE_IRQ + select USE_OF diff --git a/arch/arm/mach-virt/Makefile b/arch/arm/mach-virt/Makefile new file mode 100644 index 0000000..7ddbfa6 --- /dev/null +++ b/arch/arm/mach-virt/Makefile @@ -0,0 +1,5 @@ +# +# Makefile for the linux kernel. +# + +obj-y := virt.o diff --git a/arch/arm/mach-virt/virt.c b/arch/arm/mach-virt/virt.c new file mode 100644 index 0000000..174b9da --- /dev/null +++ b/arch/arm/mach-virt/virt.c @@ -0,0 +1,65 @@ +/* + * Dummy Virtual Machine - does what it says on the tin. + * + * Copyright (C) 2012 ARM Ltd + * Authors: Will Deacon , + * Marc Zyngier + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program. If not, see . + */ + +#include +#include + +#include +#include +#include +#include + +const static struct of_device_id irq_match[] = { + { .compatible = "arm,cortex-a15-gic", .data = gic_of_init, }, + {} +}; + +static void __init gic_init_irq(void) +{ + of_irq_init(irq_match); +} + +static void __init virt_init(void) +{ + of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL); +} + +static void __init virt_timer_init(void) +{ + WARN_ON(arch_timer_of_register() != 0); + WARN_ON(arch_timer_sched_clock_init() != 0); +} + +static const char *virt_dt_match[] = { + "linux,dummy-virt", + NULL +}; + +static struct sys_timer virt_timer = { + .init = virt_timer_init, +}; + +DT_MACHINE_START(VIRT, "Dummy Virtual Machine") + .init_irq = gic_init_irq, + .handle_irq = gic_handle_irq, + .timer = &virt_timer, + .init_machine = virt_init, + .dt_compat = virt_dt_match, +MACHINE_END -- 1.8.0 _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCb-0006FX-2m; Fri, 03 May 2013 12:35:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyE4P-0004DA-Kd for xen-arm@lists.xensource.com; Thu, 24 Jan 2013 04:05:45 +0000 Received: from [85.158.143.99:23872] by server-2.bemta-4.messagelabs.com id A4/EA-03518-913B0015; Thu, 24 Jan 2013 04:05:45 +0000 X-Env-Sender: apache@u15729190.onlinehome-server.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1359000341!23971600!1 X-Originating-IP: [74.208.231.119] X-SpamReason: No, hits=2.0 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,INFO_TLD,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16066 invoked from network); 24 Jan 2013 04:05:43 -0000 Received: from tmb440.info (HELO u15729190.onlinehome-server.com) (74.208.231.119) by server-2.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jan 2013 04:05:43 -0000 Received: from u15729190.onlinehome-server.com (unknown [127.0.0.1]) by u15729190.onlinehome-server.com (Postfix) with ESMTP id 907854194F4 for ; Thu, 24 Jan 2013 04:05:41 +0000 (UTC) Received: by u15729190.onlinehome-server.com (Postfix, from userid 48) id 8694B41254F; Thu, 24 Jan 2013 04:05:41 +0000 (UTC) To: xen-arm@lists.xensource.com Date: Thu, 24 Jan 2013 01:05:41 -0300 From: Maia Divicenzo Message-ID: <772740afef9e2ac0b31269c11d22513f@tmb443.info> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.14 X-MessageID: 3 X-ListMember: xen-arm@lists.xensource.com MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Subject: [XenARM] Envios ilimitados de emails por solo $215. Cupos limitados 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="===============1543903791883793900==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============1543903791883793900== Content-Type: multipart/alternative; boundary="b1_772740afef9e2ac0b31269c11d22513f" --b1_772740afef9e2ac0b31269c11d22513f Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit Buenas tardes! Promo Enero - Sólo hasta agotar plazas disponibles: Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $215/mes .- (u$d 45.-) Promoción internacional para varios países. Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing. Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente. Recibes las respuestas en tu propio email. Regalo especial para clientes nuevos: ¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente. ¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos) No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles. Esperamos tu contacto en: maiadivicenzo@yahoo.com Te responderemos desde el email oficial de nuestra empresa. (Empresas de Email Marketing, consultar promociones especiales) Maia Divicenzo. La Revolución en Email Marketing +54(223)156140605 Internacional: +1.323.924.7376 -- Para desuscribirse, http://tmb443.info/lists/?p=unsubscribe&uid=c2c473d23e0b9036c15ae1799b90ffbc -- powered by phpList, www.phplist.com -- --b1_772740afef9e2ac0b31269c11d22513f Content-Type: text/html; charset = "UTF-8" Content-Transfer-Encoding: 8bit

Buenas tardes!

 

Promo Enero - Sólo hasta agotar plazas disponibles:

 

Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $215/mes .- (u$d 45.-) Promoción internacional para varios países.

 

Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing.

Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente.

Recibes las respuestas en tu propio email.

 

Regalo especial para clientes nuevos:

 

¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente.

 

¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos)

 

No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles.

 

Esperamos tu contacto en:

maiadivicenzo@yahoo.com

 

Te responderemos desde el email oficial de nuestra empresa.

 

(Empresas de Email Marketing, consultar promociones especiales)

 

Maia Divicenzo.

 

La Revolución en Email Marketing

+54(223)156140605  
Internacional: +1.323.924.7376

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



--
Para desuscribirse, this link
powered by phplist v 2.10.14, © phpList ltd
--b1_772740afef9e2ac0b31269c11d22513f-- --===============1543903791883793900== 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 --===============1543903791883793900==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006Df-Ky; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGLh-0004Zx-Pk for xen-arm@lists.xen.org; Wed, 05 Dec 2012 14:53:22 +0000 Received: from [85.158.139.211:38586] by server-13.bemta-5.messagelabs.com id FB/F9-27809-0EF5FB05; Wed, 05 Dec 2012 14:53:20 +0000 X-Env-Sender: catalin.marinas@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1354719197!18396143!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9310 invoked from network); 5 Dec 2012 14:53:18 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Dec 2012 14:53:18 -0000 Received: by mail-qc0-f173.google.com with SMTP id b12so3238117qca.32 for ; Wed, 05 Dec 2012 06:53:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=HvMQ4c5fbLu57S6Idyji18aXx5ILIiydWfQE/gvhQbg=; b=eolsY8kdy0+Ub3Q0S7cSdhmDWLArD8LAJn5A28vuTnAp5kyJlJcR54Cuy4GJnOqY63 KCehkbXRVS93W5e6KIHVGAB3FVD6mbp+J5+5aw+hba4lWqEUri3zYbAVEZG01OrXQGMV Cb92t6kXCZeskCBGUlNkx048lZz0KcHLcU5yMVcTJGo94S6NYEjx3PXlrqN/d3FV1p70 DRAjNJKO11U2/6E0RheR7j3E5fuJpF8NdVSknqMpDxIGmbw3ihTF+eVO6wIUMrLPjGMb yWC4EjIxT+r7ROGfUaPUTqBw/l+tyna2/k6pvBBbiRRCSbp9KGD4F77uXCAvhVMkh8BK QT5w== Received: by 10.49.127.139 with SMTP id ng11mr16633479qeb.54.1354719197644; Wed, 05 Dec 2012 06:53:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.49.98.39 with HTTP; Wed, 5 Dec 2012 06:52:57 -0800 (PST) In-Reply-To: <20121204181446.GJ5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> From: Catalin Marinas Date: Wed, 5 Dec 2012 14:52:57 +0000 X-Google-Sender-Auth: vl_VKwaU3mhqOO5YSEJp2Jda0VY Message-ID: To: Will Deacon X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Nicolas Pitre , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 4 December 2012 18:14, Will Deacon wrote: > On Tue, Dec 04, 2012 at 06:02:13PM +0000, Nicolas Pitre wrote: >> On Tue, 4 Dec 2012, Will Deacon wrote: >> > On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: >> > > on the topic of a para-virtualised machine, I think that it should >> > > simply implement the PSCI calls to bring up CPUs _without_ any holding >> > > pen nor spinning tables. You issue the appropriate PSCI call with the >> > > physical address for secondary_startup() as argument and you're done. >> > > The host intercepts that call and free a new CPU instance in response. >> > > That's all. >> > >> > I'd be happy to go with this suggestion if it wasn't for one thing: >> > platforms that do not implement a secure mode. For these platforms, smc will >> > be an undefined instruction at the exception level where it is executed and >> > therefore cannot be trapped by the hypervisor. >> >> Really? I thought the hypervisor could virtualize SMC calls. Or is >> that considered a security hazard? > > If the security extensions aren't implemented, the hypervisor can't trap the > smc instruction. > >> I don't remember all the PSCI spec details, but I think there was some >> provision for this case i.e. the SMC call could be a HYP call instead. >> And if that's not in the spec, then it probably should be added and >> implemented as if it was. > > Well, this depends on the guest taking an undefined instruction exception on > the smc, then deciding to issue an hvc instead and *then* having the > hypervisor somehow translate that into a PSCI invocation. It could work, but > it sounds easy to mess up and relies on the PSCI firmware co-existing with > things like kvm. We can have enable-method DT entries independent of the SoC and one of them can be psci-hvc. Just for clarification, AArch32 with virtualisation mandates the security extensions, so the SMC can be trapped. On AArch64 it is a bit tricky since the presence of EL3 is not mandate, in which case SMC would undef (don't as why ;). That's where we can have different enable methods specified via the DT. -- Catalin _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006AL-05; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfwEf-0008HL-0g for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:24:45 +0000 Received: from [85.158.143.35:2800] by server-3.bemta-4.messagelabs.com id E7/2E-06841-CD13EB05; Tue, 04 Dec 2012 17:24:44 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1354641821!14043232!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=2.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21699 invoked from network); 4 Dec 2012 17:23:43 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2012 17:23:43 -0000 Received: by mail-ob0-f173.google.com with SMTP id xn12so4792720obc.32 for ; Tue, 04 Dec 2012 09:23:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=BwFidflbyVtpgM5IDS4O7su8pbz1LEA7aKA4jdqHzRA=; b=mszeiS1yrFJ6zx3Mybal52y9DbVY/VFwrcE2CujYuWUdr6KM/pJvtvvnSpUcQ1jk8L qED6AAU9e7vozihjl8Vwk130kJUfAF7+M+p73Vi4GRed94f6yL1HiZ9wHsL/R8uijhtI Zvu4Vw6dVjdfsc7cH3m+QOrg0u8uO+7eEYC1sxAYa8z1fYKxs3icoLSk4+nIdKlV4JEm /1sSI9VurFsOnZFQN8wT/NLAJ0qtVx4bGLpIbSaUpctwsFcU+TmrMSbEy/jv077SII0l xYAqMVcKnUOCsjaDHeFWP5W/Sxv/JzUh7px4xpPr/Rc3Oa31gBo0B8sFswbhmA8vm56C +M5g== Received: by 10.60.7.129 with SMTP id j1mr11945506oea.54.1354641821526; Tue, 04 Dec 2012 09:23:41 -0800 (PST) Received: from [10.10.10.90] ([173.226.190.126]) by mx.google.com with ESMTPS id zn9sm1277782obb.23.2012.12.04.09.23.40 (version=SSLv3 cipher=OTHER); Tue, 04 Dec 2012 09:23:40 -0800 (PST) Message-ID: <50BE3199.40407@gmail.com> Date: Tue, 04 Dec 2012 11:23:37 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> <20121204171628.GF5314@mudshark.cambridge.arm.com> In-Reply-To: <20121204171628.GF5314@mudshark.cambridge.arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 12/04/2012 11:16 AM, Will Deacon wrote: > On Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: >> On 12/04/2012 10:11 AM, Will Deacon wrote: >>> On Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: >>>> Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec >>>> into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which >>>> will be located at 32K into the RAM. The v3.7 kernel will also want to >>>> occupy the same place. At some point you have to overwrite the v3.6 >>>> kernel with the v3.7 kernel image. >>> >>> If the 3.6 kernel didn't bring those CPUs online, they will sit in the >>> bootloader pen (out of the way of the kernel image) rather than the kernel >>> pen so I don't think there will be a problem. >>> >>> The problem you're describing actually happens when the 3.6 kernel onlines >>> all of the CPUs, because now it has no way to hotplug them off safely. This >>> is also an issue with non-virtualised hardware but we could solve it for the >>> virtual platform by having a para-virtualised device for doing CPU hotplug. >>> >>>> That happens _before_ the DT has been parsed, so any memreserve stuff >>>> will be ignored. And it's at that point that your "offline" secondary >>>> CPUs will have their instructions overwritten. >>>> >>>> That's fine if the pen ends up being at the same place but that's not >>>> something we guarantee. >>> >>> Having CPUs in limbo between the bootloader the being online in the kernel >>> is something we should just avoid. Isn't that pen __init anyway? >> >> Aren't we mixing 2 pens here? You must have some simple bootloader >> containing vector table and a pen that the dtb points to, right? The pen >> you have in the kernel is only needed when hotplug only does a wfi. As >> you don't yet support hotplug, then you can drop all the kernel pen code. > > Yes, both qemu and kvmtool have bootloader pens outside of the kernel but > since wfi is not trapped by kvm, the secondaries can be released early due > to a spurious wakeup so we need the second pen. Wouldn't the pen requiring both a valid address (perhaps !0 or !-1) and a wake-up fix this? Rob _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006F7-VW; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGhz-0005L4-RS for xen-arm@lists.xen.org; Wed, 05 Dec 2012 15:16:24 +0000 Received: from [85.158.139.83:36579] by server-10.bemta-5.messagelabs.com id C1/69-09257-7456FB05; Wed, 05 Dec 2012 15:16:23 +0000 X-Env-Sender: catalin.marinas@arm.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1354720565!28574001!1 X-Originating-IP: [91.220.42.44] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogOTEuMjIwLjQyLjQ0ID0+IDM0MTcwMg==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11134 invoked from network); 5 Dec 2012 15:16:05 -0000 Received: from service87.mimecast.com (HELO service87.mimecast.com) (91.220.42.44) by server-5.tower-182.messagelabs.com with SMTP; 5 Dec 2012 15:16:05 -0000 Received: from emea-cam-gw1.Emea.Arm.com (fw-tnat.cambridge.arm.com [217.140.96.21]) (Using TLS) by service87.mimecast.com; Wed, 05 Dec 2012 15:16:04 +0000 Received: from arm.com (10.1.2.13) by emea-cam-gw1.Emea.Arm.com (10.1.248.203) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 5 Dec 2012 15:16:02 +0000 Date: Wed, 5 Dec 2012 15:15:57 +0000 From: Catalin Marinas To: Will Deacon Message-ID: <20121205151557.GE27057@arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> <20121205150732.GJ22385@mudshark.cambridge.arm.com> MIME-Version: 1.0 In-Reply-To: <20121205150732.GJ22385@mudshark.cambridge.arm.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-MC-Unique: 112120515160403601 Content-Disposition: inline X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Nicolas Pitre , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Wed, Dec 05, 2012 at 03:07:32PM +0000, Will Deacon wrote: > On Wed, Dec 05, 2012 at 02:52:57PM +0000, Catalin Marinas wrote: > > Just for clarification, AArch32 with virtualisation mandates the > > security extensions, so the SMC can be trapped. On AArch64 it is a bit > > tricky since the presence of EL3 is not mandate, in which case SMC > > would undef (don't as why ;). That's where we can have different > > enable methods specified via the DT. > > Not entirely true: only ARMv7 mandates the security extensions in this > manner. You can still have ARMv8 CPUs running AArch32 code without the > security extensions. Yes, I pretty much had the 32-bit and 64-bit ARM ports in mind. An AArch32 guest OS running on an AArch64 KVM would indeed have this issue. But HVC PSCI would still work for the mach-virt in all cases. -- Catalin -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ 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 May 03 12:35:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCb-0006Fo-Du; Fri, 03 May 2013 12:35:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6FO7-0001F8-DH for xen-arm@lists.xensource.com; Fri, 15 Feb 2013 07:07:15 +0000 Received: from [85.158.138.51:30246] by server-16.bemta-3.messagelabs.com id 32/10-02727-2AEDD115; Fri, 15 Feb 2013 07:07:14 +0000 X-Env-Sender: apache@u15729190.onlinehome-server.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1360912031!19574785!1 X-Originating-IP: [74.208.231.119] X-SpamReason: No, hits=2.0 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,INFO_TLD,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10569 invoked from network); 15 Feb 2013 07:07:12 -0000 Received: from tmb440.info (HELO u15729190.onlinehome-server.com) (74.208.231.119) by server-3.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2013 07:07:12 -0000 Received: from u15729190.onlinehome-server.com (unknown [127.0.0.1]) by u15729190.onlinehome-server.com (Postfix) with ESMTP id 405A142691A for ; Fri, 15 Feb 2013 07:07:11 +0000 (UTC) Received: by u15729190.onlinehome-server.com (Postfix, from userid 48) id 2B93741AAB7; Fri, 15 Feb 2013 07:07:11 +0000 (UTC) To: xen-arm@lists.xensource.com Date: Fri, 15 Feb 2013 04:07:11 -0300 From: Maia Divicenzo Message-ID: X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.14 X-MessageID: 4 X-ListMember: xen-arm@lists.xensource.com MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Subject: [XenARM] Envios ilimitados de emails por solo $215. Cupos limitados 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="===============8917774597558720246==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8917774597558720246== Content-Type: multipart/alternative; boundary="b1_c9f501da4669604e1dcdf6de835d4708" --b1_c9f501da4669604e1dcdf6de835d4708 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit Buenas tardes! Promo Febrero - Sólo hasta agotar plazas disponibles: Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $215/mes .- (u$d 45.-) Promoción internacional para varios países. Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing. Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente. Recibes las respuestas en tu propio email. Regalo especial para clientes nuevos: ¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente. ¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos) No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles. Esperamos tu contacto en: maiadivicenzo@yahoo.com Te responderemos desde el email oficial de nuestra empresa. (Empresas de Email Marketing, consultar promociones especiales) Maia Divicenzo. La Revolución en Email Marketing +54(223)156140605 Internacional: +1.323.924.7376 -- Para desuscribirse, http://tmb443.info/lists/?p=unsubscribe&uid=c2c473d23e0b9036c15ae1799b90ffbc -- powered by phpList, www.phplist.com -- --b1_c9f501da4669604e1dcdf6de835d4708 Content-Type: text/html; charset = "UTF-8" Content-Transfer-Encoding: 8bit

Buenas tardes!

 

Promo Febrero - Sólo hasta agotar plazas disponibles:

 

Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $215/mes .- (u$d 45.-) Promoción internacional para varios países.

 

Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing.

Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente.

Recibes las respuestas en tu propio email.

 

Regalo especial para clientes nuevos:

 

¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente.

 

¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos)

 

No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles.

 

Esperamos tu contacto en:

maiadivicenzo@yahoo.com

 

Te responderemos desde el email oficial de nuestra empresa.

 

(Empresas de Email Marketing, consultar promociones especiales)

 

Maia Divicenzo.

 

La Revolución en Email Marketing

+54(223)156140605  
Internacional: +1.323.924.7376

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



--
Para desuscribirse, this link
powered by phplist v 2.10.14, © phpList ltd
--b1_c9f501da4669604e1dcdf6de835d4708-- --===============8917774597558720246== 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 --===============8917774597558720246==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006AL-05; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfwEf-0008HL-0g for xen-arm@lists.xen.org; Tue, 04 Dec 2012 17:24:45 +0000 Received: from [85.158.143.35:2800] by server-3.bemta-4.messagelabs.com id E7/2E-06841-CD13EB05; Tue, 04 Dec 2012 17:24:44 +0000 X-Env-Sender: robherring2@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1354641821!14043232!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=2.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RATWARE_GECKO_BUILD,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21699 invoked from network); 4 Dec 2012 17:23:43 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2012 17:23:43 -0000 Received: by mail-ob0-f173.google.com with SMTP id xn12so4792720obc.32 for ; Tue, 04 Dec 2012 09:23:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=BwFidflbyVtpgM5IDS4O7su8pbz1LEA7aKA4jdqHzRA=; b=mszeiS1yrFJ6zx3Mybal52y9DbVY/VFwrcE2CujYuWUdr6KM/pJvtvvnSpUcQ1jk8L qED6AAU9e7vozihjl8Vwk130kJUfAF7+M+p73Vi4GRed94f6yL1HiZ9wHsL/R8uijhtI Zvu4Vw6dVjdfsc7cH3m+QOrg0u8uO+7eEYC1sxAYa8z1fYKxs3icoLSk4+nIdKlV4JEm /1sSI9VurFsOnZFQN8wT/NLAJ0qtVx4bGLpIbSaUpctwsFcU+TmrMSbEy/jv077SII0l xYAqMVcKnUOCsjaDHeFWP5W/Sxv/JzUh7px4xpPr/Rc3Oa31gBo0B8sFswbhmA8vm56C +M5g== Received: by 10.60.7.129 with SMTP id j1mr11945506oea.54.1354641821526; Tue, 04 Dec 2012 09:23:41 -0800 (PST) Received: from [10.10.10.90] ([173.226.190.126]) by mx.google.com with ESMTPS id zn9sm1277782obb.23.2012.12.04.09.23.40 (version=SSLv3 cipher=OTHER); Tue, 04 Dec 2012 09:23:40 -0800 (PST) Message-ID: <50BE3199.40407@gmail.com> Date: Tue, 04 Dec 2012 11:23:37 -0600 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Will Deacon References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> <20121204171628.GF5314@mudshark.cambridge.arm.com> In-Reply-To: <20121204171628.GF5314@mudshark.cambridge.arm.com> X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 12/04/2012 11:16 AM, Will Deacon wrote: > On Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: >> On 12/04/2012 10:11 AM, Will Deacon wrote: >>> On Tue, Dec 04, 2012 at 02:37:25PM +0000, Russell King - ARM Linux wrote: >>>> Umm. So let's see. If I'm running v3.6 stock kernel and want to kexec >>>> into a v3.7 stock kernel. The SMP pen is part of the v3.6 kernel, which >>>> will be located at 32K into the RAM. The v3.7 kernel will also want to >>>> occupy the same place. At some point you have to overwrite the v3.6 >>>> kernel with the v3.7 kernel image. >>> >>> If the 3.6 kernel didn't bring those CPUs online, they will sit in the >>> bootloader pen (out of the way of the kernel image) rather than the kernel >>> pen so I don't think there will be a problem. >>> >>> The problem you're describing actually happens when the 3.6 kernel onlines >>> all of the CPUs, because now it has no way to hotplug them off safely. This >>> is also an issue with non-virtualised hardware but we could solve it for the >>> virtual platform by having a para-virtualised device for doing CPU hotplug. >>> >>>> That happens _before_ the DT has been parsed, so any memreserve stuff >>>> will be ignored. And it's at that point that your "offline" secondary >>>> CPUs will have their instructions overwritten. >>>> >>>> That's fine if the pen ends up being at the same place but that's not >>>> something we guarantee. >>> >>> Having CPUs in limbo between the bootloader the being online in the kernel >>> is something we should just avoid. Isn't that pen __init anyway? >> >> Aren't we mixing 2 pens here? You must have some simple bootloader >> containing vector table and a pen that the dtb points to, right? The pen >> you have in the kernel is only needed when hotplug only does a wfi. As >> you don't yet support hotplug, then you can drop all the kernel pen code. > > Yes, both qemu and kvmtool have bootloader pens outside of the kernel but > since wfi is not trapped by kvm, the secondaries can be released early due > to a spurious wakeup so we need the second pen. Wouldn't the pen requiring both a valid address (perhaps !0 or !-1) and a wake-up fix this? Rob _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCb-0006FX-2m; Fri, 03 May 2013 12:35:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TyE4P-0004DA-Kd for xen-arm@lists.xensource.com; Thu, 24 Jan 2013 04:05:45 +0000 Received: from [85.158.143.99:23872] by server-2.bemta-4.messagelabs.com id A4/EA-03518-913B0015; Thu, 24 Jan 2013 04:05:45 +0000 X-Env-Sender: apache@u15729190.onlinehome-server.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1359000341!23971600!1 X-Originating-IP: [74.208.231.119] X-SpamReason: No, hits=2.0 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,INFO_TLD,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16066 invoked from network); 24 Jan 2013 04:05:43 -0000 Received: from tmb440.info (HELO u15729190.onlinehome-server.com) (74.208.231.119) by server-2.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Jan 2013 04:05:43 -0000 Received: from u15729190.onlinehome-server.com (unknown [127.0.0.1]) by u15729190.onlinehome-server.com (Postfix) with ESMTP id 907854194F4 for ; Thu, 24 Jan 2013 04:05:41 +0000 (UTC) Received: by u15729190.onlinehome-server.com (Postfix, from userid 48) id 8694B41254F; Thu, 24 Jan 2013 04:05:41 +0000 (UTC) To: xen-arm@lists.xensource.com Date: Thu, 24 Jan 2013 01:05:41 -0300 From: Maia Divicenzo Message-ID: <772740afef9e2ac0b31269c11d22513f@tmb443.info> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.14 X-MessageID: 3 X-ListMember: xen-arm@lists.xensource.com MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Subject: [XenARM] Envios ilimitados de emails por solo $215. Cupos limitados 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="===============1543903791883793900==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============1543903791883793900== Content-Type: multipart/alternative; boundary="b1_772740afef9e2ac0b31269c11d22513f" --b1_772740afef9e2ac0b31269c11d22513f Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit Buenas tardes! Promo Enero - Sólo hasta agotar plazas disponibles: Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $215/mes .- (u$d 45.-) Promoción internacional para varios países. Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing. Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente. Recibes las respuestas en tu propio email. Regalo especial para clientes nuevos: ¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente. ¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos) No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles. Esperamos tu contacto en: maiadivicenzo@yahoo.com Te responderemos desde el email oficial de nuestra empresa. (Empresas de Email Marketing, consultar promociones especiales) Maia Divicenzo. La Revolución en Email Marketing +54(223)156140605 Internacional: +1.323.924.7376 -- Para desuscribirse, http://tmb443.info/lists/?p=unsubscribe&uid=c2c473d23e0b9036c15ae1799b90ffbc -- powered by phpList, www.phplist.com -- --b1_772740afef9e2ac0b31269c11d22513f Content-Type: text/html; charset = "UTF-8" Content-Transfer-Encoding: 8bit

Buenas tardes!

 

Promo Enero - Sólo hasta agotar plazas disponibles:

 

Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $215/mes .- (u$d 45.-) Promoción internacional para varios países.

 

Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing.

Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente.

Recibes las respuestas en tu propio email.

 

Regalo especial para clientes nuevos:

 

¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente.

 

¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos)

 

No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles.

 

Esperamos tu contacto en:

maiadivicenzo@yahoo.com

 

Te responderemos desde el email oficial de nuestra empresa.

 

(Empresas de Email Marketing, consultar promociones especiales)

 

Maia Divicenzo.

 

La Revolución en Email Marketing

+54(223)156140605  
Internacional: +1.323.924.7376

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



--
Para desuscribirse, this link
powered by phplist v 2.10.14, © phpList ltd
--b1_772740afef9e2ac0b31269c11d22513f-- --===============1543903791883793900== 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 --===============1543903791883793900==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006Df-Ky; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGLh-0004Zx-Pk for xen-arm@lists.xen.org; Wed, 05 Dec 2012 14:53:22 +0000 Received: from [85.158.139.211:38586] by server-13.bemta-5.messagelabs.com id FB/F9-27809-0EF5FB05; Wed, 05 Dec 2012 14:53:20 +0000 X-Env-Sender: catalin.marinas@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1354719197!18396143!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9310 invoked from network); 5 Dec 2012 14:53:18 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Dec 2012 14:53:18 -0000 Received: by mail-qc0-f173.google.com with SMTP id b12so3238117qca.32 for ; Wed, 05 Dec 2012 06:53:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=HvMQ4c5fbLu57S6Idyji18aXx5ILIiydWfQE/gvhQbg=; b=eolsY8kdy0+Ub3Q0S7cSdhmDWLArD8LAJn5A28vuTnAp5kyJlJcR54Cuy4GJnOqY63 KCehkbXRVS93W5e6KIHVGAB3FVD6mbp+J5+5aw+hba4lWqEUri3zYbAVEZG01OrXQGMV Cb92t6kXCZeskCBGUlNkx048lZz0KcHLcU5yMVcTJGo94S6NYEjx3PXlrqN/d3FV1p70 DRAjNJKO11U2/6E0RheR7j3E5fuJpF8NdVSknqMpDxIGmbw3ihTF+eVO6wIUMrLPjGMb yWC4EjIxT+r7ROGfUaPUTqBw/l+tyna2/k6pvBBbiRRCSbp9KGD4F77uXCAvhVMkh8BK QT5w== Received: by 10.49.127.139 with SMTP id ng11mr16633479qeb.54.1354719197644; Wed, 05 Dec 2012 06:53:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.49.98.39 with HTTP; Wed, 5 Dec 2012 06:52:57 -0800 (PST) In-Reply-To: <20121204181446.GJ5314@mudshark.cambridge.arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> From: Catalin Marinas Date: Wed, 5 Dec 2012 14:52:57 +0000 X-Google-Sender-Auth: vl_VKwaU3mhqOO5YSEJp2Jda0VY Message-ID: To: Will Deacon X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Nicolas Pitre , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 4 December 2012 18:14, Will Deacon wrote: > On Tue, Dec 04, 2012 at 06:02:13PM +0000, Nicolas Pitre wrote: >> On Tue, 4 Dec 2012, Will Deacon wrote: >> > On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: >> > > on the topic of a para-virtualised machine, I think that it should >> > > simply implement the PSCI calls to bring up CPUs _without_ any holding >> > > pen nor spinning tables. You issue the appropriate PSCI call with the >> > > physical address for secondary_startup() as argument and you're done. >> > > The host intercepts that call and free a new CPU instance in response. >> > > That's all. >> > >> > I'd be happy to go with this suggestion if it wasn't for one thing: >> > platforms that do not implement a secure mode. For these platforms, smc will >> > be an undefined instruction at the exception level where it is executed and >> > therefore cannot be trapped by the hypervisor. >> >> Really? I thought the hypervisor could virtualize SMC calls. Or is >> that considered a security hazard? > > If the security extensions aren't implemented, the hypervisor can't trap the > smc instruction. > >> I don't remember all the PSCI spec details, but I think there was some >> provision for this case i.e. the SMC call could be a HYP call instead. >> And if that's not in the spec, then it probably should be added and >> implemented as if it was. > > Well, this depends on the guest taking an undefined instruction exception on > the smc, then deciding to issue an hvc instead and *then* having the > hypervisor somehow translate that into a PSCI invocation. It could work, but > it sounds easy to mess up and relies on the PSCI firmware co-existing with > things like kvm. We can have enable-method DT entries independent of the SoC and one of them can be psci-hvc. Just for clarification, AArch32 with virtualisation mandates the security extensions, so the SMC can be trapped. On AArch64 it is a bit tricky since the presence of EL3 is not mandate, in which case SMC would undef (don't as why ;). That's where we can have different enable methods specified via the DT. -- Catalin _______________________________________________ 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 May 03 12:35:05 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCa-0006F7-VW; Fri, 03 May 2013 12:35:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGhz-0005L4-RS for xen-arm@lists.xen.org; Wed, 05 Dec 2012 15:16:24 +0000 Received: from [85.158.139.83:36579] by server-10.bemta-5.messagelabs.com id C1/69-09257-7456FB05; Wed, 05 Dec 2012 15:16:23 +0000 X-Env-Sender: catalin.marinas@arm.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1354720565!28574001!1 X-Originating-IP: [91.220.42.44] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogOTEuMjIwLjQyLjQ0ID0+IDM0MTcwMg==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11134 invoked from network); 5 Dec 2012 15:16:05 -0000 Received: from service87.mimecast.com (HELO service87.mimecast.com) (91.220.42.44) by server-5.tower-182.messagelabs.com with SMTP; 5 Dec 2012 15:16:05 -0000 Received: from emea-cam-gw1.Emea.Arm.com (fw-tnat.cambridge.arm.com [217.140.96.21]) (Using TLS) by service87.mimecast.com; Wed, 05 Dec 2012 15:16:04 +0000 Received: from arm.com (10.1.2.13) by emea-cam-gw1.Emea.Arm.com (10.1.248.203) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 5 Dec 2012 15:16:02 +0000 Date: Wed, 5 Dec 2012 15:15:57 +0000 From: Catalin Marinas To: Will Deacon Message-ID: <20121205151557.GE27057@arm.com> References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> <20121205150732.GJ22385@mudshark.cambridge.arm.com> MIME-Version: 1.0 In-Reply-To: <20121205150732.GJ22385@mudshark.cambridge.arm.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-MC-Unique: 112120515160403601 Content-Disposition: inline X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Nicolas Pitre , Marc Zyngier , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Wed, Dec 05, 2012 at 03:07:32PM +0000, Will Deacon wrote: > On Wed, Dec 05, 2012 at 02:52:57PM +0000, Catalin Marinas wrote: > > Just for clarification, AArch32 with virtualisation mandates the > > security extensions, so the SMC can be trapped. On AArch64 it is a bit > > tricky since the presence of EL3 is not mandate, in which case SMC > > would undef (don't as why ;). That's where we can have different > > enable methods specified via the DT. > > Not entirely true: only ARMv7 mandates the security extensions in this > manner. You can still have ARMv8 CPUs running AArch32 code without the > security extensions. Yes, I pretty much had the 32-bit and 64-bit ARM ports in mind. An AArch32 guest OS running on an AArch64 KVM would indeed have this issue. But HVC PSCI would still work for the mach-virt in all cases. -- Catalin -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ 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 May 03 12:35:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCb-0006Fo-Du; Fri, 03 May 2013 12:35:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1U6FO7-0001F8-DH for xen-arm@lists.xensource.com; Fri, 15 Feb 2013 07:07:15 +0000 Received: from [85.158.138.51:30246] by server-16.bemta-3.messagelabs.com id 32/10-02727-2AEDD115; Fri, 15 Feb 2013 07:07:14 +0000 X-Env-Sender: apache@u15729190.onlinehome-server.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1360912031!19574785!1 X-Originating-IP: [74.208.231.119] X-SpamReason: No, hits=2.0 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,INFO_TLD,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10569 invoked from network); 15 Feb 2013 07:07:12 -0000 Received: from tmb440.info (HELO u15729190.onlinehome-server.com) (74.208.231.119) by server-3.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2013 07:07:12 -0000 Received: from u15729190.onlinehome-server.com (unknown [127.0.0.1]) by u15729190.onlinehome-server.com (Postfix) with ESMTP id 405A142691A for ; Fri, 15 Feb 2013 07:07:11 +0000 (UTC) Received: by u15729190.onlinehome-server.com (Postfix, from userid 48) id 2B93741AAB7; Fri, 15 Feb 2013 07:07:11 +0000 (UTC) To: xen-arm@lists.xensource.com Date: Fri, 15 Feb 2013 04:07:11 -0300 From: Maia Divicenzo Message-ID: X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.14 X-MessageID: 4 X-ListMember: xen-arm@lists.xensource.com MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Subject: [XenARM] Envios ilimitados de emails por solo $215. Cupos limitados 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="===============8917774597558720246==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8917774597558720246== Content-Type: multipart/alternative; boundary="b1_c9f501da4669604e1dcdf6de835d4708" --b1_c9f501da4669604e1dcdf6de835d4708 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit Buenas tardes! Promo Febrero - Sólo hasta agotar plazas disponibles: Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $215/mes .- (u$d 45.-) Promoción internacional para varios países. Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing. Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente. Recibes las respuestas en tu propio email. Regalo especial para clientes nuevos: ¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente. ¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos) No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles. Esperamos tu contacto en: maiadivicenzo@yahoo.com Te responderemos desde el email oficial de nuestra empresa. (Empresas de Email Marketing, consultar promociones especiales) Maia Divicenzo. La Revolución en Email Marketing +54(223)156140605 Internacional: +1.323.924.7376 -- Para desuscribirse, http://tmb443.info/lists/?p=unsubscribe&uid=c2c473d23e0b9036c15ae1799b90ffbc -- powered by phpList, www.phplist.com -- --b1_c9f501da4669604e1dcdf6de835d4708 Content-Type: text/html; charset = "UTF-8" Content-Transfer-Encoding: 8bit

Buenas tardes!

 

Promo Febrero - Sólo hasta agotar plazas disponibles:

 

Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $215/mes .- (u$d 45.-) Promoción internacional para varios países.

 

Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing.

Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente.

Recibes las respuestas en tu propio email.

 

Regalo especial para clientes nuevos:

 

¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente.

 

¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos)

 

No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles.

 

Esperamos tu contacto en:

maiadivicenzo@yahoo.com

 

Te responderemos desde el email oficial de nuestra empresa.

 

(Empresas de Email Marketing, consultar promociones especiales)

 

Maia Divicenzo.

 

La Revolución en Email Marketing

+54(223)156140605  
Internacional: +1.323.924.7376

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



--
Para desuscribirse, this link
powered by phplist v 2.10.14, © phpList ltd
--b1_c9f501da4669604e1dcdf6de835d4708-- --===============8917774597558720246== 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 --===============8917774597558720246==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCd-0006J7-F7; Fri, 03 May 2013 12:35:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB2Vg-00079y-2h for xen-arm@lists.xen.org; Thu, 28 Feb 2013 12:22:52 +0000 Received: from [85.158.138.51:2933] by server-12.bemta-3.messagelabs.com id 29/E7-01357-B1C4F215; Thu, 28 Feb 2013 12:22:51 +0000 X-Env-Sender: Shubham.Khandelwal@harman.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1362054170!20761694!1 X-Originating-IP: [195.245.230.164] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjI0NS4yMzAuMTY0ID0+IDc5NTI5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8230 invoked from network); 28 Feb 2013 12:22:50 -0000 Received: from mail1.bemta3.messagelabs.com (HELO mail1.bemta3.messagelabs.com) (195.245.230.164) by server-7.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Feb 2013 12:22:50 -0000 Received: from [85.158.137.3:23089] by server-4.bemta-3.messagelabs.com id B2/49-21470-A1C4F215; Thu, 28 Feb 2013 12:22:50 +0000 X-Env-Sender: Shubham.Khandelwal@harman.com X-Msg-Ref: server-15.tower-38.messagelabs.com!1362054169!15259052!1 X-Originating-IP: [194.121.90.173] X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17514 invoked from network); 28 Feb 2013 12:22:49 -0000 Received: from unassigned (HELO HIKAWSEX03.ad.harman.com) (194.121.90.173) by server-15.tower-38.messagelabs.com with AES128-SHA encrypted SMTP; 28 Feb 2013 12:22:49 -0000 Received: from HIKAWSEX01.ad.harman.com ([fe80::f023:31d4:f809:b22e]) by HIKAWSEX03.ad.harman.com ([172.16.1.217]) with mapi; Thu, 28 Feb 2013 13:22:49 +0100 From: "Khandelwal, Shubham" To: "'xen-arm@lists.xen.org'" Date: Thu, 28 Feb 2013 13:22:48 +0100 Thread-Topic: release for v4.3 Thread-Index: Ac4Vrk2jhadA713FTfSumgd4vFmCHQ== Message-ID: <3A6586556649FF42BA3240F179473FD11409A0568F@HIKAWSEX01.ad.harman.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: "Datta, Souvik" Subject: [XenARM] release for v4.3 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="===============3953613373897710233==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3953613373897710233== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3A6586556649FF42BA3240F179473FD11409A0568FHIKAWSEX01adh_" --_000_3A6586556649FF42BA3240F179473FD11409A0568FHIKAWSEX01adh_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I would like to know when will Xen-Arm version 4.3 which co= ntains support for Virtualization Extensions in cortex A15 will be released= . Also are there any plans in pipeline to support the TI based OMAP5 hardwa= re which supports these Virtualization Extensions on A15. Will the 4.3 rele= ase be a part of the Xen stable releases ? Thanks and Regards Shubham Khandelwal --_000_3A6586556649FF42BA3240F179473FD11409A0568FHIKAWSEX01adh_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

 

 =             &nb= sp;  I would like to know when will Xen-Arm version 4.3 which contains= support for Virtualization Extensions in cortex A15 will be released. Also= are there any plans in pipeline to support the TI based OMAP5 hardware whi= ch supports these Virtualization Extensions on A15. Will the 4.3 release be= a part of the Xen stable releases ?

 

 

Thanks and Regards

 

Shubham Khandelwal

 

= --_000_3A6586556649FF42BA3240F179473FD11409A0568FHIKAWSEX01adh_-- --===============3953613373897710233== 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 --===============3953613373897710233==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCd-0006J7-F7; Fri, 03 May 2013 12:35:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UB2Vg-00079y-2h for xen-arm@lists.xen.org; Thu, 28 Feb 2013 12:22:52 +0000 Received: from [85.158.138.51:2933] by server-12.bemta-3.messagelabs.com id 29/E7-01357-B1C4F215; Thu, 28 Feb 2013 12:22:51 +0000 X-Env-Sender: Shubham.Khandelwal@harman.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1362054170!20761694!1 X-Originating-IP: [195.245.230.164] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjI0NS4yMzAuMTY0ID0+IDc5NTI5\n X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8230 invoked from network); 28 Feb 2013 12:22:50 -0000 Received: from mail1.bemta3.messagelabs.com (HELO mail1.bemta3.messagelabs.com) (195.245.230.164) by server-7.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Feb 2013 12:22:50 -0000 Received: from [85.158.137.3:23089] by server-4.bemta-3.messagelabs.com id B2/49-21470-A1C4F215; Thu, 28 Feb 2013 12:22:50 +0000 X-Env-Sender: Shubham.Khandelwal@harman.com X-Msg-Ref: server-15.tower-38.messagelabs.com!1362054169!15259052!1 X-Originating-IP: [194.121.90.173] X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17514 invoked from network); 28 Feb 2013 12:22:49 -0000 Received: from unassigned (HELO HIKAWSEX03.ad.harman.com) (194.121.90.173) by server-15.tower-38.messagelabs.com with AES128-SHA encrypted SMTP; 28 Feb 2013 12:22:49 -0000 Received: from HIKAWSEX01.ad.harman.com ([fe80::f023:31d4:f809:b22e]) by HIKAWSEX03.ad.harman.com ([172.16.1.217]) with mapi; Thu, 28 Feb 2013 13:22:49 +0100 From: "Khandelwal, Shubham" To: "'xen-arm@lists.xen.org'" Date: Thu, 28 Feb 2013 13:22:48 +0100 Thread-Topic: release for v4.3 Thread-Index: Ac4Vrk2jhadA713FTfSumgd4vFmCHQ== Message-ID: <3A6586556649FF42BA3240F179473FD11409A0568F@HIKAWSEX01.ad.harman.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: "Datta, Souvik" Subject: [XenARM] release for v4.3 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="===============3953613373897710233==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3953613373897710233== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3A6586556649FF42BA3240F179473FD11409A0568FHIKAWSEX01adh_" --_000_3A6586556649FF42BA3240F179473FD11409A0568FHIKAWSEX01adh_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I would like to know when will Xen-Arm version 4.3 which co= ntains support for Virtualization Extensions in cortex A15 will be released= . Also are there any plans in pipeline to support the TI based OMAP5 hardwa= re which supports these Virtualization Extensions on A15. Will the 4.3 rele= ase be a part of the Xen stable releases ? Thanks and Regards Shubham Khandelwal --_000_3A6586556649FF42BA3240F179473FD11409A0568FHIKAWSEX01adh_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

 

 =             &nb= sp;  I would like to know when will Xen-Arm version 4.3 which contains= support for Virtualization Extensions in cortex A15 will be released. Also= are there any plans in pipeline to support the TI based OMAP5 hardware whi= ch supports these Virtualization Extensions on A15. Will the 4.3 release be= a part of the Xen stable releases ?

 

 

Thanks and Regards

 

Shubham Khandelwal

 

= --_000_3A6586556649FF42BA3240F179473FD11409A0568FHIKAWSEX01adh_-- --===============3953613373897710233== 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 --===============3953613373897710233==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCe-0006K6-3w; Fri, 03 May 2013 12:35:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UDIPh-0000Dv-GA for xen-arm@lists.xensource.com; Wed, 06 Mar 2013 17:46:01 +0000 Received: from [85.158.138.51:50618] by server-14.bemta-3.messagelabs.com id 0B/C7-27076-8D087315; Wed, 06 Mar 2013 17:46:00 +0000 X-Env-Sender: apache@u15729190.onlinehome-server.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1362591955!29551962!1 X-Originating-IP: [74.208.231.119] X-SpamReason: No, hits=2.0 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,INFO_TLD,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29633 invoked from network); 6 Mar 2013 17:45:56 -0000 Received: from tmb440.info (HELO u15729190.onlinehome-server.com) (74.208.231.119) by server-2.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Mar 2013 17:45:56 -0000 Received: from u15729190.onlinehome-server.com (unknown [127.0.0.1]) by u15729190.onlinehome-server.com (Postfix) with ESMTP id B62AE412760 for ; Wed, 6 Mar 2013 17:45:31 +0000 (UTC) Received: by u15729190.onlinehome-server.com (Postfix, from userid 48) id AB95741273A; Wed, 6 Mar 2013 17:45:31 +0000 (UTC) To: xen-arm@lists.xensource.com Date: Wed, 6 Mar 2013 14:45:31 -0300 From: Maia Divicenzo Message-ID: <87a7d02feb0c713fd9cea8b43d4b8e3c@tmb443.info> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.14 X-MessageID: 5 X-ListMember: xen-arm@lists.xensource.com MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Subject: [XenARM] Envios ilimitados de emails por solo $250. Cupos limitados 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="===============5772605763050826706==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============5772605763050826706== Content-Type: multipart/alternative; boundary="b1_87a7d02feb0c713fd9cea8b43d4b8e3c" --b1_87a7d02feb0c713fd9cea8b43d4b8e3c Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit Buenas tardes! Promo Marzo - Sólo hasta agotar plazas disponibles: Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $250/mes .- Promoción internacional para varios países. Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing. Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente. Recibes las respuestas en tu propio email. Regalo especial para clientes nuevos: ¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente. ¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos) No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles. Esperamos tu contacto en: maiadivicenzo@yahoo.com Te responderemos desde el email oficial de nuestra empresa. (Empresas de Email Marketing, consultar promociones especiales) Maia Divicenzo. La Revolución en Email Marketing +54(223)156140605 Internacional: +1.323.924.7376 -- Para desuscribirse, http://tmb443.info/lists/?p=unsubscribe&uid=c2c473d23e0b9036c15ae1799b90ffbc -- powered by phpList, www.phplist.com -- --b1_87a7d02feb0c713fd9cea8b43d4b8e3c Content-Type: text/html; charset = "UTF-8" Content-Transfer-Encoding: 8bit

Buenas tardes!

 

Promo Marzo - Sólo hasta agotar plazas disponibles:

 

Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $250/mes .- Promoción internacional para varios países.

 

Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing.

Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente.

Recibes las respuestas en tu propio email.

 

Regalo especial para clientes nuevos:

 

¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente.

 

¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos)

 

No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles.

 

Esperamos tu contacto en:

maiadivicenzo@yahoo.com

 

Te responderemos desde el email oficial de nuestra empresa.

 

(Empresas de Email Marketing, consultar promociones especiales)

 

Maia Divicenzo.

 

La Revolución en Email Marketing

+54(223)156140605  
Internacional: +1.323.924.7376

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



--
Para desuscribirse, this link
powered by phplist v 2.10.14, © phpList ltd
--b1_87a7d02feb0c713fd9cea8b43d4b8e3c-- --===============5772605763050826706== 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 --===============5772605763050826706==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCe-0006K6-3w; Fri, 03 May 2013 12:35:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UDIPh-0000Dv-GA for xen-arm@lists.xensource.com; Wed, 06 Mar 2013 17:46:01 +0000 Received: from [85.158.138.51:50618] by server-14.bemta-3.messagelabs.com id 0B/C7-27076-8D087315; Wed, 06 Mar 2013 17:46:00 +0000 X-Env-Sender: apache@u15729190.onlinehome-server.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1362591955!29551962!1 X-Originating-IP: [74.208.231.119] X-SpamReason: No, hits=2.0 required=7.0 tests=FORGED_YAHOO_RCVD, HTML_MESSAGE,INFO_TLD,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29633 invoked from network); 6 Mar 2013 17:45:56 -0000 Received: from tmb440.info (HELO u15729190.onlinehome-server.com) (74.208.231.119) by server-2.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Mar 2013 17:45:56 -0000 Received: from u15729190.onlinehome-server.com (unknown [127.0.0.1]) by u15729190.onlinehome-server.com (Postfix) with ESMTP id B62AE412760 for ; Wed, 6 Mar 2013 17:45:31 +0000 (UTC) Received: by u15729190.onlinehome-server.com (Postfix, from userid 48) id AB95741273A; Wed, 6 Mar 2013 17:45:31 +0000 (UTC) To: xen-arm@lists.xensource.com Date: Wed, 6 Mar 2013 14:45:31 -0300 From: Maia Divicenzo Message-ID: <87a7d02feb0c713fd9cea8b43d4b8e3c@tmb443.info> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.14 X-MessageID: 5 X-ListMember: xen-arm@lists.xensource.com MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Subject: [XenARM] Envios ilimitados de emails por solo $250. Cupos limitados 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="===============5772605763050826706==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============5772605763050826706== Content-Type: multipart/alternative; boundary="b1_87a7d02feb0c713fd9cea8b43d4b8e3c" --b1_87a7d02feb0c713fd9cea8b43d4b8e3c Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit Buenas tardes! Promo Marzo - Sólo hasta agotar plazas disponibles: Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $250/mes .- Promoción internacional para varios países. Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing. Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente. Recibes las respuestas en tu propio email. Regalo especial para clientes nuevos: ¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente. ¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos) No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles. Esperamos tu contacto en: maiadivicenzo@yahoo.com Te responderemos desde el email oficial de nuestra empresa. (Empresas de Email Marketing, consultar promociones especiales) Maia Divicenzo. La Revolución en Email Marketing +54(223)156140605 Internacional: +1.323.924.7376 -- Para desuscribirse, http://tmb443.info/lists/?p=unsubscribe&uid=c2c473d23e0b9036c15ae1799b90ffbc -- powered by phpList, www.phplist.com -- --b1_87a7d02feb0c713fd9cea8b43d4b8e3c Content-Type: text/html; charset = "UTF-8" Content-Transfer-Encoding: 8bit

Buenas tardes!

 

Promo Marzo - Sólo hasta agotar plazas disponibles:

 

Ingresando este mes podrás utilizar toda nuestra tecnología de envíos masivos de emails por sólo $250/mes .- Promoción internacional para varios países.

 

Podrás enviar una cantidad ilimitada de emails para conseguir más ventas, más contactos, para hacer crecer tu negocio a través de esta gran herramienta del email marketing.

Contamos con tecnología propia de alta performance para suplir tus necesidades. Fácil, simple y eficiente.

Recibes las respuestas en tu propio email.

 

Regalo especial para clientes nuevos:

 

¿No tienes bases de datos? Puedes utilizar las nuestras. Te entregamos el sistema con bases instaladas de acuerdo a tu zona objetivo y además podrás utilizar las propias. Una vez que nos pruebes, querrás seguir como cliente.

 

¿Necesitás bases especiales? Tenemos un equipo de especialistas para obtener lo que estás buscando. (Consultar costos)

 

No pierdas tu plataforma a precio especial promoción. Pocas plazas disponibles.

 

Esperamos tu contacto en:

maiadivicenzo@yahoo.com

 

Te responderemos desde el email oficial de nuestra empresa.

 

(Empresas de Email Marketing, consultar promociones especiales)

 

Maia Divicenzo.

 

La Revolución en Email Marketing

+54(223)156140605  
Internacional: +1.323.924.7376

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



--
Para desuscribirse, this link
powered by phplist v 2.10.14, © phpList ltd
--b1_87a7d02feb0c713fd9cea8b43d4b8e3c-- --===============5772605763050826706== 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 --===============5772605763050826706==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCe-0006Ko-CG; Fri, 03 May 2013 12:35:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UPyzm-0007wV-4C; Wed, 10 Apr 2013 17:39:42 +0000 Received: from [193.109.254.147:27229] by server-16.bemta-14.messagelabs.com id 63/CB-20064-DD3A5615; Wed, 10 Apr 2013 17:39:41 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1365615578!8629255!1 X-Originating-IP: [209.85.210.174] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_10_20,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17315 invoked from network); 10 Apr 2013 17:39:40 -0000 Received: from mail-ia0-f174.google.com (HELO mail-ia0-f174.google.com) (209.85.210.174) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2013 17:39:40 -0000 Received: by mail-ia0-f174.google.com with SMTP id r13so634235iar.5 for ; Wed, 10 Apr 2013 10:39:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=mJtHyvDOBPdD5F+wahUgt0x5WlXTCY3zeiC6IgkMRB4=; b=rs340CSXAffja2oQ3k+La+eQcYDaRwmiCzvZ767cyyssfO2FgXtKZUrolt5kSkQiiS ypDNOYx0cx1DryJGnee1eFNd90iqb7oZKTBrT0RdxXWn4kvWb2mMJNNXDfY9e2I9oRwK imxvsUJOB9cvhVXx/cXHkaVXLu6M3XwXw8mg7EljmLxUhIj/OOiTBz9+fLryI9zSAFmM waM3yHT+cHBvSYG/MJbhREnlaMTjeGhb1X12LJLyLLF/QlIgbi1Rf3VuYRJSZpflQNvl t6z+qs6828k/Und/YTcX+E6E9doQMffIRyCjgJfGk6S2DqXh16Y/5Up8qxlDeivFZ1IU FzMA== MIME-Version: 1.0 X-Received: by 10.50.13.228 with SMTP id k4mr13823265igc.30.1365615578625; Wed, 10 Apr 2013 10:39:38 -0700 (PDT) Received: by 10.42.237.198 with HTTP; Wed, 10 Apr 2013 10:39:38 -0700 (PDT) Received: by 10.42.237.198 with HTTP; Wed, 10 Apr 2013 10:39:38 -0700 (PDT) In-Reply-To: <5165A076.5040300@xen.org> References: <5165A076.5040300@xen.org> Date: Wed, 10 Apr 2013 11:39:38 -0600 Message-ID: From: jacek burghardt To: lars.kurth@xen.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: xen-users , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , xen-arm@lists.xen.org Subject: Re: [XenARM] [Xen-devel] Xen has now a Facebook page : invitation Project Leads, Committers and Maintainers to be content creators 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="===============2023804047585984634==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============2023804047585984634== Content-Type: multipart/alternative; boundary=f46d04462d4676c83f04da05270d --f46d04462d4676c83f04da05270d Content-Type: text/plain; charset=ISO-8859-1 That is great xen needs forum. --f46d04462d4676c83f04da05270d Content-Type: text/html; charset=ISO-8859-1

That is great xen needs forum.

--f46d04462d4676c83f04da05270d-- --===============2023804047585984634== 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 --===============2023804047585984634==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:08 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCe-0006Ko-CG; Fri, 03 May 2013 12:35:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UPyzm-0007wV-4C; Wed, 10 Apr 2013 17:39:42 +0000 Received: from [193.109.254.147:27229] by server-16.bemta-14.messagelabs.com id 63/CB-20064-DD3A5615; Wed, 10 Apr 2013 17:39:41 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1365615578!8629255!1 X-Originating-IP: [209.85.210.174] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_10_20,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17315 invoked from network); 10 Apr 2013 17:39:40 -0000 Received: from mail-ia0-f174.google.com (HELO mail-ia0-f174.google.com) (209.85.210.174) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2013 17:39:40 -0000 Received: by mail-ia0-f174.google.com with SMTP id r13so634235iar.5 for ; Wed, 10 Apr 2013 10:39:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=mJtHyvDOBPdD5F+wahUgt0x5WlXTCY3zeiC6IgkMRB4=; b=rs340CSXAffja2oQ3k+La+eQcYDaRwmiCzvZ767cyyssfO2FgXtKZUrolt5kSkQiiS ypDNOYx0cx1DryJGnee1eFNd90iqb7oZKTBrT0RdxXWn4kvWb2mMJNNXDfY9e2I9oRwK imxvsUJOB9cvhVXx/cXHkaVXLu6M3XwXw8mg7EljmLxUhIj/OOiTBz9+fLryI9zSAFmM waM3yHT+cHBvSYG/MJbhREnlaMTjeGhb1X12LJLyLLF/QlIgbi1Rf3VuYRJSZpflQNvl t6z+qs6828k/Und/YTcX+E6E9doQMffIRyCjgJfGk6S2DqXh16Y/5Up8qxlDeivFZ1IU FzMA== MIME-Version: 1.0 X-Received: by 10.50.13.228 with SMTP id k4mr13823265igc.30.1365615578625; Wed, 10 Apr 2013 10:39:38 -0700 (PDT) Received: by 10.42.237.198 with HTTP; Wed, 10 Apr 2013 10:39:38 -0700 (PDT) Received: by 10.42.237.198 with HTTP; Wed, 10 Apr 2013 10:39:38 -0700 (PDT) In-Reply-To: <5165A076.5040300@xen.org> References: <5165A076.5040300@xen.org> Date: Wed, 10 Apr 2013 11:39:38 -0600 Message-ID: From: jacek burghardt To: lars.kurth@xen.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: xen-users , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , xen-arm@lists.xen.org Subject: Re: [XenARM] [Xen-devel] Xen has now a Facebook page : invitation Project Leads, Committers and Maintainers to be content creators 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="===============2023804047585984634==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============2023804047585984634== Content-Type: multipart/alternative; boundary=f46d04462d4676c83f04da05270d --f46d04462d4676c83f04da05270d Content-Type: text/plain; charset=ISO-8859-1 That is great xen needs forum. --f46d04462d4676c83f04da05270d Content-Type: text/html; charset=ISO-8859-1

That is great xen needs forum.

--f46d04462d4676c83f04da05270d-- --===============2023804047585984634== 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 --===============2023804047585984634==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCe-0006LS-KR; Fri, 03 May 2013 12:35:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UQExy-0003bw-Km; Thu, 11 Apr 2013 10:42:54 +0000 Received: from [85.158.143.99:45153] by server-1.bemta-4.messagelabs.com id 5F/29-06203-DA396615; Thu, 11 Apr 2013 10:42:53 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1365676972!22431973!1 X-Originating-IP: [74.125.82.53] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3823 invoked from network); 11 Apr 2013 10:42:52 -0000 Received: from mail-wg0-f53.google.com (HELO mail-wg0-f53.google.com) (74.125.82.53) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 11 Apr 2013 10:42:52 -0000 Received: by mail-wg0-f53.google.com with SMTP id c11so1503915wgh.20 for ; Thu, 11 Apr 2013 03:42:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:subject:message-id:importance:from:to:cc :mime-version:content-type; bh=XNJU3SIKcx1tyL8LUJZhXhDZbmhsDlXRCptpntMo9QU=; b=AduYAnmFNT9qO9+da4CMVfGo+iPR5/1msqBQmLG9BXXDU5MDzbxoHbbzHhj82vV5bH lPIi2sT5B12nAQNic4u3qcZVb4b0Gyd01k+gXnR2ibFTWNQcoWTXiYcuNnY6J1jkFB2X U3UI7Si8xC8SFpI6x15KuYIWzxsmy0uOT+AoyqUKHxgeabv/BHUGE2jFTz6xkakMmXt4 cemBaxt4ARFpC5HnlB6F4oay14rQpmcmEES5UXtwFR06ZuRaSpK/H1dXl/N8rbh3APbZ Qnh38RW0neRDtcInkS7SBO5wkY516J1ycyvDGLkiyG2U2ZWQ8Kl76iwSu3vG0vWyjMax 4U4A== X-Received: by 10.194.178.100 with SMTP id cx4mr9689277wjc.47.1365676972512; Thu, 11 Apr 2013 03:42:52 -0700 (PDT) Received: from localhost ([31.124.158.184]) by mx.google.com with ESMTPS id dp5sm2314606wib.1.2013.04.11.03.42.49 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 11 Apr 2013 03:42:51 -0700 (PDT) Date: Thu, 11 Apr 2013 11:42:49 +0100 Message-ID: Importance: normal From: "Lars.kurth.xen" To: george.dunlap@eu.citrix.com, lars.kurth@xen.org MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: xen-users@lists.xen.org, xen-arm@lists.xen.org, xen-api@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] [Xen-devel] Xen has now a Facebook page : invitation Project Leads, Committers and Maintainers to be content creators 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="===============3027801692698945749==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3027801692698945749== Content-Type: multipart/alternative; boundary="--_com.android.email_60869619142621" ----_com.android.email_60869619142621 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 SW5kZWVkOiB0aGUgZW1haWwgYXNzb2NpYXRlZCB3aXRoIHlvdXIgCGZhY2Vib29rIGFjY291bnQu IERvbnQgc2VuZCBpdCBvbiB0aGUgbGlzdCwgYnV0IHRvIG1lIG9ubHkuCkxhcnMKCgpTZW50IGZy b20gU2Ftc3VuZ1NhbXN1bmcgTW9iaWxlCgotLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0t LS0tClN1YmplY3Q6IFJlOiBbWGVuLWRldmVsXSBYZW4gaGFzIG5vdyBhIEZhY2Vib29rIHBhZ2Ug OiBpbnZpdGF0aW9uIFByb2plY3QgTGVhZHMsIENvbW1pdHRlcnMgYW5kIE1haW50YWluZXJzIHRv IGJlIGNvbnRlbnQgY3JlYXRvcnMgCkZyb206IEdlb3JnZSBEdW5sYXAgPEdlb3JnZS5EdW5sYXBA ZXUuY2l0cml4LmNvbT4gClRvOiBMYXJzIEt1cnRoIDxsYXJzLmt1cnRoQHhlbi5vcmc+IApDQzog Inhlbi1kZXZlbEBsaXN0cy54ZW4ub3JnIiA8eGVuLWRldmVsQGxpc3RzLnhlbi5vcmc+LCJ4ZW4t dXNlcnNAbGlzdHMueGVuLm9yZyIgPHhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnPiwieGVuLWFwaUBs aXN0cy54ZW4ub3JnIiA8eGVuLWFwaUBsaXN0cy54ZW4ub3JnPix4ZW4tYXJtQGxpc3RzLnhlbi5v cmcgCgpPbiBXZWQsIEFwciAxMCwgMjAxMyBhdCA2OjI1IFBNLCBMYXJzIEt1cnRoIDxsYXJzLmt1 cnRoQHhlbi5vcmc+IHdyb3RlOgo+IEhpIGV2ZXJ5Ym9keSwKPgo+IFhlbiBoYXMgbm93IGEgZmFj ZWJvb2sgcGFnZS4gSXQgaXMgc3RpbGwgcHJldHR5IHVucG9wdWxhdGVkLiBBcyB0aGlzIGlzIGEK PiBjb21tdW5pdHkgcGFnZSwgSSB3YW50ZWQgdG8gaW5pdGlhbGx5IGludml0ZSBQcm9qZWN0IExl YWRzLCBDb21taXR0ZXJzIGFuZAo+IE1haW50YWluZXJzIG9mIGFsbCBwcm9qZWN0cyB0byBiZSBD b250ZW50IENyZWF0b3Igb2YgdGhlIHBhZ2UuIFRoaXMgbWVhbnMKPiBha2EgeW91IGNhbiBlZGl0 IHRoZSBwYWdlLCBzZW5kIG1lc3NhZ2VzIGFuZCBjcmVhdGUgcG9zdHMgb24gYmVoYWxmIG9mIHRo ZQo+IHBhZ2UsIGNyZWF0ZSBhZHZlcnRzIGFuZCB2aWV3IGluc2lnaHRzLiBUbyBkbyB0aGlzIHlv dSBuZWVkIHRvCj4gYSkgTGlrZSB0aGUgcGFnZQo+IGIpIFNlbmQgbWUgdGhlIGUtbWFpbCBhZGRy ZXNzIGFzc29jaWF0ZWQgd2l0aCB0aGUgcGFnZQoKSSBhc3N1bWUgeW91IG1lYW4sICJhbiBlLW1h aWwgYWRkcmVzcyBhc3NvY2lhdGVkIHdpdGggeW91ciBGQiBhY2NvdW50Ij8KCi1HZW9yZ2UK ----_com.android.email_60869619142621 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT5JbmRlZWQ6IHRoZSBlbWFpbCBhc3Nv Y2lhdGVkIHdpdGggeW91ciAIZmFjZWJvb2sgYWNjb3VudC4gRG9udCBzZW5kIGl0IG9uIHRoZSBs aXN0LCBidXQgdG8gbWUgb25seS48ZGl2PkxhcnM8L2Rpdj48ZGl2Pjxicj48YnI+PHNwYW4gc3R5 bGU9ImZvbnQtc2l6ZTo4NyUiPlNlbnQgZnJvbSBTYW1zdW5nU2Ftc3VuZyBNb2JpbGU8L3NwYW4+ IDwvZGl2Pjxicj48YnI+PGJyPi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS08YnI+ U3ViamVjdDogUmU6IFtYZW4tZGV2ZWxdIFhlbiBoYXMgbm93IGEgRmFjZWJvb2sgcGFnZSA6IGlu dml0YXRpb24gUHJvamVjdCBMZWFkcywgQ29tbWl0dGVycyBhbmQgTWFpbnRhaW5lcnMgdG8gYmUg Y29udGVudCBjcmVhdG9ycyA8YnI+RnJvbTogR2VvcmdlIER1bmxhcCAmbHQ7R2VvcmdlLkR1bmxh cEBldS5jaXRyaXguY29tJmd0OyA8YnI+VG86IExhcnMgS3VydGggJmx0O2xhcnMua3VydGhAeGVu Lm9yZyZndDsgPGJyPkNDOiAieGVuLWRldmVsQGxpc3RzLnhlbi5vcmciICZsdDt4ZW4tZGV2ZWxA bGlzdHMueGVuLm9yZyZndDssInhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnIiAmbHQ7eGVuLXVzZXJz QGxpc3RzLnhlbi5vcmcmZ3Q7LCJ4ZW4tYXBpQGxpc3RzLnhlbi5vcmciICZsdDt4ZW4tYXBpQGxp c3RzLnhlbi5vcmcmZ3Q7LHhlbi1hcm1AbGlzdHMueGVuLm9yZyA8YnI+PGJyPjxicj48ZGl2IHN0 eWxlPSJ3b3JkLWJyZWFrOmJyZWFrLWFsbDsiPk9uIFdlZCwgQXByIDEwLCAyMDEzIGF0IDY6MjUg UE0sIExhcnMgS3VydGggJmx0O2xhcnMua3VydGhAeGVuLm9yZyZndDsgd3JvdGU6PGJyPiZndDsg SGkgZXZlcnlib2R5LDxicj4mZ3Q7PGJyPiZndDsgWGVuIGhhcyBub3cgYSBmYWNlYm9vayBwYWdl LiBJdCBpcyBzdGlsbCBwcmV0dHkgdW5wb3B1bGF0ZWQuIEFzIHRoaXMgaXMgYTxicj4mZ3Q7IGNv bW11bml0eSBwYWdlLCBJIHdhbnRlZCB0byBpbml0aWFsbHkgaW52aXRlIFByb2plY3QgTGVhZHMs IENvbW1pdHRlcnMgYW5kPGJyPiZndDsgTWFpbnRhaW5lcnMgb2YgYWxsIHByb2plY3RzIHRvIGJl IENvbnRlbnQgQ3JlYXRvciBvZiB0aGUgcGFnZS4gVGhpcyBtZWFuczxicj4mZ3Q7IGFrYSB5b3Ug Y2FuIGVkaXQgdGhlIHBhZ2UsIHNlbmQgbWVzc2FnZXMgYW5kIGNyZWF0ZSBwb3N0cyBvbiBiZWhh bGYgb2YgdGhlPGJyPiZndDsgcGFnZSwgY3JlYXRlIGFkdmVydHMgYW5kIHZpZXcgaW5zaWdodHMu IFRvIGRvIHRoaXMgeW91IG5lZWQgdG88YnI+Jmd0OyBhKSBMaWtlIHRoZSBwYWdlPGJyPiZndDsg YikgU2VuZCBtZSB0aGUgZS1tYWlsIGFkZHJlc3MgYXNzb2NpYXRlZCB3aXRoIHRoZSBwYWdlPGJy Pjxicj5JIGFzc3VtZSB5b3UgbWVhbiwgImFuIGUtbWFpbCBhZGRyZXNzIGFzc29jaWF0ZWQgd2l0 aCB5b3VyIEZCIGFjY291bnQiPzxicj48YnI+IC1HZW9yZ2U8YnI+PC9kaXY+IDwvYm9keT4= ----_com.android.email_60869619142621-- --===============3027801692698945749== 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 --===============3027801692698945749==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCe-0006LS-KR; Fri, 03 May 2013 12:35:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UQExy-0003bw-Km; Thu, 11 Apr 2013 10:42:54 +0000 Received: from [85.158.143.99:45153] by server-1.bemta-4.messagelabs.com id 5F/29-06203-DA396615; Thu, 11 Apr 2013 10:42:53 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1365676972!22431973!1 X-Originating-IP: [74.125.82.53] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3823 invoked from network); 11 Apr 2013 10:42:52 -0000 Received: from mail-wg0-f53.google.com (HELO mail-wg0-f53.google.com) (74.125.82.53) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 11 Apr 2013 10:42:52 -0000 Received: by mail-wg0-f53.google.com with SMTP id c11so1503915wgh.20 for ; Thu, 11 Apr 2013 03:42:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:subject:message-id:importance:from:to:cc :mime-version:content-type; bh=XNJU3SIKcx1tyL8LUJZhXhDZbmhsDlXRCptpntMo9QU=; b=AduYAnmFNT9qO9+da4CMVfGo+iPR5/1msqBQmLG9BXXDU5MDzbxoHbbzHhj82vV5bH lPIi2sT5B12nAQNic4u3qcZVb4b0Gyd01k+gXnR2ibFTWNQcoWTXiYcuNnY6J1jkFB2X U3UI7Si8xC8SFpI6x15KuYIWzxsmy0uOT+AoyqUKHxgeabv/BHUGE2jFTz6xkakMmXt4 cemBaxt4ARFpC5HnlB6F4oay14rQpmcmEES5UXtwFR06ZuRaSpK/H1dXl/N8rbh3APbZ Qnh38RW0neRDtcInkS7SBO5wkY516J1ycyvDGLkiyG2U2ZWQ8Kl76iwSu3vG0vWyjMax 4U4A== X-Received: by 10.194.178.100 with SMTP id cx4mr9689277wjc.47.1365676972512; Thu, 11 Apr 2013 03:42:52 -0700 (PDT) Received: from localhost ([31.124.158.184]) by mx.google.com with ESMTPS id dp5sm2314606wib.1.2013.04.11.03.42.49 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 11 Apr 2013 03:42:51 -0700 (PDT) Date: Thu, 11 Apr 2013 11:42:49 +0100 Message-ID: Importance: normal From: "Lars.kurth.xen" To: george.dunlap@eu.citrix.com, lars.kurth@xen.org MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: xen-users@lists.xen.org, xen-arm@lists.xen.org, xen-api@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [XenARM] [Xen-devel] Xen has now a Facebook page : invitation Project Leads, Committers and Maintainers to be content creators 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="===============3027801692698945749==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3027801692698945749== Content-Type: multipart/alternative; boundary="--_com.android.email_60869619142621" ----_com.android.email_60869619142621 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 SW5kZWVkOiB0aGUgZW1haWwgYXNzb2NpYXRlZCB3aXRoIHlvdXIgCGZhY2Vib29rIGFjY291bnQu IERvbnQgc2VuZCBpdCBvbiB0aGUgbGlzdCwgYnV0IHRvIG1lIG9ubHkuCkxhcnMKCgpTZW50IGZy b20gU2Ftc3VuZ1NhbXN1bmcgTW9iaWxlCgotLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0t LS0tClN1YmplY3Q6IFJlOiBbWGVuLWRldmVsXSBYZW4gaGFzIG5vdyBhIEZhY2Vib29rIHBhZ2Ug OiBpbnZpdGF0aW9uIFByb2plY3QgTGVhZHMsIENvbW1pdHRlcnMgYW5kIE1haW50YWluZXJzIHRv IGJlIGNvbnRlbnQgY3JlYXRvcnMgCkZyb206IEdlb3JnZSBEdW5sYXAgPEdlb3JnZS5EdW5sYXBA ZXUuY2l0cml4LmNvbT4gClRvOiBMYXJzIEt1cnRoIDxsYXJzLmt1cnRoQHhlbi5vcmc+IApDQzog Inhlbi1kZXZlbEBsaXN0cy54ZW4ub3JnIiA8eGVuLWRldmVsQGxpc3RzLnhlbi5vcmc+LCJ4ZW4t dXNlcnNAbGlzdHMueGVuLm9yZyIgPHhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnPiwieGVuLWFwaUBs aXN0cy54ZW4ub3JnIiA8eGVuLWFwaUBsaXN0cy54ZW4ub3JnPix4ZW4tYXJtQGxpc3RzLnhlbi5v cmcgCgpPbiBXZWQsIEFwciAxMCwgMjAxMyBhdCA2OjI1IFBNLCBMYXJzIEt1cnRoIDxsYXJzLmt1 cnRoQHhlbi5vcmc+IHdyb3RlOgo+IEhpIGV2ZXJ5Ym9keSwKPgo+IFhlbiBoYXMgbm93IGEgZmFj ZWJvb2sgcGFnZS4gSXQgaXMgc3RpbGwgcHJldHR5IHVucG9wdWxhdGVkLiBBcyB0aGlzIGlzIGEK PiBjb21tdW5pdHkgcGFnZSwgSSB3YW50ZWQgdG8gaW5pdGlhbGx5IGludml0ZSBQcm9qZWN0IExl YWRzLCBDb21taXR0ZXJzIGFuZAo+IE1haW50YWluZXJzIG9mIGFsbCBwcm9qZWN0cyB0byBiZSBD b250ZW50IENyZWF0b3Igb2YgdGhlIHBhZ2UuIFRoaXMgbWVhbnMKPiBha2EgeW91IGNhbiBlZGl0 IHRoZSBwYWdlLCBzZW5kIG1lc3NhZ2VzIGFuZCBjcmVhdGUgcG9zdHMgb24gYmVoYWxmIG9mIHRo ZQo+IHBhZ2UsIGNyZWF0ZSBhZHZlcnRzIGFuZCB2aWV3IGluc2lnaHRzLiBUbyBkbyB0aGlzIHlv dSBuZWVkIHRvCj4gYSkgTGlrZSB0aGUgcGFnZQo+IGIpIFNlbmQgbWUgdGhlIGUtbWFpbCBhZGRy ZXNzIGFzc29jaWF0ZWQgd2l0aCB0aGUgcGFnZQoKSSBhc3N1bWUgeW91IG1lYW4sICJhbiBlLW1h aWwgYWRkcmVzcyBhc3NvY2lhdGVkIHdpdGggeW91ciBGQiBhY2NvdW50Ij8KCi1HZW9yZ2UK ----_com.android.email_60869619142621 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT5JbmRlZWQ6IHRoZSBlbWFpbCBhc3Nv Y2lhdGVkIHdpdGggeW91ciAIZmFjZWJvb2sgYWNjb3VudC4gRG9udCBzZW5kIGl0IG9uIHRoZSBs aXN0LCBidXQgdG8gbWUgb25seS48ZGl2PkxhcnM8L2Rpdj48ZGl2Pjxicj48YnI+PHNwYW4gc3R5 bGU9ImZvbnQtc2l6ZTo4NyUiPlNlbnQgZnJvbSBTYW1zdW5nU2Ftc3VuZyBNb2JpbGU8L3NwYW4+ IDwvZGl2Pjxicj48YnI+PGJyPi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS08YnI+ U3ViamVjdDogUmU6IFtYZW4tZGV2ZWxdIFhlbiBoYXMgbm93IGEgRmFjZWJvb2sgcGFnZSA6IGlu dml0YXRpb24gUHJvamVjdCBMZWFkcywgQ29tbWl0dGVycyBhbmQgTWFpbnRhaW5lcnMgdG8gYmUg Y29udGVudCBjcmVhdG9ycyA8YnI+RnJvbTogR2VvcmdlIER1bmxhcCAmbHQ7R2VvcmdlLkR1bmxh cEBldS5jaXRyaXguY29tJmd0OyA8YnI+VG86IExhcnMgS3VydGggJmx0O2xhcnMua3VydGhAeGVu Lm9yZyZndDsgPGJyPkNDOiAieGVuLWRldmVsQGxpc3RzLnhlbi5vcmciICZsdDt4ZW4tZGV2ZWxA bGlzdHMueGVuLm9yZyZndDssInhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnIiAmbHQ7eGVuLXVzZXJz QGxpc3RzLnhlbi5vcmcmZ3Q7LCJ4ZW4tYXBpQGxpc3RzLnhlbi5vcmciICZsdDt4ZW4tYXBpQGxp c3RzLnhlbi5vcmcmZ3Q7LHhlbi1hcm1AbGlzdHMueGVuLm9yZyA8YnI+PGJyPjxicj48ZGl2IHN0 eWxlPSJ3b3JkLWJyZWFrOmJyZWFrLWFsbDsiPk9uIFdlZCwgQXByIDEwLCAyMDEzIGF0IDY6MjUg UE0sIExhcnMgS3VydGggJmx0O2xhcnMua3VydGhAeGVuLm9yZyZndDsgd3JvdGU6PGJyPiZndDsg SGkgZXZlcnlib2R5LDxicj4mZ3Q7PGJyPiZndDsgWGVuIGhhcyBub3cgYSBmYWNlYm9vayBwYWdl LiBJdCBpcyBzdGlsbCBwcmV0dHkgdW5wb3B1bGF0ZWQuIEFzIHRoaXMgaXMgYTxicj4mZ3Q7IGNv bW11bml0eSBwYWdlLCBJIHdhbnRlZCB0byBpbml0aWFsbHkgaW52aXRlIFByb2plY3QgTGVhZHMs IENvbW1pdHRlcnMgYW5kPGJyPiZndDsgTWFpbnRhaW5lcnMgb2YgYWxsIHByb2plY3RzIHRvIGJl IENvbnRlbnQgQ3JlYXRvciBvZiB0aGUgcGFnZS4gVGhpcyBtZWFuczxicj4mZ3Q7IGFrYSB5b3Ug Y2FuIGVkaXQgdGhlIHBhZ2UsIHNlbmQgbWVzc2FnZXMgYW5kIGNyZWF0ZSBwb3N0cyBvbiBiZWhh bGYgb2YgdGhlPGJyPiZndDsgcGFnZSwgY3JlYXRlIGFkdmVydHMgYW5kIHZpZXcgaW5zaWdodHMu IFRvIGRvIHRoaXMgeW91IG5lZWQgdG88YnI+Jmd0OyBhKSBMaWtlIHRoZSBwYWdlPGJyPiZndDsg YikgU2VuZCBtZSB0aGUgZS1tYWlsIGFkZHJlc3MgYXNzb2NpYXRlZCB3aXRoIHRoZSBwYWdlPGJy Pjxicj5JIGFzc3VtZSB5b3UgbWVhbiwgImFuIGUtbWFpbCBhZGRyZXNzIGFzc29jaWF0ZWQgd2l0 aCB5b3VyIEZCIGFjY291bnQiPzxicj48YnI+IC1HZW9yZ2U8YnI+PC9kaXY+IDwvYm9keT4= ----_com.android.email_60869619142621-- --===============3027801692698945749== 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 --===============3027801692698945749==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCe-0006Mj-VG; Fri, 03 May 2013 12:35:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USLHB-0007NU-Ai; Wed, 17 Apr 2013 05:51:25 +0000 Received: from [85.158.143.99:13062] by server-3.bemta-4.messagelabs.com id F4/97-02186-C583E615; Wed, 17 Apr 2013 05:51:24 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1366177881!25233124!1 X-Originating-IP: [209.85.219.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30580 invoked from network); 17 Apr 2013 05:51:23 -0000 Received: from mail-oa0-f43.google.com (HELO mail-oa0-f43.google.com) (209.85.219.43) by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Apr 2013 05:51:23 -0000 Received: by mail-oa0-f43.google.com with SMTP id l10so1241705oag.16 for ; Tue, 16 Apr 2013 22:51:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=IMFV2ZtN85ciXY3yuX81/WI4z/Zfk/bZmhOsjKyHHd8=; b=Aeghaocx9+/Ulp1g2NqJJ3HhKHnF2qhkqL0nNc8eDFb/CVmK+begbs4XWGMQNUFOiX k2h9O50raEesPTc3/ZEGd1NXKfBsMfGmReFtc2OflEkpXdMtQW1OL+8PuZKsrjD8Nxti ZU9TzcDohwtdW9I1N38kCsOw6wpE72zX4yr1Lmr42gC7EL8qn02taIdOSSe3gKyhD8u8 AO+nRbNWo1+6kARJGWuSVNTh9mUjYKliHQQ8kwBnt1Bpl0DHBHxHnoLYus29s//B7j36 uB6Bta9pNk6khtATdaUdqvNiiVk0AGPgFzbZDPdWukk4paQ9/Y4LpUz1pcD4nUIwaMyF GhJw== MIME-Version: 1.0 X-Received: by 10.60.15.98 with SMTP id w2mr2012092oec.128.1366177881109; Tue, 16 Apr 2013 22:51:21 -0700 (PDT) Received: by 10.60.46.33 with HTTP; Tue, 16 Apr 2013 22:51:21 -0700 (PDT) Date: Wed, 17 Apr 2013 06:51:21 +0100 Message-ID: From: Lars Kurth To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , xen-arm@lists.xen.org, "xen-users@lists.xen.org" X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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="===============8810449971387995236==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8810449971387995236== Content-Type: multipart/alternative; boundary=089e013a0a1e4dba4004da8813d2 --089e013a0a1e4dba4004da8813d2 Content-Type: text/plain; charset=ISO-8859-1 Hi everybody, we had a Xen Project Advisory Board meeting this morning and I had an action to get community input on XenSummit and Hackathon locations for 2014. I need to start tying these down pretty soon such that I can reserve the space. So I took an action to get community input. To remind you in 2013, XenSummit will be in Edinburgh, UK in October. So I took Europe off the menu for 2014 : please shout if this is an issue. Can I ask you to respond to this thread and order the options based on your preferences (highest first). I also wanted to remind you that a few months back, we had a discussion to distribute the summits more evenly around the globe. All options would be co-located with one or several Linux events. Here are the options for events: 1) Rio de Janeiro, May 2014 2) Chicago, end of August 2014 3) Korea, end of November 2014 Note that if we want to do an event in Rio, I have to book the space by mid-May this year. Also note that Chicago may be a bit busy with at least 2-3 other Linux events that are likely to take place at the same time (I remember there were some complaints that XenSummit 2012 in San Diego was a bit to stressful as too much was going on in the same week). Also note that Seattle, August 2015 would be an option to host XenSummit, assuming we didn't chose a US location in 2014. I will make a start and vote in order of my preference (highest first) for Rio, Korea, Chicago. My reasoning is that this would allow us to have a XenSummit in Rio and a Hackathon in Korea (or vice versa). This would fit nicely with a XenSummit in Seattle in 2015. As far as I can tell. there would also be fairly good alignment with the Xen release cycle. Let me know your preferences (but remember, I need to know by the end of April). Cheers Lars --089e013a0a1e4dba4004da8813d2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi everybody,

we had a Xen Project Advi= sory Board meeting this morning and I had an action to get community input = on XenSummit and Hackathon locations for 2014. I need to start tying these = down pretty soon such that I can reserve the space. So I took an action to = get community input. To remind you in 2013, XenSummit will be in Edinburgh,= UK in October. So I took Europe off the menu for 2014 : please shout if th= is is an issue.

Can I ask you to respond to this thre= ad and order the options based on your preferences (highest first). I also = wanted to remind you that a few months back, we had a discussion to distrib= ute the summits more evenly around the globe. All options would be co-locat= ed with one or several Linux events.

Here are the options for events:

1) Rio de Janeiro, May 2014=A0
2= ) Chicago, end of August 2014
3) Korea, end of November 201= 4

Note that if we want to do an event in Rio,= I have to book the space by mid-May this year. Also note that Chicago may = be a bit busy with at least 2-3 other Linux events that are likely to take = place at the same time (I remember there were some complaints that XenSummi= t 2012 in San Diego was a bit to stressful as too much was going on in the = same week). Also note that Seattle, August 2015 would be an option to host = XenSummit, assuming we didn't chose a US location in 2014.

I will make a start and vote in order of my= preference (highest first) for=A0
Rio, Korea, Chicago. =A0=

My reasoning is that this would allow= us to have a XenSummit in Rio and a Hackathon in Korea (or vice versa). Th= is would fit nicely with a XenSummit in Seattle in 2015. As far as I can te= ll. there would also be fairly good alignment with the Xen release cycle.= =A0

Let me know your preferences (but remember,= I need to know by the end of April).

= Cheers
Lars=A0

--089e013a0a1e4dba4004da8813d2-- --===============8810449971387995236== 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 --===============8810449971387995236==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCe-0006Mj-VG; Fri, 03 May 2013 12:35:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USLHB-0007NU-Ai; Wed, 17 Apr 2013 05:51:25 +0000 Received: from [85.158.143.99:13062] by server-3.bemta-4.messagelabs.com id F4/97-02186-C583E615; Wed, 17 Apr 2013 05:51:24 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-216.messagelabs.com!1366177881!25233124!1 X-Originating-IP: [209.85.219.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30580 invoked from network); 17 Apr 2013 05:51:23 -0000 Received: from mail-oa0-f43.google.com (HELO mail-oa0-f43.google.com) (209.85.219.43) by server-7.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Apr 2013 05:51:23 -0000 Received: by mail-oa0-f43.google.com with SMTP id l10so1241705oag.16 for ; Tue, 16 Apr 2013 22:51:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=IMFV2ZtN85ciXY3yuX81/WI4z/Zfk/bZmhOsjKyHHd8=; b=Aeghaocx9+/Ulp1g2NqJJ3HhKHnF2qhkqL0nNc8eDFb/CVmK+begbs4XWGMQNUFOiX k2h9O50raEesPTc3/ZEGd1NXKfBsMfGmReFtc2OflEkpXdMtQW1OL+8PuZKsrjD8Nxti ZU9TzcDohwtdW9I1N38kCsOw6wpE72zX4yr1Lmr42gC7EL8qn02taIdOSSe3gKyhD8u8 AO+nRbNWo1+6kARJGWuSVNTh9mUjYKliHQQ8kwBnt1Bpl0DHBHxHnoLYus29s//B7j36 uB6Bta9pNk6khtATdaUdqvNiiVk0AGPgFzbZDPdWukk4paQ9/Y4LpUz1pcD4nUIwaMyF GhJw== MIME-Version: 1.0 X-Received: by 10.60.15.98 with SMTP id w2mr2012092oec.128.1366177881109; Tue, 16 Apr 2013 22:51:21 -0700 (PDT) Received: by 10.60.46.33 with HTTP; Tue, 16 Apr 2013 22:51:21 -0700 (PDT) Date: Wed, 17 Apr 2013 06:51:21 +0100 Message-ID: From: Lars Kurth To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , xen-arm@lists.xen.org, "xen-users@lists.xen.org" X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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="===============8810449971387995236==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8810449971387995236== Content-Type: multipart/alternative; boundary=089e013a0a1e4dba4004da8813d2 --089e013a0a1e4dba4004da8813d2 Content-Type: text/plain; charset=ISO-8859-1 Hi everybody, we had a Xen Project Advisory Board meeting this morning and I had an action to get community input on XenSummit and Hackathon locations for 2014. I need to start tying these down pretty soon such that I can reserve the space. So I took an action to get community input. To remind you in 2013, XenSummit will be in Edinburgh, UK in October. So I took Europe off the menu for 2014 : please shout if this is an issue. Can I ask you to respond to this thread and order the options based on your preferences (highest first). I also wanted to remind you that a few months back, we had a discussion to distribute the summits more evenly around the globe. All options would be co-located with one or several Linux events. Here are the options for events: 1) Rio de Janeiro, May 2014 2) Chicago, end of August 2014 3) Korea, end of November 2014 Note that if we want to do an event in Rio, I have to book the space by mid-May this year. Also note that Chicago may be a bit busy with at least 2-3 other Linux events that are likely to take place at the same time (I remember there were some complaints that XenSummit 2012 in San Diego was a bit to stressful as too much was going on in the same week). Also note that Seattle, August 2015 would be an option to host XenSummit, assuming we didn't chose a US location in 2014. I will make a start and vote in order of my preference (highest first) for Rio, Korea, Chicago. My reasoning is that this would allow us to have a XenSummit in Rio and a Hackathon in Korea (or vice versa). This would fit nicely with a XenSummit in Seattle in 2015. As far as I can tell. there would also be fairly good alignment with the Xen release cycle. Let me know your preferences (but remember, I need to know by the end of April). Cheers Lars --089e013a0a1e4dba4004da8813d2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi everybody,

we had a Xen Project Advi= sory Board meeting this morning and I had an action to get community input = on XenSummit and Hackathon locations for 2014. I need to start tying these = down pretty soon such that I can reserve the space. So I took an action to = get community input. To remind you in 2013, XenSummit will be in Edinburgh,= UK in October. So I took Europe off the menu for 2014 : please shout if th= is is an issue.

Can I ask you to respond to this thre= ad and order the options based on your preferences (highest first). I also = wanted to remind you that a few months back, we had a discussion to distrib= ute the summits more evenly around the globe. All options would be co-locat= ed with one or several Linux events.

Here are the options for events:

1) Rio de Janeiro, May 2014=A0
2= ) Chicago, end of August 2014
3) Korea, end of November 201= 4

Note that if we want to do an event in Rio,= I have to book the space by mid-May this year. Also note that Chicago may = be a bit busy with at least 2-3 other Linux events that are likely to take = place at the same time (I remember there were some complaints that XenSummi= t 2012 in San Diego was a bit to stressful as too much was going on in the = same week). Also note that Seattle, August 2015 would be an option to host = XenSummit, assuming we didn't chose a US location in 2014.

I will make a start and vote in order of my= preference (highest first) for=A0
Rio, Korea, Chicago. =A0=

My reasoning is that this would allow= us to have a XenSummit in Rio and a Hackathon in Korea (or vice versa). Th= is would fit nicely with a XenSummit in Seattle in 2015. As far as I can te= ll. there would also be fairly good alignment with the Xen release cycle.= =A0

Let me know your preferences (but remember,= I need to know by the end of April).

= Cheers
Lars=A0

--089e013a0a1e4dba4004da8813d2-- --===============8810449971387995236== 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 --===============8810449971387995236==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCf-0006NN-60; Fri, 03 May 2013 12:35:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USTTt-0007Hq-93; Wed, 17 Apr 2013 14:37:05 +0000 Received: from [85.158.139.83:31304] by server-10.bemta-5.messagelabs.com id F7/4A-23714-F83BE615; Wed, 17 Apr 2013 14:37:03 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1366209413!25508712!1 X-Originating-IP: [209.85.219.44] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23143 invoked from network); 17 Apr 2013 14:36:58 -0000 Received: from mail-oa0-f44.google.com (HELO mail-oa0-f44.google.com) (209.85.219.44) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Apr 2013 14:36:58 -0000 Received: by mail-oa0-f44.google.com with SMTP id h1so1672687oag.3 for ; Wed, 17 Apr 2013 07:35:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=T90YnOtA2RO5+o2rhFir7FTl+ZSw7zOOcqZXuuWAu0k=; b=adkm0CLSk8V34/SXqZFxXsVp4xUtWrwh9aO3wprvkrb8pMa8i0bQL7aWTjWVFcz/rq Y9AP5lpjP5DFXo2H0TE/yqXRH6W+v6yDDhROjIJS/SogSVnqFQ/VBq3I+7pt+xj0akwi vXTQC06mWbDyrB1YhfKuTMKDEBUhayRfLQvrdf+z5vldcV+wMgpIf7EMgFBm6bYmqeUI KCVxJGP/fN5bfHHchNJr5QyP5toUpnP1ibONFVdV8XkPNRW3O6uC92a+H7vlYGdmCo4s ZjBusxJ/SRyhT8Cm/BeeqS57K+C1mhvkiASdWlWB5013RGon9SEgpYNaWxo2Liw2Iyv2 wFbQ== MIME-Version: 1.0 X-Received: by 10.60.37.68 with SMTP id w4mr2717312oej.62.1366209353615; Wed, 17 Apr 2013 07:35:53 -0700 (PDT) Received: by 10.60.13.1 with HTTP; Wed, 17 Apr 2013 07:35:53 -0700 (PDT) In-Reply-To: <619F5B48-3FC8-4C06-A570-171965AFE047@recoil.org> References: <1366203621.25579.25.camel@zakaz.uk.xensource.com> <619F5B48-3FC8-4C06-A570-171965AFE047@recoil.org> Date: Wed, 17 Apr 2013 15:35:53 +0100 Message-ID: From: Lars Kurth To: Anil Madhavapeddy X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-users] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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="===============3819285648640796168==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3819285648640796168== Content-Type: multipart/alternative; boundary=089e0111c13036120404da8f6705 --089e0111c13036120404da8f6705 Content-Type: text/plain; charset=ISO-8859-1 > I have a strong preference for a XenSummit near some other big event > such as LinuxCon or FOSDEM. All the locations suggested are co-located with big Linux Foundation events (but I don't want to pre-announce their schedule) On Wed, Apr 17, 2013 at 3:30 PM, Anil Madhavapeddy wrote: > On 17 Apr 2013, at 14:00, Ian Campbell wrote: > > > > WRT "too much going on" when co-locating -- can we aim to abut with > > other conferences rather than overlapping? At least this way travel can > > be amortized. > > > > Or do people have an issue with the setup where Mon-Wed: Big Conference > > (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Where > > XenSummit is on the Thur+Fri because there are too many other smaller > > conferences doing the same thing? > > I have a strong preference for a XenSummit near some other big event > such as LinuxCon or FOSDEM. It's not worth making the trip to a far-off > location just for a one or two-day dev summit, much as I'd enjoy it! > > The overloading of microconferences happens all the time. Most > people only really have a conflict between one or two things, and I > just hop between events for the interesting bits for me. > > -anil > --089e0111c13036120404da8f6705 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>=A0I have a strong preference for a XenSummit near some other big eve= nt
> such as LinuxCon o= r FOSDEM.
All the locations suggested are co-located with big Linux Foundation events= (but I don't want to pre-announce their schedule)


On Wed, Apr 17, 2013 a= t 3:30 PM, Anil Madhavapeddy <anil@recoil.org> wrote:
On 17 Apr 2013, at 14:00, = Ian Campbell <Ian.Campbell@ci= trix.com> wrote:
>
> WRT "too much going on" when co-locating -- can we aim to ab= ut with
> other conferences rather than overlapping? At least this way travel ca= n
> be amortized.
>
> Or do people have an issue with the setup where Mon-Wed: Big Conferenc= e
> (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Where > XenSummit is on the Thur+Fri because there are too many other smaller<= br> > conferences doing the same thing?

I have a strong preference for a XenSummit near some other big event<= br> such as LinuxCon or FOSDEM. =A0It's not worth making the trip to a far-= off
location just for a one or two-day dev summit, much as I'd enjoy it!
The overloading of microconferences happens all the time. =A0Most
people only really have a conflict between one or two things, and I
just hop between events for the interesting bits for me.

-anil

--089e0111c13036120404da8f6705-- --===============3819285648640796168== 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 --===============3819285648640796168==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCf-0006NN-60; Fri, 03 May 2013 12:35:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USTTt-0007Hq-93; Wed, 17 Apr 2013 14:37:05 +0000 Received: from [85.158.139.83:31304] by server-10.bemta-5.messagelabs.com id F7/4A-23714-F83BE615; Wed, 17 Apr 2013 14:37:03 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1366209413!25508712!1 X-Originating-IP: [209.85.219.44] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23143 invoked from network); 17 Apr 2013 14:36:58 -0000 Received: from mail-oa0-f44.google.com (HELO mail-oa0-f44.google.com) (209.85.219.44) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Apr 2013 14:36:58 -0000 Received: by mail-oa0-f44.google.com with SMTP id h1so1672687oag.3 for ; Wed, 17 Apr 2013 07:35:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=T90YnOtA2RO5+o2rhFir7FTl+ZSw7zOOcqZXuuWAu0k=; b=adkm0CLSk8V34/SXqZFxXsVp4xUtWrwh9aO3wprvkrb8pMa8i0bQL7aWTjWVFcz/rq Y9AP5lpjP5DFXo2H0TE/yqXRH6W+v6yDDhROjIJS/SogSVnqFQ/VBq3I+7pt+xj0akwi vXTQC06mWbDyrB1YhfKuTMKDEBUhayRfLQvrdf+z5vldcV+wMgpIf7EMgFBm6bYmqeUI KCVxJGP/fN5bfHHchNJr5QyP5toUpnP1ibONFVdV8XkPNRW3O6uC92a+H7vlYGdmCo4s ZjBusxJ/SRyhT8Cm/BeeqS57K+C1mhvkiASdWlWB5013RGon9SEgpYNaWxo2Liw2Iyv2 wFbQ== MIME-Version: 1.0 X-Received: by 10.60.37.68 with SMTP id w4mr2717312oej.62.1366209353615; Wed, 17 Apr 2013 07:35:53 -0700 (PDT) Received: by 10.60.13.1 with HTTP; Wed, 17 Apr 2013 07:35:53 -0700 (PDT) In-Reply-To: <619F5B48-3FC8-4C06-A570-171965AFE047@recoil.org> References: <1366203621.25579.25.camel@zakaz.uk.xensource.com> <619F5B48-3FC8-4C06-A570-171965AFE047@recoil.org> Date: Wed, 17 Apr 2013 15:35:53 +0100 Message-ID: From: Lars Kurth To: Anil Madhavapeddy X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-users] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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="===============3819285648640796168==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3819285648640796168== Content-Type: multipart/alternative; boundary=089e0111c13036120404da8f6705 --089e0111c13036120404da8f6705 Content-Type: text/plain; charset=ISO-8859-1 > I have a strong preference for a XenSummit near some other big event > such as LinuxCon or FOSDEM. All the locations suggested are co-located with big Linux Foundation events (but I don't want to pre-announce their schedule) On Wed, Apr 17, 2013 at 3:30 PM, Anil Madhavapeddy wrote: > On 17 Apr 2013, at 14:00, Ian Campbell wrote: > > > > WRT "too much going on" when co-locating -- can we aim to abut with > > other conferences rather than overlapping? At least this way travel can > > be amortized. > > > > Or do people have an issue with the setup where Mon-Wed: Big Conference > > (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Where > > XenSummit is on the Thur+Fri because there are too many other smaller > > conferences doing the same thing? > > I have a strong preference for a XenSummit near some other big event > such as LinuxCon or FOSDEM. It's not worth making the trip to a far-off > location just for a one or two-day dev summit, much as I'd enjoy it! > > The overloading of microconferences happens all the time. Most > people only really have a conflict between one or two things, and I > just hop between events for the interesting bits for me. > > -anil > --089e0111c13036120404da8f6705 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>=A0I have a strong preference for a XenSummit near some other big eve= nt
> such as LinuxCon o= r FOSDEM.
All the locations suggested are co-located with big Linux Foundation events= (but I don't want to pre-announce their schedule)


On Wed, Apr 17, 2013 a= t 3:30 PM, Anil Madhavapeddy <anil@recoil.org> wrote:
On 17 Apr 2013, at 14:00, = Ian Campbell <Ian.Campbell@ci= trix.com> wrote:
>
> WRT "too much going on" when co-locating -- can we aim to ab= ut with
> other conferences rather than overlapping? At least this way travel ca= n
> be amortized.
>
> Or do people have an issue with the setup where Mon-Wed: Big Conferenc= e
> (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Where > XenSummit is on the Thur+Fri because there are too many other smaller<= br> > conferences doing the same thing?

I have a strong preference for a XenSummit near some other big event<= br> such as LinuxCon or FOSDEM. =A0It's not worth making the trip to a far-= off
location just for a one or two-day dev summit, much as I'd enjoy it!
The overloading of microconferences happens all the time. =A0Most
people only really have a conflict between one or two things, and I
just hop between events for the interesting bits for me.

-anil

--089e0111c13036120404da8f6705-- --===============3819285648640796168== 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 --===============3819285648640796168==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCf-0006No-Dm; Fri, 03 May 2013 12:35:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USTW2-0007sx-G9; Wed, 17 Apr 2013 14:39:18 +0000 Received: from [85.158.139.211:21784] by server-14.bemta-5.messagelabs.com id AF/37-13158-514BE615; Wed, 17 Apr 2013 14:39:17 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1366209551!17813154!1 X-Originating-IP: [209.85.219.48] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17006 invoked from network); 17 Apr 2013 14:39:13 -0000 Received: from mail-oa0-f48.google.com (HELO mail-oa0-f48.google.com) (209.85.219.48) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Apr 2013 14:39:13 -0000 Received: by mail-oa0-f48.google.com with SMTP id j1so1627450oag.7 for ; Wed, 17 Apr 2013 07:39:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=MeEX1/da93O4Zj8m9+s1pzMYN69vgkUJBLL1XEH+0EQ=; b=WVoJOqbCYOBu356a81Exl70dZ3hL0MzS+nk90FYuhQOMMuC8yF47bCL1U35mnkjPmm xjyVwoSRsJNewhPezW6KgsfxXaq1LxISGtrU9jpv5AEV+h4FJB47QuDel6yaSz8c3+WB lp8BiUgJHQhIHOq8v8CkC7dCNpebrnts67i8JMfU2gtQrIVp0l7AIzIjIJSq3D6E+b85 ysJT+tL9clDmwr5UijqTQNuDmIqKSBQCfoPP0HmuVcQPefUnwDpthNi8gbL2MqCBpAhq IefSI1VmuUDrPEtXQ5V+9HYGhV2fUtmoUnEPiH7zSF92cG+Nxd/kMlIgg6UDONjDsYng ZgQQ== MIME-Version: 1.0 X-Received: by 10.182.84.135 with SMTP id z7mr2357787oby.35.1366209551416; Wed, 17 Apr 2013 07:39:11 -0700 (PDT) Received: by 10.60.13.1 with HTTP; Wed, 17 Apr 2013 07:39:11 -0700 (PDT) In-Reply-To: <1366209241212666500@businessgrade.com> References: <1366203621.25579.25.camel@zakaz.uk.xensource.com> <619F5B48-3FC8-4C06-A570-171965AFE047@recoil.org> <1366209241212666500@businessgrade.com> Date: Wed, 17 Apr 2013 15:39:11 +0100 Message-ID: From: Lars Kurth To: eneal@businessgrade.com X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-users] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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="===============1129425389330611038==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============1129425389330611038== Content-Type: multipart/alternative; boundary=089e013a26960046da04da8f733c --089e013a26960046da04da8f733c Content-Type: text/plain; charset=ISO-8859-1 Can I ask you all to list your preferences, rather than voting for my preference or stating "+1". This will make it easier for me to count everything. Lars On Wed, Apr 17, 2013 at 3:34 PM, Errol Neal wrote: > +1 > > On Wed, 04/17/2013 10:30 AM, Anil Madhavapeddy wrote: > > On 17 Apr 2013, at 14:00, Ian Campbell wrote: > > > > > > WRT "too much going on" when co-locating -- can we aim to abut with > > > other conferences rather than overlapping? At least this way travel can > > > be amortized. > > > > > > Or do people have an issue with the setup where Mon-Wed: Big Conference > > > (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Where > > > XenSummit is on the Thur+Fri because there are too many other smaller > > > conferences doing the same thing? > > > > I have a strong preference for a XenSummit near some other big event > > such as LinuxCon or FOSDEM. It's not worth making the trip to a far-off > > location just for a one or two-day dev summit, much as I'd enjoy it! > > > > The overloading of microconferences happens all the time. Most > > people only really have a conflict between one or two things, and I > > just hop between events for the interesting bits for me. > > > > -anil > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --089e013a26960046da04da8f733c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Can I ask you all to list your preferences, rather than vo= ting for my preference or stating "+1". This will make it easier = for me to count everything.

Lars


On Wed, Apr 17, 2013 at 3:34 PM, Errol N= eal <eneal@businessgrade.com> wrote:
+1

On Wed, 04/17/2013 10:30 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> On 17 Apr 2013, at 14:00, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >
> > WRT "too much going on" when co-locating -- can we aim = to abut with
> > other conferences rather than overlapping? At least this way trav= el can
> > be amortized.
> >
> > Or do people have an issue with the setup where Mon-Wed: Big Conf= erence
> > (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Wh= ere
> > XenSummit is on the Thur+Fri because there are too many other sma= ller
> > conferences doing the same thing?
>
> I have a strong preference for a XenSummit near some other big event > such as LinuxCon or FOSDEM. =A0It's not worth making the trip to a= far-off
> location just for a one or two-day dev summit, much as I'd enjoy i= t!
>
> The overloading of microconferences happens all the time. =A0Most
> people only really have a conflict between one or two things, and I > just hop between events for the interesting bits for me.
>
> -anil
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--089e013a26960046da04da8f733c-- --===============1129425389330611038== 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 --===============1129425389330611038==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCf-0006No-Dm; Fri, 03 May 2013 12:35:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USTW2-0007sx-G9; Wed, 17 Apr 2013 14:39:18 +0000 Received: from [85.158.139.211:21784] by server-14.bemta-5.messagelabs.com id AF/37-13158-514BE615; Wed, 17 Apr 2013 14:39:17 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1366209551!17813154!1 X-Originating-IP: [209.85.219.48] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17006 invoked from network); 17 Apr 2013 14:39:13 -0000 Received: from mail-oa0-f48.google.com (HELO mail-oa0-f48.google.com) (209.85.219.48) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Apr 2013 14:39:13 -0000 Received: by mail-oa0-f48.google.com with SMTP id j1so1627450oag.7 for ; Wed, 17 Apr 2013 07:39:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=MeEX1/da93O4Zj8m9+s1pzMYN69vgkUJBLL1XEH+0EQ=; b=WVoJOqbCYOBu356a81Exl70dZ3hL0MzS+nk90FYuhQOMMuC8yF47bCL1U35mnkjPmm xjyVwoSRsJNewhPezW6KgsfxXaq1LxISGtrU9jpv5AEV+h4FJB47QuDel6yaSz8c3+WB lp8BiUgJHQhIHOq8v8CkC7dCNpebrnts67i8JMfU2gtQrIVp0l7AIzIjIJSq3D6E+b85 ysJT+tL9clDmwr5UijqTQNuDmIqKSBQCfoPP0HmuVcQPefUnwDpthNi8gbL2MqCBpAhq IefSI1VmuUDrPEtXQ5V+9HYGhV2fUtmoUnEPiH7zSF92cG+Nxd/kMlIgg6UDONjDsYng ZgQQ== MIME-Version: 1.0 X-Received: by 10.182.84.135 with SMTP id z7mr2357787oby.35.1366209551416; Wed, 17 Apr 2013 07:39:11 -0700 (PDT) Received: by 10.60.13.1 with HTTP; Wed, 17 Apr 2013 07:39:11 -0700 (PDT) In-Reply-To: <1366209241212666500@businessgrade.com> References: <1366203621.25579.25.camel@zakaz.uk.xensource.com> <619F5B48-3FC8-4C06-A570-171965AFE047@recoil.org> <1366209241212666500@businessgrade.com> Date: Wed, 17 Apr 2013 15:39:11 +0100 Message-ID: From: Lars Kurth To: eneal@businessgrade.com X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-users] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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="===============1129425389330611038==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============1129425389330611038== Content-Type: multipart/alternative; boundary=089e013a26960046da04da8f733c --089e013a26960046da04da8f733c Content-Type: text/plain; charset=ISO-8859-1 Can I ask you all to list your preferences, rather than voting for my preference or stating "+1". This will make it easier for me to count everything. Lars On Wed, Apr 17, 2013 at 3:34 PM, Errol Neal wrote: > +1 > > On Wed, 04/17/2013 10:30 AM, Anil Madhavapeddy wrote: > > On 17 Apr 2013, at 14:00, Ian Campbell wrote: > > > > > > WRT "too much going on" when co-locating -- can we aim to abut with > > > other conferences rather than overlapping? At least this way travel can > > > be amortized. > > > > > > Or do people have an issue with the setup where Mon-Wed: Big Conference > > > (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Where > > > XenSummit is on the Thur+Fri because there are too many other smaller > > > conferences doing the same thing? > > > > I have a strong preference for a XenSummit near some other big event > > such as LinuxCon or FOSDEM. It's not worth making the trip to a far-off > > location just for a one or two-day dev summit, much as I'd enjoy it! > > > > The overloading of microconferences happens all the time. Most > > people only really have a conflict between one or two things, and I > > just hop between events for the interesting bits for me. > > > > -anil > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --089e013a26960046da04da8f733c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Can I ask you all to list your preferences, rather than vo= ting for my preference or stating "+1". This will make it easier = for me to count everything.

Lars


On Wed, Apr 17, 2013 at 3:34 PM, Errol N= eal <eneal@businessgrade.com> wrote:
+1

On Wed, 04/17/2013 10:30 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> On 17 Apr 2013, at 14:00, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >
> > WRT "too much going on" when co-locating -- can we aim = to abut with
> > other conferences rather than overlapping? At least this way trav= el can
> > be amortized.
> >
> > Or do people have an issue with the setup where Mon-Wed: Big Conf= erence
> > (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Wh= ere
> > XenSummit is on the Thur+Fri because there are too many other sma= ller
> > conferences doing the same thing?
>
> I have a strong preference for a XenSummit near some other big event > such as LinuxCon or FOSDEM. =A0It's not worth making the trip to a= far-off
> location just for a one or two-day dev summit, much as I'd enjoy i= t!
>
> The overloading of microconferences happens all the time. =A0Most
> people only really have a conflict between one or two things, and I > just hop between events for the interesting bits for me.
>
> -anil
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--089e013a26960046da04da8f733c-- --===============1129425389330611038== 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 --===============1129425389330611038==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCf-0006Oc-Tj; Fri, 03 May 2013 12:35:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UT2NI-0001ph-R0 for xen-arm@lists.xen.org; Fri, 19 Apr 2013 03:52:37 +0000 Received: from [85.158.139.211:11685] by server-1.bemta-5.messagelabs.com id 60/7C-14063-38FB0715; Fri, 19 Apr 2013 03:52:35 +0000 X-Env-Sender: chip.childers@sungard.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1366343546!18982066!1 X-Originating-IP: [74.125.149.143] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4962 invoked from network); 19 Apr 2013 03:52:34 -0000 Received: from na3sys009aog130.obsmtp.com (HELO na3sys009aog130.obsmtp.com) (74.125.149.143) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Apr 2013 03:52:34 -0000 Received: from mail-gh0-f199.google.com ([209.85.160.199]) (using TLSv1) by na3sys009aob130.postini.com ([74.125.148.12]) with SMTP ID DSNKUXC/eMoa+TLwA2ZTDjSv4rSPZU+nryTr@postini.com; Thu, 18 Apr 2013 20:52:34 PDT Received: by mail-gh0-f199.google.com with SMTP id r16so479425ghr.10 for ; Thu, 18 Apr 2013 20:52:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:x-gm-message-state; bh=6HSOw4cCSmmgKej2lYHIM0Hu7P9qrth3fp0426zIvUc=; b=lEqgw4ANPxnGOTXPxwQ8ZfKsNAqN2Z8Uc/WHp01DVcvWKmIl+Bf5GYbuflahIzbuth MP2kdd/fZOYPvIvemPLYJSPtJMt89CU+194pFk4UrXgq5m+x6WTSyrT1jSaHu7L5BIoI IzvJlpC/aJYoFt19i0X5qX8FX7f63WprM3xwezKFU/37sw+FGTYB+qYHa3EWtzzKpoUs xqPeOCQOkd0xCRunq4Xm7jQBwu/VsqisoIESagjwpItJGPQhP2iiI729ACW+oRdZrgO/ zDy4m0QLwiNbVUSywLiIqAN/OSe9Nxr1bApS7u5gbI/0FG8k2SOmvjTIlfAyAtZKsrzF E0fQ== X-Received: by 10.229.73.72 with SMTP id p8mr1138187qcj.69.1366343543774; Thu, 18 Apr 2013 20:52:23 -0700 (PDT) X-Received: by 10.229.73.72 with SMTP id p8mr1138170qcj.69.1366343542629; Thu, 18 Apr 2013 20:52:22 -0700 (PDT) Received: from localhost (pool-71-255-100-148.phlapa.east.verizon.net. [71.255.100.148]) by mx.google.com with ESMTPS id dl6sm16594859qab.12.2013.04.18.20.52.20 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 18 Apr 2013 20:52:21 -0700 (PDT) Date: Thu, 18 Apr 2013 23:52:18 -0400 From: Chip Childers To: Lars Kurth Message-ID: <20130419035218.GY88962@USLT-205755.sungardas.corp> References: <516AECC9.1010603@xen.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <516AECC9.1010603@xen.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Gm-Message-State: ALoCoQlMDXLSgVvpBCAJnlC2XLMtlVbE/20tYUI/t/LKl1VRTNJ8DRCkWbU7wM0n4hrch/2U4DF/xaUqPozf9MAp7Em5wNtzI5qkdPePEGwruRw5HjbcZ705QLxKVbpj6KfqnJNfVoQNkE0WxyoFZxbjd2QYMC1dgA== X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote: > 1) A list for coordinating blog posts, other communication, > attending of event, etc. - not sure about the name, so am looking > for suggestions. I am not sure whether we should have public > archives: comparable lists of other projects don't. >From an outsider / lurker perspective, xen-marketing@lists.xen.org is a good fit. > > 2) A semi-private invite mailing list for ALL project leads, > committers and maintainers of ALL projects hosted on xen.org Similarly to above: xen-private@lists.xen.org Both of these list names are used in other projects I'm working with / observe. _______________________________________________ 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 May 03 12:35:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCf-0006Oc-Tj; Fri, 03 May 2013 12:35:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UT2NI-0001ph-R0 for xen-arm@lists.xen.org; Fri, 19 Apr 2013 03:52:37 +0000 Received: from [85.158.139.211:11685] by server-1.bemta-5.messagelabs.com id 60/7C-14063-38FB0715; Fri, 19 Apr 2013 03:52:35 +0000 X-Env-Sender: chip.childers@sungard.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1366343546!18982066!1 X-Originating-IP: [74.125.149.143] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4962 invoked from network); 19 Apr 2013 03:52:34 -0000 Received: from na3sys009aog130.obsmtp.com (HELO na3sys009aog130.obsmtp.com) (74.125.149.143) by server-10.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Apr 2013 03:52:34 -0000 Received: from mail-gh0-f199.google.com ([209.85.160.199]) (using TLSv1) by na3sys009aob130.postini.com ([74.125.148.12]) with SMTP ID DSNKUXC/eMoa+TLwA2ZTDjSv4rSPZU+nryTr@postini.com; Thu, 18 Apr 2013 20:52:34 PDT Received: by mail-gh0-f199.google.com with SMTP id r16so479425ghr.10 for ; Thu, 18 Apr 2013 20:52:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:x-gm-message-state; bh=6HSOw4cCSmmgKej2lYHIM0Hu7P9qrth3fp0426zIvUc=; b=lEqgw4ANPxnGOTXPxwQ8ZfKsNAqN2Z8Uc/WHp01DVcvWKmIl+Bf5GYbuflahIzbuth MP2kdd/fZOYPvIvemPLYJSPtJMt89CU+194pFk4UrXgq5m+x6WTSyrT1jSaHu7L5BIoI IzvJlpC/aJYoFt19i0X5qX8FX7f63WprM3xwezKFU/37sw+FGTYB+qYHa3EWtzzKpoUs xqPeOCQOkd0xCRunq4Xm7jQBwu/VsqisoIESagjwpItJGPQhP2iiI729ACW+oRdZrgO/ zDy4m0QLwiNbVUSywLiIqAN/OSe9Nxr1bApS7u5gbI/0FG8k2SOmvjTIlfAyAtZKsrzF E0fQ== X-Received: by 10.229.73.72 with SMTP id p8mr1138187qcj.69.1366343543774; Thu, 18 Apr 2013 20:52:23 -0700 (PDT) X-Received: by 10.229.73.72 with SMTP id p8mr1138170qcj.69.1366343542629; Thu, 18 Apr 2013 20:52:22 -0700 (PDT) Received: from localhost (pool-71-255-100-148.phlapa.east.verizon.net. [71.255.100.148]) by mx.google.com with ESMTPS id dl6sm16594859qab.12.2013.04.18.20.52.20 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 18 Apr 2013 20:52:21 -0700 (PDT) Date: Thu, 18 Apr 2013 23:52:18 -0400 From: Chip Childers To: Lars Kurth Message-ID: <20130419035218.GY88962@USLT-205755.sungardas.corp> References: <516AECC9.1010603@xen.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <516AECC9.1010603@xen.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Gm-Message-State: ALoCoQlMDXLSgVvpBCAJnlC2XLMtlVbE/20tYUI/t/LKl1VRTNJ8DRCkWbU7wM0n4hrch/2U4DF/xaUqPozf9MAp7Em5wNtzI5qkdPePEGwruRw5HjbcZ705QLxKVbpj6KfqnJNfVoQNkE0WxyoFZxbjd2QYMC1dgA== X-Mailman-Approved-At: Fri, 03 May 2013 12:34:58 +0000 Cc: xen-arm@lists.xen.org, "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote: > 1) A list for coordinating blog posts, other communication, > attending of event, etc. - not sure about the name, so am looking > for suggestions. I am not sure whether we should have public > archives: comparable lists of other projects don't. >From an outsider / lurker perspective, xen-marketing@lists.xen.org is a good fit. > > 2) A semi-private invite mailing list for ALL project leads, > committers and maintainers of ALL projects hosted on xen.org Similarly to above: xen-private@lists.xen.org Both of these list names are used in other projects I'm working with / observe. _______________________________________________ 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 May 03 12:35:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCg-0006Pe-9e; Fri, 03 May 2013 12:35:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfwww-0002LH-Qz for xen-arm@lists.xen.org; Tue, 04 Dec 2012 18:10:31 +0000 Received: from [85.158.137.99:28236] by server-6.bemta-3.messagelabs.com id 4A/72-28265-69C3EB05; Tue, 04 Dec 2012 18:10:30 +0000 X-Env-Sender: nico@fluxnic.net X-Msg-Ref: server-14.tower-217.messagelabs.com!1354644628!17878940!1 X-Originating-IP: [24.201.245.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n,sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28528 invoked from network); 4 Dec 2012 18:10:29 -0000 Received: from relais.videotron.ca (HELO relais.videotron.ca) (24.201.245.36) by server-14.tower-217.messagelabs.com with SMTP; 4 Dec 2012 18:10:29 -0000 MIME-version: 1.0 Received: from xanadu.home ([24.202.213.203]) by VL-VM-MR002.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MEI00MHOQHFHLB0@VL-VM-MR002.ip.videotron.ca> for xen-arm@lists.xen.org; Tue, 04 Dec 2012 13:10:28 -0500 (EST) Date: Tue, 04 Dec 2012 13:10:27 -0500 (EST) From: Nicolas Pitre To: Will Deacon In-reply-to: <20121204171628.GF5314@mudshark.cambridge.arm.com> Message-id: References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> <20121204171628.GF5314@mudshark.cambridge.arm.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, 4 Dec 2012, Will Deacon wrote: > On Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: > > If there is no way to reset the core, then couldn't the hotplug code > > tear down the cpu setup and just jump back to 0x0 which then returns to > > the bootloader's pen? > > I think hotplug really should be implemented with a virtio device. We just > trap back to the emulation and kill the vcpu thread. Hotplug and secondary boot should really be considered the same and use the same methods. So if you envision a virtio device for hotplug, then just use that for secondary boot as well. PSCI might be simpler to implement though. Nicolas _______________________________________________ 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 May 03 12:35:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCg-0006Pe-9e; Fri, 03 May 2013 12:35:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tfwww-0002LH-Qz for xen-arm@lists.xen.org; Tue, 04 Dec 2012 18:10:31 +0000 Received: from [85.158.137.99:28236] by server-6.bemta-3.messagelabs.com id 4A/72-28265-69C3EB05; Tue, 04 Dec 2012 18:10:30 +0000 X-Env-Sender: nico@fluxnic.net X-Msg-Ref: server-14.tower-217.messagelabs.com!1354644628!17878940!1 X-Originating-IP: [24.201.245.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n,sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc4NjkyMQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28528 invoked from network); 4 Dec 2012 18:10:29 -0000 Received: from relais.videotron.ca (HELO relais.videotron.ca) (24.201.245.36) by server-14.tower-217.messagelabs.com with SMTP; 4 Dec 2012 18:10:29 -0000 MIME-version: 1.0 Received: from xanadu.home ([24.202.213.203]) by VL-VM-MR002.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MEI00MHOQHFHLB0@VL-VM-MR002.ip.videotron.ca> for xen-arm@lists.xen.org; Tue, 04 Dec 2012 13:10:28 -0500 (EST) Date: Tue, 04 Dec 2012 13:10:27 -0500 (EST) From: Nicolas Pitre To: Will Deacon In-reply-to: <20121204171628.GF5314@mudshark.cambridge.arm.com> Message-id: References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <1354557160-20144-3-git-send-email-will.deacon@arm.com> <50BD1FD7.9040000@gmail.com> <20121204124047.GM23368@mudshark.cambridge.arm.com> <20121204133326.GE14363@n2100.arm.linux.org.uk> <20121204134010.GP23368@mudshark.cambridge.arm.com> <20121204143724.GF14363@n2100.arm.linux.org.uk> <20121204161113.GT23368@mudshark.cambridge.arm.com> <50BE28C6.2010403@gmail.com> <20121204171628.GF5314@mudshark.cambridge.arm.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , "arnd@arndb.de" , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tue, 4 Dec 2012, Will Deacon wrote: > On Tue, Dec 04, 2012 at 04:45:58PM +0000, Rob Herring wrote: > > If there is no way to reset the core, then couldn't the hotplug code > > tear down the cpu setup and just jump back to 0x0 which then returns to > > the bootloader's pen? > > I think hotplug really should be implemented with a virtio device. We just > trap back to the emulation and kill the vcpu thread. Hotplug and secondary boot should really be considered the same and use the same methods. So if you envision a virtio device for hotplug, then just use that for secondary boot as well. PSCI might be simpler to implement though. Nicolas _______________________________________________ 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 May 03 12:35:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCh-0006QN-2r; Fri, 03 May 2013 12:35:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfyJj-00028c-G6 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 19:38:07 +0000 Received: from [193.109.254.147:57745] by server-10.bemta-14.messagelabs.com id D6/89-31741-E115EB05; Tue, 04 Dec 2012 19:38:06 +0000 X-Env-Sender: arnd@arndb.de X-Msg-Ref: server-4.tower-27.messagelabs.com!1354649885!9345242!1 X-Originating-IP: [212.227.126.187] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODcgPT4gODIyMDA=\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODcgPT4gODIyMDA=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7521 invoked from network); 4 Dec 2012 19:38:06 -0000 Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.126.187) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2012 19:38:06 -0000 Received: from klappe2.localnet (HSI-KBW-46-223-46-140.hsi.kabel-badenwuerttemberg.de [46.223.46.140]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0LzpYp-1TAzEf20rj-014L6N; Tue, 04 Dec 2012 20:37:54 +0100 From: Arnd Bergmann To: Will Deacon Date: Tue, 4 Dec 2012 19:37:52 +0000 User-Agent: KMail/1.12.2 (Linux/3.5.0; KDE/4.3.2; x86_64; ; ) References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <20121204163555.GH14363@n2100.arm.linux.org.uk> <20121204172424.GG5314@mudshark.cambridge.arm.com> In-Reply-To: <20121204172424.GG5314@mudshark.cambridge.arm.com> MIME-Version: 1.0 Message-Id: <201212041937.53046.arnd@arndb.de> X-Provags-ID: V02:K0:5HgBDx6LCqZG/1PryLhlAdS9nziZbTBfNj5+kglwU0d 1Z/ujwhwjyLK/6nYDUlaRzo2VF68+/Sjap9rRvPsO4HAJKvA7S fhVeILxN0Vb770KMmknv2SmZ7GrCyFcL4TerfjN2B8dZggqC54 7BB4eKALCp5ibm+eMP24eKOXPJxGHwOtDJuabR8JCHOvoMuLum lQPYxfI8yCKLjfl3T+EAN9RafNh9ZbAYAcrp/HmH/W2biQHMy/ DUuB16gwM+/yG+aokoCryEaYMMnKpJgHFX7Fk9tFgX9FoW+aNY pG1P2oz3JB/cIHHLvnvxf6sX7Z3WaLKN0Of6PZ/KmE3v9spURd jCbEGU0g6V5dHTFv5myM= X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tuesday 04 December 2012, Will Deacon wrote: > > > > Most other real-world platforms out there have a way to power off the > > unused secondary CPUs - Tegra and OMAP both do. > > If a virtual machine powers off a virtual CPU, I doubt we want to power of > its corresponding CPU -- that logic can remain in the host. All we need to > do is kill the virtual CPU thread, which we can do easily enough. Booting is > the more difficult problem because we introduce a reliance on a virtual > device being ready incredibly early, essentially hardcoding part of the > virtual machine. Powering off a virtual CPU is the same as killing the virtual CPU thread. Not powering it off would imply that we schedule a host CPU to run an endless loop on it. Arnd _______________________________________________ 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 May 03 12:35:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCh-0006QN-2r; Fri, 03 May 2013 12:35:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TfyJj-00028c-G6 for xen-arm@lists.xen.org; Tue, 04 Dec 2012 19:38:07 +0000 Received: from [193.109.254.147:57745] by server-10.bemta-14.messagelabs.com id D6/89-31741-E115EB05; Tue, 04 Dec 2012 19:38:06 +0000 X-Env-Sender: arnd@arndb.de X-Msg-Ref: server-4.tower-27.messagelabs.com!1354649885!9345242!1 X-Originating-IP: [212.227.126.187] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODcgPT4gODIyMDA=\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjEyNi4xODcgPT4gODIyMDA=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7521 invoked from network); 4 Dec 2012 19:38:06 -0000 Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.126.187) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2012 19:38:06 -0000 Received: from klappe2.localnet (HSI-KBW-46-223-46-140.hsi.kabel-badenwuerttemberg.de [46.223.46.140]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0LzpYp-1TAzEf20rj-014L6N; Tue, 04 Dec 2012 20:37:54 +0100 From: Arnd Bergmann To: Will Deacon Date: Tue, 4 Dec 2012 19:37:52 +0000 User-Agent: KMail/1.12.2 (Linux/3.5.0; KDE/4.3.2; x86_64; ; ) References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <20121204163555.GH14363@n2100.arm.linux.org.uk> <20121204172424.GG5314@mudshark.cambridge.arm.com> In-Reply-To: <20121204172424.GG5314@mudshark.cambridge.arm.com> MIME-Version: 1.0 Message-Id: <201212041937.53046.arnd@arndb.de> X-Provags-ID: V02:K0:5HgBDx6LCqZG/1PryLhlAdS9nziZbTBfNj5+kglwU0d 1Z/ujwhwjyLK/6nYDUlaRzo2VF68+/Sjap9rRvPsO4HAJKvA7S fhVeILxN0Vb770KMmknv2SmZ7GrCyFcL4TerfjN2B8dZggqC54 7BB4eKALCp5ibm+eMP24eKOXPJxGHwOtDJuabR8JCHOvoMuLum lQPYxfI8yCKLjfl3T+EAN9RafNh9ZbAYAcrp/HmH/W2biQHMy/ DUuB16gwM+/yG+aokoCryEaYMMnKpJgHFX7Fk9tFgX9FoW+aNY pG1P2oz3JB/cIHHLvnvxf6sX7Z3WaLKN0Of6PZ/KmE3v9spURd jCbEGU0g6V5dHTFv5myM= X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , Russell King - ARM Linux , Marc Zyngier , Rob Herring , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 2/2] ARM: SMP support for mach-virt 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 Tuesday 04 December 2012, Will Deacon wrote: > > > > Most other real-world platforms out there have a way to power off the > > unused secondary CPUs - Tegra and OMAP both do. > > If a virtual machine powers off a virtual CPU, I doubt we want to power of > its corresponding CPU -- that logic can remain in the host. All we need to > do is kill the virtual CPU thread, which we can do easily enough. Booting is > the more difficult problem because we introduce a reliance on a virtual > device being ready incredibly early, essentially hardcoding part of the > virtual machine. Powering off a virtual CPU is the same as killing the virtual CPU thread. Not powering it off would imply that we schedule a host CPU to run an endless loop on it. Arnd _______________________________________________ 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 May 03 12:35:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCh-0006RM-Bf; Fri, 03 May 2013 12:35:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGZ2-0005Dp-A3 for xen-arm@lists.xen.org; Wed, 05 Dec 2012 15:07:08 +0000 Received: from [85.158.143.35:41283] by server-2.bemta-4.messagelabs.com id D5/58-30861-B136FB05; Wed, 05 Dec 2012 15:07:07 +0000 X-Env-Sender: nico@fluxnic.net X-Msg-Ref: server-13.tower-21.messagelabs.com!1354720026!14516700!1 X-Originating-IP: [24.201.245.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc5MDQ2MA==\n,sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc5MDQ2MA==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22216 invoked from network); 5 Dec 2012 15:07:06 -0000 Received: from relais.videotron.ca (HELO relais.videotron.ca) (24.201.245.36) by server-13.tower-21.messagelabs.com with SMTP; 5 Dec 2012 15:07:06 -0000 MIME-version: 1.0 Received: from xanadu.home ([24.202.213.203]) by VL-VM-MR005.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MEK007O6CNTV040@VL-VM-MR005.ip.videotron.ca> for xen-arm@lists.xen.org; Wed, 05 Dec 2012 10:07:06 -0500 (EST) Date: Wed, 05 Dec 2012 10:07:05 -0500 (EST) From: Nicolas Pitre To: Catalin Marinas In-reply-to: Message-id: References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Will Deacon , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Wed, 5 Dec 2012, Catalin Marinas wrote: > On 4 December 2012 18:14, Will Deacon wrote: > > On Tue, Dec 04, 2012 at 06:02:13PM +0000, Nicolas Pitre wrote: > >> On Tue, 4 Dec 2012, Will Deacon wrote: > >> > On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: > >> > > on the topic of a para-virtualised machine, I think that it should > >> > > simply implement the PSCI calls to bring up CPUs _without_ any holding > >> > > pen nor spinning tables. You issue the appropriate PSCI call with the > >> > > physical address for secondary_startup() as argument and you're done. > >> > > The host intercepts that call and free a new CPU instance in response. > >> > > That's all. > >> > > >> > I'd be happy to go with this suggestion if it wasn't for one thing: > >> > platforms that do not implement a secure mode. For these platforms, smc will > >> > be an undefined instruction at the exception level where it is executed and > >> > therefore cannot be trapped by the hypervisor. > >> > >> Really? I thought the hypervisor could virtualize SMC calls. Or is > >> that considered a security hazard? > > > > If the security extensions aren't implemented, the hypervisor can't trap the > > smc instruction. > > > >> I don't remember all the PSCI spec details, but I think there was some > >> provision for this case i.e. the SMC call could be a HYP call instead. > >> And if that's not in the spec, then it probably should be added and > >> implemented as if it was. > > > > Well, this depends on the guest taking an undefined instruction exception on > > the smc, then deciding to issue an hvc instead and *then* having the > > hypervisor somehow translate that into a PSCI invocation. It could work, but > > it sounds easy to mess up and relies on the PSCI firmware co-existing with > > things like kvm. > > We can have enable-method DT entries independent of the SoC and one of > them can be psci-hvc. > > Just for clarification, AArch32 with virtualisation mandates the > security extensions, so the SMC can be trapped. Good. Therefore this one is settled. > On AArch64 it is a bit > tricky since the presence of EL3 is not mandate, in which case SMC > would undef (don't as why ;). That's where we can have different > enable methods specified via the DT. In that case, sure. But do you expect such a configuration to be common? Especially with all this secure booting being and cie enforced across the board? I bet it won't. So it is probably best to presume PSCI by default, and have a DT specified method only when it is necessary to override the default. Nicolas _______________________________________________ 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 May 03 12:35:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCh-0006RM-Bf; Fri, 03 May 2013 12:35:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TgGZ2-0005Dp-A3 for xen-arm@lists.xen.org; Wed, 05 Dec 2012 15:07:08 +0000 Received: from [85.158.143.35:41283] by server-2.bemta-4.messagelabs.com id D5/58-30861-B136FB05; Wed, 05 Dec 2012 15:07:07 +0000 X-Env-Sender: nico@fluxnic.net X-Msg-Ref: server-13.tower-21.messagelabs.com!1354720026!14516700!1 X-Originating-IP: [24.201.245.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc5MDQ2MA==\n,sa_preprocessor: QmFkIElQOiAyNC4yMDEuMjQ1LjM2ID0+IDc5MDQ2MA==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22216 invoked from network); 5 Dec 2012 15:07:06 -0000 Received: from relais.videotron.ca (HELO relais.videotron.ca) (24.201.245.36) by server-13.tower-21.messagelabs.com with SMTP; 5 Dec 2012 15:07:06 -0000 MIME-version: 1.0 Received: from xanadu.home ([24.202.213.203]) by VL-VM-MR005.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MEK007O6CNTV040@VL-VM-MR005.ip.videotron.ca> for xen-arm@lists.xen.org; Wed, 05 Dec 2012 10:07:06 -0500 (EST) Date: Wed, 05 Dec 2012 10:07:05 -0500 (EST) From: Nicolas Pitre To: Catalin Marinas In-reply-to: Message-id: References: <1354557160-20144-1-git-send-email-will.deacon@arm.com> <50BD1F81.9080304@gmail.com> <20121204123001.GL23368@mudshark.cambridge.arm.com> <50BE04C6.4070602@gmail.com> <20121204171129.GE5314@mudshark.cambridge.arm.com> <20121204181446.GJ5314@mudshark.cambridge.arm.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Mark Rutland , "arnd@arndb.de" , Marc Zyngier , Will Deacon , "xen-arm@lists.xen.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [XenARM] [RFC PATCH 0/2] Add support for a fake, para-virtualised machine 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 Wed, 5 Dec 2012, Catalin Marinas wrote: > On 4 December 2012 18:14, Will Deacon wrote: > > On Tue, Dec 04, 2012 at 06:02:13PM +0000, Nicolas Pitre wrote: > >> On Tue, 4 Dec 2012, Will Deacon wrote: > >> > On Tue, Dec 04, 2012 at 05:00:07PM +0000, Nicolas Pitre wrote: > >> > > on the topic of a para-virtualised machine, I think that it should > >> > > simply implement the PSCI calls to bring up CPUs _without_ any holding > >> > > pen nor spinning tables. You issue the appropriate PSCI call with the > >> > > physical address for secondary_startup() as argument and you're done. > >> > > The host intercepts that call and free a new CPU instance in response. > >> > > That's all. > >> > > >> > I'd be happy to go with this suggestion if it wasn't for one thing: > >> > platforms that do not implement a secure mode. For these platforms, smc will > >> > be an undefined instruction at the exception level where it is executed and > >> > therefore cannot be trapped by the hypervisor. > >> > >> Really? I thought the hypervisor could virtualize SMC calls. Or is > >> that considered a security hazard? > > > > If the security extensions aren't implemented, the hypervisor can't trap the > > smc instruction. > > > >> I don't remember all the PSCI spec details, but I think there was some > >> provision for this case i.e. the SMC call could be a HYP call instead. > >> And if that's not in the spec, then it probably should be added and > >> implemented as if it was. > > > > Well, this depends on the guest taking an undefined instruction exception on > > the smc, then deciding to issue an hvc instead and *then* having the > > hypervisor somehow translate that into a PSCI invocation. It could work, but > > it sounds easy to mess up and relies on the PSCI firmware co-existing with > > things like kvm. > > We can have enable-method DT entries independent of the SoC and one of > them can be psci-hvc. > > Just for clarification, AArch32 with virtualisation mandates the > security extensions, so the SMC can be trapped. Good. Therefore this one is settled. > On AArch64 it is a bit > tricky since the presence of EL3 is not mandate, in which case SMC > would undef (don't as why ;). That's where we can have different > enable methods specified via the DT. In that case, sure. But do you expect such a configuration to be common? Especially with all this secure booting being and cie enforced across the board? I bet it won't. So it is probably best to presume PSCI by default, and have a DT specified method only when it is necessary to override the default. Nicolas _______________________________________________ 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 May 03 12:35:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCh-0006Ro-M7; Fri, 03 May 2013 12:35:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TlRRA-0003ZH-RO; Wed, 19 Dec 2012 21:44:25 +0000 Received: from [85.158.137.99:34601] by server-10.bemta-3.messagelabs.com id E9/BA-07616-73532D05; Wed, 19 Dec 2012 21:44:23 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1355953461!15046686!1 X-Originating-IP: [156.151.31.81] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU2LjE1MS4zMS44MSA9PiAxMzIwMTU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32370 invoked from network); 19 Dec 2012 21:44:22 -0000 Received: from userp1040.oracle.com (HELO userp1040.oracle.com) (156.151.31.81) by server-6.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Dec 2012 21:44:22 -0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id qBJLiH21029662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Dec 2012 21:44:18 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id qBJLiGPL027252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Dec 2012 21:44:16 GMT Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id qBJLiFku020364; Wed, 19 Dec 2012 15:44:15 -0600 Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 19 Dec 2012 13:44:15 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 64EAD1C032B; Wed, 19 Dec 2012 16:44:14 -0500 (EST) Date: Wed, 19 Dec 2012 16:44:14 -0500 From: Konrad Rzeszutek Wilk To: Lars Kurth , konrad@kernel.org Message-ID: <20121219214414.GA25858@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50A4F83D.4000205@xen.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet21.oracle.com [156.151.31.93] X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: xen-arm@lists.xen.org, "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Getting into shape for GSOC 2013 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, Nov 15, 2012 at 02:12:13PM +0000, Lars Kurth wrote: > Hi everybody, > > this is a gentle reminder to update > http://wiki.xen.org/wiki/Xen_Development_Projects and to start Let me put some extra items on the list. > thinking about projects that are suitable for GSoC. The template to > add items to the project page is below... > > {{project > |Project=Project description > |Date=date of insert > |Contact=Owner name > |Desc=Description of > |GSoC=Yes or No, or any other GSoC related comment > }} > > In 2012, we didn't make it into GSoC because we didn't have a good > enough project list. We need to have a list of about 10 good project > proposals for GSoC and present these nicely. It would be a real > shame, if we didn't make it in 2013, in particular with some of the > exciting work which is going on at the moment. > > In 2011, when we made it our project list was at > http://wiki.xen.org/wiki/Archived/GSoc_2011_Ideas ... Google has > raised the bar, so we need to have > a) Really good descriptions for our GSoC projects > b) Pre-assign mentors to each project > c) Ideally I would like to add biography and interest section for > all our mentors. I can create a wiki template for mentors if it > helps Please do. > > All this needs to be in place when we apply for GSoC as a mentoring > organisation. The application deadline is likely in early February > 2013, so starting on this now should leave us in good shape! If we Aye. Feb. > get a good list of projects together this year, we can tidy it up, > iterate and improve in January! > > Best Regards > Lars > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > _______________________________________________ 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 May 03 12:35:11 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCh-0006Ro-M7; Fri, 03 May 2013 12:35:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TlRRA-0003ZH-RO; Wed, 19 Dec 2012 21:44:25 +0000 Received: from [85.158.137.99:34601] by server-10.bemta-3.messagelabs.com id E9/BA-07616-73532D05; Wed, 19 Dec 2012 21:44:23 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-6.tower-217.messagelabs.com!1355953461!15046686!1 X-Originating-IP: [156.151.31.81] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU2LjE1MS4zMS44MSA9PiAxMzIwMTU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32370 invoked from network); 19 Dec 2012 21:44:22 -0000 Received: from userp1040.oracle.com (HELO userp1040.oracle.com) (156.151.31.81) by server-6.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Dec 2012 21:44:22 -0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id qBJLiH21029662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Dec 2012 21:44:18 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id qBJLiGPL027252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Dec 2012 21:44:16 GMT Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id qBJLiFku020364; Wed, 19 Dec 2012 15:44:15 -0600 Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 19 Dec 2012 13:44:15 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 64EAD1C032B; Wed, 19 Dec 2012 16:44:14 -0500 (EST) Date: Wed, 19 Dec 2012 16:44:14 -0500 From: Konrad Rzeszutek Wilk To: Lars Kurth , konrad@kernel.org Message-ID: <20121219214414.GA25858@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50A4F83D.4000205@xen.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet21.oracle.com [156.151.31.93] X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: xen-arm@lists.xen.org, "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Getting into shape for GSOC 2013 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, Nov 15, 2012 at 02:12:13PM +0000, Lars Kurth wrote: > Hi everybody, > > this is a gentle reminder to update > http://wiki.xen.org/wiki/Xen_Development_Projects and to start Let me put some extra items on the list. > thinking about projects that are suitable for GSoC. The template to > add items to the project page is below... > > {{project > |Project=Project description > |Date=date of insert > |Contact=Owner name > |Desc=Description of > |GSoC=Yes or No, or any other GSoC related comment > }} > > In 2012, we didn't make it into GSoC because we didn't have a good > enough project list. We need to have a list of about 10 good project > proposals for GSoC and present these nicely. It would be a real > shame, if we didn't make it in 2013, in particular with some of the > exciting work which is going on at the moment. > > In 2011, when we made it our project list was at > http://wiki.xen.org/wiki/Archived/GSoc_2011_Ideas ... Google has > raised the bar, so we need to have > a) Really good descriptions for our GSoC projects > b) Pre-assign mentors to each project > c) Ideally I would like to add biography and interest section for > all our mentors. I can create a wiki template for mentors if it > helps Please do. > > All this needs to be in place when we apply for GSoC as a mentoring > organisation. The application deadline is likely in early February > 2013, so starting on this now should leave us in good shape! If we Aye. Feb. > get a good list of projects together this year, we can tidy it up, > iterate and improve in January! > > Best Regards > Lars > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > _______________________________________________ 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 May 03 12:35:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCi-0006T3-C9; Fri, 03 May 2013 12:35:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFYR-0004tV-Tx; Mon, 07 Jan 2013 16:28:04 +0000 Received: from [85.158.138.51:55894] by server-16.bemta-3.messagelabs.com id 50/11-27634-297FAE05; Mon, 07 Jan 2013 16:28:02 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1357576065!9674328!1 X-Originating-IP: [141.146.126.69] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuNjkgPT4gMTQ0ODE5\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3646 invoked from network); 7 Jan 2013 16:27:49 -0000 Received: from aserp1040.oracle.com (HELO aserp1040.oracle.com) (141.146.126.69) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Jan 2013 16:27:49 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r07GRcuB006304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 Jan 2013 16:27:39 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r07GRaQ2012149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jan 2013 16:27:37 GMT Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r07GRanb031614; Mon, 7 Jan 2013 10:27:36 -0600 Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 07 Jan 2013 08:27:36 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id B85761BF844; Mon, 7 Jan 2013 11:27:34 -0500 (EST) Date: Mon, 7 Jan 2013 11:27:34 -0500 From: Konrad Rzeszutek Wilk To: Dario Faggioli Message-ID: <20130107162734.GA6402@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1355959883.28419.8.camel@Abyss> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: konrad@kernel.org, xen-arm@lists.xen.org, "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Getting into shape for GSOC 2013 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, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > > > c) Ideally I would like to add biography and interest section for > > > all our mentors. I can create a wiki template for mentors if it > > > helps Ideas for GSOC: - Support microcode update bundled in with the initrd in Xen. Here is the Linux side of it comes out looking: http://markmail.org/thread/ewrs7fa66knfwzbo - Write Xen PV Architecture Book/Manual/whatever. We have been slowly going through the PV architecture and documenting it. It would nice to have somebody full-time doing it and asking questions. And then the answers would be written in this book. _______________________________________________ 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 May 03 12:35:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCi-0006T3-C9; Fri, 03 May 2013 12:35:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsFYR-0004tV-Tx; Mon, 07 Jan 2013 16:28:04 +0000 Received: from [85.158.138.51:55894] by server-16.bemta-3.messagelabs.com id 50/11-27634-297FAE05; Mon, 07 Jan 2013 16:28:02 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1357576065!9674328!1 X-Originating-IP: [141.146.126.69] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuNjkgPT4gMTQ0ODE5\n X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3646 invoked from network); 7 Jan 2013 16:27:49 -0000 Received: from aserp1040.oracle.com (HELO aserp1040.oracle.com) (141.146.126.69) by server-13.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Jan 2013 16:27:49 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r07GRcuB006304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 Jan 2013 16:27:39 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r07GRaQ2012149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jan 2013 16:27:37 GMT Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r07GRanb031614; Mon, 7 Jan 2013 10:27:36 -0600 Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 07 Jan 2013 08:27:36 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id B85761BF844; Mon, 7 Jan 2013 11:27:34 -0500 (EST) Date: Mon, 7 Jan 2013 11:27:34 -0500 From: Konrad Rzeszutek Wilk To: Dario Faggioli Message-ID: <20130107162734.GA6402@phenom.dumpdata.com> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1355959883.28419.8.camel@Abyss> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: konrad@kernel.org, xen-arm@lists.xen.org, "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] Getting into shape for GSOC 2013 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, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: > > > c) Ideally I would like to add biography and interest section for > > > all our mentors. I can create a wiki template for mentors if it > > > helps Ideas for GSOC: - Support microcode update bundled in with the initrd in Xen. Here is the Linux side of it comes out looking: http://markmail.org/thread/ewrs7fa66knfwzbo - Write Xen PV Architecture Book/Manual/whatever. We have been slowly going through the PV architecture and documenting it. It would nice to have somebody full-time doing it and asking questions. And then the answers would be written in this book. _______________________________________________ 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 May 03 12:35:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCi-0006Te-JK; Fri, 03 May 2013 12:35:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxpg-0003bp-Gr for xen-arm@lists.xen.org; Wed, 09 Jan 2013 15:44:48 +0000 Received: from [85.158.139.211:53256] by server-15.bemta-5.messagelabs.com id 27/65-20523-F609DE05; Wed, 09 Jan 2013 15:44:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-206.messagelabs.com!1357746287!23350037!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24584 invoked from network); 9 Jan 2013 15:44:47 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-206.messagelabs.com with SMTP; 9 Jan 2013 15:44:47 -0000 Received: (qmail 23840 invoked by uid 634); 9 Jan 2013 15:44:46 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 09 Jan 2013 15:44:43 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1357576754.13581.15.camel@iceland> Date: Wed, 9 Jan 2013 15:44:42 +0000 Message-Id: <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> To: Wei Liu X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 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 7 Jan 2013, at 16:39, Wei Liu wrote: > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: >> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: >>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: >>>>> c) Ideally I would like to add biography and interest section for >>>>> all our mentors. I can create a wiki template for mentors if it >>>>> helps >> >> Ideas for GSOC: >> >> - Support microcode update bundled in with the initrd in Xen. >> Here is the Linux side of it comes out looking: >> http://markmail.org/thread/ewrs7fa66knfwzbo >> >> - Write Xen PV Architecture Book/Manual/whatever. We have been >> slowly going through the PV architecture and documenting it. >> It would nice to have somebody full-time doing it and asking >> questions. And then the answers would be written in this book. >> > > IIRC the documentation-only project will not be accepted. So turn it into an executable specification and use that to generate fuzz tests as well as documentation. In particular, doing this for more than just hypercalls, but also for the ring protocols (to find bugs in the backend drivers) would be a useful regression harness. Throw in all the latest additions like multipage rings and various frontend options, and you will certainly shake out a few bugs (I just accidentally found a netback crash that I'm reporting separately). -anil _______________________________________________ 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 May 03 12:35:12 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35: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 1UYFCi-0006Te-JK; Fri, 03 May 2013 12:35:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Tsxpg-0003bp-Gr for xen-arm@lists.xen.org; Wed, 09 Jan 2013 15:44:48 +0000 Received: from [85.158.139.211:53256] by server-15.bemta-5.messagelabs.com id 27/65-20523-F609DE05; Wed, 09 Jan 2013 15:44:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-206.messagelabs.com!1357746287!23350037!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24584 invoked from network); 9 Jan 2013 15:44:47 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-206.messagelabs.com with SMTP; 9 Jan 2013 15:44:47 -0000 Received: (qmail 23840 invoked by uid 634); 9 Jan 2013 15:44:46 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 09 Jan 2013 15:44:43 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1357576754.13581.15.camel@iceland> Date: Wed, 9 Jan 2013 15:44:42 +0000 Message-Id: <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> To: Wei Liu X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 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 7 Jan 2013, at 16:39, Wei Liu wrote: > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: >> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: >>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: >>>>> c) Ideally I would like to add biography and interest section for >>>>> all our mentors. I can create a wiki template for mentors if it >>>>> helps >> >> Ideas for GSOC: >> >> - Support microcode update bundled in with the initrd in Xen. >> Here is the Linux side of it comes out looking: >> http://markmail.org/thread/ewrs7fa66knfwzbo >> >> - Write Xen PV Architecture Book/Manual/whatever. We have been >> slowly going through the PV architecture and documenting it. >> It would nice to have somebody full-time doing it and asking >> questions. And then the answers would be written in this book. >> > > IIRC the documentation-only project will not be accepted. So turn it into an executable specification and use that to generate fuzz tests as well as documentation. In particular, doing this for more than just hypercalls, but also for the ring protocols (to find bugs in the backend drivers) would be a useful regression harness. Throw in all the latest additions like multipage rings and various frontend options, and you will certainly shake out a few bugs (I just accidentally found a netback crash that I'm reporting separately). -anil _______________________________________________ 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 May 03 12:35:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCj-0006UT-0w; Fri, 03 May 2013 12:35:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyNO-0005LZ-VW for xen-arm@lists.xen.org; Wed, 09 Jan 2013 16:19:39 +0000 Received: from [85.158.139.83:25667] by server-7.bemta-5.messagelabs.com id 6D/77-08009-A989DE05; Wed, 09 Jan 2013 16:19:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-182.messagelabs.com!1357748377!30806085!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11237 invoked from network); 9 Jan 2013 16:19:37 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-182.messagelabs.com with SMTP; 9 Jan 2013 16:19:37 -0000 Received: (qmail 486 invoked by uid 634); 9 Jan 2013 16:19:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 09 Jan 2013 16:19:34 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1357747958.9068.10.camel@iceland> Date: Wed, 9 Jan 2013 16:19:35 +0000 Message-Id: References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> <1357747958.9068.10.camel@iceland> To: Wei Liu X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 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 9 Jan 2013, at 16:12, Wei Liu wrote: > On Wed, 2013-01-09 at 15:44 +0000, Anil Madhavapeddy wrote: >> On 7 Jan 2013, at 16:39, Wei Liu wrote: >> >>> On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: >>>> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: >>>>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: >>>>>>> c) Ideally I would like to add biography and interest section for >>>>>>> all our mentors. I can create a wiki template for mentors if it >>>>>>> helps >>>> >>>> Ideas for GSOC: >>>> >>>> - Support microcode update bundled in with the initrd in Xen. >>>> Here is the Linux side of it comes out looking: >>>> http://markmail.org/thread/ewrs7fa66knfwzbo >>>> >>>> - Write Xen PV Architecture Book/Manual/whatever. We have been >>>> slowly going through the PV architecture and documenting it. >>>> It would nice to have somebody full-time doing it and asking >>>> questions. And then the answers would be written in this book. >>>> >>> >>> IIRC the documentation-only project will not be accepted. >> >> So turn it into an executable specification and use that to generate >> fuzz tests as well as documentation. >> >> In particular, doing this for more than just hypercalls, but also for >> the ring protocols (to find bugs in the backend drivers) would be a >> useful regression harness. Throw in all the latest additions like >> multipage rings and various frontend options, and you will certainly >> shake out a few bugs (I just accidentally found a netback crash that >> I'm reporting separately). >> > > Anil could you put this idea on the project list if you're interested. > > http://wiki.xen.org/wiki/Xen_Development_Projects > > We will start polishing the list for GSoC soon. I put a similar one up a few months ago ("Fuzz testing Xen with Mirage"). -anil _______________________________________________ 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 May 03 12:35:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCj-0006UT-0w; Fri, 03 May 2013 12:35:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TsyNO-0005LZ-VW for xen-arm@lists.xen.org; Wed, 09 Jan 2013 16:19:39 +0000 Received: from [85.158.139.83:25667] by server-7.bemta-5.messagelabs.com id 6D/77-08009-A989DE05; Wed, 09 Jan 2013 16:19:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-182.messagelabs.com!1357748377!30806085!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.8; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11237 invoked from network); 9 Jan 2013 16:19:37 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-182.messagelabs.com with SMTP; 9 Jan 2013 16:19:37 -0000 Received: (qmail 486 invoked by uid 634); 9 Jan 2013 16:19:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 09 Jan 2013 16:19:34 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1357747958.9068.10.camel@iceland> Date: Wed, 9 Jan 2013 16:19:35 +0000 Message-Id: References: <50A4F83D.4000205@xen.org> <20121219214414.GA25858@phenom.dumpdata.com> <1355959883.28419.8.camel@Abyss> <20130107162734.GA6402@phenom.dumpdata.com> <1357576754.13581.15.camel@iceland> <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org> <1357747958.9068.10.camel@iceland> To: Wei Liu X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , "konrad@kernel.org" , Dario Faggioli , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-devel] Getting into shape for GSOC 2013 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 9 Jan 2013, at 16:12, Wei Liu wrote: > On Wed, 2013-01-09 at 15:44 +0000, Anil Madhavapeddy wrote: >> On 7 Jan 2013, at 16:39, Wei Liu wrote: >> >>> On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote: >>>> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote: >>>>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: >>>>>>> c) Ideally I would like to add biography and interest section for >>>>>>> all our mentors. I can create a wiki template for mentors if it >>>>>>> helps >>>> >>>> Ideas for GSOC: >>>> >>>> - Support microcode update bundled in with the initrd in Xen. >>>> Here is the Linux side of it comes out looking: >>>> http://markmail.org/thread/ewrs7fa66knfwzbo >>>> >>>> - Write Xen PV Architecture Book/Manual/whatever. We have been >>>> slowly going through the PV architecture and documenting it. >>>> It would nice to have somebody full-time doing it and asking >>>> questions. And then the answers would be written in this book. >>>> >>> >>> IIRC the documentation-only project will not be accepted. >> >> So turn it into an executable specification and use that to generate >> fuzz tests as well as documentation. >> >> In particular, doing this for more than just hypercalls, but also for >> the ring protocols (to find bugs in the backend drivers) would be a >> useful regression harness. Throw in all the latest additions like >> multipage rings and various frontend options, and you will certainly >> shake out a few bugs (I just accidentally found a netback crash that >> I'm reporting separately). >> > > Anil could you put this idea on the project list if you're interested. > > http://wiki.xen.org/wiki/Xen_Development_Projects > > We will start polishing the list for GSoC soon. I put a similar one up a few months ago ("Fuzz testing Xen with Mirage"). -anil _______________________________________________ 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 May 03 12:35:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCj-0006Uo-78; Fri, 03 May 2013 12:35:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtLGO-000419-1f for xen-arm@lists.xen.org; Thu, 10 Jan 2013 16:45:56 +0000 Received: from [85.158.143.35:9023] by server-2.bemta-4.messagelabs.com id C5/F1-24322-340FEE05; Thu, 10 Jan 2013 16:45:55 +0000 X-Env-Sender: lra@sics.se X-Msg-Ref: server-14.tower-21.messagelabs.com!1357836263!15794254!1 X-Originating-IP: [193.10.64.202] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13033 invoked from network); 10 Jan 2013 16:44:24 -0000 Received: from unknown (HELO fsmsg1.sics.se) (193.10.64.202) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2013 16:44:24 -0000 Received: from pps.filterd (fsmsg1 [127.0.0.1]) by fsmsg1.sics.se (8.14.5/8.14.5) with SMTP id r0AGhr0n002047 for ; Thu, 10 Jan 2013 17:43:53 +0100 Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by fsmsg1.sics.se with ESMTP id 19sx5m89jt-1 for ; Thu, 10 Jan 2013 17:43:53 +0100 Received: from stolichnaya.sics.se (stolichnaya.sics.se [193.10.67.151]) (Authenticated sender: lra@sics.se) by letter.sics.se (Postfix) with ESMTPSA id 5769B40008 for ; Thu, 10 Jan 2013 17:43:53 +0100 (CET) From: Lars Rasmusson Message-Id: <88B4069E-C096-4726-8486-B52D320E2DA9@sics.se> Date: Thu, 10 Jan 2013 17:43:53 +0100 To: xen-arm@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2013-01-10_08:2013-01-10, 2013-01-10, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1211240000 definitions=main-1301100128 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] Xen-arm patch to early init_uart in head.S 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, reading the PL011 UART documentation on http://infocenter.arm.com/help/topic/com.arm.doc.ddi0183f/DDI0183.pdf the early initialisation of the UART on the Versatile Express is incorrect. (Currently it probably works only because the default values are sane.) Cheers, /Lars >From 7184ce113d907ce8cf366dddbe8145e59987a656 Mon Sep 17 00:00:00 2001 From: Lars Rasmusson Date: Thu, 10 Jan 2013 17:10:44 +0100 Subject: [PATCH] Fixed register values and comment in early init_uart to match documentation of PL011 UART Signed-off-by: Lars Rasmusson --- xen/arch/arm/head.S | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xen/arch/arm/head.S b/xen/arch/arm/head.S index cdbe011..a884592 100644 --- a/xen/arch/arm/head.S +++ b/xen/arch/arm/head.S @@ -291,11 +291,11 @@ fail: PRINT("- Boot failed -\r\n") * Clobbers r0-r2 */ init_uart: mov r1, #0x0 - str r1, [r11, #0x24] /* -> UARTIBRD (Baud divisor fraction) */ + str r1, [r11, #0x28] /* -> UARTFBRD (Baud divisor fraction) */ mov r1, #0x4 /* 7.3728MHz / 0x4 == 16 * 115200 */ str r1, [r11, #0x24] /* -> UARTIBRD (Baud divisor integer) */ mov r1, #0x60 /* 8n1 */ - str r1, [r11, #0x24] /* -> UARTLCR_H (Line control) */ + str r1, [r11, #0x2C] /* -> UARTLCR_H (Line control) */ ldr r1, =0x00000301 /* RXE | TXE | UARTEN */ str r1, [r11, #0x30] /* -> UARTCR (Control Register) */ adr r0, 1f -- 1.7.9.5 _______________________________________________ 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 May 03 12:35:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCj-0006Uo-78; Fri, 03 May 2013 12:35:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TtLGO-000419-1f for xen-arm@lists.xen.org; Thu, 10 Jan 2013 16:45:56 +0000 Received: from [85.158.143.35:9023] by server-2.bemta-4.messagelabs.com id C5/F1-24322-340FEE05; Thu, 10 Jan 2013 16:45:55 +0000 X-Env-Sender: lra@sics.se X-Msg-Ref: server-14.tower-21.messagelabs.com!1357836263!15794254!1 X-Originating-IP: [193.10.64.202] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13033 invoked from network); 10 Jan 2013 16:44:24 -0000 Received: from unknown (HELO fsmsg1.sics.se) (193.10.64.202) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jan 2013 16:44:24 -0000 Received: from pps.filterd (fsmsg1 [127.0.0.1]) by fsmsg1.sics.se (8.14.5/8.14.5) with SMTP id r0AGhr0n002047 for ; Thu, 10 Jan 2013 17:43:53 +0100 Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by fsmsg1.sics.se with ESMTP id 19sx5m89jt-1 for ; Thu, 10 Jan 2013 17:43:53 +0100 Received: from stolichnaya.sics.se (stolichnaya.sics.se [193.10.67.151]) (Authenticated sender: lra@sics.se) by letter.sics.se (Postfix) with ESMTPSA id 5769B40008 for ; Thu, 10 Jan 2013 17:43:53 +0100 (CET) From: Lars Rasmusson Message-Id: <88B4069E-C096-4726-8486-B52D320E2DA9@sics.se> Date: Thu, 10 Jan 2013 17:43:53 +0100 To: xen-arm@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2013-01-10_08:2013-01-10, 2013-01-10, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1211240000 definitions=main-1301100128 X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] Xen-arm patch to early init_uart in head.S 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, reading the PL011 UART documentation on http://infocenter.arm.com/help/topic/com.arm.doc.ddi0183f/DDI0183.pdf the early initialisation of the UART on the Versatile Express is incorrect. (Currently it probably works only because the default values are sane.) Cheers, /Lars >From 7184ce113d907ce8cf366dddbe8145e59987a656 Mon Sep 17 00:00:00 2001 From: Lars Rasmusson Date: Thu, 10 Jan 2013 17:10:44 +0100 Subject: [PATCH] Fixed register values and comment in early init_uart to match documentation of PL011 UART Signed-off-by: Lars Rasmusson --- xen/arch/arm/head.S | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xen/arch/arm/head.S b/xen/arch/arm/head.S index cdbe011..a884592 100644 --- a/xen/arch/arm/head.S +++ b/xen/arch/arm/head.S @@ -291,11 +291,11 @@ fail: PRINT("- Boot failed -\r\n") * Clobbers r0-r2 */ init_uart: mov r1, #0x0 - str r1, [r11, #0x24] /* -> UARTIBRD (Baud divisor fraction) */ + str r1, [r11, #0x28] /* -> UARTFBRD (Baud divisor fraction) */ mov r1, #0x4 /* 7.3728MHz / 0x4 == 16 * 115200 */ str r1, [r11, #0x24] /* -> UARTIBRD (Baud divisor integer) */ mov r1, #0x60 /* 8n1 */ - str r1, [r11, #0x24] /* -> UARTLCR_H (Line control) */ + str r1, [r11, #0x2C] /* -> UARTLCR_H (Line control) */ ldr r1, =0x00000301 /* RXE | TXE | UARTEN */ str r1, [r11, #0x30] /* -> UARTCR (Control Register) */ adr r0, 1f -- 1.7.9.5 _______________________________________________ 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 May 03 12:35:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCj-0006VF-EI; Fri, 03 May 2013 12:35:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWmL-0006XE-JV for xen-arm@lists.xen.org; Wed, 16 Jan 2013 17:27:57 +0000 Received: from [85.158.137.99:49550] by server-9.bemta-3.messagelabs.com id 5C/0A-04352-C13E6F05; Wed, 16 Jan 2013 17:27:56 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-217.messagelabs.com!1358357272!17235908!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31637 invoked from network); 16 Jan 2013 17:27:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-217.messagelabs.com with SMTP; 16 Jan 2013 17:27:53 -0000 Received: (qmail 4199 invoked by uid 634); 16 Jan 2013 17:27:51 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 16 Jan 2013 17:27:51 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1358357036.13856.14.camel@zakaz.uk.xensource.com> Date: Wed, 16 Jan 2013 17:27:52 +0000 Message-Id: <53A794F5-259A-46D5-8BA9-CBE06242E7F3@recoil.org> References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> <1358357036.13856.14.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Amir M Chaudhry , "xen-devel@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal 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 16 Jan 2013, at 17:23, Ian Campbell wrote: > On Wed, 2013-01-16 at 17:17 +0000, Goswin von Brederlow wrote: >> On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: >>> On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: >>>> this e-mail is to let you know that the OpenMirage project is seeking to >>>> become a Xen.org hosted project. >>> >>> Mirage is cool stuff. >>> >>> I'm all for this, FWIW. >>> >>> Ian. >> >> Mirage is cool indeed. Only used it on x86 though. >> >> Since I got this mail via the xen-arm ML does that mean mirage supports >> xen-arm too? > > You might get a better response if you don't drop the CC. > > AIUI the intention is to eventually support ARM. > > I expect the xen-api CC was because it is the existing project leads who > ultimately vote to accept the project or something like that. We are indeed planning to support xen-arm, but are waiting for hardware. Dave and I both have Chromebooks A15 now, and we have patches floating around for HVM/x86_minios. An ARM PVHVM version should be quite straightforward. Another summer project I'm happy to supervise (particularly for GSoC) is a direct Raspberry Pi port, using uBoot as the main bootloader. That should shake out any ARM-specific issues in advance of a Xen/ARM port. Please get in touch with me if interested in this one. -anil _______________________________________________ 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 May 03 12:35:13 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCj-0006VF-EI; Fri, 03 May 2013 12:35:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TvWmL-0006XE-JV for xen-arm@lists.xen.org; Wed, 16 Jan 2013 17:27:57 +0000 Received: from [85.158.137.99:49550] by server-9.bemta-3.messagelabs.com id 5C/0A-04352-C13E6F05; Wed, 16 Jan 2013 17:27:56 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-217.messagelabs.com!1358357272!17235908!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31637 invoked from network); 16 Jan 2013 17:27:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-217.messagelabs.com with SMTP; 16 Jan 2013 17:27:53 -0000 Received: (qmail 4199 invoked by uid 634); 16 Jan 2013 17:27:51 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.0.83]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 16 Jan 2013 17:27:51 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anil Madhavapeddy In-Reply-To: <1358357036.13856.14.camel@zakaz.uk.xensource.com> Date: Wed, 16 Jan 2013 17:27:52 +0000 Message-Id: <53A794F5-259A-46D5-8BA9-CBE06242E7F3@recoil.org> References: <50F044C3.7010400@xen.org> <1358352891.32431.100.camel@zakaz.uk.xensource.com> <20130116171723.GB15900@frosties> <1358357036.13856.14.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Amir M Chaudhry , "xen-devel@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] [Community Review] Mirage Incubation Project Proposal 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 16 Jan 2013, at 17:23, Ian Campbell wrote: > On Wed, 2013-01-16 at 17:17 +0000, Goswin von Brederlow wrote: >> On Wed, Jan 16, 2013 at 04:14:51PM +0000, Ian Campbell wrote: >>> On Fri, 2013-01-11 at 16:58 +0000, Lars Kurth wrote: >>>> this e-mail is to let you know that the OpenMirage project is seeking to >>>> become a Xen.org hosted project. >>> >>> Mirage is cool stuff. >>> >>> I'm all for this, FWIW. >>> >>> Ian. >> >> Mirage is cool indeed. Only used it on x86 though. >> >> Since I got this mail via the xen-arm ML does that mean mirage supports >> xen-arm too? > > You might get a better response if you don't drop the CC. > > AIUI the intention is to eventually support ARM. > > I expect the xen-api CC was because it is the existing project leads who > ultimately vote to accept the project or something like that. We are indeed planning to support xen-arm, but are waiting for hardware. Dave and I both have Chromebooks A15 now, and we have patches floating around for HVM/x86_minios. An ARM PVHVM version should be quite straightforward. Another summer project I'm happy to supervise (particularly for GSoC) is a direct Raspberry Pi port, using uBoot as the main bootloader. That should shake out any ARM-specific issues in advance of a Xen/ARM port. Please get in touch with me if interested in this one. -anil _______________________________________________ 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 May 03 12:35:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCk-0006XJ-Ks; Fri, 03 May 2013 12:35:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UE60e-0003hK-BH for xen-arm@lists.xen.org; Fri, 08 Mar 2013 22:43:28 +0000 Received: from [85.158.138.51:48915] by server-15.bemta-3.messagelabs.com id 7C/03-23142-F896A315; Fri, 08 Mar 2013 22:43:27 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1362782606!23286883!1 X-Originating-IP: [209.85.217.195] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17073 invoked from network); 8 Mar 2013 22:43:26 -0000 Received: from mail-lb0-f195.google.com (HELO mail-lb0-f195.google.com) (209.85.217.195) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 8 Mar 2013 22:43:26 -0000 Received: by mail-lb0-f195.google.com with SMTP id gf14so378242lbb.10 for ; Fri, 08 Mar 2013 14:43:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=YVR+tngEHLQpq+5VBCZoJrrd+CMe393fh2VM/nsNpSs=; b=Ke0lkxUr4uSJtJdCpfjsBT0agAn2EZMsScfqAhc27cjz5yGSxo9n9m2TeRyRj6lDAM vqsWWG4udaNyNR7TXiyadZ8IBMwA8YKpeeeNFnXOWjGb86mD21ACrap/gpZaC31wljnJ lgbAHTf11ovHc99rZTGWTlSJjf5Zn5fEw7JfFkDTIK1DECYpj8mRNuG4aXslmCKqebHI 9WEqrSR6UKZk81GRDdpL7Smf5FPaeYkrCWU/1x4GqBh+O2BLbdCRGYaY74N5ObCHcZyY gA8rKKjioXwEPVyChVhphjGo1l1pT3P/wHTw0zThcKb222WQJw9yZKDJ/QULYNejZq67 E7gg== MIME-Version: 1.0 X-Received: by 10.112.37.129 with SMTP id y1mr1698332lbj.17.1362782606008; Fri, 08 Mar 2013 14:43:26 -0800 (PST) Received: by 10.112.13.3 with HTTP; Fri, 8 Mar 2013 14:43:25 -0800 (PST) Date: Fri, 8 Mar 2013 17:43:25 -0500 X-Google-Sender-Auth: gZj-5b-zZoHkRrY2crJ4t-gX0K8 Message-ID: From: Russ Pavlicek To: xen-arm@lists.xen.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] Xen Hackathon hosted by Google, May 16-17 in Dublin 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="===============2053421884367483787==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============2053421884367483787== Content-Type: multipart/alternative; boundary=e0cb4efe3306232a5d04d7718d7e --e0cb4efe3306232a5d04d7718d7e Content-Type: text/plain; charset=ISO-8859-1 It's time for another Xen Hackathon! This year's event will be held May 16-17 in Dublin, Ireland. Details can be found here: http://blog.xen.org/index.php/2013/03/07/google-hosted-xen-hackathon-may-16-17-dublin/ Thanks, Russell Pavlicek Xen Evangelist --e0cb4efe3306232a5d04d7718d7e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It's time for another Xen Hackathon!

This year's event will be held May 16-17 in Dublin, Ireland.

Details can be found here:=

=
Thanks,

Russell Pavlicek
Xen Evangelist
--e0cb4efe3306232a5d04d7718d7e-- --===============2053421884367483787== 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 --===============2053421884367483787==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:14 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCk-0006XJ-Ks; Fri, 03 May 2013 12:35:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UE60e-0003hK-BH for xen-arm@lists.xen.org; Fri, 08 Mar 2013 22:43:28 +0000 Received: from [85.158.138.51:48915] by server-15.bemta-3.messagelabs.com id 7C/03-23142-F896A315; Fri, 08 Mar 2013 22:43:27 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1362782606!23286883!1 X-Originating-IP: [209.85.217.195] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17073 invoked from network); 8 Mar 2013 22:43:26 -0000 Received: from mail-lb0-f195.google.com (HELO mail-lb0-f195.google.com) (209.85.217.195) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 8 Mar 2013 22:43:26 -0000 Received: by mail-lb0-f195.google.com with SMTP id gf14so378242lbb.10 for ; Fri, 08 Mar 2013 14:43:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=YVR+tngEHLQpq+5VBCZoJrrd+CMe393fh2VM/nsNpSs=; b=Ke0lkxUr4uSJtJdCpfjsBT0agAn2EZMsScfqAhc27cjz5yGSxo9n9m2TeRyRj6lDAM vqsWWG4udaNyNR7TXiyadZ8IBMwA8YKpeeeNFnXOWjGb86mD21ACrap/gpZaC31wljnJ lgbAHTf11ovHc99rZTGWTlSJjf5Zn5fEw7JfFkDTIK1DECYpj8mRNuG4aXslmCKqebHI 9WEqrSR6UKZk81GRDdpL7Smf5FPaeYkrCWU/1x4GqBh+O2BLbdCRGYaY74N5ObCHcZyY gA8rKKjioXwEPVyChVhphjGo1l1pT3P/wHTw0zThcKb222WQJw9yZKDJ/QULYNejZq67 E7gg== MIME-Version: 1.0 X-Received: by 10.112.37.129 with SMTP id y1mr1698332lbj.17.1362782606008; Fri, 08 Mar 2013 14:43:26 -0800 (PST) Received: by 10.112.13.3 with HTTP; Fri, 8 Mar 2013 14:43:25 -0800 (PST) Date: Fri, 8 Mar 2013 17:43:25 -0500 X-Google-Sender-Auth: gZj-5b-zZoHkRrY2crJ4t-gX0K8 Message-ID: From: Russ Pavlicek To: xen-arm@lists.xen.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] Xen Hackathon hosted by Google, May 16-17 in Dublin 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="===============2053421884367483787==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============2053421884367483787== Content-Type: multipart/alternative; boundary=e0cb4efe3306232a5d04d7718d7e --e0cb4efe3306232a5d04d7718d7e Content-Type: text/plain; charset=ISO-8859-1 It's time for another Xen Hackathon! This year's event will be held May 16-17 in Dublin, Ireland. Details can be found here: http://blog.xen.org/index.php/2013/03/07/google-hosted-xen-hackathon-may-16-17-dublin/ Thanks, Russell Pavlicek Xen Evangelist --e0cb4efe3306232a5d04d7718d7e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It's time for another Xen Hackathon!

This year's event will be held May 16-17 in Dublin, Ireland.

Details can be found here:=

=
Thanks,

Russell Pavlicek
Xen Evangelist
--e0cb4efe3306232a5d04d7718d7e-- --===============2053421884367483787== 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 --===============2053421884367483787==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCk-0006Xn-RO; Fri, 03 May 2013 12:35:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UKWMx-0003YZ-SI; Tue, 26 Mar 2013 16:05:04 +0000 Received: from [85.158.139.211:18441] by server-5.bemta-5.messagelabs.com id E6/0B-02762-F27C1515; Tue, 26 Mar 2013 16:05:03 +0000 X-Env-Sender: anthony.perard@citrix.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1364313899!19781948!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12220 invoked from network); 26 Mar 2013 16:05:02 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2013 16:05:02 -0000 X-IronPort-AV: E=Sophos;i="4.84,913,1355097600"; d="scan'208";a="15657259" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 26 Mar 2013 16:04:34 +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.3; Tue, 26 Mar 2013 12:04:33 -0400 Received: from [10.80.3.61] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UKWMT-00043s-Eq; Tue, 26 Mar 2013 16:04:33 +0000 Message-ID: <5151C711.5090604@citrix.com> Date: Tue, 26 Mar 2013 16:04:33 +0000 From: Anthony PERARD User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: Sengul Thomas References: In-Reply-To: X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , Xen Devel Subject: Re: [XenARM] 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 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? Sorry, I don't know where this address come from. So, let's look at what Linux is doing. > One more question: > How can I look up the function that PC is pointing (4000893c)? There is a programme called `addr2line` and you can use it like that: $ addr2line -e vmlinux 4000893c and it will give a source file and hopefully a line. Then, if this does not help, there is always objdump to disassemble and get addresses associated with instructions and function names. So I do `arm-unknown-linux-gnueabi-objdump -d vmlinux | less` and search for the PC. There is 2 vmlinux, one (linux.git/arch/arm/boot/compressed/vmlinux) that decompress the second one (linux.git/vmlinux). Regards, -- Anthony PERARD _______________________________________________ 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 May 03 12:35:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCk-0006Xn-RO; Fri, 03 May 2013 12:35:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UKWMx-0003YZ-SI; Tue, 26 Mar 2013 16:05:04 +0000 Received: from [85.158.139.211:18441] by server-5.bemta-5.messagelabs.com id E6/0B-02762-F27C1515; Tue, 26 Mar 2013 16:05:03 +0000 X-Env-Sender: anthony.perard@citrix.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1364313899!19781948!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12220 invoked from network); 26 Mar 2013 16:05:02 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2013 16:05:02 -0000 X-IronPort-AV: E=Sophos;i="4.84,913,1355097600"; d="scan'208";a="15657259" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 26 Mar 2013 16:04:34 +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.3; Tue, 26 Mar 2013 12:04:33 -0400 Received: from [10.80.3.61] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UKWMT-00043s-Eq; Tue, 26 Mar 2013 16:04:33 +0000 Message-ID: <5151C711.5090604@citrix.com> Date: Tue, 26 Mar 2013 16:04:33 +0000 From: Anthony PERARD User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: Sengul Thomas References: In-Reply-To: X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , Xen Devel Subject: Re: [XenARM] 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 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? Sorry, I don't know where this address come from. So, let's look at what Linux is doing. > One more question: > How can I look up the function that PC is pointing (4000893c)? There is a programme called `addr2line` and you can use it like that: $ addr2line -e vmlinux 4000893c and it will give a source file and hopefully a line. Then, if this does not help, there is always objdump to disassemble and get addresses associated with instructions and function names. So I do `arm-unknown-linux-gnueabi-objdump -d vmlinux | less` and search for the PC. There is 2 vmlinux, one (linux.git/arch/arm/boot/compressed/vmlinux) that decompress the second one (linux.git/vmlinux). Regards, -- Anthony PERARD _______________________________________________ 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 May 03 12:35:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCl-0006YL-0K; Fri, 03 May 2013 12:35:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USTNN-0006Pr-QV for xen-arm@lists.xen.org; Wed, 17 Apr 2013 14:30:22 +0000 Received: from [193.109.254.147:36900] by server-13.bemta-14.messagelabs.com id 19/C2-07387-DF1BE615; Wed, 17 Apr 2013 14:30:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-27.messagelabs.com!1366209018!1834656!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28431 invoked from network); 17 Apr 2013 14:30:19 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-27.messagelabs.com with SMTP; 17 Apr 2013 14:30:19 -0000 Received: (qmail 15627 invoked by uid 634); 17 Apr 2013 14:30:18 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.1.75]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 17 Apr 2013 15:30:17 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Anil Madhavapeddy In-Reply-To: <1366203621.25579.25.camel@zakaz.uk.xensource.com> Date: Wed, 17 Apr 2013 15:30:16 +0100 Message-Id: <619F5B48-3FC8-4C06-A570-171965AFE047@recoil.org> References: <1366203621.25579.25.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Lars Kurth , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-users] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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 17 Apr 2013, at 14:00, Ian Campbell wrote: > > WRT "too much going on" when co-locating -- can we aim to abut with > other conferences rather than overlapping? At least this way travel can > be amortized. > > Or do people have an issue with the setup where Mon-Wed: Big Conference > (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Where > XenSummit is on the Thur+Fri because there are too many other smaller > conferences doing the same thing? I have a strong preference for a XenSummit near some other big event such as LinuxCon or FOSDEM. It's not worth making the trip to a far-off location just for a one or two-day dev summit, much as I'd enjoy it! The overloading of microconferences happens all the time. Most people only really have a conflict between one or two things, and I just hop between events for the interesting bits for me. -anil _______________________________________________ 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 May 03 12:35:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCl-0006YL-0K; Fri, 03 May 2013 12:35:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USTNN-0006Pr-QV for xen-arm@lists.xen.org; Wed, 17 Apr 2013 14:30:22 +0000 Received: from [193.109.254.147:36900] by server-13.bemta-14.messagelabs.com id 19/C2-07387-DF1BE615; Wed, 17 Apr 2013 14:30:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-27.messagelabs.com!1366209018!1834656!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28431 invoked from network); 17 Apr 2013 14:30:19 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-27.messagelabs.com with SMTP; 17 Apr 2013 14:30:19 -0000 Received: (qmail 15627 invoked by uid 634); 17 Apr 2013 14:30:18 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO [10.0.1.75]) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 17 Apr 2013 15:30:17 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Anil Madhavapeddy In-Reply-To: <1366203621.25579.25.camel@zakaz.uk.xensource.com> Date: Wed, 17 Apr 2013 15:30:16 +0100 Message-Id: <619F5B48-3FC8-4C06-A570-171965AFE047@recoil.org> References: <1366203621.25579.25.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: Lars Kurth , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Xen-users] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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 17 Apr 2013, at 14:00, Ian Campbell wrote: > > WRT "too much going on" when co-locating -- can we aim to abut with > other conferences rather than overlapping? At least this way travel can > be amortized. > > Or do people have an issue with the setup where Mon-Wed: Big Conference > (LinuxCon etc), Thur-Fri: Micro/specialised/smaller-confs etc. Where > XenSummit is on the Thur+Fri because there are too many other smaller > conferences doing the same thing? I have a strong preference for a XenSummit near some other big event such as LinuxCon or FOSDEM. It's not worth making the trip to a far-off location just for a one or two-day dev summit, much as I'd enjoy it! The overloading of microconferences happens all the time. Most people only really have a conflict between one or two things, and I just hop between events for the interesting bits for me. -anil _______________________________________________ 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 May 03 12:35:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCl-0006Yx-9u; Fri, 03 May 2013 12:35:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USTS8-0006ry-Nh; Wed, 17 Apr 2013 14:35:16 +0000 Received: from [85.158.143.99:6086] by server-1.bemta-4.messagelabs.com id 1A/C5-06203-323BE615; Wed, 17 Apr 2013 14:35:15 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1366209312!22933101!1 X-Originating-IP: [156.151.31.81] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU2LjE1MS4zMS44MSA9PiAyODgzMzk=\n X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4414 invoked from network); 17 Apr 2013 14:35:14 -0000 Received: from userp1040.oracle.com (HELO userp1040.oracle.com) (156.151.31.81) by server-4.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2013 14:35:14 -0000 Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r3HEZ9oU016730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Apr 2013 14:35:10 GMT Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r3HEZ8Ax027197 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 17 Apr 2013 14:35:09 GMT Received: from abhmt107.oracle.com (abhmt107.oracle.com [141.146.116.59]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r3HEZ89g029545; Wed, 17 Apr 2013 14:35:08 GMT Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 17 Apr 2013 07:35:07 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 994CC1BF781; Wed, 17 Apr 2013 10:35:06 -0400 (EDT) Date: Wed, 17 Apr 2013 10:35:06 -0400 From: Konrad Rzeszutek Wilk To: Lars Kurth Message-ID: <20130417143506.GA23651@phenom.dumpdata.com> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: acsinet21.oracle.com [141.146.126.237] X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: xen-arm@lists.xen.org, "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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 Wed, Apr 17, 2013 at 06:51:21AM +0100, Lars Kurth wrote: > Hi everybody, > > we had a Xen Project Advisory Board meeting this morning and I had an > action to get community input on XenSummit and Hackathon locations for > 2014. I need to start tying these down pretty soon such that I can reserve > the space. So I took an action to get community input. To remind you in > 2013, XenSummit will be in Edinburgh, UK in October. So I took Europe off > the menu for 2014 : please shout if this is an issue. > > Can I ask you to respond to this thread and order the options based on your > preferences (highest first). I also wanted to remind you that a few months > back, we had a discussion to distribute the summits more evenly around the > globe. All options would be co-located with one or several Linux events. > > Here are the options for events: > > 1) Rio de Janeiro, May 2014 > 2) Chicago, end of August 2014 > 3) Korea, end of November 2014 > > Note that if we want to do an event in Rio, I have to book the space by > mid-May this year. Also note that Chicago may be a bit busy with at least > 2-3 other Linux events that are likely to take place at the same time (I > remember there were some complaints that XenSummit 2012 in San Diego was a > bit to stressful as too much was going on in the same week). Also note that > Seattle, August 2015 would be an option to host XenSummit, assuming we > didn't chose a US location in 2014. > > I will make a start and vote in order of my preference (highest first) for > Rio, Korea, Chicago. > > My reasoning is that this would allow us to have a XenSummit in Rio and a > Hackathon in Korea (or vice versa). This would fit nicely with a XenSummit > in Seattle in 2015. As far as I can tell. there would also be fairly good > alignment with the Xen release cycle. > > Let me know your preferences (but remember, I need to know by the end of > April). My preference: Chicago, Rio, Korea > > Cheers > Lars > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel _______________________________________________ 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 May 03 12:35:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCl-0006Yx-9u; Fri, 03 May 2013 12:35:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1USTS8-0006ry-Nh; Wed, 17 Apr 2013 14:35:16 +0000 Received: from [85.158.143.99:6086] by server-1.bemta-4.messagelabs.com id 1A/C5-06203-323BE615; Wed, 17 Apr 2013 14:35:15 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1366209312!22933101!1 X-Originating-IP: [156.151.31.81] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU2LjE1MS4zMS44MSA9PiAyODgzMzk=\n X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4414 invoked from network); 17 Apr 2013 14:35:14 -0000 Received: from userp1040.oracle.com (HELO userp1040.oracle.com) (156.151.31.81) by server-4.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Apr 2013 14:35:14 -0000 Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r3HEZ9oU016730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Apr 2013 14:35:10 GMT Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r3HEZ8Ax027197 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 17 Apr 2013 14:35:09 GMT Received: from abhmt107.oracle.com (abhmt107.oracle.com [141.146.116.59]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r3HEZ89g029545; Wed, 17 Apr 2013 14:35:08 GMT Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 17 Apr 2013 07:35:07 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 994CC1BF781; Wed, 17 Apr 2013 10:35:06 -0400 (EDT) Date: Wed, 17 Apr 2013 10:35:06 -0400 From: Konrad Rzeszutek Wilk To: Lars Kurth Message-ID: <20130417143506.GA23651@phenom.dumpdata.com> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: acsinet21.oracle.com [141.146.126.237] X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: xen-arm@lists.xen.org, "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] [Need Input] Options for XenSummits in 2014 (and beyond) - need input by end of April 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 Wed, Apr 17, 2013 at 06:51:21AM +0100, Lars Kurth wrote: > Hi everybody, > > we had a Xen Project Advisory Board meeting this morning and I had an > action to get community input on XenSummit and Hackathon locations for > 2014. I need to start tying these down pretty soon such that I can reserve > the space. So I took an action to get community input. To remind you in > 2013, XenSummit will be in Edinburgh, UK in October. So I took Europe off > the menu for 2014 : please shout if this is an issue. > > Can I ask you to respond to this thread and order the options based on your > preferences (highest first). I also wanted to remind you that a few months > back, we had a discussion to distribute the summits more evenly around the > globe. All options would be co-located with one or several Linux events. > > Here are the options for events: > > 1) Rio de Janeiro, May 2014 > 2) Chicago, end of August 2014 > 3) Korea, end of November 2014 > > Note that if we want to do an event in Rio, I have to book the space by > mid-May this year. Also note that Chicago may be a bit busy with at least > 2-3 other Linux events that are likely to take place at the same time (I > remember there were some complaints that XenSummit 2012 in San Diego was a > bit to stressful as too much was going on in the same week). Also note that > Seattle, August 2015 would be an option to host XenSummit, assuming we > didn't chose a US location in 2014. > > I will make a start and vote in order of my preference (highest first) for > Rio, Korea, Chicago. > > My reasoning is that this would allow us to have a XenSummit in Rio and a > Hackathon in Korea (or vice versa). This would fit nicely with a XenSummit > in Seattle in 2015. As far as I can tell. there would also be fairly good > alignment with the Xen release cycle. > > Let me know your preferences (but remember, I need to know by the end of > April). My preference: Chicago, Rio, Korea > > Cheers > Lars > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel _______________________________________________ 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 May 03 12:35:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCm-0006ai-2l; Fri, 03 May 2013 12:35:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UUYJE-0002m4-BJ; Tue, 23 Apr 2013 08:10:40 +0000 Received: from [85.158.137.99:43313] by server-14.bemta-3.messagelabs.com id D0/F9-27076-FF146715; Tue, 23 Apr 2013 08:10:39 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1366704633!13638101!1 X-Originating-IP: [209.85.214.178] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19610 invoked from network); 23 Apr 2013 08:10:35 -0000 Received: from mail-ob0-f178.google.com (HELO mail-ob0-f178.google.com) (209.85.214.178) by server-3.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2013 08:10:35 -0000 Received: by mail-ob0-f178.google.com with SMTP id 16so285174obc.9 for ; Tue, 23 Apr 2013 01:10:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=FogW47cwC6tAPU/59FXIPTRnUSzDBywH0MOCV/xMVmg=; b=PdAlqufwR9vUJzHyy3+jQoB8iI9LPgRCGyJ5IsWaqqUZpLrQUIankhAg93Z3/fzIwr xCttDKQdinlw24eb7C2d1ctvVJ5NWQXxj95bYWJx+kDMKhvxxkBDmGlVXCAx1bvopObS n51mcNv0pWdP5cAHEC4N2JNu/CbzXIt6sVOiBxjn6XgLHOYG6cWjuN/cZ54bf2X+fphc TgZE/i23LlZeeIjiyTdDiNbEvlF/2fKzCRiryjdJ3zrq3ElTHmNtA13aNZSYxJWP6EWW cb5V0NcMzjFqALTJIOJ7wMb/MJoayQSvu9+Uj7FE+iGrwwdhzXhT8KXwNr3vPzEJ96Q+ PZyg== MIME-Version: 1.0 X-Received: by 10.182.246.198 with SMTP id xy6mr11287119obc.1.1366704632832; Tue, 23 Apr 2013 01:10:32 -0700 (PDT) Received: by 10.60.3.232 with HTTP; Tue, 23 Apr 2013 01:10:32 -0700 (PDT) In-Reply-To: References: <516AECC9.1010603@xen.org> <20130419035218.GY88962@USLT-205755.sungardas.corp> <51756872.7040402@xen.org> Date: Tue, 23 Apr 2013 09:10:32 +0100 Message-ID: From: Lars Kurth To: samir benkhellat X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , Chip Childers , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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="===============8899019892573457290==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8899019892573457290== Content-Type: multipart/alternative; boundary=001a11c1bc042729da04db02b803 --001a11c1bc042729da04db02b803 Content-Type: text/plain; charset=ISO-8859-1 > I also want to know why we can't create/use a forum: It'll be more organized, easier to seach, > more categorized and more user frendly for new comers I don't think that our developers will want a forum. However for user questions, we created http://xenproject.org/help/questions-and-answers.html which are inessence a forum. You just need to start using it. On Mon, Apr 22, 2013 at 6:10 PM, samir benkhellat < benkhellat_samir@hotmail.com> wrote: > I also want to know why we can't create/use a forum: It'll be more > organized, easier to seach, more categorized and more user frendly for new > comers > > So what do you think? > > Regards > > ------------------------------ > Date: Mon, 22 Apr 2013 17:42:26 +0100 > From: lars.kurth@xen.org > To: chip.childers@sungard.com > CC: xen-arm@lists.xen.org; xen-devel@lists.xen.org; xen-api@lists.xen.org > Subject: Re: [Xen-API] [Proposal] Additional mailing lists for specific > purposes > > > Hi, > > seems nobody has any views. How about I make a more concrete proposal. I > also noticed that we have no real global list for voting and proposals (and > to discuss issues like this). I have to include all lists, which creates > spam. As already indicated on the blog, at some point we should move to @ > lists.xenproject.org, which will cause some impact on mailfilters, etc. > (similar to when we moved from @lists.xensource.com to @lists.xen.orgabout a year ago). So that may be a good opportunity to deal with some > inconsistencies that have grown over time. > > It also raises questions about naming conventions for new lists. Should > lists be > - xen-...@lists.xenproject.org, or should they be > - xenproject-...@lists.xenproject.org > And then of course, should any convention be forward looking or should we > rename lists to be consistent and (as we are already changing @ > lists.xenproject.org, changing the actual list name may not be any worse). > > On new lists, we will need lists for > > - xenproject-marketing@lists.xenproject.org ... maybe > xenproject-publicity@lists.xenproject.org hits it better than > marketing (seems to work for debian) > - I need something for votes and discussions that cut accross > sub-project and teams. Maybe xenproject-proposals@lists.xenproject.orgor > xenproject-decisionmaking@lists.xenproject.org? Just putting these > into the room: none of these sound right to me. Maybe > xenproject-leadership@lists.xenproject.org is better? > - We will have a list for the advisory board, which wants to be > totally open and transparent. So this would be > xenproject-advisoryboard@lists.xenproject.org and I will post minutes, > etc. of the last meeting when we created the list. > - xenproject-private, if we actually need it would work too. However > the advisory board recommended in the meeting last week not to have any > private lists at all. So maybe we don't need this. > > Also, for example XAPI does not have a separate dev or user list. That is > also one to consider at some point. > > Anyway, I am just putting these into the room for discussion. > > Lars > > On 19/04/2013 04:52, Chip Childers wrote: > > On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote: > > 1) A list for coordinating blog posts, other communication, > attending of event, etc. - not sure about the name, so am looking > for suggestions. I am not sure whether we should have public > archives: comparable lists of other projects don't. > > From an outsider / lurker perspective, xen-marketing@lists.xen.org is a > good fit. > > > 2) A semi-private invite mailing list for ALL project leads, > committers and maintainers of ALL projects hosted on xen.org > > Similarly to above: xen-private@lists.xen.org > > Both of these list names are used in other projects I'm working with / > observe. > > > > > _______________________________________________ Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --001a11c1bc042729da04db02b803 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>=A0I also want to know why we can't create/use a forum: It'll= =A0 be more organized, easier to seach,=A0
> more categorized and more user = frendly for new comers
I do= n't think that our developers will want a forum.
However for us= er questions, we created=A0http://xenproject.org/help/questions-and-answers.h= tml=A0which are inessence a forum. You just need to start using it.


On Mon,= Apr 22, 2013 at 6:10 PM, samir benkhellat <benkhellat_samir@ho= tmail.com> wrote:
I also want to know why we can't create/use a for= um: It'll=A0 be more organized, easier to seach, more categorized and m= ore user frendly for new comers

So what do you think?

Regards=

Date: Mon, 22 Apr 2013 17:42:26 +0100
From: lars.kurth@xen.org<= br>To: chip.= childers@sungard.com
CC: xen-arm@list= s.xen.org; xen-devel@lists.xen.org; xen-api@lists.xen.org
Subject: Re: [Xen-API] [Proposal] Additional mailing lists for specific pur= poses


=20 =20 =20 =20
Hi,

seems nobody has any views. How about I make a more concrete proposal. I also noticed that we have no real global list for voting and proposals (and to discuss issues like this). I have to include all lists, which creates spam. As already indicated on the blog, at some point we should move to @lists.xenproject.org, which will cause some impact on mailfilters, etc. (similar to when we moved from @= lists.xensource.com to @lists.xen.org about a year ago). So that may be a good opportunity to deal with some inconsistencies that have grown over time.

It also raises questions about naming conventions for new lists. Should lists be
- x= en-...@lists.xenproject.org, or should they be
- xenproject-...@lists.xenproject.org
And then of course, should any convention be forward looking or should we rename lists to be consistent and (as we are already changing @l= ists.xenproject.org, changing the actual list name may not be any worse).

On new lists, we will need lists for
Also, for example XAPI does not have a separate dev or user list. That is also one to consider at some point.

Anyway, I am just putting these into the room for discussion.

Lars

On 19/04/2013 04:52, Chip Childers wrote:
On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote:

1) A list for coordinating blog posts, other communication,
attending of event, etc. - not sure about the name, so am looking
for suggestions. I am not sure whether we should have public
archives: comparable lists of other projects don't.

From an outsider / lurker perspective, xen-marketing@lists.xen.org is =
a
good fit.


2) A semi-private invite mailing list for ALL project leads,
committers and maintainers of ALL projects hosted on xen.org

Similarly to above: xen-private@lists.xen.org

Both of these list names are used in other projects I'm working with /
observe.

=20
_______________________________________________ Xen-api mailing list Xen-api@lists.xe= n.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
=

--001a11c1bc042729da04db02b803-- --===============8899019892573457290== 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 --===============8899019892573457290==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:16 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCm-0006ai-2l; Fri, 03 May 2013 12:35:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UUYJE-0002m4-BJ; Tue, 23 Apr 2013 08:10:40 +0000 Received: from [85.158.137.99:43313] by server-14.bemta-3.messagelabs.com id D0/F9-27076-FF146715; Tue, 23 Apr 2013 08:10:39 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1366704633!13638101!1 X-Originating-IP: [209.85.214.178] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19610 invoked from network); 23 Apr 2013 08:10:35 -0000 Received: from mail-ob0-f178.google.com (HELO mail-ob0-f178.google.com) (209.85.214.178) by server-3.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2013 08:10:35 -0000 Received: by mail-ob0-f178.google.com with SMTP id 16so285174obc.9 for ; Tue, 23 Apr 2013 01:10:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=FogW47cwC6tAPU/59FXIPTRnUSzDBywH0MOCV/xMVmg=; b=PdAlqufwR9vUJzHyy3+jQoB8iI9LPgRCGyJ5IsWaqqUZpLrQUIankhAg93Z3/fzIwr xCttDKQdinlw24eb7C2d1ctvVJ5NWQXxj95bYWJx+kDMKhvxxkBDmGlVXCAx1bvopObS n51mcNv0pWdP5cAHEC4N2JNu/CbzXIt6sVOiBxjn6XgLHOYG6cWjuN/cZ54bf2X+fphc TgZE/i23LlZeeIjiyTdDiNbEvlF/2fKzCRiryjdJ3zrq3ElTHmNtA13aNZSYxJWP6EWW cb5V0NcMzjFqALTJIOJ7wMb/MJoayQSvu9+Uj7FE+iGrwwdhzXhT8KXwNr3vPzEJ96Q+ PZyg== MIME-Version: 1.0 X-Received: by 10.182.246.198 with SMTP id xy6mr11287119obc.1.1366704632832; Tue, 23 Apr 2013 01:10:32 -0700 (PDT) Received: by 10.60.3.232 with HTTP; Tue, 23 Apr 2013 01:10:32 -0700 (PDT) In-Reply-To: References: <516AECC9.1010603@xen.org> <20130419035218.GY88962@USLT-205755.sungardas.corp> <51756872.7040402@xen.org> Date: Tue, 23 Apr 2013 09:10:32 +0100 Message-ID: From: Lars Kurth To: samir benkhellat X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , Chip Childers , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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="===============8899019892573457290==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8899019892573457290== Content-Type: multipart/alternative; boundary=001a11c1bc042729da04db02b803 --001a11c1bc042729da04db02b803 Content-Type: text/plain; charset=ISO-8859-1 > I also want to know why we can't create/use a forum: It'll be more organized, easier to seach, > more categorized and more user frendly for new comers I don't think that our developers will want a forum. However for user questions, we created http://xenproject.org/help/questions-and-answers.html which are inessence a forum. You just need to start using it. On Mon, Apr 22, 2013 at 6:10 PM, samir benkhellat < benkhellat_samir@hotmail.com> wrote: > I also want to know why we can't create/use a forum: It'll be more > organized, easier to seach, more categorized and more user frendly for new > comers > > So what do you think? > > Regards > > ------------------------------ > Date: Mon, 22 Apr 2013 17:42:26 +0100 > From: lars.kurth@xen.org > To: chip.childers@sungard.com > CC: xen-arm@lists.xen.org; xen-devel@lists.xen.org; xen-api@lists.xen.org > Subject: Re: [Xen-API] [Proposal] Additional mailing lists for specific > purposes > > > Hi, > > seems nobody has any views. How about I make a more concrete proposal. I > also noticed that we have no real global list for voting and proposals (and > to discuss issues like this). I have to include all lists, which creates > spam. As already indicated on the blog, at some point we should move to @ > lists.xenproject.org, which will cause some impact on mailfilters, etc. > (similar to when we moved from @lists.xensource.com to @lists.xen.orgabout a year ago). So that may be a good opportunity to deal with some > inconsistencies that have grown over time. > > It also raises questions about naming conventions for new lists. Should > lists be > - xen-...@lists.xenproject.org, or should they be > - xenproject-...@lists.xenproject.org > And then of course, should any convention be forward looking or should we > rename lists to be consistent and (as we are already changing @ > lists.xenproject.org, changing the actual list name may not be any worse). > > On new lists, we will need lists for > > - xenproject-marketing@lists.xenproject.org ... maybe > xenproject-publicity@lists.xenproject.org hits it better than > marketing (seems to work for debian) > - I need something for votes and discussions that cut accross > sub-project and teams. Maybe xenproject-proposals@lists.xenproject.orgor > xenproject-decisionmaking@lists.xenproject.org? Just putting these > into the room: none of these sound right to me. Maybe > xenproject-leadership@lists.xenproject.org is better? > - We will have a list for the advisory board, which wants to be > totally open and transparent. So this would be > xenproject-advisoryboard@lists.xenproject.org and I will post minutes, > etc. of the last meeting when we created the list. > - xenproject-private, if we actually need it would work too. However > the advisory board recommended in the meeting last week not to have any > private lists at all. So maybe we don't need this. > > Also, for example XAPI does not have a separate dev or user list. That is > also one to consider at some point. > > Anyway, I am just putting these into the room for discussion. > > Lars > > On 19/04/2013 04:52, Chip Childers wrote: > > On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote: > > 1) A list for coordinating blog posts, other communication, > attending of event, etc. - not sure about the name, so am looking > for suggestions. I am not sure whether we should have public > archives: comparable lists of other projects don't. > > From an outsider / lurker perspective, xen-marketing@lists.xen.org is a > good fit. > > > 2) A semi-private invite mailing list for ALL project leads, > committers and maintainers of ALL projects hosted on xen.org > > Similarly to above: xen-private@lists.xen.org > > Both of these list names are used in other projects I'm working with / > observe. > > > > > _______________________________________________ Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --001a11c1bc042729da04db02b803 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>=A0I also want to know why we can't create/use a forum: It'll= =A0 be more organized, easier to seach,=A0
> more categorized and more user = frendly for new comers
I do= n't think that our developers will want a forum.
However for us= er questions, we created=A0http://xenproject.org/help/questions-and-answers.h= tml=A0which are inessence a forum. You just need to start using it.


On Mon,= Apr 22, 2013 at 6:10 PM, samir benkhellat <benkhellat_samir@ho= tmail.com> wrote:
I also want to know why we can't create/use a for= um: It'll=A0 be more organized, easier to seach, more categorized and m= ore user frendly for new comers

So what do you think?

Regards=

Date: Mon, 22 Apr 2013 17:42:26 +0100
From: lars.kurth@xen.org<= br>To: chip.= childers@sungard.com
CC: xen-arm@list= s.xen.org; xen-devel@lists.xen.org; xen-api@lists.xen.org
Subject: Re: [Xen-API] [Proposal] Additional mailing lists for specific pur= poses


=20 =20 =20 =20
Hi,

seems nobody has any views. How about I make a more concrete proposal. I also noticed that we have no real global list for voting and proposals (and to discuss issues like this). I have to include all lists, which creates spam. As already indicated on the blog, at some point we should move to @lists.xenproject.org, which will cause some impact on mailfilters, etc. (similar to when we moved from @= lists.xensource.com to @lists.xen.org about a year ago). So that may be a good opportunity to deal with some inconsistencies that have grown over time.

It also raises questions about naming conventions for new lists. Should lists be
- x= en-...@lists.xenproject.org, or should they be
- xenproject-...@lists.xenproject.org
And then of course, should any convention be forward looking or should we rename lists to be consistent and (as we are already changing @l= ists.xenproject.org, changing the actual list name may not be any worse).

On new lists, we will need lists for
Also, for example XAPI does not have a separate dev or user list. That is also one to consider at some point.

Anyway, I am just putting these into the room for discussion.

Lars

On 19/04/2013 04:52, Chip Childers wrote:
On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote:

1) A list for coordinating blog posts, other communication,
attending of event, etc. - not sure about the name, so am looking
for suggestions. I am not sure whether we should have public
archives: comparable lists of other projects don't.

From an outsider / lurker perspective, xen-marketing@lists.xen.org is =
a
good fit.


2) A semi-private invite mailing list for ALL project leads,
committers and maintainers of ALL projects hosted on xen.org

Similarly to above: xen-private@lists.xen.org

Both of these list names are used in other projects I'm working with /
observe.

=20
_______________________________________________ Xen-api mailing list Xen-api@lists.xe= n.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
=

--001a11c1bc042729da04db02b803-- --===============8899019892573457290== 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 --===============8899019892573457290==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCn-0006cL-2n; Fri, 03 May 2013 12:35:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UUYOn-0003Mb-UY; Tue, 23 Apr 2013 08:16:26 +0000 Received: from [193.109.254.147:4112] by server-3.bemta-14.messagelabs.com id E9/82-17488-85346715; Tue, 23 Apr 2013 08:16:24 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1366704968!9062695!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2187 invoked from network); 23 Apr 2013 08:16:10 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2013 08:16:10 -0000 Received: by mail-ob0-f171.google.com with SMTP id er7so284953obc.16 for ; Tue, 23 Apr 2013 01:16:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ox4mZi2LDeKYnDxL4rKBRoo4/6O+Lc4KWeMCzDIqrbo=; b=W0xfDkIq5qdJnFe6h6VbBVWTRSmYbBPLasigvSRTE1Bwa+pWmdUCVKdxJo7jvaWYng DHZsgRcz/TdySMi4HkpYZ57P6428/B9HQOVRbRI9mc1eXQh42/Da/oYgpflPQpSYp8ok bXGFwtGUI01wV9yfCCD9MyDcB4uMYHKN88D6hoSaaqHvUCk/+hNM/zML8MKYRy6nQjDg VNnF/IvQxpeWR6sX/+Br2FilJFmAock2VRjWjik4DG2l+RWvOF6tMWlgTAKeM+Q8ToWi l6O1Ehu0Br7zkV1pdEpYLwXufb54vBwiTU0ioEb4oANr7XwrG+KTUgUgHFqM8UmnBQ4e 9xIQ== MIME-Version: 1.0 X-Received: by 10.60.146.227 with SMTP id tf3mr3875159oeb.50.1366704967582; Tue, 23 Apr 2013 01:16:07 -0700 (PDT) Received: by 10.60.3.232 with HTTP; Tue, 23 Apr 2013 01:16:07 -0700 (PDT) In-Reply-To: References: <516AECC9.1010603@xen.org> <20130419035218.GY88962@USLT-205755.sungardas.corp> <51756872.7040402@xen.org> Date: Tue, 23 Apr 2013 09:16:07 +0100 Message-ID: From: Lars Kurth To: samir benkhellat X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , Chip Childers , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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="===============6989984071923597354==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============6989984071923597354== Content-Type: multipart/alternative; boundary=047d7b5d3b821b0b3304db02cc02 --047d7b5d3b821b0b3304db02cc02 Content-Type: text/plain; charset=ISO-8859-1 I think Ian's proposal makes sense. There is no real need to have a pre-fix, I raised this because it seems to be convention with debian and many other projects. Personally I don't like xen-... xenproject-..., etc. Let's wait for a couple of days and see what else comes back and then I can make a concrete proposal for voting. I also need to check with timescales on the domain change. Lars On Tue, Apr 23, 2013 at 9:10 AM, Lars Kurth wrote: > > I also want to know why we can't create/use a forum: It'll be more > organized, easier to seach, > > more categorized and more user frendly for new comers > I don't think that our developers will want a forum. > However for user questions, we created > http://xenproject.org/help/questions-and-answers.html which are inessence > a forum. You just need to start using it. > > > On Mon, Apr 22, 2013 at 6:10 PM, samir benkhellat < > benkhellat_samir@hotmail.com> wrote: > >> I also want to know why we can't create/use a forum: It'll be more >> organized, easier to seach, more categorized and more user frendly for new >> comers >> >> So what do you think? >> >> Regards >> >> ------------------------------ >> Date: Mon, 22 Apr 2013 17:42:26 +0100 >> From: lars.kurth@xen.org >> To: chip.childers@sungard.com >> CC: xen-arm@lists.xen.org; xen-devel@lists.xen.org; xen-api@lists.xen.org >> Subject: Re: [Xen-API] [Proposal] Additional mailing lists for specific >> purposes >> >> >> Hi, >> >> seems nobody has any views. How about I make a more concrete proposal. I >> also noticed that we have no real global list for voting and proposals (and >> to discuss issues like this). I have to include all lists, which creates >> spam. As already indicated on the blog, at some point we should move to @ >> lists.xenproject.org, which will cause some impact on mailfilters, etc. >> (similar to when we moved from @lists.xensource.com to @lists.xen.orgabout a year ago). So that may be a good opportunity to deal with some >> inconsistencies that have grown over time. >> >> It also raises questions about naming conventions for new lists. Should >> lists be >> - xen-...@lists.xenproject.org, or should they be >> - xenproject-...@lists.xenproject.org >> And then of course, should any convention be forward looking or should we >> rename lists to be consistent and (as we are already changing @ >> lists.xenproject.org, changing the actual list name may not be any >> worse). >> >> On new lists, we will need lists for >> >> - xenproject-marketing@lists.xenproject.org ... maybe >> xenproject-publicity@lists.xenproject.org hits it better than >> marketing (seems to work for debian) >> - I need something for votes and discussions that cut accross >> sub-project and teams. Maybe xenproject-proposals@lists.xenproject.orgor >> xenproject-decisionmaking@lists.xenproject.org? Just putting these >> into the room: none of these sound right to me. Maybe >> xenproject-leadership@lists.xenproject.org is better? >> - We will have a list for the advisory board, which wants to be >> totally open and transparent. So this would be >> xenproject-advisoryboard@lists.xenproject.org and I will post >> minutes, etc. of the last meeting when we created the list. >> - xenproject-private, if we actually need it would work too. However >> the advisory board recommended in the meeting last week not to have any >> private lists at all. So maybe we don't need this. >> >> Also, for example XAPI does not have a separate dev or user list. That is >> also one to consider at some point. >> >> Anyway, I am just putting these into the room for discussion. >> >> Lars >> >> On 19/04/2013 04:52, Chip Childers wrote: >> >> On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote: >> >> 1) A list for coordinating blog posts, other communication, >> attending of event, etc. - not sure about the name, so am looking >> for suggestions. I am not sure whether we should have public >> archives: comparable lists of other projects don't. >> >> From an outsider / lurker perspective, xen-marketing@lists.xen.org is a >> good fit. >> >> >> 2) A semi-private invite mailing list for ALL project leads, >> committers and maintainers of ALL projects hosted on xen.org >> >> Similarly to above: xen-private@lists.xen.org >> >> Both of these list names are used in other projects I'm working with / >> observe. >> >> >> >> >> _______________________________________________ Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> > > --047d7b5d3b821b0b3304db02cc02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I think Ian's proposal makes sense. There is no real n= eed to have a pre-fix, I raised this because it seems to be convention with= debian and many other projects. Personally I don't like xen-... xenpro= ject-..., etc. Let's wait for a couple of days and see what else comes = back and then I can make a concrete proposal for voting. I also need to che= ck with timescales on the domain change.
Lars


On Tue, Apr 23, 2013 at 9:10 AM, Lars Kurth <lars.kurth.xen@gmai= l.com> wrote:
>=A0I also want to kn= ow why we can't create/use a forum: It'll=A0 be more organized, eas= ier to seach,=A0
> more categ= orized and more user frendly for new comers
I do= n't think that our developers will want a forum.
However for user que= stions, we created=A0http://xenproject.org/help/questions-a= nd-answers.html=A0which are inessence a forum. You just need to start u= sing it.

On Mon, Apr 22, 2013 at 6:10 PM, samir ben= khellat <benkhellat_samir@hotmail.com> wrote:
I also want to know why we can't create/use a for= um: It'll=A0 be more organized, easier to seach, more categorized and m= ore user frendly for new comers

So what do you think?

Regards=

Date: Mon, 22 Apr 2013 17:42:26 +0100
From: lars.kurth@xen.org<= br>To: chip.= childers@sungard.com
CC: xen-arm@list= s.xen.org; xen-devel@lists.xen.org; xen-api@lists.xen.org
Subject: Re: [Xen-API] [Proposal] Additional mailing lists for specific pur= poses


=20 =20 =20 =20
Hi,

seems nobody has any views. How about I make a more concrete proposal. I also noticed that we have no real global list for voting and proposals (and to discuss issues like this). I have to include all lists, which creates spam. As already indicated on the blog, at some point we should move to @lists.xenproject.org, which will cause some impact on mailfilters, etc. (similar to when we moved from @= lists.xensource.com to @lists.xen.org about a year ago). So that may be a good opportunity to deal with some inconsistencies that have grown over time.

It also raises questions about naming conventions for new lists. Should lists be
- x= en-...@lists.xenproject.org, or should they be
- xenproject-...@lists.xenproject.org
And then of course, should any convention be forward looking or should we rename lists to be consistent and (as we are already changing @l= ists.xenproject.org, changing the actual list name may not be any worse).

On new lists, we will need lists for
Also, for example XAPI does not have a separate dev or user list. That is also one to consider at some point.

Anyway, I am just putting these into the room for discussion.

Lars

On 19/04/2013 04:52, Chip Childers wrote:
On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote:

1) A list for coordinating blog posts, other communication,
attending of event, etc. - not sure about the name, so am looking
for suggestions. I am not sure whether we should have public
archives: comparable lists of other projects don't.

From an outsider / lurker perspective, xen-marketing@lists.xen.org is =
a
good fit.


2) A semi-private invite mailing list for ALL project leads,
committers and maintainers of ALL projects hosted on xen.org

Similarly to above: xen-private@lists.xen.org

Both of these list names are used in other projects I'm working with /
observe.

=20
_______________________________________________ Xen-api mailing list Xen-api@lists.xe= n.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
=


--047d7b5d3b821b0b3304db02cc02-- --===============6989984071923597354== 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 --===============6989984071923597354==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:17 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCn-0006cL-2n; Fri, 03 May 2013 12:35:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UUYOn-0003Mb-UY; Tue, 23 Apr 2013 08:16:26 +0000 Received: from [193.109.254.147:4112] by server-3.bemta-14.messagelabs.com id E9/82-17488-85346715; Tue, 23 Apr 2013 08:16:24 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1366704968!9062695!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2187 invoked from network); 23 Apr 2013 08:16:10 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2013 08:16:10 -0000 Received: by mail-ob0-f171.google.com with SMTP id er7so284953obc.16 for ; Tue, 23 Apr 2013 01:16:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ox4mZi2LDeKYnDxL4rKBRoo4/6O+Lc4KWeMCzDIqrbo=; b=W0xfDkIq5qdJnFe6h6VbBVWTRSmYbBPLasigvSRTE1Bwa+pWmdUCVKdxJo7jvaWYng DHZsgRcz/TdySMi4HkpYZ57P6428/B9HQOVRbRI9mc1eXQh42/Da/oYgpflPQpSYp8ok bXGFwtGUI01wV9yfCCD9MyDcB4uMYHKN88D6hoSaaqHvUCk/+hNM/zML8MKYRy6nQjDg VNnF/IvQxpeWR6sX/+Br2FilJFmAock2VRjWjik4DG2l+RWvOF6tMWlgTAKeM+Q8ToWi l6O1Ehu0Br7zkV1pdEpYLwXufb54vBwiTU0ioEb4oANr7XwrG+KTUgUgHFqM8UmnBQ4e 9xIQ== MIME-Version: 1.0 X-Received: by 10.60.146.227 with SMTP id tf3mr3875159oeb.50.1366704967582; Tue, 23 Apr 2013 01:16:07 -0700 (PDT) Received: by 10.60.3.232 with HTTP; Tue, 23 Apr 2013 01:16:07 -0700 (PDT) In-Reply-To: References: <516AECC9.1010603@xen.org> <20130419035218.GY88962@USLT-205755.sungardas.corp> <51756872.7040402@xen.org> Date: Tue, 23 Apr 2013 09:16:07 +0100 Message-ID: From: Lars Kurth To: samir benkhellat X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Cc: "xen-arm@lists.xen.org" , Chip Childers , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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="===============6989984071923597354==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============6989984071923597354== Content-Type: multipart/alternative; boundary=047d7b5d3b821b0b3304db02cc02 --047d7b5d3b821b0b3304db02cc02 Content-Type: text/plain; charset=ISO-8859-1 I think Ian's proposal makes sense. There is no real need to have a pre-fix, I raised this because it seems to be convention with debian and many other projects. Personally I don't like xen-... xenproject-..., etc. Let's wait for a couple of days and see what else comes back and then I can make a concrete proposal for voting. I also need to check with timescales on the domain change. Lars On Tue, Apr 23, 2013 at 9:10 AM, Lars Kurth wrote: > > I also want to know why we can't create/use a forum: It'll be more > organized, easier to seach, > > more categorized and more user frendly for new comers > I don't think that our developers will want a forum. > However for user questions, we created > http://xenproject.org/help/questions-and-answers.html which are inessence > a forum. You just need to start using it. > > > On Mon, Apr 22, 2013 at 6:10 PM, samir benkhellat < > benkhellat_samir@hotmail.com> wrote: > >> I also want to know why we can't create/use a forum: It'll be more >> organized, easier to seach, more categorized and more user frendly for new >> comers >> >> So what do you think? >> >> Regards >> >> ------------------------------ >> Date: Mon, 22 Apr 2013 17:42:26 +0100 >> From: lars.kurth@xen.org >> To: chip.childers@sungard.com >> CC: xen-arm@lists.xen.org; xen-devel@lists.xen.org; xen-api@lists.xen.org >> Subject: Re: [Xen-API] [Proposal] Additional mailing lists for specific >> purposes >> >> >> Hi, >> >> seems nobody has any views. How about I make a more concrete proposal. I >> also noticed that we have no real global list for voting and proposals (and >> to discuss issues like this). I have to include all lists, which creates >> spam. As already indicated on the blog, at some point we should move to @ >> lists.xenproject.org, which will cause some impact on mailfilters, etc. >> (similar to when we moved from @lists.xensource.com to @lists.xen.orgabout a year ago). So that may be a good opportunity to deal with some >> inconsistencies that have grown over time. >> >> It also raises questions about naming conventions for new lists. Should >> lists be >> - xen-...@lists.xenproject.org, or should they be >> - xenproject-...@lists.xenproject.org >> And then of course, should any convention be forward looking or should we >> rename lists to be consistent and (as we are already changing @ >> lists.xenproject.org, changing the actual list name may not be any >> worse). >> >> On new lists, we will need lists for >> >> - xenproject-marketing@lists.xenproject.org ... maybe >> xenproject-publicity@lists.xenproject.org hits it better than >> marketing (seems to work for debian) >> - I need something for votes and discussions that cut accross >> sub-project and teams. Maybe xenproject-proposals@lists.xenproject.orgor >> xenproject-decisionmaking@lists.xenproject.org? Just putting these >> into the room: none of these sound right to me. Maybe >> xenproject-leadership@lists.xenproject.org is better? >> - We will have a list for the advisory board, which wants to be >> totally open and transparent. So this would be >> xenproject-advisoryboard@lists.xenproject.org and I will post >> minutes, etc. of the last meeting when we created the list. >> - xenproject-private, if we actually need it would work too. However >> the advisory board recommended in the meeting last week not to have any >> private lists at all. So maybe we don't need this. >> >> Also, for example XAPI does not have a separate dev or user list. That is >> also one to consider at some point. >> >> Anyway, I am just putting these into the room for discussion. >> >> Lars >> >> On 19/04/2013 04:52, Chip Childers wrote: >> >> On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote: >> >> 1) A list for coordinating blog posts, other communication, >> attending of event, etc. - not sure about the name, so am looking >> for suggestions. I am not sure whether we should have public >> archives: comparable lists of other projects don't. >> >> From an outsider / lurker perspective, xen-marketing@lists.xen.org is a >> good fit. >> >> >> 2) A semi-private invite mailing list for ALL project leads, >> committers and maintainers of ALL projects hosted on xen.org >> >> Similarly to above: xen-private@lists.xen.org >> >> Both of these list names are used in other projects I'm working with / >> observe. >> >> >> >> >> _______________________________________________ Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> > > --047d7b5d3b821b0b3304db02cc02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I think Ian's proposal makes sense. There is no real n= eed to have a pre-fix, I raised this because it seems to be convention with= debian and many other projects. Personally I don't like xen-... xenpro= ject-..., etc. Let's wait for a couple of days and see what else comes = back and then I can make a concrete proposal for voting. I also need to che= ck with timescales on the domain change.
Lars


On Tue, Apr 23, 2013 at 9:10 AM, Lars Kurth <lars.kurth.xen@gmai= l.com> wrote:
>=A0I also want to kn= ow why we can't create/use a forum: It'll=A0 be more organized, eas= ier to seach,=A0
> more categ= orized and more user frendly for new comers
I do= n't think that our developers will want a forum.
However for user que= stions, we created=A0http://xenproject.org/help/questions-a= nd-answers.html=A0which are inessence a forum. You just need to start u= sing it.

On Mon, Apr 22, 2013 at 6:10 PM, samir ben= khellat <benkhellat_samir@hotmail.com> wrote:
I also want to know why we can't create/use a for= um: It'll=A0 be more organized, easier to seach, more categorized and m= ore user frendly for new comers

So what do you think?

Regards=

Date: Mon, 22 Apr 2013 17:42:26 +0100
From: lars.kurth@xen.org<= br>To: chip.= childers@sungard.com
CC: xen-arm@list= s.xen.org; xen-devel@lists.xen.org; xen-api@lists.xen.org
Subject: Re: [Xen-API] [Proposal] Additional mailing lists for specific pur= poses


=20 =20 =20 =20
Hi,

seems nobody has any views. How about I make a more concrete proposal. I also noticed that we have no real global list for voting and proposals (and to discuss issues like this). I have to include all lists, which creates spam. As already indicated on the blog, at some point we should move to @lists.xenproject.org, which will cause some impact on mailfilters, etc. (similar to when we moved from @= lists.xensource.com to @lists.xen.org about a year ago). So that may be a good opportunity to deal with some inconsistencies that have grown over time.

It also raises questions about naming conventions for new lists. Should lists be
- x= en-...@lists.xenproject.org, or should they be
- xenproject-...@lists.xenproject.org
And then of course, should any convention be forward looking or should we rename lists to be consistent and (as we are already changing @l= ists.xenproject.org, changing the actual list name may not be any worse).

On new lists, we will need lists for
Also, for example XAPI does not have a separate dev or user list. That is also one to consider at some point.

Anyway, I am just putting these into the room for discussion.

Lars

On 19/04/2013 04:52, Chip Childers wrote:
On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote:

1) A list for coordinating blog posts, other communication,
attending of event, etc. - not sure about the name, so am looking
for suggestions. I am not sure whether we should have public
archives: comparable lists of other projects don't.

From an outsider / lurker perspective, xen-marketing@lists.xen.org is =
a
good fit.


2) A semi-private invite mailing list for ALL project leads,
committers and maintainers of ALL projects hosted on xen.org

Similarly to above: xen-private@lists.xen.org

Both of these list names are used in other projects I'm working with /
observe.

=20
_______________________________________________ Xen-api mailing list Xen-api@lists.xe= n.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
=


--047d7b5d3b821b0b3304db02cc02-- --===============6989984071923597354== 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 --===============6989984071923597354==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCo-0006fU-DR; Fri, 03 May 2013 12:35:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UVdHn-0003fj-0O; Fri, 26 Apr 2013 07:41:39 +0000 Received: from [85.158.137.99:63254] by server-16.bemta-3.messagelabs.com id 35/22-20692-CAF2A715; Fri, 26 Apr 2013 07:41:32 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-217.messagelabs.com!1366962089!16105446!1 X-Originating-IP: [209.85.219.41] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3753 invoked from network); 26 Apr 2013 07:41:31 -0000 Received: from mail-oa0-f41.google.com (HELO mail-oa0-f41.google.com) (209.85.219.41) by server-11.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2013 07:41:31 -0000 Received: by mail-oa0-f41.google.com with SMTP id g12so3745981oah.0 for ; Fri, 26 Apr 2013 00:41:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=UoGDz+zUDXoKpnpCczkG4/jWJjCMg2jB9honLBH6ol8=; b=O039APqrRx+MhClT+QV9iHFSGkEt3uN6CgF9QJEAaMDHGCuOZxAld3HiuU14o6T3ss a0iKH7PCOtaHwYllGL1+3Gu9i9RqF8LHcmdXapN8vHa6R+taD9zpqJGsM29LSIv9r7L6 q3Dcrp5cjkYeSapu8qqQO5az/IOjvJXe118OTB+PWD5mwOWk2c2qFLAbqJveWyvMOetL 7ZO33AcgREqNz7dghgLoDNnb2LAe4+BwXXAiWM+NM/EbRLK4pEaTV1zVUSshF9aFGhgR PhjBu4RjeU6gxFLnhirdxLxeFa0nlRFMgH5UK1izxFaS1isvuxl9U33TL/WCJBS1igWM wZkQ== MIME-Version: 1.0 X-Received: by 10.60.146.227 with SMTP id tf3mr9715759oeb.50.1366962089264; Fri, 26 Apr 2013 00:41:29 -0700 (PDT) Received: by 10.60.3.232 with HTTP; Fri, 26 Apr 2013 00:41:29 -0700 (PDT) Date: Fri, 26 Apr 2013 08:41:29 +0100 Message-ID: From: Lars Kurth To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] Xen Document Day is on Monday, April 29th on IRC freenode #xendocs 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="===============8927310673817281790==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8927310673817281790== Content-Type: multipart/alternative; boundary=047d7b5d3b82c089c404db3ea9e9 --047d7b5d3b82c089c404db3ea9e9 Content-Type: text/plain; charset=ISO-8859-1 Hi all, we have another *document* *day* coming up soon! More information about docs *day* at http://wiki.xen.org/wiki/Xen_Document_Days The TODO list is at http://wiki.xen.org/wiki/Xen_Document_Days/TODO It would be great if we could focus on getting the material for the Xen Test Day that start in 2 weeks together. Regards Lars --047d7b5d3b82c089c404db3ea9e9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,
we = have another document day coming up soon! More informat= ion about docs day at http://wiki.xen.org/wiki/Xen_Document_Days
It would be great if we could focus on getting the material for the Xen Te= st Day that start in 2 weeks together.

Regards Lars
--047d7b5d3b82c089c404db3ea9e9-- --===============8927310673817281790== 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 --===============8927310673817281790==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:35:18 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:35:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFCo-0006fU-DR; Fri, 03 May 2013 12:35:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UVdHn-0003fj-0O; Fri, 26 Apr 2013 07:41:39 +0000 Received: from [85.158.137.99:63254] by server-16.bemta-3.messagelabs.com id 35/22-20692-CAF2A715; Fri, 26 Apr 2013 07:41:32 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-217.messagelabs.com!1366962089!16105446!1 X-Originating-IP: [209.85.219.41] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3753 invoked from network); 26 Apr 2013 07:41:31 -0000 Received: from mail-oa0-f41.google.com (HELO mail-oa0-f41.google.com) (209.85.219.41) by server-11.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 26 Apr 2013 07:41:31 -0000 Received: by mail-oa0-f41.google.com with SMTP id g12so3745981oah.0 for ; Fri, 26 Apr 2013 00:41:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=UoGDz+zUDXoKpnpCczkG4/jWJjCMg2jB9honLBH6ol8=; b=O039APqrRx+MhClT+QV9iHFSGkEt3uN6CgF9QJEAaMDHGCuOZxAld3HiuU14o6T3ss a0iKH7PCOtaHwYllGL1+3Gu9i9RqF8LHcmdXapN8vHa6R+taD9zpqJGsM29LSIv9r7L6 q3Dcrp5cjkYeSapu8qqQO5az/IOjvJXe118OTB+PWD5mwOWk2c2qFLAbqJveWyvMOetL 7ZO33AcgREqNz7dghgLoDNnb2LAe4+BwXXAiWM+NM/EbRLK4pEaTV1zVUSshF9aFGhgR PhjBu4RjeU6gxFLnhirdxLxeFa0nlRFMgH5UK1izxFaS1isvuxl9U33TL/WCJBS1igWM wZkQ== MIME-Version: 1.0 X-Received: by 10.60.146.227 with SMTP id tf3mr9715759oeb.50.1366962089264; Fri, 26 Apr 2013 00:41:29 -0700 (PDT) Received: by 10.60.3.232 with HTTP; Fri, 26 Apr 2013 00:41:29 -0700 (PDT) Date: Fri, 26 Apr 2013 08:41:29 +0100 Message-ID: From: Lars Kurth To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" X-Mailman-Approved-At: Fri, 03 May 2013 12:34:59 +0000 Subject: [XenARM] Xen Document Day is on Monday, April 29th on IRC freenode #xendocs 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="===============8927310673817281790==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8927310673817281790== Content-Type: multipart/alternative; boundary=047d7b5d3b82c089c404db3ea9e9 --047d7b5d3b82c089c404db3ea9e9 Content-Type: text/plain; charset=ISO-8859-1 Hi all, we have another *document* *day* coming up soon! More information about docs *day* at http://wiki.xen.org/wiki/Xen_Document_Days The TODO list is at http://wiki.xen.org/wiki/Xen_Document_Days/TODO It would be great if we could focus on getting the material for the Xen Test Day that start in 2 weeks together. Regards Lars --047d7b5d3b82c089c404db3ea9e9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,
we = have another document day coming up soon! More informat= ion about docs day at http://wiki.xen.org/wiki/Xen_Document_Days
It would be great if we could focus on getting the material for the Xen Te= st Day that start in 2 weeks together.

Regards Lars
--047d7b5d3b82c089c404db3ea9e9-- --===============8927310673817281790== 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 --===============8927310673817281790==-- From xen-arm-bounces@lists.xen.org Fri May 03 12:38:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:38: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 1UYFFW-00088C-Sq; Fri, 03 May 2013 12:38:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFFV-000886-I6 for xen-arm@lists.xen.org; Fri, 03 May 2013 12:38:05 +0000 Received: from [193.109.254.147:50777] by server-15.bemta-14.messagelabs.com id A0/01-14305-CAFA3815; Fri, 03 May 2013 12:38:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1367584680!1848931!1 X-Originating-IP: [74.125.82.179] 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 2780 invoked from network); 3 May 2013 12:38:00 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 May 2013 12:38:00 -0000 Received: by mail-we0-f179.google.com with SMTP id t9so1281021wey.24 for ; Fri, 03 May 2013 05:38:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=1AXF+WLCVXLtyfXNKZtQ5YOmJ0hDRHlXXTFEFu+uMUw=; b=uRJoyHs2IgNFqESqYs6IMiNhI0gW1KOhEQQ9FT/P1sZx5oA1W61QnqDMcAK47LYDxj 4VF1v9UsEoRfhK91kkZD+PuYRpM/BpHxTXrtDDGTGS3cDu+l08j7kkKBV9ByieDgEK9s sevusM2AakedvjOxLZlKFiMEbwxNwV3G3tgo6JQAqbrH0IGOsGjymGMDipVvS8HI1VuV +QZ+QcGp6Ekt+gbYL3O72Li+TKjqD2TPaFQ+/RlSBqiCJi1oF5q3BU/MwnX/rsP96swd 4jw35qHJfnvN+dsCAJeKyWj+1H1UgsMs3jx2sQUyb9jhjM51IHwzSB6gfh6IOwh3IfLS jQaA== X-Received: by 10.180.181.104 with SMTP id dv8mr10345496wic.0.1367584680261; Fri, 03 May 2013 05:38:00 -0700 (PDT) Received: from [172.16.26.11] ([90.199.171.123]) by mx.google.com with ESMTPSA id nf9sm44072516wic.3.2013.05.03.05.37.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 05:37:59 -0700 (PDT) Message-ID: <5183AFA4.6060208@xen.org> Date: Fri, 03 May 2013 13:37:56 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: "xen-arm@lists.xen.org" Subject: [XenARM] List moderation for xen-arm 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 everybody, I just noticed that the xen-arm list had not been moderated for some time. Apologies: I will pick this up until another volunteer steps up. Regards 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 May 03 12:38:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 03 May 2013 12:38: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 1UYFFW-00088C-Sq; Fri, 03 May 2013 12:38:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UYFFV-000886-I6 for xen-arm@lists.xen.org; Fri, 03 May 2013 12:38:05 +0000 Received: from [193.109.254.147:50777] by server-15.bemta-14.messagelabs.com id A0/01-14305-CAFA3815; Fri, 03 May 2013 12:38:04 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1367584680!1848931!1 X-Originating-IP: [74.125.82.179] 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 2780 invoked from network); 3 May 2013 12:38:00 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 May 2013 12:38:00 -0000 Received: by mail-we0-f179.google.com with SMTP id t9so1281021wey.24 for ; Fri, 03 May 2013 05:38:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=1AXF+WLCVXLtyfXNKZtQ5YOmJ0hDRHlXXTFEFu+uMUw=; b=uRJoyHs2IgNFqESqYs6IMiNhI0gW1KOhEQQ9FT/P1sZx5oA1W61QnqDMcAK47LYDxj 4VF1v9UsEoRfhK91kkZD+PuYRpM/BpHxTXrtDDGTGS3cDu+l08j7kkKBV9ByieDgEK9s sevusM2AakedvjOxLZlKFiMEbwxNwV3G3tgo6JQAqbrH0IGOsGjymGMDipVvS8HI1VuV +QZ+QcGp6Ekt+gbYL3O72Li+TKjqD2TPaFQ+/RlSBqiCJi1oF5q3BU/MwnX/rsP96swd 4jw35qHJfnvN+dsCAJeKyWj+1H1UgsMs3jx2sQUyb9jhjM51IHwzSB6gfh6IOwh3IfLS jQaA== X-Received: by 10.180.181.104 with SMTP id dv8mr10345496wic.0.1367584680261; Fri, 03 May 2013 05:38:00 -0700 (PDT) Received: from [172.16.26.11] ([90.199.171.123]) by mx.google.com with ESMTPSA id nf9sm44072516wic.3.2013.05.03.05.37.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 05:37:59 -0700 (PDT) Message-ID: <5183AFA4.6060208@xen.org> Date: Fri, 03 May 2013 13:37:56 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: "xen-arm@lists.xen.org" Subject: [XenARM] List moderation for xen-arm 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 everybody, I just noticed that the xen-arm list had not been moderated for some time. Apologies: I will pick this up until another volunteer steps up. Regards 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 Mon May 06 03:21:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 06 May 2013 03:21: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 1UZBze-00071O-OG; Mon, 06 May 2013 03:21:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZBzd-00071J-Pq for xen-arm@lists.xen.org; Mon, 06 May 2013 03:21:37 +0000 Received: from [85.158.143.99:8607] by server-1.bemta-4.messagelabs.com id DE/8E-06122-1C127815; Mon, 06 May 2013 03:21:37 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1367810494!24018456!1 X-Originating-IP: [209.85.210.48] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28536 invoked from network); 6 May 2013 03:21:36 -0000 Received: from mail-da0-f48.google.com (HELO mail-da0-f48.google.com) (209.85.210.48) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 May 2013 03:21:36 -0000 Received: by mail-da0-f48.google.com with SMTP id h32so1616112dak.35 for ; Sun, 05 May 2013 20:21:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=eC5rqijiRpGQq888T8Nayd2xT/l6VXd7Xt9/VRnPgo0=; b=clkFc48KWHTBsS+QiOFusVKEdNZWSEHuim4JQZVHZhjFwpPDV+sZO5NrjgSaZ21RbJ nKZNOus1buRrddHKkqkYJnsc7xQZeI5BbJruJNVyYQ1fY1FArb7edp1ujvV2BHfC6U0r FLCg0mjbdMVvK4AHRO+5E1W4xphHkYtazl391WRpeK6FmwbsQQfQlH/Wo7c/xo6JCBNx cErtlDmVWpylXs/WZJBDrz3wnSNnzwbIR9CF61OzRPIYKJO9hwc6fg2rWgjUTuVsMDzo d3vVGLn3hjkEj9VO+rySDjgfaF39psaqJ8YCteV0d2hpRv4yv99ZZQOtJWvKV0Ko4h+l +TJg== X-Received: by 10.66.13.194 with SMTP id j2mr24315058pac.205.1367810493848; Sun, 05 May 2013 20:21:33 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id ag4sm21942069pbc.20.2013.05.05.20.21.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 05 May 2013 20:21:33 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: Date: Mon, 6 May 2013 11:21:29 +0800 Message-Id: References: <20130324070650.GA9800@cbz-workstation> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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 Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > On Sun, 24 Mar 2013, Chen Baozi wrote: >> Hi all, >> >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to >> ARM (Ian's GSoC idea this year). >> >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to >> the guest through ESI register. And Mini-OS would use this structure as the >> argument of start_kernel. However, I didn't see codes handle the >> start_info_t on ARM side. Instead, I see a more standard protocal when >> booting ARM's dom0, which follows linux kernel bootstrap rules: >> >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer >> >> Does it mean that Xen for ARM does not use the start_info_t to pass >> information when booting PV guest? >> Or did I miss something important? > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > not exactly like x86 PV guests. > The information present in the start_info page are either available via > device tree or no used on ARM. I'm thinking of parsing the dtb and fill the start_info structure according to it before jump to the start_kernel. In that case, it won't break some original mini-os interface. _______________________________________________ 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 May 06 03:21:43 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 06 May 2013 03:21: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 1UZBze-00071O-OG; Mon, 06 May 2013 03:21:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZBzd-00071J-Pq for xen-arm@lists.xen.org; Mon, 06 May 2013 03:21:37 +0000 Received: from [85.158.143.99:8607] by server-1.bemta-4.messagelabs.com id DE/8E-06122-1C127815; Mon, 06 May 2013 03:21:37 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1367810494!24018456!1 X-Originating-IP: [209.85.210.48] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28536 invoked from network); 6 May 2013 03:21:36 -0000 Received: from mail-da0-f48.google.com (HELO mail-da0-f48.google.com) (209.85.210.48) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 May 2013 03:21:36 -0000 Received: by mail-da0-f48.google.com with SMTP id h32so1616112dak.35 for ; Sun, 05 May 2013 20:21:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=eC5rqijiRpGQq888T8Nayd2xT/l6VXd7Xt9/VRnPgo0=; b=clkFc48KWHTBsS+QiOFusVKEdNZWSEHuim4JQZVHZhjFwpPDV+sZO5NrjgSaZ21RbJ nKZNOus1buRrddHKkqkYJnsc7xQZeI5BbJruJNVyYQ1fY1FArb7edp1ujvV2BHfC6U0r FLCg0mjbdMVvK4AHRO+5E1W4xphHkYtazl391WRpeK6FmwbsQQfQlH/Wo7c/xo6JCBNx cErtlDmVWpylXs/WZJBDrz3wnSNnzwbIR9CF61OzRPIYKJO9hwc6fg2rWgjUTuVsMDzo d3vVGLn3hjkEj9VO+rySDjgfaF39psaqJ8YCteV0d2hpRv4yv99ZZQOtJWvKV0Ko4h+l +TJg== X-Received: by 10.66.13.194 with SMTP id j2mr24315058pac.205.1367810493848; Sun, 05 May 2013 20:21:33 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id ag4sm21942069pbc.20.2013.05.05.20.21.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 05 May 2013 20:21:33 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: Date: Mon, 6 May 2013 11:21:29 +0800 Message-Id: References: <20130324070650.GA9800@cbz-workstation> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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 Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > On Sun, 24 Mar 2013, Chen Baozi wrote: >> Hi all, >> >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to >> ARM (Ian's GSoC idea this year). >> >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to >> the guest through ESI register. And Mini-OS would use this structure as the >> argument of start_kernel. However, I didn't see codes handle the >> start_info_t on ARM side. Instead, I see a more standard protocal when >> booting ARM's dom0, which follows linux kernel bootstrap rules: >> >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer >> >> Does it mean that Xen for ARM does not use the start_info_t to pass >> information when booting PV guest? >> Or did I miss something important? > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > not exactly like x86 PV guests. > The information present in the start_info page are either available via > device tree or no used on ARM. I'm thinking of parsing the dtb and fill the start_info structure according to it before jump to the start_kernel. In that case, it won't break some original mini-os interface. _______________________________________________ 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 May 06 10:41:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 06 May 2013 10:41: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 1UZIqp-0007KW-35; Mon, 06 May 2013 10:40:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZIqo-0007KB-97 for xen-arm@lists.xen.org; Mon, 06 May 2013 10:40:58 +0000 Received: from [85.158.137.99:24035] by server-12.bemta-3.messagelabs.com id B8/07-17342-9B887815; Mon, 06 May 2013 10:40:57 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1367836852!20642184!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29580 invoked from network); 6 May 2013 10:40:54 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 6 May 2013 10:40:54 -0000 X-IronPort-AV: E=Sophos;i="4.87,621,1363132800"; d="scan'208";a="23455579" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 06 May 2013 10:40:52 +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.3; Mon, 6 May 2013 06:40:51 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UZIqh-0003JS-K8; Mon, 06 May 2013 11:40:51 +0100 Date: Mon, 6 May 2013 11:40:49 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Chen Baozi In-Reply-To: Message-ID: References: <20130324070650.GA9800@cbz-workstation> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Cc: xen-arm , xen-devel@lists.xensource.com, Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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, 6 May 2013, Chen Baozi wrote: > On Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > > > On Sun, 24 Mar 2013, Chen Baozi wrote: > >> Hi all, > >> > >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to > >> ARM (Ian's GSoC idea this year). > >> > >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to > >> the guest through ESI register. And Mini-OS would use this structure as the > >> argument of start_kernel. However, I didn't see codes handle the > >> start_info_t on ARM side. Instead, I see a more standard protocal when > >> booting ARM's dom0, which follows linux kernel bootstrap rules: > >> > >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer > >> > >> Does it mean that Xen for ARM does not use the start_info_t to pass > >> information when booting PV guest? > >> Or did I miss something important? > > > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > > not exactly like x86 PV guests. > > The information present in the start_info page are either available via > > device tree or no used on ARM. > > I'm thinking of parsing the dtb and fill the start_info structure according to it before jump to the start_kernel. In that case, it won't break some original mini-os interface. You can try that, or you can refactor the code dividing it into x86 specific and common stuff. _______________________________________________ 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 May 06 10:41:02 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 06 May 2013 10:41: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 1UZIqp-0007KW-35; Mon, 06 May 2013 10:40:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZIqo-0007KB-97 for xen-arm@lists.xen.org; Mon, 06 May 2013 10:40:58 +0000 Received: from [85.158.137.99:24035] by server-12.bemta-3.messagelabs.com id B8/07-17342-9B887815; Mon, 06 May 2013 10:40:57 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1367836852!20642184!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29580 invoked from network); 6 May 2013 10:40:54 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 6 May 2013 10:40:54 -0000 X-IronPort-AV: E=Sophos;i="4.87,621,1363132800"; d="scan'208";a="23455579" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 06 May 2013 10:40:52 +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.3; Mon, 6 May 2013 06:40:51 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UZIqh-0003JS-K8; Mon, 06 May 2013 11:40:51 +0100 Date: Mon, 6 May 2013 11:40:49 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Chen Baozi In-Reply-To: Message-ID: References: <20130324070650.GA9800@cbz-workstation> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Cc: xen-arm , xen-devel@lists.xensource.com, Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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, 6 May 2013, Chen Baozi wrote: > On Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > > > On Sun, 24 Mar 2013, Chen Baozi wrote: > >> Hi all, > >> > >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to > >> ARM (Ian's GSoC idea this year). > >> > >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to > >> the guest through ESI register. And Mini-OS would use this structure as the > >> argument of start_kernel. However, I didn't see codes handle the > >> start_info_t on ARM side. Instead, I see a more standard protocal when > >> booting ARM's dom0, which follows linux kernel bootstrap rules: > >> > >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer > >> > >> Does it mean that Xen for ARM does not use the start_info_t to pass > >> information when booting PV guest? > >> Or did I miss something important? > > > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > > not exactly like x86 PV guests. > > The information present in the start_info page are either available via > > device tree or no used on ARM. > > I'm thinking of parsing the dtb and fill the start_info structure according to it before jump to the start_kernel. In that case, it won't break some original mini-os interface. You can try that, or you can refactor the code dividing it into x86 specific and common stuff. _______________________________________________ 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 May 07 08:43:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 08:43:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZdUC-0001mp-SH; Tue, 07 May 2013 08:43:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZdUB-0001mS-2m for xen-arm@lists.xen.org; Tue, 07 May 2013 08:42:59 +0000 Received: from [193.109.254.147:35445] by server-12.bemta-14.messagelabs.com id 12/4E-15557-29EB8815; Tue, 07 May 2013 08:42:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1367915981!3401288!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30518 invoked from network); 7 May 2013 08:39:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 08:39:42 -0000 X-IronPort-AV: E=Sophos;i="4.87,552,1363132800"; d="scan'208";a="4288074" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 May 2013 08:35:08 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Tue, 7 May 2013 09:39:41 +0100 Message-ID: <1367915980.26321.15.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Stefano Stabellini Date: Tue, 7 May 2013 09:39:40 +0100 In-Reply-To: References: <20130324070650.GA9800@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-arm , "xen-devel@lists.xensource.com" , Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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-05-06 at 11:40 +0100, Stefano Stabellini wrote: > On Mon, 6 May 2013, Chen Baozi wrote: > > On Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > > > > > On Sun, 24 Mar 2013, Chen Baozi wrote: > > >> Hi all, > > >> > > >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to > > >> ARM (Ian's GSoC idea this year). > > >> > > >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to > > >> the guest through ESI register. And Mini-OS would use this structure as the > > >> argument of start_kernel. However, I didn't see codes handle the > > >> start_info_t on ARM side. Instead, I see a more standard protocal when > > >> booting ARM's dom0, which follows linux kernel bootstrap rules: > > >> > > >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer > > >> > > >> Does it mean that Xen for ARM does not use the start_info_t to pass > > >> information when booting PV guest? > > >> Or did I miss something important? > > > > > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > > > not exactly like x86 PV guests. > > > The information present in the start_info page are either available via > > > device tree or no used on ARM. > > > > I'm thinking of parsing the dtb and fill the start_info structure > according to it before jump to the start_kernel. In that case, it > won't break some original mini-os interface. If you go this path then trying to do it in arch_init would be preferable. Nothing in start_kernel before arch_init seems like it should need start info. This is effectively what we do for Linux guests too -- populate a stunt start info early on. > You can try that, or you can refactor the code dividing it into x86 > specific and common stuff. There is bound to be a bunch of this sort of refactoring required, just because mini-os in practice has only really supported x86 until now and even with the best intentions arch specific stuff tends to leak out unless you are actively using something on multiple arches. 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 Tue May 07 08:43:03 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 08:43:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZdUC-0001mp-SH; Tue, 07 May 2013 08:43:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZdUB-0001mS-2m for xen-arm@lists.xen.org; Tue, 07 May 2013 08:42:59 +0000 Received: from [193.109.254.147:35445] by server-12.bemta-14.messagelabs.com id 12/4E-15557-29EB8815; Tue, 07 May 2013 08:42:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1367915981!3401288!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30518 invoked from network); 7 May 2013 08:39:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 08:39:42 -0000 X-IronPort-AV: E=Sophos;i="4.87,552,1363132800"; d="scan'208";a="4288074" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 May 2013 08:35:08 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Tue, 7 May 2013 09:39:41 +0100 Message-ID: <1367915980.26321.15.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Stefano Stabellini Date: Tue, 7 May 2013 09:39:40 +0100 In-Reply-To: References: <20130324070650.GA9800@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-arm , "xen-devel@lists.xensource.com" , Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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-05-06 at 11:40 +0100, Stefano Stabellini wrote: > On Mon, 6 May 2013, Chen Baozi wrote: > > On Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > > > > > On Sun, 24 Mar 2013, Chen Baozi wrote: > > >> Hi all, > > >> > > >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to > > >> ARM (Ian's GSoC idea this year). > > >> > > >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to > > >> the guest through ESI register. And Mini-OS would use this structure as the > > >> argument of start_kernel. However, I didn't see codes handle the > > >> start_info_t on ARM side. Instead, I see a more standard protocal when > > >> booting ARM's dom0, which follows linux kernel bootstrap rules: > > >> > > >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer > > >> > > >> Does it mean that Xen for ARM does not use the start_info_t to pass > > >> information when booting PV guest? > > >> Or did I miss something important? > > > > > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > > > not exactly like x86 PV guests. > > > The information present in the start_info page are either available via > > > device tree or no used on ARM. > > > > I'm thinking of parsing the dtb and fill the start_info structure > according to it before jump to the start_kernel. In that case, it > won't break some original mini-os interface. If you go this path then trying to do it in arch_init would be preferable. Nothing in start_kernel before arch_init seems like it should need start info. This is effectively what we do for Linux guests too -- populate a stunt start info early on. > You can try that, or you can refactor the code dividing it into x86 > specific and common stuff. There is bound to be a bunch of this sort of refactoring required, just because mini-os in practice has only really supported x86 until now and even with the best intentions arch specific stuff tends to leak out unless you are actively using something on multiple arches. 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 Tue May 07 11:56:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 11:56: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 1UZgVT-0000qv-N5; Tue, 07 May 2013 11:56:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZgVS-0000qY-DD for Xen-arm@lists.xen.org; Tue, 07 May 2013 11:56:30 +0000 Received: from [193.109.254.147:8318] by server-9.bemta-14.messagelabs.com id DB/AA-15694-DEBE8815; Tue, 07 May 2013 11:56:29 +0000 X-Env-Sender: wasabee18@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1367927619!9158710!1 X-Originating-IP: [209.85.217.179] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25569 invoked from network); 7 May 2013 11:53:40 -0000 Received: from mail-lb0-f179.google.com (HELO mail-lb0-f179.google.com) (209.85.217.179) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 11:53:40 -0000 Received: by mail-lb0-f179.google.com with SMTP id d10so609473lbj.38 for ; Tue, 07 May 2013 04:53:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=GJxSPyAcqqM6oUJSch0/fC+SBNJ/o7imye7mZTQkO6I=; b=TzXS7ESWJqVM8rLciVq3Q5U2Ad8AQUPJnxvVityNRSvyCazVfTLcY2ZDy8FBXhSbSc /LeKVdUPfu9ZJWY2Cn++KfdHvRew1aUFLe+30QRQKaZ/ogeC3xXrnuHOa2q1EkuPh1vP lvqAIpm4j322AGUX6PDiKFTX8jfN90e0mfcLOK7TiMDnMlS7z6ZfgHfDkBwzGtqA6uXq Mj2HqUVSVr61ZzwqtIWPXAqq1Qo0s9kvPZ9DfJsb2hocY5XKT02A69o0+MLq7XuLmPru BoWX7Xwi04L3zeA9mnwuzetLXAtZ8tXlSB/cBHxW5cCx8FcTkgeCHJwviEddttBBUX6H 2GbQ== MIME-Version: 1.0 X-Received: by 10.152.88.115 with SMTP id bf19mr778476lab.56.1367927619125; Tue, 07 May 2013 04:53:39 -0700 (PDT) Received: by 10.114.182.202 with HTTP; Tue, 7 May 2013 04:53:39 -0700 (PDT) Date: Tue, 7 May 2013 12:53:39 +0100 Message-ID: From: wasa bee To: Xen-arm@lists.xen.org Subject: [XenARM] GPU sharing with 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="===============5866546838817074644==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============5866546838817074644== Content-Type: multipart/alternative; boundary=001a11c36702d108a504dc1f7772 --001a11c36702d108a504dc1f7772 Content-Type: text/plain; charset=ISO-8859-1 Hi is it possible to share the GPU between VMs with Xen? I am interested in mobile devices (e.g. android) both ARM/x86. Is there something already available? Under way? If not, what is the best way to go? I have come across this: http://lists.xen.org/archives/html/xen-devel/2012-02/msg01064.html Is it still relevant? is this the right list to send my inquiry? Or shall I send it xen-devel instead? Thanks, Wasa --001a11c36702d108a504dc1f7772 Content-Type: text/html; charset=ISO-8859-1 Hi

is it possible to share the GPU between VMs with Xen? I am interested in mobile devices (e.g. android)
both ARM/x86. Is there something already available? Under way? If not, what is the best way to go?

I have come across this: http://lists.xen.org/archives/html/xen-devel/2012-02/msg01064.html
Is it still relevant?

is this the right list to send my inquiry? Or shall I send it xen-devel instead?

Thanks,
Wasa --001a11c36702d108a504dc1f7772-- --===============5866546838817074644== 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 --===============5866546838817074644==-- From xen-arm-bounces@lists.xen.org Tue May 07 11:56:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 11:56: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 1UZgVT-0000qv-N5; Tue, 07 May 2013 11:56:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZgVS-0000qY-DD for Xen-arm@lists.xen.org; Tue, 07 May 2013 11:56:30 +0000 Received: from [193.109.254.147:8318] by server-9.bemta-14.messagelabs.com id DB/AA-15694-DEBE8815; Tue, 07 May 2013 11:56:29 +0000 X-Env-Sender: wasabee18@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1367927619!9158710!1 X-Originating-IP: [209.85.217.179] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25569 invoked from network); 7 May 2013 11:53:40 -0000 Received: from mail-lb0-f179.google.com (HELO mail-lb0-f179.google.com) (209.85.217.179) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 11:53:40 -0000 Received: by mail-lb0-f179.google.com with SMTP id d10so609473lbj.38 for ; Tue, 07 May 2013 04:53:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=GJxSPyAcqqM6oUJSch0/fC+SBNJ/o7imye7mZTQkO6I=; b=TzXS7ESWJqVM8rLciVq3Q5U2Ad8AQUPJnxvVityNRSvyCazVfTLcY2ZDy8FBXhSbSc /LeKVdUPfu9ZJWY2Cn++KfdHvRew1aUFLe+30QRQKaZ/ogeC3xXrnuHOa2q1EkuPh1vP lvqAIpm4j322AGUX6PDiKFTX8jfN90e0mfcLOK7TiMDnMlS7z6ZfgHfDkBwzGtqA6uXq Mj2HqUVSVr61ZzwqtIWPXAqq1Qo0s9kvPZ9DfJsb2hocY5XKT02A69o0+MLq7XuLmPru BoWX7Xwi04L3zeA9mnwuzetLXAtZ8tXlSB/cBHxW5cCx8FcTkgeCHJwviEddttBBUX6H 2GbQ== MIME-Version: 1.0 X-Received: by 10.152.88.115 with SMTP id bf19mr778476lab.56.1367927619125; Tue, 07 May 2013 04:53:39 -0700 (PDT) Received: by 10.114.182.202 with HTTP; Tue, 7 May 2013 04:53:39 -0700 (PDT) Date: Tue, 7 May 2013 12:53:39 +0100 Message-ID: From: wasa bee To: Xen-arm@lists.xen.org Subject: [XenARM] GPU sharing with 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="===============5866546838817074644==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============5866546838817074644== Content-Type: multipart/alternative; boundary=001a11c36702d108a504dc1f7772 --001a11c36702d108a504dc1f7772 Content-Type: text/plain; charset=ISO-8859-1 Hi is it possible to share the GPU between VMs with Xen? I am interested in mobile devices (e.g. android) both ARM/x86. Is there something already available? Under way? If not, what is the best way to go? I have come across this: http://lists.xen.org/archives/html/xen-devel/2012-02/msg01064.html Is it still relevant? is this the right list to send my inquiry? Or shall I send it xen-devel instead? Thanks, Wasa --001a11c36702d108a504dc1f7772 Content-Type: text/html; charset=ISO-8859-1 Hi

is it possible to share the GPU between VMs with Xen? I am interested in mobile devices (e.g. android)
both ARM/x86. Is there something already available? Under way? If not, what is the best way to go?

I have come across this: http://lists.xen.org/archives/html/xen-devel/2012-02/msg01064.html
Is it still relevant?

is this the right list to send my inquiry? Or shall I send it xen-devel instead?

Thanks,
Wasa --001a11c36702d108a504dc1f7772-- --===============5866546838817074644== 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 --===============5866546838817074644==-- From xen-arm-bounces@lists.xen.org Tue May 07 12:33:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 12:33: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 1UZh4p-0003AA-T5; Tue, 07 May 2013 12:33:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZh4o-00039v-Nx for Xen-arm@lists.xen.org; Tue, 07 May 2013 12:33:02 +0000 Received: from [85.158.139.83:27825] by server-11.bemta-5.messagelabs.com id 06/D8-26693-D74F8815; Tue, 07 May 2013 12:33:01 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1367929973!29272284!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16219 invoked from network); 7 May 2013 12:32:54 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 12:32:54 -0000 X-IronPort-AV: E=Sophos;i="4.87,628,1363132800"; d="scan'208";a="22590338" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 07 May 2013 12:32:53 +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.3; Tue, 7 May 2013 08:32:52 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UZh4e-0003mo-Gg; Tue, 07 May 2013 13:32:52 +0100 Date: Tue, 7 May 2013 13:32:51 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: wasa bee 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] GPU sharing with 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 Tue, 7 May 2013, wasa bee wrote: > Hi > > is it possible to share the GPU between VMs with Xen? I am interested in mobile devices (e.g. android) > both ARM/x86. Is there something already available? Under way? If not, what is the best way to go? > > I have come across this: http://lists.xen.org/archives/html/xen-devel/2012-02/msg01064.html > Is it still relevant? > > is this the right list to send my inquiry? Or shall I send it xen-devel instead? For questions like this one it is probably best to send it to both xen-arm and xen-devel. >From the upstream Xen point of view, nothing is available out of the box, however a PV framebuffer frontend driver exists in Linux (drivers/video/xen-fbfront.c) and a corresponding backend in QEMU (hw/xenfb.c): it should be relatively easy to make them work on ARM. They would allow you to export a framebuffer to each guest and render them in dom0 using QEMU. In the past people also managed to export OpenGL to guest VMs, but none of the code went upstream: http://en.wikipedia.org/wiki/VMGL http://www.diku.dk/~jacobg/gfx/ You would need to resurrect that code, port it over to new versions of Xen and Linux and upstream it yourself. _______________________________________________ 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 May 07 12:33:07 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 12:33: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 1UZh4p-0003AA-T5; Tue, 07 May 2013 12:33:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZh4o-00039v-Nx for Xen-arm@lists.xen.org; Tue, 07 May 2013 12:33:02 +0000 Received: from [85.158.139.83:27825] by server-11.bemta-5.messagelabs.com id 06/D8-26693-D74F8815; Tue, 07 May 2013 12:33:01 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1367929973!29272284!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16219 invoked from network); 7 May 2013 12:32:54 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 12:32:54 -0000 X-IronPort-AV: E=Sophos;i="4.87,628,1363132800"; d="scan'208";a="22590338" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 07 May 2013 12:32:53 +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.3; Tue, 7 May 2013 08:32:52 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UZh4e-0003mo-Gg; Tue, 07 May 2013 13:32:52 +0100 Date: Tue, 7 May 2013 13:32:51 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: wasa bee 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] GPU sharing with 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 Tue, 7 May 2013, wasa bee wrote: > Hi > > is it possible to share the GPU between VMs with Xen? I am interested in mobile devices (e.g. android) > both ARM/x86. Is there something already available? Under way? If not, what is the best way to go? > > I have come across this: http://lists.xen.org/archives/html/xen-devel/2012-02/msg01064.html > Is it still relevant? > > is this the right list to send my inquiry? Or shall I send it xen-devel instead? For questions like this one it is probably best to send it to both xen-arm and xen-devel. >From the upstream Xen point of view, nothing is available out of the box, however a PV framebuffer frontend driver exists in Linux (drivers/video/xen-fbfront.c) and a corresponding backend in QEMU (hw/xenfb.c): it should be relatively easy to make them work on ARM. They would allow you to export a framebuffer to each guest and render them in dom0 using QEMU. In the past people also managed to export OpenGL to guest VMs, but none of the code went upstream: http://en.wikipedia.org/wiki/VMGL http://www.diku.dk/~jacobg/gfx/ You would need to resurrect that code, port it over to new versions of Xen and Linux and upstream it yourself. _______________________________________________ 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 May 07 15:52:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 15:52: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 1UZkBg-0000OC-RM; Tue, 07 May 2013 15:52:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZkBf-0000O4-Kw for xen-arm@lists.xen.org; Tue, 07 May 2013 15:52:19 +0000 Received: from [85.158.139.83:21762] by server-16.bemta-5.messagelabs.com id 65/9D-31493-23329815; Tue, 07 May 2013 15:52:18 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1367941936!29321693!1 X-Originating-IP: [209.85.192.176] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30730 invoked from network); 7 May 2013 15:52:17 -0000 Received: from mail-pd0-f176.google.com (HELO mail-pd0-f176.google.com) (209.85.192.176) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 15:52:17 -0000 Received: by mail-pd0-f176.google.com with SMTP id x10so504769pdj.7 for ; Tue, 07 May 2013 08:52:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=6e9SxnDqL0rCYkfKrGF8bfEnZmVO8AjSb2UuqZfUHuQ=; b=R7ppHGLBzcPIeDpevvWLNKukk0fV3B9sNHZvE8B/0ueU2GkhKfRBeBFF+Zp8rlfyDC jSqSBmcc+rTQzsctyq8pLhVQKEHnWO0+H1aaxDCP6GVT4ZKczk/zWfcZgVEVCnzdeFZw ZsfP5m/eZHE5xdrncG+olsgf56TuLSsiM7TIL2g5PCE40DCr81xqvrQI/lIHmRQoK07z liwh0F7WMLMqvLoqDwpRrgOI/CYJiZgyyupE82HxHtVjee2S0hmV+YQqkaSSIadhF3Et +pCos46ECP3qEetv2p4ThZaxgmC11VLN2HJhGaIn7XMoGnyampMcCEsnMSb6WhuLM0E1 nI6g== X-Received: by 10.68.65.134 with SMTP id x6mr2939101pbs.219.1367941935715; Tue, 07 May 2013 08:52:15 -0700 (PDT) Received: from [192.168.1.102] ([222.247.146.246]) by mx.google.com with ESMTPSA id c5sm28696740pbl.37.2013.05.07.08.52.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 May 2013 08:52:14 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1367915980.26321.15.camel@zakaz.uk.xensource.com> Date: Tue, 7 May 2013 23:52:04 +0800 Message-Id: <8E74206E-0294-483B-8A29-2716AF4FF6F0@gmail.com> References: <20130324070650.GA9800@cbz-workstation> <1367915980.26321.15.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm , "xen-devel@lists.xensource.com" , Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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 May 7, 2013, at 4:39 PM, Ian Campbell wrote: > On Mon, 2013-05-06 at 11:40 +0100, Stefano Stabellini wrote: >> On Mon, 6 May 2013, Chen Baozi wrote: >>> On Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: >>> >>>> On Sun, 24 Mar 2013, Chen Baozi wrote: >>>>> Hi all, >>>>> >>>>> I'm reading Mini-OS's codes and to estimate the amount of work porting it to >>>>> ARM (Ian's GSoC idea this year). >>>>> >>>>> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to >>>>> the guest through ESI register. And Mini-OS would use this structure as the >>>>> argument of start_kernel. However, I didn't see codes handle the >>>>> start_info_t on ARM side. Instead, I see a more standard protocal when >>>>> booting ARM's dom0, which follows linux kernel bootstrap rules: >>>>> >>>>> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer >>>>> >>>>> Does it mean that Xen for ARM does not use the start_info_t to pass >>>>> information when booting PV guest? >>>>> Or did I miss something important? >>>> >>>> That's right, we don't use start_info_t on ARM, in fact ARM guests are >>>> not exactly like x86 PV guests. >>>> The information present in the start_info page are either available via >>>> device tree or no used on ARM. >>> >>> I'm thinking of parsing the dtb and fill the start_info structure >> according to it before jump to the start_kernel. In that case, it >> won't break some original mini-os interface. > > If you go this path then trying to do it in arch_init would be > preferable. Nothing in start_kernel before arch_init seems like it > should need start info. > > This is effectively what we do for Linux guests too -- populate a stunt > start info early on. > >> You can try that, or you can refactor the code dividing it into x86 >> specific and common stuff. > > There is bound to be a bunch of this sort of refactoring required, just > because mini-os in practice has only really supported x86 until now and > even with the best intentions arch specific stuff tends to leak out > unless you are actively using something on multiple arches. Yes. Right now I'm testing "make" to complete the "infrastructure" headers and interfaces that arm64 needs. It turns out that it lacks some basic type definition such as "uint64_t", which is introduced from headers files of xen hypervisor. I checked x86's implementation. Those types are defined at include/public/arch-x86/xen-x86_32.h. If we follows x86's convention, we should define them in xen hypervisor's tree. I don't think it is a good idea. Any ideas? > > 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 Tue May 07 15:52:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 15:52: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 1UZkBg-0000OC-RM; Tue, 07 May 2013 15:52:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZkBf-0000O4-Kw for xen-arm@lists.xen.org; Tue, 07 May 2013 15:52:19 +0000 Received: from [85.158.139.83:21762] by server-16.bemta-5.messagelabs.com id 65/9D-31493-23329815; Tue, 07 May 2013 15:52:18 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1367941936!29321693!1 X-Originating-IP: [209.85.192.176] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30730 invoked from network); 7 May 2013 15:52:17 -0000 Received: from mail-pd0-f176.google.com (HELO mail-pd0-f176.google.com) (209.85.192.176) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 15:52:17 -0000 Received: by mail-pd0-f176.google.com with SMTP id x10so504769pdj.7 for ; Tue, 07 May 2013 08:52:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=6e9SxnDqL0rCYkfKrGF8bfEnZmVO8AjSb2UuqZfUHuQ=; b=R7ppHGLBzcPIeDpevvWLNKukk0fV3B9sNHZvE8B/0ueU2GkhKfRBeBFF+Zp8rlfyDC jSqSBmcc+rTQzsctyq8pLhVQKEHnWO0+H1aaxDCP6GVT4ZKczk/zWfcZgVEVCnzdeFZw ZsfP5m/eZHE5xdrncG+olsgf56TuLSsiM7TIL2g5PCE40DCr81xqvrQI/lIHmRQoK07z liwh0F7WMLMqvLoqDwpRrgOI/CYJiZgyyupE82HxHtVjee2S0hmV+YQqkaSSIadhF3Et +pCos46ECP3qEetv2p4ThZaxgmC11VLN2HJhGaIn7XMoGnyampMcCEsnMSb6WhuLM0E1 nI6g== X-Received: by 10.68.65.134 with SMTP id x6mr2939101pbs.219.1367941935715; Tue, 07 May 2013 08:52:15 -0700 (PDT) Received: from [192.168.1.102] ([222.247.146.246]) by mx.google.com with ESMTPSA id c5sm28696740pbl.37.2013.05.07.08.52.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 May 2013 08:52:14 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1367915980.26321.15.camel@zakaz.uk.xensource.com> Date: Tue, 7 May 2013 23:52:04 +0800 Message-Id: <8E74206E-0294-483B-8A29-2716AF4FF6F0@gmail.com> References: <20130324070650.GA9800@cbz-workstation> <1367915980.26321.15.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm , "xen-devel@lists.xensource.com" , Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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 May 7, 2013, at 4:39 PM, Ian Campbell wrote: > On Mon, 2013-05-06 at 11:40 +0100, Stefano Stabellini wrote: >> On Mon, 6 May 2013, Chen Baozi wrote: >>> On Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: >>> >>>> On Sun, 24 Mar 2013, Chen Baozi wrote: >>>>> Hi all, >>>>> >>>>> I'm reading Mini-OS's codes and to estimate the amount of work porting it to >>>>> ARM (Ian's GSoC idea this year). >>>>> >>>>> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to >>>>> the guest through ESI register. And Mini-OS would use this structure as the >>>>> argument of start_kernel. However, I didn't see codes handle the >>>>> start_info_t on ARM side. Instead, I see a more standard protocal when >>>>> booting ARM's dom0, which follows linux kernel bootstrap rules: >>>>> >>>>> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer >>>>> >>>>> Does it mean that Xen for ARM does not use the start_info_t to pass >>>>> information when booting PV guest? >>>>> Or did I miss something important? >>>> >>>> That's right, we don't use start_info_t on ARM, in fact ARM guests are >>>> not exactly like x86 PV guests. >>>> The information present in the start_info page are either available via >>>> device tree or no used on ARM. >>> >>> I'm thinking of parsing the dtb and fill the start_info structure >> according to it before jump to the start_kernel. In that case, it >> won't break some original mini-os interface. > > If you go this path then trying to do it in arch_init would be > preferable. Nothing in start_kernel before arch_init seems like it > should need start info. > > This is effectively what we do for Linux guests too -- populate a stunt > start info early on. > >> You can try that, or you can refactor the code dividing it into x86 >> specific and common stuff. > > There is bound to be a bunch of this sort of refactoring required, just > because mini-os in practice has only really supported x86 until now and > even with the best intentions arch specific stuff tends to leak out > unless you are actively using something on multiple arches. Yes. Right now I'm testing "make" to complete the "infrastructure" headers and interfaces that arm64 needs. It turns out that it lacks some basic type definition such as "uint64_t", which is introduced from headers files of xen hypervisor. I checked x86's implementation. Those types are defined at include/public/arch-x86/xen-x86_32.h. If we follows x86's convention, we should define them in xen hypervisor's tree. I don't think it is a good idea. Any ideas? > > 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 Tue May 07 16:01:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 16:01: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 1UZkKQ-0001Iv-JG; Tue, 07 May 2013 16:01:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZkKP-0001Ip-De for xen-arm@lists.xen.org; Tue, 07 May 2013 16:01:21 +0000 Received: from [85.158.139.211:32754] by server-10.bemta-5.messagelabs.com id D7/0A-19016-05529815; Tue, 07 May 2013 16:01:20 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1367942477!20551584!1 X-Originating-IP: [209.85.220.50] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6311 invoked from network); 7 May 2013 16:01:19 -0000 Received: from mail-pa0-f50.google.com (HELO mail-pa0-f50.google.com) (209.85.220.50) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 16:01:19 -0000 Received: by mail-pa0-f50.google.com with SMTP id fb10so594276pad.23 for ; Tue, 07 May 2013 09:01:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=rXAaECojgHoplDOMddd13X1Mgy6RrChsn5jdEkB3xlI=; b=BO7sPrT540KIOsgWiQOu6GfjIOPFi/8i0wcQFS9utet60+lu7uByklCDivIIRBxx2f XXQOEawvubtGc/Yn41KdFybuUjGJqOy9eNpipaQw+VC06BHBqPktsWXfM+qE7Rt15jQv fns37UNGKtQipOoPIQru3lCcQJfjs70BRJjp8XUarDW5rCn1HmC4w9UJjAlegKvXml9D 7OHACI0y9fR55Hp2vUlmrmBWxR0HWxv7O336w2iu/37UwoyFTuVUZig+y4cRw5Ywzt6a KzLXCYBB9isTjnhBx6tEsqPOQURwTJiEYZ77pCTYe6laI9/VkOah5KxfwR7t9uZ8TOSw rhyg== X-Received: by 10.66.74.170 with SMTP id u10mr3569966pav.202.1367942477480; Tue, 07 May 2013 09:01:17 -0700 (PDT) Received: from [192.168.1.102] ([222.247.146.246]) by mx.google.com with ESMTPSA id bs3sm28724368pbb.36.2013.05.07.09.01.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 May 2013 09:01:16 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <20130507155456.GC6143@type.bordeaux.inria.fr> Date: Wed, 8 May 2013 00:01:12 +0800 Message-Id: <1EE19087-5DE1-4F28-B4BA-4B9A5336C2AA@gmail.com> References: <20130324070650.GA9800@cbz-workstation> <1367915980.26321.15.camel@zakaz.uk.xensource.com> <8E74206E-0294-483B-8A29-2716AF4FF6F0@gmail.com> <20130507155456.GC6143@type.bordeaux.inria.fr> To: Samuel Thibault X-Mailer: Apple Mail (2.1503) Cc: xen-arm , "xen-devel@lists.xensource.com" Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On May 7, 2013, at 11:54 PM, Samuel Thibault = wrote: > Chen Baozi, le Tue 07 May 2013 23:52:04 +0800, a =E9crit : >> it lacks some basic type definition such as "uint64_t", >> which is introduced from headers files of xen hypervisor. > = > ? I see it coming from extras/mini-os/include/types.h Oh, my bad! I didn't check this file. Yes. The origin types.h lacks logic t= o deal with arm64 situation. Thanks a lot! 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 May 07 16:01:25 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 07 May 2013 16:01: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 1UZkKQ-0001Iv-JG; Tue, 07 May 2013 16:01:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZkKP-0001Ip-De for xen-arm@lists.xen.org; Tue, 07 May 2013 16:01:21 +0000 Received: from [85.158.139.211:32754] by server-10.bemta-5.messagelabs.com id D7/0A-19016-05529815; Tue, 07 May 2013 16:01:20 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1367942477!20551584!1 X-Originating-IP: [209.85.220.50] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6311 invoked from network); 7 May 2013 16:01:19 -0000 Received: from mail-pa0-f50.google.com (HELO mail-pa0-f50.google.com) (209.85.220.50) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 16:01:19 -0000 Received: by mail-pa0-f50.google.com with SMTP id fb10so594276pad.23 for ; Tue, 07 May 2013 09:01:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=rXAaECojgHoplDOMddd13X1Mgy6RrChsn5jdEkB3xlI=; b=BO7sPrT540KIOsgWiQOu6GfjIOPFi/8i0wcQFS9utet60+lu7uByklCDivIIRBxx2f XXQOEawvubtGc/Yn41KdFybuUjGJqOy9eNpipaQw+VC06BHBqPktsWXfM+qE7Rt15jQv fns37UNGKtQipOoPIQru3lCcQJfjs70BRJjp8XUarDW5rCn1HmC4w9UJjAlegKvXml9D 7OHACI0y9fR55Hp2vUlmrmBWxR0HWxv7O336w2iu/37UwoyFTuVUZig+y4cRw5Ywzt6a KzLXCYBB9isTjnhBx6tEsqPOQURwTJiEYZ77pCTYe6laI9/VkOah5KxfwR7t9uZ8TOSw rhyg== X-Received: by 10.66.74.170 with SMTP id u10mr3569966pav.202.1367942477480; Tue, 07 May 2013 09:01:17 -0700 (PDT) Received: from [192.168.1.102] ([222.247.146.246]) by mx.google.com with ESMTPSA id bs3sm28724368pbb.36.2013.05.07.09.01.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 May 2013 09:01:16 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <20130507155456.GC6143@type.bordeaux.inria.fr> Date: Wed, 8 May 2013 00:01:12 +0800 Message-Id: <1EE19087-5DE1-4F28-B4BA-4B9A5336C2AA@gmail.com> References: <20130324070650.GA9800@cbz-workstation> <1367915980.26321.15.camel@zakaz.uk.xensource.com> <8E74206E-0294-483B-8A29-2716AF4FF6F0@gmail.com> <20130507155456.GC6143@type.bordeaux.inria.fr> To: Samuel Thibault X-Mailer: Apple Mail (2.1503) Cc: xen-arm , "xen-devel@lists.xensource.com" Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org On May 7, 2013, at 11:54 PM, Samuel Thibault = wrote: > Chen Baozi, le Tue 07 May 2013 23:52:04 +0800, a =E9crit : >> it lacks some basic type definition such as "uint64_t", >> which is introduced from headers files of xen hypervisor. > = > ? I see it coming from extras/mini-os/include/types.h Oh, my bad! I didn't check this file. Yes. The origin types.h lacks logic t= o deal with arm64 situation. Thanks a lot! 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 Wed May 08 08:38:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 May 2013 08:38:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZzte-0001Q7-LQ; Wed, 08 May 2013 08:38:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZkEE-0000YY-Pi for xen-arm@lists.xen.org; Tue, 07 May 2013 15:54:58 +0000 Received: from [85.158.139.211:4763] by server-16.bemta-5.messagelabs.com id B5/03-31493-2D329815; Tue, 07 May 2013 15:54:58 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1367942096!20550543!1 X-Originating-IP: [192.134.164.83] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12471 invoked from network); 7 May 2013 15:54:57 -0000 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 15:54:57 -0000 X-IronPort-AV: E=Sophos;i="4.87,629,1363129200"; d="scan'208";a="16413178" Received: from nat-inria-bordeaux-52-gw-01-bso.bordeaux.inria.fr (HELO type.ipv6) ([194.199.1.52]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 May 2013 17:54:56 +0200 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1UZkEC-00037L-5J; Tue, 07 May 2013 17:54:56 +0200 Date: Tue, 7 May 2013 17:54:56 +0200 From: Samuel Thibault To: Chen Baozi Message-ID: <20130507155456.GC6143@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , Chen Baozi , Ian Campbell , Stefano Stabellini , xen-arm , "xen-devel@lists.xensource.com" References: <20130324070650.GA9800@cbz-workstation> <1367915980.26321.15.camel@zakaz.uk.xensource.com> <8E74206E-0294-483B-8A29-2716AF4FF6F0@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <8E74206E-0294-483B-8A29-2716AF4FF6F0@gmail.com> User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) X-Mailman-Approved-At: Wed, 08 May 2013 08:38:45 +0000 Cc: xen-arm , "xen-devel@lists.xensource.com" Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org Chen Baozi, le Tue 07 May 2013 23:52:04 +0800, a =E9crit : > it lacks some basic type definition such as "uint64_t", > which is introduced from headers files of xen hypervisor. ? I see it coming from extras/mini-os/include/types.h Samuel _______________________________________________ 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 Wed May 08 08:38:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 08 May 2013 08:38:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZzte-0001Q7-LQ; Wed, 08 May 2013 08:38:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UZkEE-0000YY-Pi for xen-arm@lists.xen.org; Tue, 07 May 2013 15:54:58 +0000 Received: from [85.158.139.211:4763] by server-16.bemta-5.messagelabs.com id B5/03-31493-2D329815; Tue, 07 May 2013 15:54:58 +0000 X-Env-Sender: samuel.thibault@ens-lyon.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1367942096!20550543!1 X-Originating-IP: [192.134.164.83] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12471 invoked from network); 7 May 2013 15:54:57 -0000 Received: from mail2-relais-roc.national.inria.fr (HELO mail2-relais-roc.national.inria.fr) (192.134.164.83) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 May 2013 15:54:57 -0000 X-IronPort-AV: E=Sophos;i="4.87,629,1363129200"; d="scan'208";a="16413178" Received: from nat-inria-bordeaux-52-gw-01-bso.bordeaux.inria.fr (HELO type.ipv6) ([194.199.1.52]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 07 May 2013 17:54:56 +0200 Received: from samy by type.ipv6 with local (Exim 4.80) (envelope-from ) id 1UZkEC-00037L-5J; Tue, 07 May 2013 17:54:56 +0200 Date: Tue, 7 May 2013 17:54:56 +0200 From: Samuel Thibault To: Chen Baozi Message-ID: <20130507155456.GC6143@type.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , Chen Baozi , Ian Campbell , Stefano Stabellini , xen-arm , "xen-devel@lists.xensource.com" References: <20130324070650.GA9800@cbz-workstation> <1367915980.26321.15.camel@zakaz.uk.xensource.com> <8E74206E-0294-483B-8A29-2716AF4FF6F0@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <8E74206E-0294-483B-8A29-2716AF4FF6F0@gmail.com> User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) X-Mailman-Approved-At: Wed, 08 May 2013 08:38:45 +0000 Cc: xen-arm , "xen-devel@lists.xensource.com" Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org Chen Baozi, le Tue 07 May 2013 23:52:04 +0800, a =E9crit : > it lacks some basic type definition such as "uint64_t", > which is introduced from headers files of xen hypervisor. ? I see it coming from extras/mini-os/include/types.h Samuel _______________________________________________ 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 May 09 17:35:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 May 2013 17:35: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 1UaUkn-0007PV-NF; Thu, 09 May 2013 17:35:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UaUkm-0007P9-3S; Thu, 09 May 2013 17:35:40 +0000 Received: from [85.158.139.83:9333] by server-9.bemta-5.messagelabs.com id FF/14-14875-B6EDB815; Thu, 09 May 2013 17:35:39 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1368120938!28155994!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12122 invoked from network); 9 May 2013 17:35:38 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 9 May 2013 17:35:38 -0000 Received: by mail-wg0-f52.google.com with SMTP id k13so3395275wgh.7 for ; Thu, 09 May 2013 10:35:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=97zC1iWtsGGY0rNWtQvnnqeCq5BlR7mqxuBUfknr56c=; b=hQvRGoctR0XRkiZWaXXO3qSdiLYuWc6sAgvzFXNNzfYsPXDO/RFeCe+OGH6wIQZGrA 01eT2GwkvTQpTBZySM/PI/lU6dGGrAuSZvEIMSp6dwENggi+JdSkSPYEpjZWqehFaN27 0xLhGHJ8xR0PGjnFsP53F5hWxjlOifWpcWtZn6hsPLuMWyKlcsARbCPODUSrkoYJltvo fb5jSszV+6gElorWHVIZhsxYnhq2qQxdFew1yIa9WoRbYLgLCp0Yl8soupoDfbEb1Q3/ Uz9YHcckCV411nNrJY9ZfymxftNWJloO8RaVT4j6jtttdWRyE2hkazH1EduXGyCnKOfh CPRQ== X-Received: by 10.180.76.103 with SMTP id j7mr19120211wiw.21.1368120938384; Thu, 09 May 2013 10:35:38 -0700 (PDT) Received: from [172.16.26.11] ([94.3.142.121]) by mx.google.com with ESMTPSA id x13sm5952179wib.3.2013.05.09.10.35.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 May 2013 10:35:37 -0700 (PDT) Message-ID: <518BDE66.3000700@xen.org> Date: Thu, 09 May 2013 18:35:34 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 References: <516AECC9.1010603@xen.org> <20130419035218.GY88962@USLT-205755.sungardas.corp> <51756872.7040402@xen.org> <1366702922.12931.14.camel@dagon.hellion.org.uk> In-Reply-To: <1366702922.12931.14.camel@dagon.hellion.org.uk> Cc: "xen-api@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-devel@lists.xen.org" , Amir M Chaudhry Subject: Re: [XenARM] [Xen-devel] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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 everybody, I put together a more detailed proposal on mailing list naming conventions at http://www.xenproject.org/component/content/article/80-developers/139-mailing-list-conventions.html, which I believe reflects the previous discussion on this thread. Unless anybody objects, I will put this proposal up for a vote with other governance changes from Monday. This will then guide the transition of mailing lists from lists.xen.org to lists.xenproject.org. In other words, we can take the opportunity to clean up some of the odd naming issues that have crept in over time. Best Regards 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 Thu May 09 17:35:45 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 09 May 2013 17:35: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 1UaUkn-0007PV-NF; Thu, 09 May 2013 17:35:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UaUkm-0007P9-3S; Thu, 09 May 2013 17:35:40 +0000 Received: from [85.158.139.83:9333] by server-9.bemta-5.messagelabs.com id FF/14-14875-B6EDB815; Thu, 09 May 2013 17:35:39 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1368120938!28155994!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12122 invoked from network); 9 May 2013 17:35:38 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 9 May 2013 17:35:38 -0000 Received: by mail-wg0-f52.google.com with SMTP id k13so3395275wgh.7 for ; Thu, 09 May 2013 10:35:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=97zC1iWtsGGY0rNWtQvnnqeCq5BlR7mqxuBUfknr56c=; b=hQvRGoctR0XRkiZWaXXO3qSdiLYuWc6sAgvzFXNNzfYsPXDO/RFeCe+OGH6wIQZGrA 01eT2GwkvTQpTBZySM/PI/lU6dGGrAuSZvEIMSp6dwENggi+JdSkSPYEpjZWqehFaN27 0xLhGHJ8xR0PGjnFsP53F5hWxjlOifWpcWtZn6hsPLuMWyKlcsARbCPODUSrkoYJltvo fb5jSszV+6gElorWHVIZhsxYnhq2qQxdFew1yIa9WoRbYLgLCp0Yl8soupoDfbEb1Q3/ Uz9YHcckCV411nNrJY9ZfymxftNWJloO8RaVT4j6jtttdWRyE2hkazH1EduXGyCnKOfh CPRQ== X-Received: by 10.180.76.103 with SMTP id j7mr19120211wiw.21.1368120938384; Thu, 09 May 2013 10:35:38 -0700 (PDT) Received: from [172.16.26.11] ([94.3.142.121]) by mx.google.com with ESMTPSA id x13sm5952179wib.3.2013.05.09.10.35.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 May 2013 10:35:37 -0700 (PDT) Message-ID: <518BDE66.3000700@xen.org> Date: Thu, 09 May 2013 18:35:34 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 References: <516AECC9.1010603@xen.org> <20130419035218.GY88962@USLT-205755.sungardas.corp> <51756872.7040402@xen.org> <1366702922.12931.14.camel@dagon.hellion.org.uk> In-Reply-To: <1366702922.12931.14.camel@dagon.hellion.org.uk> Cc: "xen-api@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-devel@lists.xen.org" , Amir M Chaudhry Subject: Re: [XenARM] [Xen-devel] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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 everybody, I put together a more detailed proposal on mailing list naming conventions at http://www.xenproject.org/component/content/article/80-developers/139-mailing-list-conventions.html, which I believe reflects the previous discussion on this thread. Unless anybody objects, I will put this proposal up for a vote with other governance changes from Monday. This will then guide the transition of mailing lists from lists.xen.org to lists.xenproject.org. In other words, we can take the opportunity to clean up some of the odd naming issues that have crept in over time. Best Regards 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 May 10 10:06:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 May 2013 10:06:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UakDh-0002P5-DJ; Fri, 10 May 2013 10:06:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UakDf-0002Om-V0; Fri, 10 May 2013 10:06:32 +0000 Received: from [85.158.138.51:16710] by server-11.bemta-3.messagelabs.com id D4/D2-05438-6A6CC815; Fri, 10 May 2013 10:06:30 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1368180381!28685702!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27155 invoked from network); 10 May 2013 10:06:22 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 May 2013 10:06:22 -0000 X-IronPort-AV: E=Sophos;i="4.87,552,1363132800"; d="scan'208";a="4431198" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 May 2013 09:59:34 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Fri, 10 May 2013 11:06:18 +0100 Message-ID: <1368180377.27857.60.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Fri, 10 May 2013 11:06:17 +0100 In-Reply-To: <518BDE66.3000700@xen.org> References: <516AECC9.1010603@xen.org> <20130419035218.GY88962@USLT-205755.sungardas.corp> <51756872.7040402@xen.org> <1366702922.12931.14.camel@dagon.hellion.org.uk> <518BDE66.3000700@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , Amir M Chaudhry , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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, 2013-05-09 at 18:35 +0100, Lars Kurth wrote: > Hi everybody, > > I put together a more detailed proposal on mailing list naming > conventions at > http://www.xenproject.org/component/content/article/80-developers/139-mailing-list-conventions.html, > which I believe reflects the previous discussion on this thread. Unless > anybody objects, I will put this proposal up for a vote with other > governance changes from Monday. Looks good to me. A few minor comments: The text says everything is lower case but all the examples are upper case... The incoming security alert address is currently security@xen.org and I'd expect it to become security@xenproject.org not @lists.xenproject.org, is the security@ list there intended to be the outgoing security alert list (i.e. the current predisclosure list)? Should the predisclosure list be per-team? I think the intention is that the invite only lists will still be archived publicly, and this is what makes them distinct from the private lists, is that correct? 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 Fri May 10 10:06:37 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 10 May 2013 10:06:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UakDh-0002P5-DJ; Fri, 10 May 2013 10:06:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UakDf-0002Om-V0; Fri, 10 May 2013 10:06:32 +0000 Received: from [85.158.138.51:16710] by server-11.bemta-3.messagelabs.com id D4/D2-05438-6A6CC815; Fri, 10 May 2013 10:06:30 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1368180381!28685702!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27155 invoked from network); 10 May 2013 10:06:22 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 May 2013 10:06:22 -0000 X-IronPort-AV: E=Sophos;i="4.87,552,1363132800"; d="scan'208";a="4431198" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 May 2013 09:59:34 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Fri, 10 May 2013 11:06:18 +0100 Message-ID: <1368180377.27857.60.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Fri, 10 May 2013 11:06:17 +0100 In-Reply-To: <518BDE66.3000700@xen.org> References: <516AECC9.1010603@xen.org> <20130419035218.GY88962@USLT-205755.sungardas.corp> <51756872.7040402@xen.org> <1366702922.12931.14.camel@dagon.hellion.org.uk> <518BDE66.3000700@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , Amir M Chaudhry , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [XenARM] [Xen-devel] [Xen-API] [Proposal] Additional mailing lists for specific purposes 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, 2013-05-09 at 18:35 +0100, Lars Kurth wrote: > Hi everybody, > > I put together a more detailed proposal on mailing list naming > conventions at > http://www.xenproject.org/component/content/article/80-developers/139-mailing-list-conventions.html, > which I believe reflects the previous discussion on this thread. Unless > anybody objects, I will put this proposal up for a vote with other > governance changes from Monday. Looks good to me. A few minor comments: The text says everything is lower case but all the examples are upper case... The incoming security alert address is currently security@xen.org and I'd expect it to become security@xenproject.org not @lists.xenproject.org, is the security@ list there intended to be the outgoing security alert list (i.e. the current predisclosure list)? Should the predisclosure list be per-team? I think the intention is that the invite only lists will still be archived publicly, and this is what makes them distinct from the private lists, is that correct? 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 May 13 10:31:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 May 2013 10:31: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 1Ubq25-00011Q-Ff; Mon, 13 May 2013 10:31:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ubq24-000111-1g; Mon, 13 May 2013 10:31:04 +0000 Received: from [85.158.143.99:23808] by server-3.bemta-4.messagelabs.com id 33/03-02015-7E0C0915; Mon, 13 May 2013 10:31:03 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1368441024!22506281!1 X-Originating-IP: [209.85.214.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24918 invoked from network); 13 May 2013 10:30:24 -0000 Received: from mail-bk0-f51.google.com (HELO mail-bk0-f51.google.com) (209.85.214.51) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 May 2013 10:30:24 -0000 Received: by mail-bk0-f51.google.com with SMTP id ji2so2353676bkc.24 for ; Mon, 13 May 2013 03:30:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=gS4FbBWHGJClymguk1I5kmRGnnwXHMnX3FDD86fVzHQ=; b=fzmQTCetlVVx25Dwl7Bwiw5LPC90KGGiWYOrLdA7hykWX/9PbDZNnnCxAAC82K/pvI GDo2n3312m7Y5NQ+izUxVkQYp2dFPxREy3LWZKk2l6VBD3Oj2uiPClOqwJaBf1OhKJKr BFsHp+RQynsZQt8J5dC3voFv0q8fz6rVy/AIbJ5qlQpgRV+QsWZlE/ym/RAnrCDgRocL FPMv7fhPKOsAL3KrKItScu4ctH7ndjSehhlDQ2Kyx58IJaniF8y1eUAG6UOfsh4MqUse i8sfkCwVDot29Kdyst0JMQXKqu47eMU4Ojx/HZNviT/Al96Twdnf4lXfR9d9Ek5u9jLQ Jt4A== X-Received: by 10.204.26.8 with SMTP id b8mr5477988bkc.83.1368441023929; Mon, 13 May 2013 03:30:23 -0700 (PDT) Received: from [172.16.26.11] ([5.69.56.103]) by mx.google.com with ESMTPSA id x5sm1916196bkh.15.2013.05.13.03.30.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 May 2013 03:30:22 -0700 (PDT) Message-ID: <5190C0BC.5060008@xen.org> Date: Mon, 13 May 2013 11:30:20 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" Subject: [XenARM] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) 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 Dear Community Members, as part of the move of Xen to the Linux Foundation, I have made a few proposals for Governance changes on the Xen Project mailing lists in the last few weeks. To avoid voting fatigue, several proposals are up for review or voting: - For vote:Xen Project Governance v2 at http://www.xenproject.org/component/content/article/80-developers/136-governance-v2-proposal.html - For vote:Mailing List Conventions v1 at http://www.xenproject.org/component/content/article/80-developers/139-mailing-list-conventions.html - For vote: Dates and Locations for 2014 Events (see below) Regards Lars Voting for Proposals ==================== Two proposals Xen Project Governance v2 and Mailing List Conventions v1 are up for vote using this voting form (http://www.xenproject.org/component/content/article/98-developers/vote/127-vote-governance-v2-and-mailing-list-conventions-v1.html). As the two proposals affect all Xen Project teams, all maintainers, committers and project leads of mature projects and the community manager can vote. The vote will be open until May 20, 2013. Voting for Events ================= As it is very hard to book event space on short notice, I wanted to ask you all where to hold Xen Project user and developer events in 2014. Earlier this year, there was a debate whether we should rotate Xen Events around the globe. The answer was a very strong*yes*. As we have a Hackathon and Xen Developer Summit in Europe this year, Europe will not be an option for a developer event in 2014. Rather than creating a voting form, I decided to use the voting feature on the newxenproject.org website. To vote, you need to create an account. If you have difficulties, let me know. The poll isat http://www.xenproject.org/help/questions-and-answers/vote-on-2014-event-locations.html. The vote will stay open until the middle of June. _______________________________________________ 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 May 13 10:31:10 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 May 2013 10:31: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 1Ubq25-00011Q-Ff; Mon, 13 May 2013 10:31:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ubq24-000111-1g; Mon, 13 May 2013 10:31:04 +0000 Received: from [85.158.143.99:23808] by server-3.bemta-4.messagelabs.com id 33/03-02015-7E0C0915; Mon, 13 May 2013 10:31:03 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1368441024!22506281!1 X-Originating-IP: [209.85.214.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24918 invoked from network); 13 May 2013 10:30:24 -0000 Received: from mail-bk0-f51.google.com (HELO mail-bk0-f51.google.com) (209.85.214.51) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 May 2013 10:30:24 -0000 Received: by mail-bk0-f51.google.com with SMTP id ji2so2353676bkc.24 for ; Mon, 13 May 2013 03:30:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=gS4FbBWHGJClymguk1I5kmRGnnwXHMnX3FDD86fVzHQ=; b=fzmQTCetlVVx25Dwl7Bwiw5LPC90KGGiWYOrLdA7hykWX/9PbDZNnnCxAAC82K/pvI GDo2n3312m7Y5NQ+izUxVkQYp2dFPxREy3LWZKk2l6VBD3Oj2uiPClOqwJaBf1OhKJKr BFsHp+RQynsZQt8J5dC3voFv0q8fz6rVy/AIbJ5qlQpgRV+QsWZlE/ym/RAnrCDgRocL FPMv7fhPKOsAL3KrKItScu4ctH7ndjSehhlDQ2Kyx58IJaniF8y1eUAG6UOfsh4MqUse i8sfkCwVDot29Kdyst0JMQXKqu47eMU4Ojx/HZNviT/Al96Twdnf4lXfR9d9Ek5u9jLQ Jt4A== X-Received: by 10.204.26.8 with SMTP id b8mr5477988bkc.83.1368441023929; Mon, 13 May 2013 03:30:23 -0700 (PDT) Received: from [172.16.26.11] ([5.69.56.103]) by mx.google.com with ESMTPSA id x5sm1916196bkh.15.2013.05.13.03.30.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 May 2013 03:30:22 -0700 (PDT) Message-ID: <5190C0BC.5060008@xen.org> Date: Mon, 13 May 2013 11:30:20 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" Subject: [XenARM] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) 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 Dear Community Members, as part of the move of Xen to the Linux Foundation, I have made a few proposals for Governance changes on the Xen Project mailing lists in the last few weeks. To avoid voting fatigue, several proposals are up for review or voting: - For vote:Xen Project Governance v2 at http://www.xenproject.org/component/content/article/80-developers/136-governance-v2-proposal.html - For vote:Mailing List Conventions v1 at http://www.xenproject.org/component/content/article/80-developers/139-mailing-list-conventions.html - For vote: Dates and Locations for 2014 Events (see below) Regards Lars Voting for Proposals ==================== Two proposals Xen Project Governance v2 and Mailing List Conventions v1 are up for vote using this voting form (http://www.xenproject.org/component/content/article/98-developers/vote/127-vote-governance-v2-and-mailing-list-conventions-v1.html). As the two proposals affect all Xen Project teams, all maintainers, committers and project leads of mature projects and the community manager can vote. The vote will be open until May 20, 2013. Voting for Events ================= As it is very hard to book event space on short notice, I wanted to ask you all where to hold Xen Project user and developer events in 2014. Earlier this year, there was a debate whether we should rotate Xen Events around the globe. The answer was a very strong*yes*. As we have a Hackathon and Xen Developer Summit in Europe this year, Europe will not be an option for a developer event in 2014. Rather than creating a voting form, I decided to use the voting feature on the newxenproject.org website. To vote, you need to create an account. If you have difficulties, let me know. The poll isat http://www.xenproject.org/help/questions-and-answers/vote-on-2014-event-locations.html. The vote will stay open until the middle of June. _______________________________________________ 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 May 13 12:11:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 May 2013 12:11: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 1UbrbX-0006iW-5U; Mon, 13 May 2013 12:11:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UbrbV-0006iB-NT; Mon, 13 May 2013 12:11:45 +0000 Received: from [85.158.139.211:27217] by server-7.bemta-5.messagelabs.com id C8/B2-12828-088D0915; Mon, 13 May 2013 12:11:44 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1368447079!22729479!1 X-Originating-IP: [209.85.214.53] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27331 invoked from network); 13 May 2013 12:11:19 -0000 Received: from mail-bk0-f53.google.com (HELO mail-bk0-f53.google.com) (209.85.214.53) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 13 May 2013 12:11:19 -0000 Received: by mail-bk0-f53.google.com with SMTP id mx1so211320bkb.12 for ; Mon, 13 May 2013 05:11:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hLmuV24RrlGz0u4Mc10CI0AcPqgjTUoU/0+2CVqcUso=; b=z2UGVO7QEP52PJXVnIclCaRLw6Sl1O4/wRsSMJ8Hw8snYpxV9SpW1fhL5h+SaNXf5S wNkettM4u87hUc75DJ3uHj12NEHdobKyyHGpec+OtoOdp3RtOC/LmKvCeTNXNnomfgbU hlmiIyVQ7xyerc81oSoLwl/c6JCGD592NJIkTuMqJfiN9m06yABIjbWHr7wYzYLQ6NYC 6Az29eCCCdWyrkf8k1FqAyuZQSe3IQPNxaudkfoDGP8HTR/vgamte/JtwWRwscKfVRR5 obaWfyyPYepl/UroeJtw4y9rtrmS8ChjK93fEhgS1O/KsF4wpm3HR3XLFmoyDrBwlNVV NegA== X-Received: by 10.205.128.68 with SMTP id hd4mr5624556bkc.23.1368447079436; Mon, 13 May 2013 05:11:19 -0700 (PDT) Received: from [172.16.26.11] ([5.69.56.103]) by mx.google.com with ESMTPSA id f14sm2070115bky.16.2013.05.13.05.11.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 May 2013 05:11:18 -0700 (PDT) Message-ID: <5190D855.2020608@xen.org> Date: Mon, 13 May 2013 13:11:01 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: lars.kurth@xen.org References: <5190C0BC.5060008@xen.org> In-Reply-To: <5190C0BC.5060008@xen.org> Cc: "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) 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 On 13/05/2013 11:30, Lars Kurth wrote: > Dear Community Members, > > ... To avoid voting fatigue, several proposals are up for review or > voting: I created a slight confusion here by taking the blog post at http://blog.xen.org/index.php/2013/05/13/xen-project-governance-changes-for-review-and-vote/ and not removing "for review" from it. The *only* proposal that is for review has been sent out separately on friday to xen-devel and xen-users named "[Final Community Review] Xen Security Problem Response Process v2" (see http://lists.xen.org/archives/html/xen-devel/2013-05/msg01243.html). All proposals in this mail are for voting, with the original discussions x-reffed in http://blog.xen.org/index.php/2013/05/13/xen-project-governance-changes-for-review-and-vote/ Regards 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 Mon May 13 12:11:51 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 May 2013 12:11: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 1UbrbX-0006iW-5U; Mon, 13 May 2013 12:11:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UbrbV-0006iB-NT; Mon, 13 May 2013 12:11:45 +0000 Received: from [85.158.139.211:27217] by server-7.bemta-5.messagelabs.com id C8/B2-12828-088D0915; Mon, 13 May 2013 12:11:44 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1368447079!22729479!1 X-Originating-IP: [209.85.214.53] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27331 invoked from network); 13 May 2013 12:11:19 -0000 Received: from mail-bk0-f53.google.com (HELO mail-bk0-f53.google.com) (209.85.214.53) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 13 May 2013 12:11:19 -0000 Received: by mail-bk0-f53.google.com with SMTP id mx1so211320bkb.12 for ; Mon, 13 May 2013 05:11:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:reply-to:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hLmuV24RrlGz0u4Mc10CI0AcPqgjTUoU/0+2CVqcUso=; b=z2UGVO7QEP52PJXVnIclCaRLw6Sl1O4/wRsSMJ8Hw8snYpxV9SpW1fhL5h+SaNXf5S wNkettM4u87hUc75DJ3uHj12NEHdobKyyHGpec+OtoOdp3RtOC/LmKvCeTNXNnomfgbU hlmiIyVQ7xyerc81oSoLwl/c6JCGD592NJIkTuMqJfiN9m06yABIjbWHr7wYzYLQ6NYC 6Az29eCCCdWyrkf8k1FqAyuZQSe3IQPNxaudkfoDGP8HTR/vgamte/JtwWRwscKfVRR5 obaWfyyPYepl/UroeJtw4y9rtrmS8ChjK93fEhgS1O/KsF4wpm3HR3XLFmoyDrBwlNVV NegA== X-Received: by 10.205.128.68 with SMTP id hd4mr5624556bkc.23.1368447079436; Mon, 13 May 2013 05:11:19 -0700 (PDT) Received: from [172.16.26.11] ([5.69.56.103]) by mx.google.com with ESMTPSA id f14sm2070115bky.16.2013.05.13.05.11.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 May 2013 05:11:18 -0700 (PDT) Message-ID: <5190D855.2020608@xen.org> Date: Mon, 13 May 2013 13:11:01 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: lars.kurth@xen.org References: <5190C0BC.5060008@xen.org> In-Reply-To: <5190C0BC.5060008@xen.org> Cc: "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) 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 On 13/05/2013 11:30, Lars Kurth wrote: > Dear Community Members, > > ... To avoid voting fatigue, several proposals are up for review or > voting: I created a slight confusion here by taking the blog post at http://blog.xen.org/index.php/2013/05/13/xen-project-governance-changes-for-review-and-vote/ and not removing "for review" from it. The *only* proposal that is for review has been sent out separately on friday to xen-devel and xen-users named "[Final Community Review] Xen Security Problem Response Process v2" (see http://lists.xen.org/archives/html/xen-devel/2013-05/msg01243.html). All proposals in this mail are for voting, with the original discussions x-reffed in http://blog.xen.org/index.php/2013/05/13/xen-project-governance-changes-for-review-and-vote/ Regards 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 Mon May 13 13:17:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 May 2013 13:17: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 1Ubsd7-0000os-LQ; Mon, 13 May 2013 13:17:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ubsd6-0000od-Vu for xen-arm@lists.xen.org; Mon, 13 May 2013 13:17:29 +0000 Received: from [85.158.137.99:65286] by server-1.bemta-3.messagelabs.com id 61/D0-20211-6E7E0915; Mon, 13 May 2013 13:17:26 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1368450995!21663366!1 X-Originating-IP: [209.85.160.51] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4024 invoked from network); 13 May 2013 13:16:37 -0000 Received: from mail-pb0-f51.google.com (HELO mail-pb0-f51.google.com) (209.85.160.51) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 13 May 2013 13:16:37 -0000 Received: by mail-pb0-f51.google.com with SMTP id wy7so4433684pbc.38 for ; Mon, 13 May 2013 06:16:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=2zA8yZ7SfbdS2nAglxWR/zcOaVbZgTjl69fNdeNzK+s=; b=FlkEpp/HXAQanNNMobDPnhOJn++Z4JDiIo55sKx2ExEXjZOHtr/SKo9MBb2+MU/+ek 6eM0grDPDjRCYRpCs6c3MoqJTmd2Gzgr26JqDI6AEw0F9eC9sg7FHhnye+i2zmwOMXTJ AymWHH+L5EdlDh3EtnbsHzZhOeqEeib0nY5OxZWtdzMAup2PQzoLzSnQvTtQTdS5mHGi JaxDDh12eDabVbE0v4HbTWHaYwvSoZwjoh5eBRCpjxgvfL8FCWhBoMwdF8nlQqEcetkg QKVssc9ZB3zBbzuyiJeBN+3ORt9EOS3VGbQ11CEw1xpO6NeUwh3jUZlDHX/oYRoxzySc EXxg== X-Received: by 10.66.250.131 with SMTP id zc3mr11669762pac.157.1368450994672; Mon, 13 May 2013 06:16:34 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id fm2sm14987924pab.13.2013.05.13.06.16.31 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 13 May 2013 06:16:33 -0700 (PDT) Date: Mon, 13 May 2013 21:12:51 +0800 From: Chen Baozi To: Stefano Stabellini Message-ID: <20130513131251.GA21131@cbz-workstation> References: <20130324070650.GA9800@cbz-workstation> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm , xen-devel@lists.xensource.com, Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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 Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > On Sun, 24 Mar 2013, Chen Baozi wrote: >> Hi all, >> >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to >> ARM (Ian's GSoC idea this year). >> >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to >> the guest through ESI register. And Mini-OS would use this structure as the >> argument of start_kernel. However, I didn't see codes handle the >> start_info_t on ARM side. Instead, I see a more standard protocal when >> booting ARM's dom0, which follows linux kernel bootstrap rules: >> >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer >> >> Does it mean that Xen for ARM does not use the start_info_t to pass >> information when booting PV guest? >> Or did I miss something important? > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > not exactly like x86 PV guests. > The information present in the start_info page are either available via > device tree or no used on ARM. I noticed that in arch_domain_create() for arm there are codes allocating xen heap pages for domain->shared_info: arch_domain_create: if ((d->shared_info = alloc_xenheap_pages(0, 0)) == NULL) But it seems it is used nowhere and even not mapped by libxc: int arch_setup_bootlate(struct xc_dom_image *dom) { /* XXX * map shared info * map grant tables * setup shared info */ return 0; } So my question is what is the role of shared_info page in arm? And is there any relations between shared_info and start_info? Thanks. Chen 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 May 13 13:17:34 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 May 2013 13:17: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 1Ubsd7-0000os-LQ; Mon, 13 May 2013 13:17:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ubsd6-0000od-Vu for xen-arm@lists.xen.org; Mon, 13 May 2013 13:17:29 +0000 Received: from [85.158.137.99:65286] by server-1.bemta-3.messagelabs.com id 61/D0-20211-6E7E0915; Mon, 13 May 2013 13:17:26 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1368450995!21663366!1 X-Originating-IP: [209.85.160.51] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4024 invoked from network); 13 May 2013 13:16:37 -0000 Received: from mail-pb0-f51.google.com (HELO mail-pb0-f51.google.com) (209.85.160.51) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 13 May 2013 13:16:37 -0000 Received: by mail-pb0-f51.google.com with SMTP id wy7so4433684pbc.38 for ; Mon, 13 May 2013 06:16:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=2zA8yZ7SfbdS2nAglxWR/zcOaVbZgTjl69fNdeNzK+s=; b=FlkEpp/HXAQanNNMobDPnhOJn++Z4JDiIo55sKx2ExEXjZOHtr/SKo9MBb2+MU/+ek 6eM0grDPDjRCYRpCs6c3MoqJTmd2Gzgr26JqDI6AEw0F9eC9sg7FHhnye+i2zmwOMXTJ AymWHH+L5EdlDh3EtnbsHzZhOeqEeib0nY5OxZWtdzMAup2PQzoLzSnQvTtQTdS5mHGi JaxDDh12eDabVbE0v4HbTWHaYwvSoZwjoh5eBRCpjxgvfL8FCWhBoMwdF8nlQqEcetkg QKVssc9ZB3zBbzuyiJeBN+3ORt9EOS3VGbQ11CEw1xpO6NeUwh3jUZlDHX/oYRoxzySc EXxg== X-Received: by 10.66.250.131 with SMTP id zc3mr11669762pac.157.1368450994672; Mon, 13 May 2013 06:16:34 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id fm2sm14987924pab.13.2013.05.13.06.16.31 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 13 May 2013 06:16:33 -0700 (PDT) Date: Mon, 13 May 2013 21:12:51 +0800 From: Chen Baozi To: Stefano Stabellini Message-ID: <20130513131251.GA21131@cbz-workstation> References: <20130324070650.GA9800@cbz-workstation> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm , xen-devel@lists.xensource.com, Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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 Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > On Sun, 24 Mar 2013, Chen Baozi wrote: >> Hi all, >> >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to >> ARM (Ian's GSoC idea this year). >> >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to >> the guest through ESI register. And Mini-OS would use this structure as the >> argument of start_kernel. However, I didn't see codes handle the >> start_info_t on ARM side. Instead, I see a more standard protocal when >> booting ARM's dom0, which follows linux kernel bootstrap rules: >> >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer >> >> Does it mean that Xen for ARM does not use the start_info_t to pass >> information when booting PV guest? >> Or did I miss something important? > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > not exactly like x86 PV guests. > The information present in the start_info page are either available via > device tree or no used on ARM. I noticed that in arch_domain_create() for arm there are codes allocating xen heap pages for domain->shared_info: arch_domain_create: if ((d->shared_info = alloc_xenheap_pages(0, 0)) == NULL) But it seems it is used nowhere and even not mapped by libxc: int arch_setup_bootlate(struct xc_dom_image *dom) { /* XXX * map shared info * map grant tables * setup shared info */ return 0; } So my question is what is the role of shared_info page in arm? And is there any relations between shared_info and start_info? Thanks. Chen 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 May 13 13:25:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 May 2013 13:25:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UbslI-0001Ib-51; Mon, 13 May 2013 13:25:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UbslG-0001IH-0L for xen-arm@lists.xen.org; Mon, 13 May 2013 13:25:54 +0000 Received: from [85.158.143.99:33607] by server-2.bemta-4.messagelabs.com id 6E/D0-27124-1E9E0915; Mon, 13 May 2013 13:25:53 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1368451551!23635890!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13785 invoked from network); 13 May 2013 13:25:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 May 2013 13:25:52 -0000 X-IronPort-AV: E=Sophos;i="4.87,552,1363132800"; d="scan'208";a="4497854" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 May 2013 13:16:54 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 13 May 2013 14:25:50 +0100 Message-ID: <1368451548.537.101.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 13 May 2013 14:25:48 +0100 In-Reply-To: <20130513131251.GA21131@cbz-workstation> References: <20130324070650.GA9800@cbz-workstation> <20130513131251.GA21131@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-arm , "xen-devel@lists.xensource.com" , Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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-05-13 at 14:12 +0100, Chen Baozi wrote: > On Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > > On Sun, 24 Mar 2013, Chen Baozi wrote: > >> Hi all, > >> > >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to > >> ARM (Ian's GSoC idea this year). > >> > >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to > >> the guest through ESI register. And Mini-OS would use this structure as the > >> argument of start_kernel. However, I didn't see codes handle the > >> start_info_t on ARM side. Instead, I see a more standard protocal when > >> booting ARM's dom0, which follows linux kernel bootstrap rules: > >> > >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer > >> > >> Does it mean that Xen for ARM does not use the start_info_t to pass > >> information when booting PV guest? > >> Or did I miss something important? > > > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > > not exactly like x86 PV guests. > > The information present in the start_info page are either available via > > device tree or no used on ARM. > > I noticed that in arch_domain_create() for arm there are codes > allocating xen heap pages for domain->shared_info: > > arch_domain_create: > if ((d->shared_info = alloc_xenheap_pages(0, 0)) == NULL) > > But it seems it is used nowhere and even not mapped by libxc: > > int arch_setup_bootlate(struct xc_dom_image *dom) > { > /* XXX > * map shared info > * map grant tables > * setup shared info > */ > return 0; > } This comment is out of date, in fact on ARM the guest itself takes care of mapping these things by using XENMEM_add_to_physmap with XENMAPSPACE_shared_info et al. > So my question is what is the role of shared_info page in arm? It is mostly the same as on x86 with a couple of exceptions which spring to mind. Firstly XEN_LEGACY_MAX_VCPUS == 1 on ARM so guests are required to use VCPUOP_register_vcpu_info for secondary CPUs instead of relying on some number of vcpu_info's being present in the shared info. Secondly we don't actually implement the wall-clock stuff there (yet). The bit we currently use is the evtchn_* stuff. > And is there any relations between shared_info and start_info? Not really no, one is start of day and one is runtime. 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 May 13 13:25:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 13 May 2013 13:25:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UbslI-0001Ib-51; Mon, 13 May 2013 13:25:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UbslG-0001IH-0L for xen-arm@lists.xen.org; Mon, 13 May 2013 13:25:54 +0000 Received: from [85.158.143.99:33607] by server-2.bemta-4.messagelabs.com id 6E/D0-27124-1E9E0915; Mon, 13 May 2013 13:25:53 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1368451551!23635890!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13785 invoked from network); 13 May 2013 13:25:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 May 2013 13:25:52 -0000 X-IronPort-AV: E=Sophos;i="4.87,552,1363132800"; d="scan'208";a="4497854" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 May 2013 13:16:54 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 13 May 2013 14:25:50 +0100 Message-ID: <1368451548.537.101.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 13 May 2013 14:25:48 +0100 In-Reply-To: <20130513131251.GA21131@cbz-workstation> References: <20130324070650.GA9800@cbz-workstation> <20130513131251.GA21131@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-arm , "xen-devel@lists.xensource.com" , Samuel Thibault Subject: Re: [XenARM] Question about booting parameter of Mini-OS for ARM 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-05-13 at 14:12 +0100, Chen Baozi wrote: > On Mar 25, 2013, at 6:00 PM, Stefano Stabellini wrote: > > On Sun, 24 Mar 2013, Chen Baozi wrote: > >> Hi all, > >> > >> I'm reading Mini-OS's codes and to estimate the amount of work porting it to > >> ARM (Ian's GSoC idea this year). > >> > >> While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to > >> the guest through ESI register. And Mini-OS would use this structure as the > >> argument of start_kernel. However, I didn't see codes handle the > >> start_info_t on ARM side. Instead, I see a more standard protocal when > >> booting ARM's dom0, which follows linux kernel bootstrap rules: > >> > >> r0 = 0, r1 = machine nr, r2 = atags or dtb pointer > >> > >> Does it mean that Xen for ARM does not use the start_info_t to pass > >> information when booting PV guest? > >> Or did I miss something important? > > > > That's right, we don't use start_info_t on ARM, in fact ARM guests are > > not exactly like x86 PV guests. > > The information present in the start_info page are either available via > > device tree or no used on ARM. > > I noticed that in arch_domain_create() for arm there are codes > allocating xen heap pages for domain->shared_info: > > arch_domain_create: > if ((d->shared_info = alloc_xenheap_pages(0, 0)) == NULL) > > But it seems it is used nowhere and even not mapped by libxc: > > int arch_setup_bootlate(struct xc_dom_image *dom) > { > /* XXX > * map shared info > * map grant tables > * setup shared info > */ > return 0; > } This comment is out of date, in fact on ARM the guest itself takes care of mapping these things by using XENMEM_add_to_physmap with XENMAPSPACE_shared_info et al. > So my question is what is the role of shared_info page in arm? It is mostly the same as on x86 with a couple of exceptions which spring to mind. Firstly XEN_LEGACY_MAX_VCPUS == 1 on ARM so guests are required to use VCPUOP_register_vcpu_info for secondary CPUs instead of relying on some number of vcpu_info's being present in the shared info. Secondly we don't actually implement the wall-clock stuff there (yet). The bit we currently use is the evtchn_* stuff. > And is there any relations between shared_info and start_info? Not really no, one is start of day and one is runtime. 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 Thu May 16 09:53:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 May 2013 09:53:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ucusg-00007g-51; Thu, 16 May 2013 09:53:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ucusd-00007P-ET for xen-arm@lists.xen.org; Thu, 16 May 2013 09:53:47 +0000 Received: from [85.158.139.83:8793] by server-10.bemta-5.messagelabs.com id FF/A4-19016-AACA4915; Thu, 16 May 2013 09:53:46 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1368698024!26942164!1 X-Originating-IP: [209.85.160.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5870 invoked from network); 16 May 2013 09:53:45 -0000 Received: from mail-pb0-f54.google.com (HELO mail-pb0-f54.google.com) (209.85.160.54) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 May 2013 09:53:45 -0000 Received: by mail-pb0-f54.google.com with SMTP id ro8so2167008pbb.41 for ; Thu, 16 May 2013 02:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:mime-version :content-type:content-disposition:user-agent; bh=boN8LS0vUk10PdczOCeXsXgAU/3v+iNJTGQ7AR3jK5U=; b=S0IoAZqLHj9QnlKje4rlMTOwOB+jpUnD2n/l9QRymFAtvSqWlJy0D+M7t/eU7PSXZ4 BML2c6lb6uQYfDYgT1FaTBwC8NN6Jw3Eh5ZiiAH9ej3xf6uRLx1UkMRzCXEUINC7l5F2 F5dZ4NvIrTvR1ZvhtVqJRU2K8rC39ii7oHAK31IBiNENauic8gRXZWVZY0QzfTH4JCkJ kyawualjLa2RH3mXW7PSvHzF8yX5Fm20iRUJzCBtCjqZRmK4pdHXnjbE6rf9nDXKK5el PsCL51TdnNDYxf8qpl1rPsayAnavh2OWBJKA+vVuQS1jKti9/qtFwS/tIB+GEVy/jHEx WbIg== X-Received: by 10.67.4.129 with SMTP id ce1mr42813888pad.107.1368698023650; Thu, 16 May 2013 02:53:43 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id cq1sm6211685pbc.13.2013.05.16.02.53.41 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 16 May 2013 02:53:43 -0700 (PDT) Date: Thu, 16 May 2013 17:49:56 +0800 From: Chen Baozi To: Ian.Campbell@citrix.com Message-ID: <20130516094956.GA19578@cbz-workstation> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: [XenARM] Cannot create mini-os guest for arm64 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 Ian, I've done the basic interfaces/framework to pass mini-os build on arm64, which still needs lots of implementation to work properly. Then I tried to create the mini-os guest for arm64 on Fast Model environment to drive the following porting. (I know it must not work at present, but it would give some feedback through the test.) However, when I tried to "xl create" the mini-os, it reported the following errors: Parsing config from /etc/xen/stubdom.pvlinux xc: error: panic: xc_dom_core.c:608: xc_dom_find_arch_hooks: not found (type xen-3.0-unknown): Invalid kernel xc: error: panic: xc_dom_core.c:763: xc_dom_mem_init: arch hooks not set: Internal error libxl: error: libxl_dom.c:384:libxl__build_pv: xc_dom_mem_init failed: No such file or directory libxl: error: libxl_create.c:908:domcreate_rebuild_done: cannot (re-)build domain: -3 And the stubdom.pvlinux configs is: # Guest name name = "mini-os.pvlinux" # Kernel image to boot kernel = "/minios/mini-os.gz" # Initial memory allocation (MB) memory = 128 # Number of VCPUS vcpus = 1 Any ideas? Thanks. Chen 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 Thu May 16 09:53:54 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 May 2013 09:53:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ucusg-00007g-51; Thu, 16 May 2013 09:53:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ucusd-00007P-ET for xen-arm@lists.xen.org; Thu, 16 May 2013 09:53:47 +0000 Received: from [85.158.139.83:8793] by server-10.bemta-5.messagelabs.com id FF/A4-19016-AACA4915; Thu, 16 May 2013 09:53:46 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1368698024!26942164!1 X-Originating-IP: [209.85.160.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5870 invoked from network); 16 May 2013 09:53:45 -0000 Received: from mail-pb0-f54.google.com (HELO mail-pb0-f54.google.com) (209.85.160.54) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 May 2013 09:53:45 -0000 Received: by mail-pb0-f54.google.com with SMTP id ro8so2167008pbb.41 for ; Thu, 16 May 2013 02:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:mime-version :content-type:content-disposition:user-agent; bh=boN8LS0vUk10PdczOCeXsXgAU/3v+iNJTGQ7AR3jK5U=; b=S0IoAZqLHj9QnlKje4rlMTOwOB+jpUnD2n/l9QRymFAtvSqWlJy0D+M7t/eU7PSXZ4 BML2c6lb6uQYfDYgT1FaTBwC8NN6Jw3Eh5ZiiAH9ej3xf6uRLx1UkMRzCXEUINC7l5F2 F5dZ4NvIrTvR1ZvhtVqJRU2K8rC39ii7oHAK31IBiNENauic8gRXZWVZY0QzfTH4JCkJ kyawualjLa2RH3mXW7PSvHzF8yX5Fm20iRUJzCBtCjqZRmK4pdHXnjbE6rf9nDXKK5el PsCL51TdnNDYxf8qpl1rPsayAnavh2OWBJKA+vVuQS1jKti9/qtFwS/tIB+GEVy/jHEx WbIg== X-Received: by 10.67.4.129 with SMTP id ce1mr42813888pad.107.1368698023650; Thu, 16 May 2013 02:53:43 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id cq1sm6211685pbc.13.2013.05.16.02.53.41 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 16 May 2013 02:53:43 -0700 (PDT) Date: Thu, 16 May 2013 17:49:56 +0800 From: Chen Baozi To: Ian.Campbell@citrix.com Message-ID: <20130516094956.GA19578@cbz-workstation> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: [XenARM] Cannot create mini-os guest for arm64 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 Ian, I've done the basic interfaces/framework to pass mini-os build on arm64, which still needs lots of implementation to work properly. Then I tried to create the mini-os guest for arm64 on Fast Model environment to drive the following porting. (I know it must not work at present, but it would give some feedback through the test.) However, when I tried to "xl create" the mini-os, it reported the following errors: Parsing config from /etc/xen/stubdom.pvlinux xc: error: panic: xc_dom_core.c:608: xc_dom_find_arch_hooks: not found (type xen-3.0-unknown): Invalid kernel xc: error: panic: xc_dom_core.c:763: xc_dom_mem_init: arch hooks not set: Internal error libxl: error: libxl_dom.c:384:libxl__build_pv: xc_dom_mem_init failed: No such file or directory libxl: error: libxl_create.c:908:domcreate_rebuild_done: cannot (re-)build domain: -3 And the stubdom.pvlinux configs is: # Guest name name = "mini-os.pvlinux" # Kernel image to boot kernel = "/minios/mini-os.gz" # Initial memory allocation (MB) memory = 128 # Number of VCPUS vcpus = 1 Any ideas? Thanks. Chen 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 Thu May 16 14:57:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 May 2013 14:57:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UczcN-0000yt-C2; Thu, 16 May 2013 14:57:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UczcL-0000yn-Od for xen-arm@lists.xen.org; Thu, 16 May 2013 14:57:17 +0000 Received: from [85.158.143.99:45104] by server-3.bemta-4.messagelabs.com id 5E/B6-02015-DC3F4915; Thu, 16 May 2013 14:57:17 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1368716234!28609623!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4873 invoked from network); 16 May 2013 14:57:16 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 May 2013 14:57:16 -0000 X-IronPort-AV: E=Sophos;i="4.87,684,1363132800"; d="scan'208";a="24419239" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 16 May 2013 14:57:14 +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.3; Thu, 16 May 2013 10:57:14 -0400 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[127.0.0.1]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UczMm-0001OD-PM; Thu, 16 May 2013 15:41:13 +0100 Message-ID: <1368715271.24012.12.camel@hastur.hellion.org.uk> From: Ian Campbell To: Chen Baozi Date: Thu, 16 May 2013 15:41:11 +0100 In-Reply-To: <20130516094956.GA19578@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > Hi Ian, > > I've done the basic interfaces/framework to pass mini-os build on arm64, > which still needs lots of implementation to work properly. > > Then I tried to create the mini-os guest for arm64 on Fast Model environment > to drive the following porting. (I know it must not work at present, but it > would give some feedback through the test.) However, when I tried to "xl > create" the mini-os, it reported the following errors: There are some issues with loading guests from ELF (rather than zImage) kernels on ARM. I think Sander (CCd) got to the bottom of it and may even have posted a patch or two? 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 Thu May 16 14:57:22 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 May 2013 14:57:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UczcN-0000yt-C2; Thu, 16 May 2013 14:57:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UczcL-0000yn-Od for xen-arm@lists.xen.org; Thu, 16 May 2013 14:57:17 +0000 Received: from [85.158.143.99:45104] by server-3.bemta-4.messagelabs.com id 5E/B6-02015-DC3F4915; Thu, 16 May 2013 14:57:17 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1368716234!28609623!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4873 invoked from network); 16 May 2013 14:57:16 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 May 2013 14:57:16 -0000 X-IronPort-AV: E=Sophos;i="4.87,684,1363132800"; d="scan'208";a="24419239" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 16 May 2013 14:57:14 +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.3; Thu, 16 May 2013 10:57:14 -0400 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[127.0.0.1]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UczMm-0001OD-PM; Thu, 16 May 2013 15:41:13 +0100 Message-ID: <1368715271.24012.12.camel@hastur.hellion.org.uk> From: Ian Campbell To: Chen Baozi Date: Thu, 16 May 2013 15:41:11 +0100 In-Reply-To: <20130516094956.GA19578@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > Hi Ian, > > I've done the basic interfaces/framework to pass mini-os build on arm64, > which still needs lots of implementation to work properly. > > Then I tried to create the mini-os guest for arm64 on Fast Model environment > to drive the following porting. (I know it must not work at present, but it > would give some feedback through the test.) However, when I tried to "xl > create" the mini-os, it reported the following errors: There are some issues with loading guests from ELF (rather than zImage) kernels on ARM. I think Sander (CCd) got to the bottom of it and may even have posted a patch or two? 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 Thu May 16 15:34:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 May 2013 15:34:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud0CK-0002Vf-Qh; Thu, 16 May 2013 15:34:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud0CJ-0002VN-NV for xen-arm@lists.xen.org; Thu, 16 May 2013 15:34:27 +0000 Received: from [85.158.138.51:43153] by server-9.bemta-3.messagelabs.com id 4E/48-29224-28CF4915; Thu, 16 May 2013 15:34:26 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1368718462!21372391!1 X-Originating-IP: [209.85.220.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1709 invoked from network); 16 May 2013 15:34:24 -0000 Received: from mail-pa0-f47.google.com (HELO mail-pa0-f47.google.com) (209.85.220.47) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 May 2013 15:34:24 -0000 Received: by mail-pa0-f47.google.com with SMTP id kl13so2634258pab.34 for ; Thu, 16 May 2013 08:34:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=7Odbj34J7Ro7EsDaZgk17z1B8dYJN+8Qbk1nZIGzMOw=; b=gu2vKBTpMVTe7/93qaCsKUBucorUDZNAxrXVQ4V3U85O5ISUgqJnrf7iv4cK2tpjfn LlpDkJF0mH2V21onWOczws3BSbiiq1fy7I8QeKa5PQWyMC6F/rCM7vCralkAffGbkCyb AHP6UWCjSVVBnvRuDeXmafdLm4mTOmTQrwn5v37aB5IAhkAIkV6aOCFXXsGKIbCPbw1Q Tq0PN8opbbHveBz3i7p85JwVJ8VvEahJQRcQ85jim6NucoxsKo+O7wY2c/OMreXJ7Yq9 GUzTXMDGytFDTjs3Owf6eqCepeKNNDsbaGWoqh1N/7gjuXF6lWWpyabw/tuYOzdGO5X3 Hq9Q== X-Received: by 10.68.40.200 with SMTP id z8mr42765013pbk.210.1368718462629; Thu, 16 May 2013 08:34:22 -0700 (PDT) Received: from [192.168.1.102] ([113.247.2.155]) by mx.google.com with ESMTPSA id gi2sm7230138pbb.2.2013.05.16.08.34.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 08:34:21 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1368715271.24012.12.camel@hastur.hellion.org.uk> Date: Thu, 16 May 2013 23:34:13 +0800 Message-Id: References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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 May 16, 2013, at 10:41 PM, Ian Campbell wrote: > On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: >> Hi Ian, >> >> I've done the basic interfaces/framework to pass mini-os build on arm64, >> which still needs lots of implementation to work properly. >> >> Then I tried to create the mini-os guest for arm64 on Fast Model environment >> to drive the following porting. (I know it must not work at present, but it >> would give some feedback through the test.) However, when I tried to "xl >> create" the mini-os, it reported the following errors: > > There are some issues with loading guests from ELF (rather than zImage) > kernels on ARM. Is it possible because of there is no arm64 "guest_type" of xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type related codes in libxc files. Baozi. > I think Sander (CCd) got to the bottom of it and may > even have posted a patch or two? > > 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 Thu May 16 15:34:32 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 May 2013 15:34:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud0CK-0002Vf-Qh; Thu, 16 May 2013 15:34:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud0CJ-0002VN-NV for xen-arm@lists.xen.org; Thu, 16 May 2013 15:34:27 +0000 Received: from [85.158.138.51:43153] by server-9.bemta-3.messagelabs.com id 4E/48-29224-28CF4915; Thu, 16 May 2013 15:34:26 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1368718462!21372391!1 X-Originating-IP: [209.85.220.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1709 invoked from network); 16 May 2013 15:34:24 -0000 Received: from mail-pa0-f47.google.com (HELO mail-pa0-f47.google.com) (209.85.220.47) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 May 2013 15:34:24 -0000 Received: by mail-pa0-f47.google.com with SMTP id kl13so2634258pab.34 for ; Thu, 16 May 2013 08:34:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=7Odbj34J7Ro7EsDaZgk17z1B8dYJN+8Qbk1nZIGzMOw=; b=gu2vKBTpMVTe7/93qaCsKUBucorUDZNAxrXVQ4V3U85O5ISUgqJnrf7iv4cK2tpjfn LlpDkJF0mH2V21onWOczws3BSbiiq1fy7I8QeKa5PQWyMC6F/rCM7vCralkAffGbkCyb AHP6UWCjSVVBnvRuDeXmafdLm4mTOmTQrwn5v37aB5IAhkAIkV6aOCFXXsGKIbCPbw1Q Tq0PN8opbbHveBz3i7p85JwVJ8VvEahJQRcQ85jim6NucoxsKo+O7wY2c/OMreXJ7Yq9 GUzTXMDGytFDTjs3Owf6eqCepeKNNDsbaGWoqh1N/7gjuXF6lWWpyabw/tuYOzdGO5X3 Hq9Q== X-Received: by 10.68.40.200 with SMTP id z8mr42765013pbk.210.1368718462629; Thu, 16 May 2013 08:34:22 -0700 (PDT) Received: from [192.168.1.102] ([113.247.2.155]) by mx.google.com with ESMTPSA id gi2sm7230138pbb.2.2013.05.16.08.34.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 08:34:21 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1368715271.24012.12.camel@hastur.hellion.org.uk> Date: Thu, 16 May 2013 23:34:13 +0800 Message-Id: References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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 May 16, 2013, at 10:41 PM, Ian Campbell wrote: > On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: >> Hi Ian, >> >> I've done the basic interfaces/framework to pass mini-os build on arm64, >> which still needs lots of implementation to work properly. >> >> Then I tried to create the mini-os guest for arm64 on Fast Model environment >> to drive the following porting. (I know it must not work at present, but it >> would give some feedback through the test.) However, when I tried to "xl >> create" the mini-os, it reported the following errors: > > There are some issues with loading guests from ELF (rather than zImage) > kernels on ARM. Is it possible because of there is no arm64 "guest_type" of xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type related codes in libxc files. Baozi. > I think Sander (CCd) got to the bottom of it and may > even have posted a patch or two? > > 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 Thu May 16 16:32:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 May 2013 16:32:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud16Z-0005H8-8w; Thu, 16 May 2013 16:32:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud16X-0005H3-T7 for xen-arm@lists.xen.org; Thu, 16 May 2013 16:32:34 +0000 Received: from [85.158.139.211:40646] by server-8.bemta-5.messagelabs.com id 9F/45-29170-12A05915; Thu, 16 May 2013 16:32:33 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1368721950!18234452!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8149 invoked from network); 16 May 2013 16:32:32 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 May 2013 16:32:32 -0000 X-IronPort-AV: E=Sophos;i="4.87,684,1363132800"; d="scan'208";a="25647625" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 16 May 2013 16:32:30 +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.3; Thu, 16 May 2013 12:32:30 -0400 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[127.0.0.1]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1Ud0uk-00034B-6M; Thu, 16 May 2013 17:20:22 +0100 Message-ID: <1368721220.24012.18.camel@hastur.hellion.org.uk> From: Ian Campbell To: Chen Baozi Date: Thu, 16 May 2013 17:20:20 +0100 In-Reply-To: References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > > On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > >> Hi Ian, > >> > >> I've done the basic interfaces/framework to pass mini-os build on arm64, > >> which still needs lots of implementation to work properly. > >> > >> Then I tried to create the mini-os guest for arm64 on Fast Model environment > >> to drive the following porting. (I know it must not work at present, but it > >> would give some feedback through the test.) However, when I tried to "xl > >> create" the mini-os, it reported the following errors: > > > > There are some issues with loading guests from ELF (rather than zImage) > > kernels on ARM. > Is it possible because of there is no arm64 "guest_type" of > xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > related codes in libxc files. Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this before. Hrm, that does rather block you from doing arm64 mini-os. I posted a series to allow 64-bit dom0 a while back but we are currently frozen so it has been committed, but that's the obvious starting point for 64-bit guest support. I don't recall why you are looking at 64-bit minios rather than 32-bit, is that an option? A lot of the code should end up common. 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 Thu May 16 16:32:38 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 16 May 2013 16:32:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud16Z-0005H8-8w; Thu, 16 May 2013 16:32:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud16X-0005H3-T7 for xen-arm@lists.xen.org; Thu, 16 May 2013 16:32:34 +0000 Received: from [85.158.139.211:40646] by server-8.bemta-5.messagelabs.com id 9F/45-29170-12A05915; Thu, 16 May 2013 16:32:33 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1368721950!18234452!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8149 invoked from network); 16 May 2013 16:32:32 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 May 2013 16:32:32 -0000 X-IronPort-AV: E=Sophos;i="4.87,684,1363132800"; d="scan'208";a="25647625" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 16 May 2013 16:32:30 +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.3; Thu, 16 May 2013 12:32:30 -0400 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[127.0.0.1]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1Ud0uk-00034B-6M; Thu, 16 May 2013 17:20:22 +0100 Message-ID: <1368721220.24012.18.camel@hastur.hellion.org.uk> From: Ian Campbell To: Chen Baozi Date: Thu, 16 May 2013 17:20:20 +0100 In-Reply-To: References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > > On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > >> Hi Ian, > >> > >> I've done the basic interfaces/framework to pass mini-os build on arm64, > >> which still needs lots of implementation to work properly. > >> > >> Then I tried to create the mini-os guest for arm64 on Fast Model environment > >> to drive the following porting. (I know it must not work at present, but it > >> would give some feedback through the test.) However, when I tried to "xl > >> create" the mini-os, it reported the following errors: > > > > There are some issues with loading guests from ELF (rather than zImage) > > kernels on ARM. > Is it possible because of there is no arm64 "guest_type" of > xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > related codes in libxc files. Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this before. Hrm, that does rather block you from doing arm64 mini-os. I posted a series to allow 64-bit dom0 a while back but we are currently frozen so it has been committed, but that's the obvious starting point for 64-bit guest support. I don't recall why you are looking at 64-bit minios rather than 32-bit, is that an option? A lot of the code should end up common. 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 Fri May 17 00:00:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 17 May 2013 00:00:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud869-0003ob-Nm; Fri, 17 May 2013 00:00:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud868-0003m6-QC for xen-arm@lists.xen.org; Fri, 17 May 2013 00:00:37 +0000 Received: from [85.158.139.83:49531] by server-3.bemta-5.messagelabs.com id 9A/CA-31108-32375915; Fri, 17 May 2013 00:00:35 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1368748827!27745490!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12794 invoked from network); 17 May 2013 00:00:29 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 May 2013 00:00:29 -0000 Received: by mail-pa0-f54.google.com with SMTP id kx1so3011274pab.13 for ; Thu, 16 May 2013 17:00:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=s9y71D8JVkGgzl8DCmbtwwPOk361PDSojXPGRWv1ZAg=; b=ytP6VMyobkD7jORkkP9TC20ot/Jg0q4VmjU1Sv31UaM9n3jNiTC5SMFcYhYtINoGj6 KX+OG1kEWPvL6LlfAvSPbJx7VfEubnD0hXWmhE4LJAiUWMOEd4hFFyD/SbbcISrI1Dw9 yNbXzN19w8lncEOpXUfFfiY92fpUxJv41lZdv7CcPLR1Qarcz8M1MinYL/qAXnYzp9rY UJRqA7d71rw30q8fFyd1dGNrFntWe2ihYw45/ZJTR3oKqXJ27zgJIk4LNxq4LByKrTg0 0xxWO3mjlqHUuqrrmMj2shrINpP3XEK8ZoGrxwKPVWvZH9q73tZW98E2HYE0XNjr4fD5 kaJA== X-Received: by 10.68.75.110 with SMTP id b14mr45862670pbw.89.1368748826966; Thu, 16 May 2013 17:00:26 -0700 (PDT) Received: from [192.168.1.102] ([113.247.2.155]) by mx.google.com with ESMTPSA id uq10sm8646601pbc.5.2013.05.16.17.00.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 17:00:26 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1368721220.24012.18.camel@hastur.hellion.org.uk> Date: Fri, 17 May 2013 08:00:22 +0800 Message-Id: <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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 May 17, 2013, at 12:20 AM, Ian Campbell wrote: > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: >> >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: >>>> Hi Ian, >>>> >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, >>>> which still needs lots of implementation to work properly. >>>> >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment >>>> to drive the following porting. (I know it must not work at present, but it >>>> would give some feedback through the test.) However, when I tried to "xl >>>> create" the mini-os, it reported the following errors: >>> >>> There are some issues with loading guests from ELF (rather than zImage) >>> kernels on ARM. >> Is it possible because of there is no arm64 "guest_type" of >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type >> related codes in libxc files. > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > before. Hrm, that does rather block you from doing arm64 mini-os. > > I posted a series to allow 64-bit dom0 a while back but we are currently > frozen so it has been committed, but that's the obvious starting point > for 64-bit guest support. > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > is that an option? A lot of the code should end up common. I did plan to start the work on arm32 at the very beginning. But The only platform of cortex-a15 I've got is the samsung's chromebook. I tried hard to run Xen on it but didn't succeed in the end due to the lack of debug method. At the same time, I've got an chance getting involved in a arm64 project of our lab so it is easy to have a FastModel license, which at least is a debugable platform for my at present. PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > 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 Fri May 17 00:00:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 17 May 2013 00:00:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud869-0003ob-Nm; Fri, 17 May 2013 00:00:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ud868-0003m6-QC for xen-arm@lists.xen.org; Fri, 17 May 2013 00:00:37 +0000 Received: from [85.158.139.83:49531] by server-3.bemta-5.messagelabs.com id 9A/CA-31108-32375915; Fri, 17 May 2013 00:00:35 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1368748827!27745490!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12794 invoked from network); 17 May 2013 00:00:29 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 May 2013 00:00:29 -0000 Received: by mail-pa0-f54.google.com with SMTP id kx1so3011274pab.13 for ; Thu, 16 May 2013 17:00:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=s9y71D8JVkGgzl8DCmbtwwPOk361PDSojXPGRWv1ZAg=; b=ytP6VMyobkD7jORkkP9TC20ot/Jg0q4VmjU1Sv31UaM9n3jNiTC5SMFcYhYtINoGj6 KX+OG1kEWPvL6LlfAvSPbJx7VfEubnD0hXWmhE4LJAiUWMOEd4hFFyD/SbbcISrI1Dw9 yNbXzN19w8lncEOpXUfFfiY92fpUxJv41lZdv7CcPLR1Qarcz8M1MinYL/qAXnYzp9rY UJRqA7d71rw30q8fFyd1dGNrFntWe2ihYw45/ZJTR3oKqXJ27zgJIk4LNxq4LByKrTg0 0xxWO3mjlqHUuqrrmMj2shrINpP3XEK8ZoGrxwKPVWvZH9q73tZW98E2HYE0XNjr4fD5 kaJA== X-Received: by 10.68.75.110 with SMTP id b14mr45862670pbw.89.1368748826966; Thu, 16 May 2013 17:00:26 -0700 (PDT) Received: from [192.168.1.102] ([113.247.2.155]) by mx.google.com with ESMTPSA id uq10sm8646601pbc.5.2013.05.16.17.00.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 17:00:26 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1368721220.24012.18.camel@hastur.hellion.org.uk> Date: Fri, 17 May 2013 08:00:22 +0800 Message-Id: <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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 May 17, 2013, at 12:20 AM, Ian Campbell wrote: > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: >> >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: >>>> Hi Ian, >>>> >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, >>>> which still needs lots of implementation to work properly. >>>> >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment >>>> to drive the following porting. (I know it must not work at present, but it >>>> would give some feedback through the test.) However, when I tried to "xl >>>> create" the mini-os, it reported the following errors: >>> >>> There are some issues with loading guests from ELF (rather than zImage) >>> kernels on ARM. >> Is it possible because of there is no arm64 "guest_type" of >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type >> related codes in libxc files. > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > before. Hrm, that does rather block you from doing arm64 mini-os. > > I posted a series to allow 64-bit dom0 a while back but we are currently > frozen so it has been committed, but that's the obvious starting point > for 64-bit guest support. > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > is that an option? A lot of the code should end up common. I did plan to start the work on arm32 at the very beginning. But The only platform of cortex-a15 I've got is the samsung's chromebook. I tried hard to run Xen on it but didn't succeed in the end due to the lack of debug method. At the same time, I've got an chance getting involved in a arm64 project of our lab so it is easy to have a FastModel license, which at least is a debugable platform for my at present. PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > 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 Fri May 17 09:26:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 17 May 2013 09:26:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdGvf-0000FC-3k; Fri, 17 May 2013 09:26:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdGvd-0000F0-Kg for xen-arm@lists.xen.org; Fri, 17 May 2013 09:26:21 +0000 Received: from [193.109.254.147:18781] by server-11.bemta-14.messagelabs.com id 6E/6E-09099-CB7F5915; Fri, 17 May 2013 09:26:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1368782771!8468414!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2854 invoked from network); 17 May 2013 09:26:13 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 May 2013 09:26:13 -0000 X-IronPort-AV: E=Sophos;i="4.87,690,1363132800"; d="scan'208";a="25805118" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 17 May 2013 09:26:11 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.3; Fri, 17 May 2013 05:26:10 -0400 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[127.0.0.1]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UdGvR-00025h-1W; Fri, 17 May 2013 10:26:09 +0100 Message-ID: <1368782768.24012.23.camel@hastur.hellion.org.uk> From: Ian Campbell To: Chen Baozi Date: Fri, 17 May 2013 10:26:08 +0100 In-Reply-To: <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-17 at 08:00 +0800, Chen Baozi wrote: > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > >> > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > >>>> Hi Ian, > >>>> > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > >>>> which still needs lots of implementation to work properly. > >>>> > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > >>>> to drive the following porting. (I know it must not work at present, but it > >>>> would give some feedback through the test.) However, when I tried to "xl > >>>> create" the mini-os, it reported the following errors: > >>> > >>> There are some issues with loading guests from ELF (rather than zImage) > >>> kernels on ARM. > >> Is it possible because of there is no arm64 "guest_type" of > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > >> related codes in libxc files. > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > frozen so it has been committed, but that's the obvious starting point > > for 64-bit guest support. > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > is that an option? A lot of the code should end up common. > I did plan to start the work on arm32 at the very beginning. But The > only platform of cortex-a15 I've got is the samsung's chromebook. I > tried hard to run Xen on it but didn't succeed in the end due to the > lack of debug method. At the same time, I've got an chance getting > involved in a arm64 project of our lab so it is easy to have a > FastModel license, which at least is a debugable platform for my at > present. You should be able to run arm32 guests on that platform. > PS, I ordered an OMAP5 development board, but it is stilling on shipping. Which devboard did you go for? _______________________________________________ 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 May 17 09:26:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 17 May 2013 09:26:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdGvf-0000FC-3k; Fri, 17 May 2013 09:26:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdGvd-0000F0-Kg for xen-arm@lists.xen.org; Fri, 17 May 2013 09:26:21 +0000 Received: from [193.109.254.147:18781] by server-11.bemta-14.messagelabs.com id 6E/6E-09099-CB7F5915; Fri, 17 May 2013 09:26:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1368782771!8468414!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2854 invoked from network); 17 May 2013 09:26:13 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 May 2013 09:26:13 -0000 X-IronPort-AV: E=Sophos;i="4.87,690,1363132800"; d="scan'208";a="25805118" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 17 May 2013 09:26:11 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.3; Fri, 17 May 2013 05:26:10 -0400 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[127.0.0.1]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UdGvR-00025h-1W; Fri, 17 May 2013 10:26:09 +0100 Message-ID: <1368782768.24012.23.camel@hastur.hellion.org.uk> From: Ian Campbell To: Chen Baozi Date: Fri, 17 May 2013 10:26:08 +0100 In-Reply-To: <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-17 at 08:00 +0800, Chen Baozi wrote: > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > >> > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > >>>> Hi Ian, > >>>> > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > >>>> which still needs lots of implementation to work properly. > >>>> > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > >>>> to drive the following porting. (I know it must not work at present, but it > >>>> would give some feedback through the test.) However, when I tried to "xl > >>>> create" the mini-os, it reported the following errors: > >>> > >>> There are some issues with loading guests from ELF (rather than zImage) > >>> kernels on ARM. > >> Is it possible because of there is no arm64 "guest_type" of > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > >> related codes in libxc files. > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > frozen so it has been committed, but that's the obvious starting point > > for 64-bit guest support. > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > is that an option? A lot of the code should end up common. > I did plan to start the work on arm32 at the very beginning. But The > only platform of cortex-a15 I've got is the samsung's chromebook. I > tried hard to run Xen on it but didn't succeed in the end due to the > lack of debug method. At the same time, I've got an chance getting > involved in a arm64 project of our lab so it is easy to have a > FastModel license, which at least is a debugable platform for my at > present. You should be able to run arm32 guests on that platform. > PS, I ordered an OMAP5 development board, but it is stilling on shipping. Which devboard did you go for? _______________________________________________ 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 May 17 10:02:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 17 May 2013 10:02:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdHUJ-0001Qg-Ri; Fri, 17 May 2013 10:02:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdHUI-0001Qb-IF for xen-arm@lists.xen.org; Fri, 17 May 2013 10:02:10 +0000 Received: from [85.158.139.83:10217] by server-4.bemta-5.messagelabs.com id A8/D4-12332-12006915; Fri, 17 May 2013 10:02:09 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1368784925!23925270!1 X-Originating-IP: [209.85.160.50] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11068 invoked from network); 17 May 2013 10:02:07 -0000 Received: from mail-pb0-f50.google.com (HELO mail-pb0-f50.google.com) (209.85.160.50) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 May 2013 10:02:07 -0000 Received: by mail-pb0-f50.google.com with SMTP id wy17so209912pbc.9 for ; Fri, 17 May 2013 03:02:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=FtvxRWAhJBB0I1c/DKcWltfORt5JUytuBqBSnQM7cPs=; b=NB7wVbHt9J9wEpZJFufRCHtwRd7SrScmuhIX+NdIxzF8tmHdmIxjYooOx3urwuollL LETN2ybpLAXncSOisVuH5quIKg4lhxaedQuo6CvtYNhXNSpFYnvW1fw+i1GYTZNXWIYK 6S4ois8SGEJLw1IQncEUPY+j3cuxwZwwfZntrrGBsvgcjSt6M3tJIzwfwQhdSc0xvLyb HLE3B1JNSUNtyMJyWfHi3hxkgCndWUne7L3owZ4hOh1LlA8SewodWU380LGpDDo/wY2+ QUIL7cGSYbeJd/Ii53TIgeuzHlXXlMJgy+9lw3Mi8NYjO24ArIgAEZdMB6ToKbC3jXez Q33A== X-Received: by 10.68.189.164 with SMTP id gj4mr47151180pbc.193.1368784925435; Fri, 17 May 2013 03:02:05 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id ea15sm11591661pad.16.2013.05.17.03.02.02 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 17 May 2013 03:02:04 -0700 (PDT) Date: Fri, 17 May 2013 17:58:14 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130517095814.GA17958@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1368782768.24012.23.camel@hastur.hellion.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, May 17, 2013 at 10:26:08AM +0100, Ian Campbell wrote: > On Fri, 2013-05-17 at 08:00 +0800, Chen Baozi wrote: > > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > >> > > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > > >>>> Hi Ian, > > >>>> > > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > > >>>> which still needs lots of implementation to work properly. > > >>>> > > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > > >>>> to drive the following porting. (I know it must not work at present, but it > > >>>> would give some feedback through the test.) However, when I tried to "xl > > >>>> create" the mini-os, it reported the following errors: > > >>> > > >>> There are some issues with loading guests from ELF (rather than zImage) > > >>> kernels on ARM. > > >> Is it possible because of there is no arm64 "guest_type" of > > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > > >> related codes in libxc files. > > > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > > frozen so it has been committed, but that's the obvious starting point > > > for 64-bit guest support. > > > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > > is that an option? A lot of the code should end up common. > > I did plan to start the work on arm32 at the very beginning. But The > > only platform of cortex-a15 I've got is the samsung's chromebook. I > > tried hard to run Xen on it but didn't succeed in the end due to the > > lack of debug method. At the same time, I've got an chance getting > > involved in a arm64 project of our lab so it is easy to have a > > FastModel license, which at least is a debugable platform for my at > > present. > > You should be able to run arm32 guests on that platform. Ok, I'll try it next. > > > PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > Which devboard did you go for? It is OMAP5432 uEVM from SVTronics. BTW, I found I can only run Xen hypervisor of your arm-cross2 git branch on Fast Model. For the version built from xen mainline, the program would run to an unknown address after paging enabled. (more exactly, from the 'isb' instruction which in line 267 of arch/arm/arm64/head.S.) Any ideas? Thanks. 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 Fri May 17 10:02:15 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 17 May 2013 10:02:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdHUJ-0001Qg-Ri; Fri, 17 May 2013 10:02:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdHUI-0001Qb-IF for xen-arm@lists.xen.org; Fri, 17 May 2013 10:02:10 +0000 Received: from [85.158.139.83:10217] by server-4.bemta-5.messagelabs.com id A8/D4-12332-12006915; Fri, 17 May 2013 10:02:09 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1368784925!23925270!1 X-Originating-IP: [209.85.160.50] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11068 invoked from network); 17 May 2013 10:02:07 -0000 Received: from mail-pb0-f50.google.com (HELO mail-pb0-f50.google.com) (209.85.160.50) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 May 2013 10:02:07 -0000 Received: by mail-pb0-f50.google.com with SMTP id wy17so209912pbc.9 for ; Fri, 17 May 2013 03:02:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=FtvxRWAhJBB0I1c/DKcWltfORt5JUytuBqBSnQM7cPs=; b=NB7wVbHt9J9wEpZJFufRCHtwRd7SrScmuhIX+NdIxzF8tmHdmIxjYooOx3urwuollL LETN2ybpLAXncSOisVuH5quIKg4lhxaedQuo6CvtYNhXNSpFYnvW1fw+i1GYTZNXWIYK 6S4ois8SGEJLw1IQncEUPY+j3cuxwZwwfZntrrGBsvgcjSt6M3tJIzwfwQhdSc0xvLyb HLE3B1JNSUNtyMJyWfHi3hxkgCndWUne7L3owZ4hOh1LlA8SewodWU380LGpDDo/wY2+ QUIL7cGSYbeJd/Ii53TIgeuzHlXXlMJgy+9lw3Mi8NYjO24ArIgAEZdMB6ToKbC3jXez Q33A== X-Received: by 10.68.189.164 with SMTP id gj4mr47151180pbc.193.1368784925435; Fri, 17 May 2013 03:02:05 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id ea15sm11591661pad.16.2013.05.17.03.02.02 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 17 May 2013 03:02:04 -0700 (PDT) Date: Fri, 17 May 2013 17:58:14 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130517095814.GA17958@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1368782768.24012.23.camel@hastur.hellion.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, May 17, 2013 at 10:26:08AM +0100, Ian Campbell wrote: > On Fri, 2013-05-17 at 08:00 +0800, Chen Baozi wrote: > > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > >> > > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > > >>>> Hi Ian, > > >>>> > > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > > >>>> which still needs lots of implementation to work properly. > > >>>> > > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > > >>>> to drive the following porting. (I know it must not work at present, but it > > >>>> would give some feedback through the test.) However, when I tried to "xl > > >>>> create" the mini-os, it reported the following errors: > > >>> > > >>> There are some issues with loading guests from ELF (rather than zImage) > > >>> kernels on ARM. > > >> Is it possible because of there is no arm64 "guest_type" of > > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > > >> related codes in libxc files. > > > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > > frozen so it has been committed, but that's the obvious starting point > > > for 64-bit guest support. > > > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > > is that an option? A lot of the code should end up common. > > I did plan to start the work on arm32 at the very beginning. But The > > only platform of cortex-a15 I've got is the samsung's chromebook. I > > tried hard to run Xen on it but didn't succeed in the end due to the > > lack of debug method. At the same time, I've got an chance getting > > involved in a arm64 project of our lab so it is easy to have a > > FastModel license, which at least is a debugable platform for my at > > present. > > You should be able to run arm32 guests on that platform. Ok, I'll try it next. > > > PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > Which devboard did you go for? It is OMAP5432 uEVM from SVTronics. BTW, I found I can only run Xen hypervisor of your arm-cross2 git branch on Fast Model. For the version built from xen mainline, the program would run to an unknown address after paging enabled. (more exactly, from the 'isb' instruction which in line 267 of arch/arm/arm64/head.S.) Any ideas? Thanks. 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 Fri May 17 14:30:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 17 May 2013 14:30:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdLg4-0006wL-Kk; Fri, 17 May 2013 14:30:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdLg2-0006wE-Jw for xen-arm@lists.xen.org; Fri, 17 May 2013 14:30:34 +0000 Received: from [85.158.139.211:62562] by server-4.bemta-5.messagelabs.com id 25/85-12332-90F36915; Fri, 17 May 2013 14:30:33 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1368801027!18438185!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1910 invoked from network); 17 May 2013 14:30:29 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 May 2013 14:30:29 -0000 X-IronPort-AV: E=Sophos;i="4.87,692,1363132800"; d="scan'208";a="24641205" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 17 May 2013 14:30:27 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.3; Fri, 17 May 2013 10:30:27 -0400 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[127.0.0.1]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UdLft-0007VE-VT; Fri, 17 May 2013 15:30:26 +0100 Message-ID: <1368801024.24012.48.camel@hastur.hellion.org.uk> From: Ian Campbell To: Chen Baozi Date: Fri, 17 May 2013 15:30:24 +0100 In-Reply-To: <20130517095814.GA17958@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-17 at 17:58 +0800, Chen Baozi wrote: > On Fri, May 17, 2013 at 10:26:08AM +0100, Ian Campbell wrote: > > On Fri, 2013-05-17 at 08:00 +0800, Chen Baozi wrote: > > > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > > > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > > > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > > >> > > > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > > > >>>> Hi Ian, > > > >>>> > > > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > > > >>>> which still needs lots of implementation to work properly. > > > >>>> > > > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > > > >>>> to drive the following porting. (I know it must not work at present, but it > > > >>>> would give some feedback through the test.) However, when I tried to "xl > > > >>>> create" the mini-os, it reported the following errors: > > > >>> > > > >>> There are some issues with loading guests from ELF (rather than zImage) > > > >>> kernels on ARM. > > > >> Is it possible because of there is no arm64 "guest_type" of > > > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > > > >> related codes in libxc files. > > > > > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > > > frozen so it has been committed, but that's the obvious starting point > > > > for 64-bit guest support. > > > > > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > > > is that an option? A lot of the code should end up common. > > > I did plan to start the work on arm32 at the very beginning. But The > > > only platform of cortex-a15 I've got is the samsung's chromebook. I > > > tried hard to run Xen on it but didn't succeed in the end due to the > > > lack of debug method. At the same time, I've got an chance getting > > > involved in a arm64 project of our lab so it is easy to have a > > > FastModel license, which at least is a debugable platform for my at > > > present. > > > > You should be able to run arm32 guests on that platform. > Ok, I'll try it next. > > > > > > PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > > > Which devboard did you go for? > It is OMAP5432 uEVM from SVTronics. > > BTW, I found I can only run Xen hypervisor of your arm-cross2 git branch on > Fast Model. For the version built from xen mainline, the program would > run to an unknown address after paging enabled. (more exactly, from the > 'isb' instruction which in line 267 of arch/arm/arm64/head.S.) > > Any ideas? That ISB is effectively the point at which paging gets enabled. I'm afraid I've not seen anything like that for a very long time, commit 56bbdea (which is pretty recent) works OK for me on both 32 and 64 bit models. What version of the model do you use? How are you invoking it? 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 Fri May 17 14:30:40 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 17 May 2013 14:30:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdLg4-0006wL-Kk; Fri, 17 May 2013 14:30:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UdLg2-0006wE-Jw for xen-arm@lists.xen.org; Fri, 17 May 2013 14:30:34 +0000 Received: from [85.158.139.211:62562] by server-4.bemta-5.messagelabs.com id 25/85-12332-90F36915; Fri, 17 May 2013 14:30:33 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1368801027!18438185!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1910 invoked from network); 17 May 2013 14:30:29 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 May 2013 14:30:29 -0000 X-IronPort-AV: E=Sophos;i="4.87,692,1363132800"; d="scan'208";a="24641205" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 17 May 2013 14:30:27 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.3; Fri, 17 May 2013 10:30:27 -0400 Received: from gateway-1.uk.xensource.com ([10.80.16.66] helo=[127.0.0.1]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UdLft-0007VE-VT; Fri, 17 May 2013 15:30:26 +0100 Message-ID: <1368801024.24012.48.camel@hastur.hellion.org.uk> From: Ian Campbell To: Chen Baozi Date: Fri, 17 May 2013 15:30:24 +0100 In-Reply-To: <20130517095814.GA17958@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-17 at 17:58 +0800, Chen Baozi wrote: > On Fri, May 17, 2013 at 10:26:08AM +0100, Ian Campbell wrote: > > On Fri, 2013-05-17 at 08:00 +0800, Chen Baozi wrote: > > > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > > > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > > > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > > >> > > > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > > > >>>> Hi Ian, > > > >>>> > > > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > > > >>>> which still needs lots of implementation to work properly. > > > >>>> > > > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > > > >>>> to drive the following porting. (I know it must not work at present, but it > > > >>>> would give some feedback through the test.) However, when I tried to "xl > > > >>>> create" the mini-os, it reported the following errors: > > > >>> > > > >>> There are some issues with loading guests from ELF (rather than zImage) > > > >>> kernels on ARM. > > > >> Is it possible because of there is no arm64 "guest_type" of > > > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > > > >> related codes in libxc files. > > > > > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > > > frozen so it has been committed, but that's the obvious starting point > > > > for 64-bit guest support. > > > > > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > > > is that an option? A lot of the code should end up common. > > > I did plan to start the work on arm32 at the very beginning. But The > > > only platform of cortex-a15 I've got is the samsung's chromebook. I > > > tried hard to run Xen on it but didn't succeed in the end due to the > > > lack of debug method. At the same time, I've got an chance getting > > > involved in a arm64 project of our lab so it is easy to have a > > > FastModel license, which at least is a debugable platform for my at > > > present. > > > > You should be able to run arm32 guests on that platform. > Ok, I'll try it next. > > > > > > PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > > > Which devboard did you go for? > It is OMAP5432 uEVM from SVTronics. > > BTW, I found I can only run Xen hypervisor of your arm-cross2 git branch on > Fast Model. For the version built from xen mainline, the program would > run to an unknown address after paging enabled. (more exactly, from the > 'isb' instruction which in line 267 of arch/arm/arm64/head.S.) > > Any ideas? That ISB is effectively the point at which paging gets enabled. I'm afraid I've not seen anything like that for a very long time, commit 56bbdea (which is pretty recent) works OK for me on both 32 and 64 bit models. What version of the model do you use? How are you invoking it? 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 May 20 01:23:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 01:23:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeEos-00041I-I6; Mon, 20 May 2013 01:23:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeEoq-00040x-9S for xen-arm@lists.xen.org; Mon, 20 May 2013 01:23:20 +0000 Received: from [85.158.137.99:23950] by server-8.bemta-3.messagelabs.com id 7B/AE-25864-70B79915; Mon, 20 May 2013 01:23:19 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1369012996!12337747!1 X-Originating-IP: [209.85.210.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17738 invoked from network); 20 May 2013 01:23:17 -0000 Received: from mail-da0-f47.google.com (HELO mail-da0-f47.google.com) (209.85.210.47) by server-3.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 01:23:17 -0000 Received: by mail-da0-f47.google.com with SMTP id k13so3557833dae.20 for ; Sun, 19 May 2013 18:23:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=XiwEQmo57cZKuxvtMGxMeXBAs5XPv8ioYfThwJMJ9X4=; b=Krxuxijg+if6qKr3UaO5iBbJ+zNe7zt6hHowcOMTBKIXtLpDEKLX7SwTulvXZackVU 3PXtlQ35RwZ77bO98r1IjLCkll+R8hPQSVdY1mtjcPvQxlxtNtekn65oCC3Hj7AFVj8v dQNbA1ZAtgfOJCH+4qWw4I6oSYi7KKWjXa06S5Ls9v1mynw6CDbGaU82+rrKQci3MzkH 1gKlltvTXw7fTeu/A+MhsL4w9uaaghvUzEuhQcf/LWvCAVeqfpq35GhWY58jgykOxavH KmWq7IMaVRXPY7J9kMVf21se5ruUWRkcyq1WImJvGvnCCA1l5QNG3Zp6jtv9A0BHTpPM 4VXg== X-Received: by 10.68.92.165 with SMTP id cn5mr59126221pbb.50.1369012995705; Sun, 19 May 2013 18:23:15 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id wp6sm21644120pbc.29.2013.05.19.18.23.12 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 19 May 2013 18:23:14 -0700 (PDT) Date: Mon, 20 May 2013 09:19:21 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130520011921.GA5502@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1368801024.24012.48.camel@hastur.hellion.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, May 17, 2013 at 03:30:24PM +0100, Ian Campbell wrote: > On Fri, 2013-05-17 at 17:58 +0800, Chen Baozi wrote: > > On Fri, May 17, 2013 at 10:26:08AM +0100, Ian Campbell wrote: > > > On Fri, 2013-05-17 at 08:00 +0800, Chen Baozi wrote: > > > > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > > > > > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > > > > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > > > >> > > > > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > > > > >>>> Hi Ian, > > > > >>>> > > > > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > > > > >>>> which still needs lots of implementation to work properly. > > > > >>>> > > > > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > > > > >>>> to drive the following porting. (I know it must not work at present, but it > > > > >>>> would give some feedback through the test.) However, when I tried to "xl > > > > >>>> create" the mini-os, it reported the following errors: > > > > >>> > > > > >>> There are some issues with loading guests from ELF (rather than zImage) > > > > >>> kernels on ARM. > > > > >> Is it possible because of there is no arm64 "guest_type" of > > > > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > > > > >> related codes in libxc files. > > > > > > > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > > > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > > > > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > > > > frozen so it has been committed, but that's the obvious starting point > > > > > for 64-bit guest support. > > > > > > > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > > > > is that an option? A lot of the code should end up common. > > > > I did plan to start the work on arm32 at the very beginning. But The > > > > only platform of cortex-a15 I've got is the samsung's chromebook. I > > > > tried hard to run Xen on it but didn't succeed in the end due to the > > > > lack of debug method. At the same time, I've got an chance getting > > > > involved in a arm64 project of our lab so it is easy to have a > > > > FastModel license, which at least is a debugable platform for my at > > > > present. > > > > > > You should be able to run arm32 guests on that platform. > > Ok, I'll try it next. > > > > > > > > > PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > > > > > Which devboard did you go for? > > It is OMAP5432 uEVM from SVTronics. > > > > BTW, I found I can only run Xen hypervisor of your arm-cross2 git branch on > > Fast Model. For the version built from xen mainline, the program would > > run to an unknown address after paging enabled. (more exactly, from the > > 'isb' instruction which in line 267 of arch/arm/arm64/head.S.) > > > > Any ideas? > > That ISB is effectively the point at which paging gets enabled. > > I'm afraid I've not seen anything like that for a very long time, commit > 56bbdea (which is pretty recent) works OK for me on both 32 and 64 bit > models. > > What version of the model do you use? How are you invoking it? I'm using Fast Model (Model Debugger - 8.0.027, Model Shell 8.0.16). To invoking it, I use the following command: modeldebugger/model_shell64 $ATLAS_MODEL /path/to/xen-syms -C motherboard.flashloader0.fname=~/path/to/zImage -C motherboard.mmc.p_mmc_file=/path/to/rootfs $ATLAS_MODEL=~/ARM/FastModelsPortfolio_8.0/examples/RTSM_VE/Build_Atlasx4/Linux-Release-GCC-4.1/cadi_system_Linux-Release-GCC-4.1.so > > 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 May 20 01:23:27 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 01:23:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeEos-00041I-I6; Mon, 20 May 2013 01:23:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeEoq-00040x-9S for xen-arm@lists.xen.org; Mon, 20 May 2013 01:23:20 +0000 Received: from [85.158.137.99:23950] by server-8.bemta-3.messagelabs.com id 7B/AE-25864-70B79915; Mon, 20 May 2013 01:23:19 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-3.tower-217.messagelabs.com!1369012996!12337747!1 X-Originating-IP: [209.85.210.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17738 invoked from network); 20 May 2013 01:23:17 -0000 Received: from mail-da0-f47.google.com (HELO mail-da0-f47.google.com) (209.85.210.47) by server-3.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 01:23:17 -0000 Received: by mail-da0-f47.google.com with SMTP id k13so3557833dae.20 for ; Sun, 19 May 2013 18:23:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=XiwEQmo57cZKuxvtMGxMeXBAs5XPv8ioYfThwJMJ9X4=; b=Krxuxijg+if6qKr3UaO5iBbJ+zNe7zt6hHowcOMTBKIXtLpDEKLX7SwTulvXZackVU 3PXtlQ35RwZ77bO98r1IjLCkll+R8hPQSVdY1mtjcPvQxlxtNtekn65oCC3Hj7AFVj8v dQNbA1ZAtgfOJCH+4qWw4I6oSYi7KKWjXa06S5Ls9v1mynw6CDbGaU82+rrKQci3MzkH 1gKlltvTXw7fTeu/A+MhsL4w9uaaghvUzEuhQcf/LWvCAVeqfpq35GhWY58jgykOxavH KmWq7IMaVRXPY7J9kMVf21se5ruUWRkcyq1WImJvGvnCCA1l5QNG3Zp6jtv9A0BHTpPM 4VXg== X-Received: by 10.68.92.165 with SMTP id cn5mr59126221pbb.50.1369012995705; Sun, 19 May 2013 18:23:15 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id wp6sm21644120pbc.29.2013.05.19.18.23.12 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 19 May 2013 18:23:14 -0700 (PDT) Date: Mon, 20 May 2013 09:19:21 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130520011921.GA5502@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1368801024.24012.48.camel@hastur.hellion.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, May 17, 2013 at 03:30:24PM +0100, Ian Campbell wrote: > On Fri, 2013-05-17 at 17:58 +0800, Chen Baozi wrote: > > On Fri, May 17, 2013 at 10:26:08AM +0100, Ian Campbell wrote: > > > On Fri, 2013-05-17 at 08:00 +0800, Chen Baozi wrote: > > > > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > > > > > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > > > > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > > > >> > > > > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > > > > >>>> Hi Ian, > > > > >>>> > > > > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > > > > >>>> which still needs lots of implementation to work properly. > > > > >>>> > > > > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > > > > >>>> to drive the following porting. (I know it must not work at present, but it > > > > >>>> would give some feedback through the test.) However, when I tried to "xl > > > > >>>> create" the mini-os, it reported the following errors: > > > > >>> > > > > >>> There are some issues with loading guests from ELF (rather than zImage) > > > > >>> kernels on ARM. > > > > >> Is it possible because of there is no arm64 "guest_type" of > > > > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > > > > >> related codes in libxc files. > > > > > > > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > > > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > > > > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > > > > frozen so it has been committed, but that's the obvious starting point > > > > > for 64-bit guest support. > > > > > > > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > > > > is that an option? A lot of the code should end up common. > > > > I did plan to start the work on arm32 at the very beginning. But The > > > > only platform of cortex-a15 I've got is the samsung's chromebook. I > > > > tried hard to run Xen on it but didn't succeed in the end due to the > > > > lack of debug method. At the same time, I've got an chance getting > > > > involved in a arm64 project of our lab so it is easy to have a > > > > FastModel license, which at least is a debugable platform for my at > > > > present. > > > > > > You should be able to run arm32 guests on that platform. > > Ok, I'll try it next. > > > > > > > > > PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > > > > > Which devboard did you go for? > > It is OMAP5432 uEVM from SVTronics. > > > > BTW, I found I can only run Xen hypervisor of your arm-cross2 git branch on > > Fast Model. For the version built from xen mainline, the program would > > run to an unknown address after paging enabled. (more exactly, from the > > 'isb' instruction which in line 267 of arch/arm/arm64/head.S.) > > > > Any ideas? > > That ISB is effectively the point at which paging gets enabled. > > I'm afraid I've not seen anything like that for a very long time, commit > 56bbdea (which is pretty recent) works OK for me on both 32 and 64 bit > models. > > What version of the model do you use? How are you invoking it? I'm using Fast Model (Model Debugger - 8.0.027, Model Shell 8.0.16). To invoking it, I use the following command: modeldebugger/model_shell64 $ATLAS_MODEL /path/to/xen-syms -C motherboard.flashloader0.fname=~/path/to/zImage -C motherboard.mmc.p_mmc_file=/path/to/rootfs $ATLAS_MODEL=~/ARM/FastModelsPortfolio_8.0/examples/RTSM_VE/Build_Atlasx4/Linux-Release-GCC-4.1/cadi_system_Linux-Release-GCC-4.1.so > > 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 May 20 03:41:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 03:41:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeGyV-0005z5-6L; Mon, 20 May 2013 03:41:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeGyT-0005yp-GN for xen-arm@lists.xen.org; Mon, 20 May 2013 03:41:25 +0000 Received: from [85.158.138.51:6090] by server-12.bemta-3.messagelabs.com id C8/48-17342-46B99915; Mon, 20 May 2013 03:41:24 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1369021281!27593791!1 X-Originating-IP: [209.85.220.43] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12145 invoked from network); 20 May 2013 03:41:23 -0000 Received: from mail-pa0-f43.google.com (HELO mail-pa0-f43.google.com) (209.85.220.43) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 03:41:23 -0000 Received: by mail-pa0-f43.google.com with SMTP id hz10so5277804pad.30 for ; Sun, 19 May 2013 20:41:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=tU5hLtXS2t9Zzt2dmPTYWipxsQ5DI9urHVEb0pN7GzM=; b=chymPe8yJayWRJfaVLTgrmCcc11o32IyIZ/W/1skrQ7Ek4TCDnJtiHPSjvprNRORF3 G5NukxodqiulqZ31bHZdZ4btreN0Yf9QumIww30ObPn42k9hQsVf5IlbMRL5tzv+Aq00 3rQs0Fe47lJ1YOGaAxdy7rWsZpKoCH5lnppm0pRo/wUAqG50boU/Iz3cldfmYkis99ck cMVGKpFOwv4SemFlKM1s/6jPP1/d/nDDq5qb5Uv3s0TJy3mjRTOCetUxosoqtoDN/7hL nofZWx73aQbLwc77bIg1hq94ifDvj8UkJIJaTbK8kaUp5IwkKsmlVEcSBthFF74QFYDu aFgw== X-Received: by 10.68.211.73 with SMTP id na9mr59153397pbc.90.1369021279908; Sun, 19 May 2013 20:41:19 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id ov2sm22106417pbc.34.2013.05.19.20.41.16 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 19 May 2013 20:41:18 -0700 (PDT) Date: Mon, 20 May 2013 11:37:26 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130520033726.GA9056@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20130520011921.GA5502@cbz-workstation> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, May 20, 2013 at 09:19:21AM +0800, Chen Baozi wrote: > On Fri, May 17, 2013 at 03:30:24PM +0100, Ian Campbell wrote: > > On Fri, 2013-05-17 at 17:58 +0800, Chen Baozi wrote: > > > On Fri, May 17, 2013 at 10:26:08AM +0100, Ian Campbell wrote: > > > > On Fri, 2013-05-17 at 08:00 +0800, Chen Baozi wrote: > > > > > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > > > > > > > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > > > > > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > > > > >> > > > > > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > > > > > >>>> Hi Ian, > > > > > >>>> > > > > > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > > > > > >>>> which still needs lots of implementation to work properly. > > > > > >>>> > > > > > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > > > > > >>>> to drive the following porting. (I know it must not work at present, but it > > > > > >>>> would give some feedback through the test.) However, when I tried to "xl > > > > > >>>> create" the mini-os, it reported the following errors: > > > > > >>> > > > > > >>> There are some issues with loading guests from ELF (rather than zImage) > > > > > >>> kernels on ARM. > > > > > >> Is it possible because of there is no arm64 "guest_type" of > > > > > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > > > > > >> related codes in libxc files. > > > > > > > > > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > > > > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > > > > > > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > > > > > frozen so it has been committed, but that's the obvious starting point > > > > > > for 64-bit guest support. > > > > > > > > > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > > > > > is that an option? A lot of the code should end up common. > > > > > I did plan to start the work on arm32 at the very beginning. But The > > > > > only platform of cortex-a15 I've got is the samsung's chromebook. I > > > > > tried hard to run Xen on it but didn't succeed in the end due to the > > > > > lack of debug method. At the same time, I've got an chance getting > > > > > involved in a arm64 project of our lab so it is easy to have a > > > > > FastModel license, which at least is a debugable platform for my at > > > > > present. > > > > > > > > You should be able to run arm32 guests on that platform. > > > Ok, I'll try it next. > > > > > > > > > > > > PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > > > > > > > Which devboard did you go for? > > > It is OMAP5432 uEVM from SVTronics. > > > > > > BTW, I found I can only run Xen hypervisor of your arm-cross2 git branch on > > > Fast Model. For the version built from xen mainline, the program would > > > run to an unknown address after paging enabled. (more exactly, from the > > > 'isb' instruction which in line 267 of arch/arm/arm64/head.S.) > > > > > > Any ideas? > > > > That ISB is effectively the point at which paging gets enabled. > > > > I'm afraid I've not seen anything like that for a very long time, commit > > 56bbdea (which is pretty recent) works OK for me on both 32 and 64 bit > > models. > > > > What version of the model do you use? How are you invoking it? > > I'm using Fast Model (Model Debugger - 8.0.027, Model Shell 8.0.16). To > invoking it, I use the following command: > > modeldebugger/model_shell64 $ATLAS_MODEL /path/to/xen-syms -C > motherboard.flashloader0.fname=~/path/to/zImage -C > motherboard.mmc.p_mmc_file=/path/to/rootfs Sorry, I think the problem described above only happened if I use "xen-syms" for debugging. If I switch to "xen", there is no such problem on paging though it still not work (phenomenons: couldn't see any output). So the situation is that xen-syms doesn't work for either arm-cross2 branch or mainline, (I used it by mistake), while xen doesn't work in mainline but arm-cross2 branch. > > $ATLAS_MODEL=~/ARM/FastModelsPortfolio_8.0/examples/RTSM_VE/Build_Atlasx4/Linux-Release-GCC-4.1/cadi_system_Linux-Release-GCC-4.1.so > > > > > 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 May 20 03:41:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 03:41:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeGyV-0005z5-6L; Mon, 20 May 2013 03:41:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeGyT-0005yp-GN for xen-arm@lists.xen.org; Mon, 20 May 2013 03:41:25 +0000 Received: from [85.158.138.51:6090] by server-12.bemta-3.messagelabs.com id C8/48-17342-46B99915; Mon, 20 May 2013 03:41:24 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1369021281!27593791!1 X-Originating-IP: [209.85.220.43] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12145 invoked from network); 20 May 2013 03:41:23 -0000 Received: from mail-pa0-f43.google.com (HELO mail-pa0-f43.google.com) (209.85.220.43) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 03:41:23 -0000 Received: by mail-pa0-f43.google.com with SMTP id hz10so5277804pad.30 for ; Sun, 19 May 2013 20:41:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=tU5hLtXS2t9Zzt2dmPTYWipxsQ5DI9urHVEb0pN7GzM=; b=chymPe8yJayWRJfaVLTgrmCcc11o32IyIZ/W/1skrQ7Ek4TCDnJtiHPSjvprNRORF3 G5NukxodqiulqZ31bHZdZ4btreN0Yf9QumIww30ObPn42k9hQsVf5IlbMRL5tzv+Aq00 3rQs0Fe47lJ1YOGaAxdy7rWsZpKoCH5lnppm0pRo/wUAqG50boU/Iz3cldfmYkis99ck cMVGKpFOwv4SemFlKM1s/6jPP1/d/nDDq5qb5Uv3s0TJy3mjRTOCetUxosoqtoDN/7hL nofZWx73aQbLwc77bIg1hq94ifDvj8UkJIJaTbK8kaUp5IwkKsmlVEcSBthFF74QFYDu aFgw== X-Received: by 10.68.211.73 with SMTP id na9mr59153397pbc.90.1369021279908; Sun, 19 May 2013 20:41:19 -0700 (PDT) Received: from localhost ([119.39.124.170]) by mx.google.com with ESMTPSA id ov2sm22106417pbc.34.2013.05.19.20.41.16 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 19 May 2013 20:41:18 -0700 (PDT) Date: Mon, 20 May 2013 11:37:26 +0800 From: Chen Baozi To: Ian Campbell Message-ID: <20130520033726.GA9056@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20130520011921.GA5502@cbz-workstation> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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, May 20, 2013 at 09:19:21AM +0800, Chen Baozi wrote: > On Fri, May 17, 2013 at 03:30:24PM +0100, Ian Campbell wrote: > > On Fri, 2013-05-17 at 17:58 +0800, Chen Baozi wrote: > > > On Fri, May 17, 2013 at 10:26:08AM +0100, Ian Campbell wrote: > > > > On Fri, 2013-05-17 at 08:00 +0800, Chen Baozi wrote: > > > > > On May 17, 2013, at 12:20 AM, Ian Campbell wrote: > > > > > > > > > > > On Thu, 2013-05-16 at 23:34 +0800, Chen Baozi wrote: > > > > > >> On May 16, 2013, at 10:41 PM, Ian Campbell wrote: > > > > > >> > > > > > >>> On Thu, 2013-05-16 at 17:49 +0800, Chen Baozi wrote: > > > > > >>>> Hi Ian, > > > > > >>>> > > > > > >>>> I've done the basic interfaces/framework to pass mini-os build on arm64, > > > > > >>>> which still needs lots of implementation to work properly. > > > > > >>>> > > > > > >>>> Then I tried to create the mini-os guest for arm64 on Fast Model environment > > > > > >>>> to drive the following porting. (I know it must not work at present, but it > > > > > >>>> would give some feedback through the test.) However, when I tried to "xl > > > > > >>>> create" the mini-os, it reported the following errors: > > > > > >>> > > > > > >>> There are some issues with loading guests from ELF (rather than zImage) > > > > > >>> kernels on ARM. > > > > > >> Is it possible because of there is no arm64 "guest_type" of > > > > > >> xc_dom_arch struct? I can only find "den-3.0-armv7l" guest_type > > > > > >> related codes in libxc files. > > > > > > > > > > > > Oh, yes, we haven't done arm64 guests yet... Sorry I forgot about this > > > > > > before. Hrm, that does rather block you from doing arm64 mini-os. > > > > > > > > > > > > I posted a series to allow 64-bit dom0 a while back but we are currently > > > > > > frozen so it has been committed, but that's the obvious starting point > > > > > > for 64-bit guest support. > > > > > > > > > > > > I don't recall why you are looking at 64-bit minios rather than 32-bit, > > > > > > is that an option? A lot of the code should end up common. > > > > > I did plan to start the work on arm32 at the very beginning. But The > > > > > only platform of cortex-a15 I've got is the samsung's chromebook. I > > > > > tried hard to run Xen on it but didn't succeed in the end due to the > > > > > lack of debug method. At the same time, I've got an chance getting > > > > > involved in a arm64 project of our lab so it is easy to have a > > > > > FastModel license, which at least is a debugable platform for my at > > > > > present. > > > > > > > > You should be able to run arm32 guests on that platform. > > > Ok, I'll try it next. > > > > > > > > > > > > PS, I ordered an OMAP5 development board, but it is stilling on shipping. > > > > > > > > Which devboard did you go for? > > > It is OMAP5432 uEVM from SVTronics. > > > > > > BTW, I found I can only run Xen hypervisor of your arm-cross2 git branch on > > > Fast Model. For the version built from xen mainline, the program would > > > run to an unknown address after paging enabled. (more exactly, from the > > > 'isb' instruction which in line 267 of arch/arm/arm64/head.S.) > > > > > > Any ideas? > > > > That ISB is effectively the point at which paging gets enabled. > > > > I'm afraid I've not seen anything like that for a very long time, commit > > 56bbdea (which is pretty recent) works OK for me on both 32 and 64 bit > > models. > > > > What version of the model do you use? How are you invoking it? > > I'm using Fast Model (Model Debugger - 8.0.027, Model Shell 8.0.16). To > invoking it, I use the following command: > > modeldebugger/model_shell64 $ATLAS_MODEL /path/to/xen-syms -C > motherboard.flashloader0.fname=~/path/to/zImage -C > motherboard.mmc.p_mmc_file=/path/to/rootfs Sorry, I think the problem described above only happened if I use "xen-syms" for debugging. If I switch to "xen", there is no such problem on paging though it still not work (phenomenons: couldn't see any output). So the situation is that xen-syms doesn't work for either arm-cross2 branch or mainline, (I used it by mistake), while xen doesn't work in mainline but arm-cross2 branch. > > $ATLAS_MODEL=~/ARM/FastModelsPortfolio_8.0/examples/RTSM_VE/Build_Atlasx4/Linux-Release-GCC-4.1/cadi_system_Linux-Release-GCC-4.1.so > > > > > 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 May 20 08:54:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 08:54:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLrf-0003du-Eh; Mon, 20 May 2013 08:54:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLre-0003dT-8B; Mon, 20 May 2013 08:54:42 +0000 Received: from [85.158.143.99:52350] by server-2.bemta-4.messagelabs.com id 27/11-27124-1D4E9915; Mon, 20 May 2013 08:54:41 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1369040073!22019679!1 X-Originating-IP: [209.85.219.53] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14728 invoked from network); 20 May 2013 08:54:35 -0000 Received: from mail-oa0-f53.google.com (HELO mail-oa0-f53.google.com) (209.85.219.53) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 08:54:35 -0000 Received: by mail-oa0-f53.google.com with SMTP id g12so7330326oah.26 for ; Mon, 20 May 2013 01:54:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=KrjN1/zYNAKRiEqTh/n6R/gL6WtC9so/LPERFkO5MjM=; b=batyXxFkO7PikcffVkMYjfK/8k7I68hLCrQ6NGaYQgY7/MPNIh0lNITPeFmc0DD/vp 8kZlounpPJ38oNdSBWTVMq/ZXgfuVp6blFGerxSFk7wSfSx3FGMFXxdwgJ9TIIHHgIbt LSMdyLvv/Epvafr4vvVJ6arhtA1wTnwNOwYS92ipUi9HpPihMyJBQdvnONNj+fBPqJ95 GPoFLIUKhNcwXxtLC/gsI3fUjMeba9SifsC8/QTsKLzxoZ9+GWkKHEkIBThbXWXzvevs Ba2LWulELhCHUWvg1oNMqZ7vyPpzgIU+x4L49ExxMotdUvc1Q8/mVNMgxS4I76ad14tW yeeA== MIME-Version: 1.0 X-Received: by 10.60.135.134 with SMTP id ps6mr19669038oeb.114.1369040073191; Mon, 20 May 2013 01:54:33 -0700 (PDT) Received: by 10.60.3.232 with HTTP; Mon, 20 May 2013 01:54:33 -0700 (PDT) Date: Mon, 20 May 2013 09:54:33 +0100 Message-ID: From: Lars Kurth To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" Subject: Re: [XenARM] [Votes] Xen Project Governance v2 , Mailing List Conventions v1 (vote closes today) 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="===============3614331589262519678==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3614331589262519678== Content-Type: multipart/alternative; boundary=047d7b33ce8c3ef71004dd227be0 --047d7b33ce8c3ef71004dd227be0 Content-Type: text/plain; charset=ISO-8859-1 Hi all, just a quick reminder that the vote on these two issues closes today! And that all maintainers, committers and project leads of mature projects are allowed to vote. Lars On Mon, May 13, 2013 at 11:30 AM, Lars Kurth wrote: > > - For vote:Xen Project Governance v2 at http://www.xenproject.org/** > component/content/article/80-**developers/136-governance-v2-** > proposal.html > - For vote:Mailing List Conventions v1 at http://www.xenproject.org/** > component/content/article/80-**developers/139-mailing-list-** > conventions.html > - For vote: Dates and Locations for 2014 Events (see below) > > --047d7b33ce8c3ef71004dd227be0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,
just a quick reminder that the vote on these t= wo issues closes today! And that all maintainers, committers and project le= ads of mature projects are allowed to vote.
Lars

On Mon, May 13, 2013 at 11:30 AM, Lars Kurth= <lars.kurth@xen.org> wrote:
- For vote:Xen Project Governance v2 at http://www.xenproject.org/component/content/articl= e/80-developers/136-governance-v2-proposal.html
- For vote:Mailing List Conventions v1 at http://www.xenproject.org/component/content/ar= ticle/80-developers/139-mailing-list-conventions.html - For vote: Dates and Locations for 2014 Events (see below)

--047d7b33ce8c3ef71004dd227be0-- --===============3614331589262519678== 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 --===============3614331589262519678==-- From xen-arm-bounces@lists.xen.org Mon May 20 08:54:47 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 08:54:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLrf-0003du-Eh; Mon, 20 May 2013 08:54:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLre-0003dT-8B; Mon, 20 May 2013 08:54:42 +0000 Received: from [85.158.143.99:52350] by server-2.bemta-4.messagelabs.com id 27/11-27124-1D4E9915; Mon, 20 May 2013 08:54:41 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1369040073!22019679!1 X-Originating-IP: [209.85.219.53] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14728 invoked from network); 20 May 2013 08:54:35 -0000 Received: from mail-oa0-f53.google.com (HELO mail-oa0-f53.google.com) (209.85.219.53) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 08:54:35 -0000 Received: by mail-oa0-f53.google.com with SMTP id g12so7330326oah.26 for ; Mon, 20 May 2013 01:54:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=KrjN1/zYNAKRiEqTh/n6R/gL6WtC9so/LPERFkO5MjM=; b=batyXxFkO7PikcffVkMYjfK/8k7I68hLCrQ6NGaYQgY7/MPNIh0lNITPeFmc0DD/vp 8kZlounpPJ38oNdSBWTVMq/ZXgfuVp6blFGerxSFk7wSfSx3FGMFXxdwgJ9TIIHHgIbt LSMdyLvv/Epvafr4vvVJ6arhtA1wTnwNOwYS92ipUi9HpPihMyJBQdvnONNj+fBPqJ95 GPoFLIUKhNcwXxtLC/gsI3fUjMeba9SifsC8/QTsKLzxoZ9+GWkKHEkIBThbXWXzvevs Ba2LWulELhCHUWvg1oNMqZ7vyPpzgIU+x4L49ExxMotdUvc1Q8/mVNMgxS4I76ad14tW yeeA== MIME-Version: 1.0 X-Received: by 10.60.135.134 with SMTP id ps6mr19669038oeb.114.1369040073191; Mon, 20 May 2013 01:54:33 -0700 (PDT) Received: by 10.60.3.232 with HTTP; Mon, 20 May 2013 01:54:33 -0700 (PDT) Date: Mon, 20 May 2013 09:54:33 +0100 Message-ID: From: Lars Kurth To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" Subject: Re: [XenARM] [Votes] Xen Project Governance v2 , Mailing List Conventions v1 (vote closes today) 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="===============3614331589262519678==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============3614331589262519678== Content-Type: multipart/alternative; boundary=047d7b33ce8c3ef71004dd227be0 --047d7b33ce8c3ef71004dd227be0 Content-Type: text/plain; charset=ISO-8859-1 Hi all, just a quick reminder that the vote on these two issues closes today! And that all maintainers, committers and project leads of mature projects are allowed to vote. Lars On Mon, May 13, 2013 at 11:30 AM, Lars Kurth wrote: > > - For vote:Xen Project Governance v2 at http://www.xenproject.org/** > component/content/article/80-**developers/136-governance-v2-** > proposal.html > - For vote:Mailing List Conventions v1 at http://www.xenproject.org/** > component/content/article/80-**developers/139-mailing-list-** > conventions.html > - For vote: Dates and Locations for 2014 Events (see below) > > --047d7b33ce8c3ef71004dd227be0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,
just a quick reminder that the vote on these t= wo issues closes today! And that all maintainers, committers and project le= ads of mature projects are allowed to vote.
Lars

On Mon, May 13, 2013 at 11:30 AM, Lars Kurth= <lars.kurth@xen.org> wrote:
- For vote:Xen Project Governance v2 at http://www.xenproject.org/component/content/articl= e/80-developers/136-governance-v2-proposal.html
- For vote:Mailing List Conventions v1 at http://www.xenproject.org/component/content/ar= ticle/80-developers/139-mailing-list-conventions.html - For vote: Dates and Locations for 2014 Events (see below)

--047d7b33ce8c3ef71004dd227be0-- --===============3614331589262519678== 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 --===============3614331589262519678==-- From xen-arm-bounces@lists.xen.org Mon May 20 08:59:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 08:59:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLwB-0004iC-CU; Mon, 20 May 2013 08:59:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLwA-0004hu-O6 for xen-arm@lists.xen.org; Mon, 20 May 2013 08:59:22 +0000 Received: from [193.109.254.147:51525] by server-14.bemta-14.messagelabs.com id CB/3C-02181-AE5E9915; Mon, 20 May 2013 08:59:22 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1369040201!3650882!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6458 invoked from network); 20 May 2013 08:56:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 08:56:42 -0000 X-IronPort-AV: E=Sophos;i="4.87,706,1363132800"; d="scan'208";a="4756150" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 May 2013 08:56:42 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 20 May 2013 09:56:41 +0100 Message-ID: <1369040200.2083.14.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 20 May 2013 09:56:40 +0100 In-Reply-To: <20130520011921.GA5502@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-20 at 09:19 +0800, Chen Baozi wrote: > I'm using Fast Model (Model Debugger - 8.0.027, Model Shell 8.0.16). That's a bit old I think, my v8 (AEM) model is 0.8.4702 and v7 (Cortex A15) is 8.0.44. _______________________________________________ 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 May 20 08:59:26 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 08:59:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLwB-0004iC-CU; Mon, 20 May 2013 08:59:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLwA-0004hu-O6 for xen-arm@lists.xen.org; Mon, 20 May 2013 08:59:22 +0000 Received: from [193.109.254.147:51525] by server-14.bemta-14.messagelabs.com id CB/3C-02181-AE5E9915; Mon, 20 May 2013 08:59:22 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1369040201!3650882!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6458 invoked from network); 20 May 2013 08:56:42 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 08:56:42 -0000 X-IronPort-AV: E=Sophos;i="4.87,706,1363132800"; d="scan'208";a="4756150" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 May 2013 08:56:42 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 20 May 2013 09:56:41 +0100 Message-ID: <1369040200.2083.14.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 20 May 2013 09:56:40 +0100 In-Reply-To: <20130520011921.GA5502@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-20 at 09:19 +0800, Chen Baozi wrote: > I'm using Fast Model (Model Debugger - 8.0.027, Model Shell 8.0.16). That's a bit old I think, my v8 (AEM) model is 0.8.4702 and v7 (Cortex A15) is 8.0.44. _______________________________________________ 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 May 20 09:11:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 09:11: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 1UeM86-0006ld-Kn; Mon, 20 May 2013 09:11:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeM84-0006lA-83 for xen-arm@lists.xen.org; Mon, 20 May 2013 09:11:40 +0000 Received: from [85.158.143.99:41265] by server-2.bemta-4.messagelabs.com id 6F/A2-27124-BC8E9915; Mon, 20 May 2013 09:11:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1369041099!29045093!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27904 invoked from network); 20 May 2013 09:11:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 09:11:39 -0000 X-IronPort-AV: E=Sophos;i="4.87,706,1363132800"; d="scan'208";a="4756622" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 May 2013 09:11:39 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 20 May 2013 10:11:38 +0100 Message-ID: <1369041096.2083.23.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 20 May 2013 10:11:36 +0100 In-Reply-To: <20130520033726.GA9056@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <20130520033726.GA9056@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-20 at 11:37 +0800, Chen Baozi wrote: > Sorry, I think the problem described above only happened if I use "xen-syms" > for debugging. If I switch to "xen", there is no such problem on paging though > it still not work (phenomenons: couldn't see any output). xen-syms is not suitable for booting, only for pointing GDB at. > So the situation is that xen-syms doesn't work for either arm-cross2 branch > or mainline, (I used it by mistake), while xen doesn't work in mainline but > arm-cross2 branch. What is the failure mode here? I'm not sure which of your previous symptoms were related to the use of xen-syms. 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 May 20 09:11:44 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 09:11: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 1UeM86-0006ld-Kn; Mon, 20 May 2013 09:11:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeM84-0006lA-83 for xen-arm@lists.xen.org; Mon, 20 May 2013 09:11:40 +0000 Received: from [85.158.143.99:41265] by server-2.bemta-4.messagelabs.com id 6F/A2-27124-BC8E9915; Mon, 20 May 2013 09:11:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1369041099!29045093!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27904 invoked from network); 20 May 2013 09:11:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 09:11:39 -0000 X-IronPort-AV: E=Sophos;i="4.87,706,1363132800"; d="scan'208";a="4756622" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 May 2013 09:11:39 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 20 May 2013 10:11:38 +0100 Message-ID: <1369041096.2083.23.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 20 May 2013 10:11:36 +0100 In-Reply-To: <20130520033726.GA9056@cbz-workstation> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <20130520033726.GA9056@cbz-workstation> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-20 at 11:37 +0800, Chen Baozi wrote: > Sorry, I think the problem described above only happened if I use "xen-syms" > for debugging. If I switch to "xen", there is no such problem on paging though > it still not work (phenomenons: couldn't see any output). xen-syms is not suitable for booting, only for pointing GDB at. > So the situation is that xen-syms doesn't work for either arm-cross2 branch > or mainline, (I used it by mistake), while xen doesn't work in mainline but > arm-cross2 branch. What is the failure mode here? I'm not sure which of your previous symptoms were related to the use of xen-syms. 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 May 20 09:18:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 09:18:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeMEE-00079b-DX; Mon, 20 May 2013 09:18:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeMEC-00078p-4a; Mon, 20 May 2013 09:18:00 +0000 Received: from [85.158.143.99:26421] by server-3.bemta-4.messagelabs.com id 04/D7-02015-74AE9915; Mon, 20 May 2013 09:17:59 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1369041478!24640043!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17829 invoked from network); 20 May 2013 09:17:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 09:17:58 -0000 X-IronPort-AV: E=Sophos;i="4.87,706,1363132800"; d="scan'208";a="4756787" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 May 2013 09:17:58 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 20 May 2013 10:17:58 +0100 Message-ID: <1369041476.2083.26.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Mon, 20 May 2013 10:17:56 +0100 In-Reply-To: <5190C0BC.5060008@xen.org> References: <5190C0BC.5060008@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) 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-05-13 at 11:30 +0100, Lars Kurth wrote: > Rather than creating a voting form, I decided to use the voting > feature > on the newxenproject.org website. To vote, you need to create an > account. If you have difficulties, let me know. The poll isat > http://www.xenproject.org/help/questions-and-answers/vote-on-2014-event-locations.html. > The vote will stay open until the middle of June. I've voted using this now but in the future perhaps we could continue to vote using the old "+1" in an email mechanism? There aren't so many maintainers and committers that this would be unwieldy IMHO. _______________________________________________ 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 May 20 09:18:06 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 09:18:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeMEE-00079b-DX; Mon, 20 May 2013 09:18:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeMEC-00078p-4a; Mon, 20 May 2013 09:18:00 +0000 Received: from [85.158.143.99:26421] by server-3.bemta-4.messagelabs.com id 04/D7-02015-74AE9915; Mon, 20 May 2013 09:17:59 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1369041478!24640043!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.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17829 invoked from network); 20 May 2013 09:17:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 09:17:58 -0000 X-IronPort-AV: E=Sophos;i="4.87,706,1363132800"; d="scan'208";a="4756787" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 May 2013 09:17:58 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Mon, 20 May 2013 10:17:58 +0100 Message-ID: <1369041476.2083.26.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Mon, 20 May 2013 10:17:56 +0100 In-Reply-To: <5190C0BC.5060008@xen.org> References: <5190C0BC.5060008@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-1 MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) 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-05-13 at 11:30 +0100, Lars Kurth wrote: > Rather than creating a voting form, I decided to use the voting > feature > on the newxenproject.org website. To vote, you need to create an > account. If you have difficulties, let me know. The poll isat > http://www.xenproject.org/help/questions-and-answers/vote-on-2014-event-locations.html. > The vote will stay open until the middle of June. I've voted using this now but in the future perhaps we could continue to vote using the old "+1" in an email mechanism? There aren't so many maintainers and committers that this would be unwieldy IMHO. _______________________________________________ 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 May 20 11:17:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 11:17:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeO6F-0003ZI-Jl; Mon, 20 May 2013 11:17:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeO6E-0003Z3-7d for xen-arm@lists.xen.org; Mon, 20 May 2013 11:17:54 +0000 Received: from [85.158.143.99:60960] by server-2.bemta-4.messagelabs.com id 7B/1F-27124-1660A915; Mon, 20 May 2013 11:17:53 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1369048671!26141326!1 X-Originating-IP: [209.85.220.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16335 invoked from network); 20 May 2013 11:17:52 -0000 Received: from mail-pa0-f47.google.com (HELO mail-pa0-f47.google.com) (209.85.220.47) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 11:17:52 -0000 Received: by mail-pa0-f47.google.com with SMTP id kl13so5583653pab.34 for ; Mon, 20 May 2013 04:17:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=Ja4pLFbxzUC7+uqyeSHOr8kspBjqobfQ7+wj9qQmwQ8=; b=HI2yABshVe54J8YcYePZMEbPGDrcZFVF6c2E/Za5m2f4dXInGglqdY3YsmOZLGJ+58 HQzDapp9ZMrwCnMzMEXBhnft187WcTQOwgxyiRJtoNoz8uzyfo97tqD5l327nCtY1vIu KD0pQWvKTbbLLhrK80zrGIari0yGffoc2/bXuOanCjY8VonbSfnbG5x3TCUiMPNzgmuG /JjaIJhNIiP+8YftJtbinFf0njRs5e5/sOPFH30gzJpZbxzVo/lGjJdAqByTk5m4eSnH Rh93f3mqiqC34agfH3P6CIHez1uedhl0XqhnUBbukMkGsmICFCfPg5azbS/HlyJ3hSzT bLSw== X-Received: by 10.66.218.170 with SMTP id ph10mr61580640pac.134.1369048671011; Mon, 20 May 2013 04:17:51 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id 10sm23710462pbr.45.2013.05.20.04.17.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 04:17:50 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1369040200.2083.14.camel@zakaz.uk.xensource.com> Date: Mon, 20 May 2013 19:17:46 +0800 Message-Id: <36668B4B-47F2-49F4-BFBF-92346C7EB95F@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <1369040200.2083.14.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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 May 20, 2013, at 4:56 PM, Ian Campbell wrote: > On Mon, 2013-05-20 at 09:19 +0800, Chen Baozi wrote: >> I'm using Fast Model (Model Debugger - 8.0.027, Model Shell 8.0.16). > > That's a bit old I think, my v8 (AEM) model is 0.8.4702 and v7 (Cortex > A15) is 8.0.44. Oh, sorry. I misunderstood the "model" referring to. I'm using the ARM_AEMv8-A_MP Model, version 8.0.44 right now. _______________________________________________ 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 May 20 11:17:59 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 11:17:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeO6F-0003ZI-Jl; Mon, 20 May 2013 11:17:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeO6E-0003Z3-7d for xen-arm@lists.xen.org; Mon, 20 May 2013 11:17:54 +0000 Received: from [85.158.143.99:60960] by server-2.bemta-4.messagelabs.com id 7B/1F-27124-1660A915; Mon, 20 May 2013 11:17:53 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1369048671!26141326!1 X-Originating-IP: [209.85.220.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16335 invoked from network); 20 May 2013 11:17:52 -0000 Received: from mail-pa0-f47.google.com (HELO mail-pa0-f47.google.com) (209.85.220.47) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 11:17:52 -0000 Received: by mail-pa0-f47.google.com with SMTP id kl13so5583653pab.34 for ; Mon, 20 May 2013 04:17:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=Ja4pLFbxzUC7+uqyeSHOr8kspBjqobfQ7+wj9qQmwQ8=; b=HI2yABshVe54J8YcYePZMEbPGDrcZFVF6c2E/Za5m2f4dXInGglqdY3YsmOZLGJ+58 HQzDapp9ZMrwCnMzMEXBhnft187WcTQOwgxyiRJtoNoz8uzyfo97tqD5l327nCtY1vIu KD0pQWvKTbbLLhrK80zrGIari0yGffoc2/bXuOanCjY8VonbSfnbG5x3TCUiMPNzgmuG /JjaIJhNIiP+8YftJtbinFf0njRs5e5/sOPFH30gzJpZbxzVo/lGjJdAqByTk5m4eSnH Rh93f3mqiqC34agfH3P6CIHez1uedhl0XqhnUBbukMkGsmICFCfPg5azbS/HlyJ3hSzT bLSw== X-Received: by 10.66.218.170 with SMTP id ph10mr61580640pac.134.1369048671011; Mon, 20 May 2013 04:17:51 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id 10sm23710462pbr.45.2013.05.20.04.17.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 04:17:50 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1369040200.2083.14.camel@zakaz.uk.xensource.com> Date: Mon, 20 May 2013 19:17:46 +0800 Message-Id: <36668B4B-47F2-49F4-BFBF-92346C7EB95F@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <1369040200.2083.14.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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 May 20, 2013, at 4:56 PM, Ian Campbell wrote: > On Mon, 2013-05-20 at 09:19 +0800, Chen Baozi wrote: >> I'm using Fast Model (Model Debugger - 8.0.027, Model Shell 8.0.16). > > That's a bit old I think, my v8 (AEM) model is 0.8.4702 and v7 (Cortex > A15) is 8.0.44. Oh, sorry. I misunderstood the "model" referring to. I'm using the ARM_AEMv8-A_MP Model, version 8.0.44 right now. _______________________________________________ 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 May 20 11:21:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 11:21: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 1UeOA7-0003tc-98; Mon, 20 May 2013 11:21:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOA5-0003tD-2X for xen-arm@lists.xen.org; Mon, 20 May 2013 11:21:53 +0000 Received: from [85.158.139.83:13852] by server-2.bemta-5.messagelabs.com id 58/00-26552-0570A915; Mon, 20 May 2013 11:21:52 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1369048909!23870238!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27699 invoked from network); 20 May 2013 11:21:51 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 11:21:51 -0000 Received: by mail-pb0-f47.google.com with SMTP id rr4so5259029pbb.20 for ; Mon, 20 May 2013 04:21:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=+Wv338h4InvBZz848qHZiRRlh2XfApde2e54Ngu06mE=; b=NaZ08TbieW6X9wHWPt9BFO5g7O2Hp0u6JMi5qaCUAZMYEirn0JeEPjNp3rPyhOx26H /0Q18cu+B6Ui+Hj1lLcUB8uSWqWiCMA3iEkEBA6oIKC9XYsPv0+MDg0QEdIgN0XJfBcl 1k4cn3g1eyqSJbdHp8C1nNDNbdpfbR6hs1Vt+GV2MtNWdXy2JRUjYHVRaRIIXp6GA5RB KnwUY7Tw6O99jCsgtu6u0mjAaD5hC7sWRDMraknSdReeYuA5HtMQfyIlE0ulyOpfrjq3 2haS5OSFY3T6irOBgidn5Pq+3e5e6AODOigb1jHg8JPXv5DjbhMJK1JyxTwJVuHkkTyj 5zxQ== X-Received: by 10.66.27.197 with SMTP id v5mr60000706pag.211.1369048908867; Mon, 20 May 2013 04:21:48 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id qi1sm25415710pac.21.2013.05.20.04.21.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 04:21:48 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1369041096.2083.23.camel@zakaz.uk.xensource.com> Date: Mon, 20 May 2013 19:21:43 +0800 Message-Id: <16FDAC42-14DE-4A63-9F43-CB4B3F662B51@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <20130520033726.GA9056@cbz-workstation> <1369041096.2083.23.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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 May 20, 2013, at 5:11 PM, Ian Campbell wrote: > On Mon, 2013-05-20 at 11:37 +0800, Chen Baozi wrote: >> Sorry, I think the problem described above only happened if I use "xen-syms" >> for debugging. If I switch to "xen", there is no such problem on paging though >> it still not work (phenomenons: couldn't see any output). > > xen-syms is not suitable for booting, only for pointing GDB at. > >> So the situation is that xen-syms doesn't work for either arm-cross2 branch >> or mainline, (I used it by mistake), while xen doesn't work in mainline but >> arm-cross2 branch. > > What is the failure mode here? I'm not sure which of your previous > symptoms were related to the use of xen-syms. I think xen-syms symptoms is because of my misusing. Sorry for my stupid. However, if I use "xen" (which works for your arm-cross2 branch) in mainline, there is not any output while booting. > > 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 May 20 11:21:58 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 11:21: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 1UeOA7-0003tc-98; Mon, 20 May 2013 11:21:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOA5-0003tD-2X for xen-arm@lists.xen.org; Mon, 20 May 2013 11:21:53 +0000 Received: from [85.158.139.83:13852] by server-2.bemta-5.messagelabs.com id 58/00-26552-0570A915; Mon, 20 May 2013 11:21:52 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1369048909!23870238!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27699 invoked from network); 20 May 2013 11:21:51 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 11:21:51 -0000 Received: by mail-pb0-f47.google.com with SMTP id rr4so5259029pbb.20 for ; Mon, 20 May 2013 04:21:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=+Wv338h4InvBZz848qHZiRRlh2XfApde2e54Ngu06mE=; b=NaZ08TbieW6X9wHWPt9BFO5g7O2Hp0u6JMi5qaCUAZMYEirn0JeEPjNp3rPyhOx26H /0Q18cu+B6Ui+Hj1lLcUB8uSWqWiCMA3iEkEBA6oIKC9XYsPv0+MDg0QEdIgN0XJfBcl 1k4cn3g1eyqSJbdHp8C1nNDNbdpfbR6hs1Vt+GV2MtNWdXy2JRUjYHVRaRIIXp6GA5RB KnwUY7Tw6O99jCsgtu6u0mjAaD5hC7sWRDMraknSdReeYuA5HtMQfyIlE0ulyOpfrjq3 2haS5OSFY3T6irOBgidn5Pq+3e5e6AODOigb1jHg8JPXv5DjbhMJK1JyxTwJVuHkkTyj 5zxQ== X-Received: by 10.66.27.197 with SMTP id v5mr60000706pag.211.1369048908867; Mon, 20 May 2013 04:21:48 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id qi1sm25415710pac.21.2013.05.20.04.21.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 04:21:48 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1369041096.2083.23.camel@zakaz.uk.xensource.com> Date: Mon, 20 May 2013 19:21:43 +0800 Message-Id: <16FDAC42-14DE-4A63-9F43-CB4B3F662B51@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <20130520033726.GA9056@cbz-workstation> <1369041096.2083.23.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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 May 20, 2013, at 5:11 PM, Ian Campbell wrote: > On Mon, 2013-05-20 at 11:37 +0800, Chen Baozi wrote: >> Sorry, I think the problem described above only happened if I use "xen-syms" >> for debugging. If I switch to "xen", there is no such problem on paging though >> it still not work (phenomenons: couldn't see any output). > > xen-syms is not suitable for booting, only for pointing GDB at. > >> So the situation is that xen-syms doesn't work for either arm-cross2 branch >> or mainline, (I used it by mistake), while xen doesn't work in mainline but >> arm-cross2 branch. > > What is the failure mode here? I'm not sure which of your previous > symptoms were related to the use of xen-syms. I think xen-syms symptoms is because of my misusing. Sorry for my stupid. However, if I use "xen" (which works for your arm-cross2 branch) in mainline, there is not any output while booting. > > 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 May 20 11:24:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 11:24:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOCE-0004Br-VT; Mon, 20 May 2013 11:24:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOCE-0004Bd-0v for xen-arm@lists.xen.org; Mon, 20 May 2013 11:24:06 +0000 Received: from [85.158.138.51:51413] by server-6.bemta-3.messagelabs.com id 90/A4-14331-5D70A915; Mon, 20 May 2013 11:24:05 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1369049044!27764612!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4622 invoked from network); 20 May 2013 11:24:04 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 11:24:04 -0000 X-IronPort-AV: E=Sophos;i="4.87,707,1363132800"; d="scan'208";a="4761407" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 20 May 2013 11:24:04 +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.3; Mon, 20 May 2013 12:24:04 +0100 Message-ID: <1369049042.10868.21.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 20 May 2013 12:24:02 +0100 In-Reply-To: <16FDAC42-14DE-4A63-9F43-CB4B3F662B51@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <20130520033726.GA9056@cbz-workstation> <1369041096.2083.23.camel@zakaz.uk.xensource.com> <16FDAC42-14DE-4A63-9F43-CB4B3F662B51@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.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-20 at 19:21 +0800, Chen Baozi wrote: > On May 20, 2013, at 5:11 PM, Ian Campbell wrote: > > > On Mon, 2013-05-20 at 11:37 +0800, Chen Baozi wrote: > >> Sorry, I think the problem described above only happened if I use "xen-syms" > >> for debugging. If I switch to "xen", there is no such problem on paging though > >> it still not work (phenomenons: couldn't see any output). > > > > xen-syms is not suitable for booting, only for pointing GDB at. > > > >> So the situation is that xen-syms doesn't work for either arm-cross2 branch > >> or mainline, (I used it by mistake), while xen doesn't work in mainline but > >> arm-cross2 branch. > > > > What is the failure mode here? I'm not sure which of your previous > > symptoms were related to the use of xen-syms. > I think xen-syms symptoms is because of my misusing. Sorry for my stupid. > > However, if I use "xen" (which works for your arm-cross2 branch) in > mainline, there is not any output while booting. There have been some changes in mainline. You need to add "dtuart=serial0" to your bootargs (where serial0 is an alias defined in your dts). You may also want to re-enable early-printk for your platform, see docs/misc/arm/early-printk.txt. 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 May 20 11:24:09 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 11:24:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOCE-0004Br-VT; Mon, 20 May 2013 11:24:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOCE-0004Bd-0v for xen-arm@lists.xen.org; Mon, 20 May 2013 11:24:06 +0000 Received: from [85.158.138.51:51413] by server-6.bemta-3.messagelabs.com id 90/A4-14331-5D70A915; Mon, 20 May 2013 11:24:05 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1369049044!27764612!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.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4622 invoked from network); 20 May 2013 11:24:04 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 11:24:04 -0000 X-IronPort-AV: E=Sophos;i="4.87,707,1363132800"; d="scan'208";a="4761407" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 20 May 2013 11:24:04 +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.3; Mon, 20 May 2013 12:24:04 +0100 Message-ID: <1369049042.10868.21.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Chen Baozi Date: Mon, 20 May 2013 12:24:02 +0100 In-Reply-To: <16FDAC42-14DE-4A63-9F43-CB4B3F662B51@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <20130520033726.GA9056@cbz-workstation> <1369041096.2083.23.camel@zakaz.uk.xensource.com> <16FDAC42-14DE-4A63-9F43-CB4B3F662B51@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.xensource.com Subject: Re: [XenARM] Cannot create mini-os guest for arm64 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-05-20 at 19:21 +0800, Chen Baozi wrote: > On May 20, 2013, at 5:11 PM, Ian Campbell wrote: > > > On Mon, 2013-05-20 at 11:37 +0800, Chen Baozi wrote: > >> Sorry, I think the problem described above only happened if I use "xen-syms" > >> for debugging. If I switch to "xen", there is no such problem on paging though > >> it still not work (phenomenons: couldn't see any output). > > > > xen-syms is not suitable for booting, only for pointing GDB at. > > > >> So the situation is that xen-syms doesn't work for either arm-cross2 branch > >> or mainline, (I used it by mistake), while xen doesn't work in mainline but > >> arm-cross2 branch. > > > > What is the failure mode here? I'm not sure which of your previous > > symptoms were related to the use of xen-syms. > I think xen-syms symptoms is because of my misusing. Sorry for my stupid. > > However, if I use "xen" (which works for your arm-cross2 branch) in > mainline, there is not any output while booting. There have been some changes in mainline. You need to add "dtuart=serial0" to your bootargs (where serial0 is an alias defined in your dts). You may also want to re-enable early-printk for your platform, see docs/misc/arm/early-printk.txt. 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 May 20 12:12:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 12:12:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOxL-00078g-RK; Mon, 20 May 2013 12:12:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOxK-00078U-8a for xen-arm@lists.xen.org; Mon, 20 May 2013 12:12:46 +0000 Received: from [193.109.254.147:19733] by server-4.bemta-14.messagelabs.com id A9/85-29620-D331A915; Mon, 20 May 2013 12:12:45 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1369051955!9123675!1 X-Originating-IP: [209.85.192.179] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32649 invoked from network); 20 May 2013 12:12:37 -0000 Received: from mail-pd0-f179.google.com (HELO mail-pd0-f179.google.com) (209.85.192.179) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 12:12:37 -0000 Received: by mail-pd0-f179.google.com with SMTP id q11so235634pdj.38 for ; Mon, 20 May 2013 05:12:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=pYsrIhWjMuAj4cTEVOSGX3DFq6zZePA4ywaCP2Nxttw=; b=WUUH5HuQbf/XMkBL1KGLsXFz0kC9ld889MUt5/3mU+Ph9RSg0XdyHIWP4pNWORuRBn 3/f/bMFU28qs1r5UjgXm+CgakZrRbV3D0Ncd3QzYuX3qhM3F421jMfAeJt/mNw+yx1+M oxbFtAoeJ3PtsvvZmVmlG82r9x/p6oIzv1XaVnhTJ9QzWCicJIIoNTG0KjyU4O+WqZIf h6cfxTUg6LaTDA7kn3DmL2DIQ2yKUf8ZqhuUKuEuNq6hiUZRWvSB1sXtXhna1LwnpAZE RsOjx4PJN9dnqM2k4kBLQFfg2wcnDSn5sMFltjyAljZ9hRC9yQjdL1349SRiEdyHRHKQ uGnA== X-Received: by 10.68.114.100 with SMTP id jf4mr59677223pbb.144.1369051955662; Mon, 20 May 2013 05:12:35 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id wp6sm23908948pbc.29.2013.05.20.05.12.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 05:12:34 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1369049042.10868.21.camel@zakaz.uk.xensource.com> Date: Mon, 20 May 2013 20:12:25 +0800 Message-Id: <9C30E102-2174-42ED-8BDC-4929D07B2419@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <20130520033726.GA9056@cbz-workstation> <1369041096.2083.23.camel@zakaz.uk.xensource.com> <16FDAC42-14DE-4A63-9F43-CB4B3F662B51@gmail.com> <1369049042.10868.21.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] [Xen-devel] Cannot create mini-os guest for arm64 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 May 20, 2013, at 7:24 PM, Ian Campbell wrote: > On Mon, 2013-05-20 at 19:21 +0800, Chen Baozi wrote: >> On May 20, 2013, at 5:11 PM, Ian Campbell wrote: >> >>> On Mon, 2013-05-20 at 11:37 +0800, Chen Baozi wrote: >>>> Sorry, I think the problem described above only happened if I use "xen-syms" >>>> for debugging. If I switch to "xen", there is no such problem on paging though >>>> it still not work (phenomenons: couldn't see any output). >>> >>> xen-syms is not suitable for booting, only for pointing GDB at. >>> >>>> So the situation is that xen-syms doesn't work for either arm-cross2 branch >>>> or mainline, (I used it by mistake), while xen doesn't work in mainline but >>>> arm-cross2 branch. >>> >>> What is the failure mode here? I'm not sure which of your previous >>> symptoms were related to the use of xen-syms. >> I think xen-syms symptoms is because of my misusing. Sorry for my stupid. >> >> However, if I use "xen" (which works for your arm-cross2 branch) in >> mainline, there is not any output while booting. > > There have been some changes in mainline. You need to add > "dtuart=serial0" to your bootargs (where serial0 is an alias defined in > your dts). > > You may also want to re-enable early-printk for your platform, see > docs/misc/arm/early-printk.txt. Thanks a lot. It works for me. 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 May 20 12:12:50 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 20 May 2013 12:12:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOxL-00078g-RK; Mon, 20 May 2013 12:12:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeOxK-00078U-8a for xen-arm@lists.xen.org; Mon, 20 May 2013 12:12:46 +0000 Received: from [193.109.254.147:19733] by server-4.bemta-14.messagelabs.com id A9/85-29620-D331A915; Mon, 20 May 2013 12:12:45 +0000 X-Env-Sender: baozich@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1369051955!9123675!1 X-Originating-IP: [209.85.192.179] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32649 invoked from network); 20 May 2013 12:12:37 -0000 Received: from mail-pd0-f179.google.com (HELO mail-pd0-f179.google.com) (209.85.192.179) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 May 2013 12:12:37 -0000 Received: by mail-pd0-f179.google.com with SMTP id q11so235634pdj.38 for ; Mon, 20 May 2013 05:12:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=pYsrIhWjMuAj4cTEVOSGX3DFq6zZePA4ywaCP2Nxttw=; b=WUUH5HuQbf/XMkBL1KGLsXFz0kC9ld889MUt5/3mU+Ph9RSg0XdyHIWP4pNWORuRBn 3/f/bMFU28qs1r5UjgXm+CgakZrRbV3D0Ncd3QzYuX3qhM3F421jMfAeJt/mNw+yx1+M oxbFtAoeJ3PtsvvZmVmlG82r9x/p6oIzv1XaVnhTJ9QzWCicJIIoNTG0KjyU4O+WqZIf h6cfxTUg6LaTDA7kn3DmL2DIQ2yKUf8ZqhuUKuEuNq6hiUZRWvSB1sXtXhna1LwnpAZE RsOjx4PJN9dnqM2k4kBLQFfg2wcnDSn5sMFltjyAljZ9hRC9yQjdL1349SRiEdyHRHKQ uGnA== X-Received: by 10.68.114.100 with SMTP id jf4mr59677223pbb.144.1369051955662; Mon, 20 May 2013 05:12:35 -0700 (PDT) Received: from [172.20.120.222] ([222.240.177.42]) by mx.google.com with ESMTPSA id wp6sm23908948pbc.29.2013.05.20.05.12.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 05:12:34 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Chen Baozi In-Reply-To: <1369049042.10868.21.camel@zakaz.uk.xensource.com> Date: Mon, 20 May 2013 20:12:25 +0800 Message-Id: <9C30E102-2174-42ED-8BDC-4929D07B2419@gmail.com> References: <20130516094956.GA19578@cbz-workstation> <1368715271.24012.12.camel@hastur.hellion.org.uk> <1368721220.24012.18.camel@hastur.hellion.org.uk> <555BA60B-4CF8-4390-9095-D5B1E8B24D1A@gmail.com> <1368782768.24012.23.camel@hastur.hellion.org.uk> <20130517095814.GA17958@cbz-workstation> <1368801024.24012.48.camel@hastur.hellion.org.uk> <20130520011921.GA5502@cbz-workstation> <20130520033726.GA9056@cbz-workstation> <1369041096.2083.23.camel@zakaz.uk.xensource.com> <16FDAC42-14DE-4A63-9F43-CB4B3F662B51@gmail.com> <1369049042.10868.21.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1503) Cc: xen-arm@lists.xen.org, xen-devel@lists.xensource.com Subject: Re: [XenARM] [Xen-devel] Cannot create mini-os guest for arm64 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 May 20, 2013, at 7:24 PM, Ian Campbell wrote: > On Mon, 2013-05-20 at 19:21 +0800, Chen Baozi wrote: >> On May 20, 2013, at 5:11 PM, Ian Campbell wrote: >> >>> On Mon, 2013-05-20 at 11:37 +0800, Chen Baozi wrote: >>>> Sorry, I think the problem described above only happened if I use "xen-syms" >>>> for debugging. If I switch to "xen", there is no such problem on paging though >>>> it still not work (phenomenons: couldn't see any output). >>> >>> xen-syms is not suitable for booting, only for pointing GDB at. >>> >>>> So the situation is that xen-syms doesn't work for either arm-cross2 branch >>>> or mainline, (I used it by mistake), while xen doesn't work in mainline but >>>> arm-cross2 branch. >>> >>> What is the failure mode here? I'm not sure which of your previous >>> symptoms were related to the use of xen-syms. >> I think xen-syms symptoms is because of my misusing. Sorry for my stupid. >> >> However, if I use "xen" (which works for your arm-cross2 branch) in >> mainline, there is not any output while booting. > > There have been some changes in mainline. You need to add > "dtuart=serial0" to your bootargs (where serial0 is an alias defined in > your dts). > > You may also want to re-enable early-printk for your platform, see > docs/misc/arm/early-printk.txt. Thanks a lot. It works for me. 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 May 21 09:07:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 May 2013 09:07:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeiX5-0002vz-3q; Tue, 21 May 2013 09:06:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeiX2-0002vZ-Rq; Tue, 21 May 2013 09:06:57 +0000 Received: from [85.158.137.99:32975] by server-2.bemta-3.messagelabs.com id DE/6F-24763-F293B915; Tue, 21 May 2013 09:06:55 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1369127214!14476189!1 X-Originating-IP: [209.85.214.54] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10860 invoked from network); 21 May 2013 09:06:55 -0000 Received: from mail-bk0-f54.google.com (HELO mail-bk0-f54.google.com) (209.85.214.54) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 May 2013 09:06:55 -0000 Received: by mail-bk0-f54.google.com with SMTP id it19so205667bkc.13 for ; Tue, 21 May 2013 02:06:54 -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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=3Zo5hKCs8PBdEY4ErXh+1n/biMBZVHsBXVyq0Vqvpi8=; b=tGepqbhEr3lFI+EUExkASQWs6dY+bhO5ManK6scnc2WAKRBNiBnv6bBIYCwHYluGus /Qak7u680Uoy6uXHfnzX9uKuV6p4mTvKHpfym09KApzgdejYY93SIFQxa0gGPiPjM7hn iPJrW8RW0m+FTLnVasgxYQoKwHOJt3vBBWwXcW+l5rlgdSIX+wigLZ5l8DCVn+BtaOn7 3Yn174RBmYHl6KfoGV4Vj5kxeBFCYbNnf4sjVgFrs9sKlYsDdoMX2kgSKbpxwtMZGTiU sP+oYMbC3VIgBHj/dtdRt2BjGl/7Hhn9JECzFY4Z9HBi0lQ9t3/KT7S6kSm9aGuiJRfS bv6A== X-Received: by 10.205.115.196 with SMTP id ff4mr528355bkc.111.1369127214420; Tue, 21 May 2013 02:06:54 -0700 (PDT) Received: from [172.16.26.11] (0544f31a.skybroadband.com. [5.68.243.26]) by mx.google.com with ESMTPSA id cm9sm329799bkb.4.2013.05.21.02.06.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 02:06:53 -0700 (PDT) Message-ID: <519B3929.3080104@xen.org> Date: Tue, 21 May 2013 10:06:49 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Ian Campbell References: <5190C0BC.5060008@xen.org> <1369041476.2083.26.camel@zakaz.uk.xensource.com> In-Reply-To: <1369041476.2083.26.camel@zakaz.uk.xensource.com> Cc: "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) 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 > perhaps we could continue to vote using the old "+1" in an email mechanism? The reason for creating a form was to a) Ensure formal votes are private (i.e. there is a space to raise issues that may be difficult to raise in public) b) Make sure that the vote is recorded and can be easily gone back to (something which is a little hard on a list) c) Comply with the process Maybe a) does not apply at all or maybe only in limited circumstances. This point may be valid when it comes for votes related to incubating/graduating or archiving sub-projects though (because it may reflect on an individuals or companies leadership of a sub-project) and it may be harder to air an issue publicly. To be honest, the turn-out on these last two votes was really poor. We had only 4 votes (and only one from Citrix). Now this of course may be because the proposed changes were rather uncontroversial. On the other hand, you often use the argument that "if somebody can't be bothered following up on their bugs/patches/etc. then bugs/patches/etc. are obviously not important enough". I am inclined to use that same argument for voring on process and policy changes. Regards Lars On 20/05/2013 10:17, Ian Campbell wrote: > On Mon, 2013-05-13 at 11:30 +0100, Lars Kurth wrote: >> Rather than creating a voting form, I decided to use the voting >> feature >> on the newxenproject.org website. To vote, you need to create an >> account. If you have difficulties, let me know. The poll isat >> http://www.xenproject.org/help/questions-and-answers/vote-on-2014-event-locations.html. >> The vote will stay open until the middle of June. > I've voted using this now but in the future perhaps we could continue to > vote using the old "+1" in an email mechanism? > > There aren't so many maintainers and committers that this would be > unwieldy IMHO. > _______________________________________________ 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 May 21 09:07:01 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 21 May 2013 09:07:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeiX5-0002vz-3q; Tue, 21 May 2013 09:06:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UeiX2-0002vZ-Rq; Tue, 21 May 2013 09:06:57 +0000 Received: from [85.158.137.99:32975] by server-2.bemta-3.messagelabs.com id DE/6F-24763-F293B915; Tue, 21 May 2013 09:06:55 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1369127214!14476189!1 X-Originating-IP: [209.85.214.54] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10860 invoked from network); 21 May 2013 09:06:55 -0000 Received: from mail-bk0-f54.google.com (HELO mail-bk0-f54.google.com) (209.85.214.54) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 May 2013 09:06:55 -0000 Received: by mail-bk0-f54.google.com with SMTP id it19so205667bkc.13 for ; Tue, 21 May 2013 02:06:54 -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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=3Zo5hKCs8PBdEY4ErXh+1n/biMBZVHsBXVyq0Vqvpi8=; b=tGepqbhEr3lFI+EUExkASQWs6dY+bhO5ManK6scnc2WAKRBNiBnv6bBIYCwHYluGus /Qak7u680Uoy6uXHfnzX9uKuV6p4mTvKHpfym09KApzgdejYY93SIFQxa0gGPiPjM7hn iPJrW8RW0m+FTLnVasgxYQoKwHOJt3vBBWwXcW+l5rlgdSIX+wigLZ5l8DCVn+BtaOn7 3Yn174RBmYHl6KfoGV4Vj5kxeBFCYbNnf4sjVgFrs9sKlYsDdoMX2kgSKbpxwtMZGTiU sP+oYMbC3VIgBHj/dtdRt2BjGl/7Hhn9JECzFY4Z9HBi0lQ9t3/KT7S6kSm9aGuiJRfS bv6A== X-Received: by 10.205.115.196 with SMTP id ff4mr528355bkc.111.1369127214420; Tue, 21 May 2013 02:06:54 -0700 (PDT) Received: from [172.16.26.11] (0544f31a.skybroadband.com. [5.68.243.26]) by mx.google.com with ESMTPSA id cm9sm329799bkb.4.2013.05.21.02.06.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 02:06:53 -0700 (PDT) Message-ID: <519B3929.3080104@xen.org> Date: Tue, 21 May 2013 10:06:49 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Ian Campbell References: <5190C0BC.5060008@xen.org> <1369041476.2083.26.camel@zakaz.uk.xensource.com> In-Reply-To: <1369041476.2083.26.camel@zakaz.uk.xensource.com> Cc: "xen-arm@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [XenARM] [Xen-users] [Votes] Xen Project Governance v2 , Mailing List Conventions v1, 2014 Event Locations (open to all) 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 > perhaps we could continue to vote using the old "+1" in an email mechanism? The reason for creating a form was to a) Ensure formal votes are private (i.e. there is a space to raise issues that may be difficult to raise in public) b) Make sure that the vote is recorded and can be easily gone back to (something which is a little hard on a list) c) Comply with the process Maybe a) does not apply at all or maybe only in limited circumstances. This point may be valid when it comes for votes related to incubating/graduating or archiving sub-projects though (because it may reflect on an individuals or companies leadership of a sub-project) and it may be harder to air an issue publicly. To be honest, the turn-out on these last two votes was really poor. We had only 4 votes (and only one from Citrix). Now this of course may be because the proposed changes were rather uncontroversial. On the other hand, you often use the argument that "if somebody can't be bothered following up on their bugs/patches/etc. then bugs/patches/etc. are obviously not important enough". I am inclined to use that same argument for voring on process and policy changes. Regards Lars On 20/05/2013 10:17, Ian Campbell wrote: > On Mon, 2013-05-13 at 11:30 +0100, Lars Kurth wrote: >> Rather than creating a voting form, I decided to use the voting >> feature >> on the newxenproject.org website. To vote, you need to create an >> account. If you have difficulties, let me know. The poll isat >> http://www.xenproject.org/help/questions-and-answers/vote-on-2014-event-locations.html. >> The vote will stay open until the middle of June. > I've voted using this now but in the future perhaps we could continue to > vote using the old "+1" in an email mechanism? > > There aren't so many maintainers and committers that this would be > unwieldy IMHO. > _______________________________________________ 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 May 24 13:50:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 24 May 2013 13:50:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UfsOM-0005NT-Sv; Fri, 24 May 2013 13:50:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UfsOL-0005NC-7V for xen-arm@lists.xen.org; Fri, 24 May 2013 13:50:45 +0000 Received: from [85.158.143.99:31453] by server-1.bemta-4.messagelabs.com id 8B/BE-06122-4307F915; Fri, 24 May 2013 13:50:44 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1369403442!33886062!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12674 invoked from network); 24 May 2013 13:50:42 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 May 2013 13:50:42 -0000 Received: by mail-la0-f49.google.com with SMTP id fp13so4408223lab.8 for ; Fri, 24 May 2013 06:50:41 -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=6IRyZs+UOUgiYqjyOW4aiMuxYOfZSoz+LZpiQP4RWzI=; b=VkMNph4xJYVKOwJjaQLFYhkaJQYdr6T9n7tmNcs1Zz7Ni1YoTNcNWFftAvNlBBfiEz c8PRNndZ2HR5jgFu1DE677euySHWLPAXUdEbKL4IvzK66Qk79rhszEsvirqSRrH/iLGo B4EmWkQ1g10hmKnHP1qMCLWVOeTkdLZnmV2nhJwbDDm5DZEewQKiUT/e3DGjMq8u5vvR N0h5wmR9Ws1WVqxWaWjLTwFz5XCTvP8uwbeYpVfOK3rQxe18WqRicOFAv0UAQ/+mi288 4+rjZKUAeYQpEilCJ0R86TPnP3HGxgy4GkURqB4wgWm1EiQtu1uVFSfU6bpvqmLs91bU GeSQ== MIME-Version: 1.0 X-Received: by 10.152.22.4 with SMTP id z4mr8867188lae.37.1369403441637; Fri, 24 May 2013 06:50:41 -0700 (PDT) Received: by 10.112.1.100 with HTTP; Fri, 24 May 2013 06:50:41 -0700 (PDT) Date: Fri, 24 May 2013 09:50:41 -0400 X-Google-Sender-Auth: SDOP0orKE8bBYIyaYGXFPda8x5U Message-ID: From: Russ Pavlicek To: xen-arm@lists.xen.org Subject: [XenARM] Xen Document Day is next TUESDAY 28 May 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="===============8216389614559802685==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8216389614559802685== Content-Type: multipart/alternative; boundary=089e0158b8e2b1713304dd77158a --089e0158b8e2b1713304dd77158a Content-Type: text/plain; charset=ISO-8859-1 REMINDER: Xen Document Day is next TUESDAY due to holidays next Monday in multiple countries. ********************* * Xen Document Days * ********************* We have another Xen document day come up next *TUESDAY*. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO ). Of course, you can work on anything you like: the list just provides suggestions. How do I participate? ===================== - Join us on IRC: freenode channel #xendocs - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! --089e0158b8e2b1713304dd77158a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
REMINDER: Xen Document Day is next TUESDAY due to hol= idays next Monday
in multiple countries.

*********************
* Xen Document Days *
**********= ***********

We have another Xen document day come up next *TUESDAY*= . Xen Document Days=A0
are for people who care about Xen Document= ation and want to improve it.=A0
We introduced Documentation Days= , because working on documentation in=A0
parallel with like minded-people, is just more fun than working alone!= =A0
Everybody who can contribute is welcome to join!
For a list of items that need work, check out the community ma= intained=A0
work on anything you like: the list just provides suggestions.

How do I participate?
=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- Join us = on IRC: freenode channel #xendocs
- Tell people what you intend to work on (to avoid doing something som= ebody
=A0 =A0else is already working on)
- Fix some doc= umentation
- Help others
- And above all: have fun!
--089e0158b8e2b1713304dd77158a-- --===============8216389614559802685== 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 --===============8216389614559802685==-- From xen-arm-bounces@lists.xen.org Fri May 24 13:50:49 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 24 May 2013 13:50:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UfsOM-0005NT-Sv; Fri, 24 May 2013 13:50:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UfsOL-0005NC-7V for xen-arm@lists.xen.org; Fri, 24 May 2013 13:50:45 +0000 Received: from [85.158.143.99:31453] by server-1.bemta-4.messagelabs.com id 8B/BE-06122-4307F915; Fri, 24 May 2013 13:50:44 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1369403442!33886062!1 X-Originating-IP: [209.85.215.49] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.8.6.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12674 invoked from network); 24 May 2013 13:50:42 -0000 Received: from mail-la0-f49.google.com (HELO mail-la0-f49.google.com) (209.85.215.49) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 May 2013 13:50:42 -0000 Received: by mail-la0-f49.google.com with SMTP id fp13so4408223lab.8 for ; Fri, 24 May 2013 06:50:41 -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=6IRyZs+UOUgiYqjyOW4aiMuxYOfZSoz+LZpiQP4RWzI=; b=VkMNph4xJYVKOwJjaQLFYhkaJQYdr6T9n7tmNcs1Zz7Ni1YoTNcNWFftAvNlBBfiEz c8PRNndZ2HR5jgFu1DE677euySHWLPAXUdEbKL4IvzK66Qk79rhszEsvirqSRrH/iLGo B4EmWkQ1g10hmKnHP1qMCLWVOeTkdLZnmV2nhJwbDDm5DZEewQKiUT/e3DGjMq8u5vvR N0h5wmR9Ws1WVqxWaWjLTwFz5XCTvP8uwbeYpVfOK3rQxe18WqRicOFAv0UAQ/+mi288 4+rjZKUAeYQpEilCJ0R86TPnP3HGxgy4GkURqB4wgWm1EiQtu1uVFSfU6bpvqmLs91bU GeSQ== MIME-Version: 1.0 X-Received: by 10.152.22.4 with SMTP id z4mr8867188lae.37.1369403441637; Fri, 24 May 2013 06:50:41 -0700 (PDT) Received: by 10.112.1.100 with HTTP; Fri, 24 May 2013 06:50:41 -0700 (PDT) Date: Fri, 24 May 2013 09:50:41 -0400 X-Google-Sender-Auth: SDOP0orKE8bBYIyaYGXFPda8x5U Message-ID: From: Russ Pavlicek To: xen-arm@lists.xen.org Subject: [XenARM] Xen Document Day is next TUESDAY 28 May 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="===============8216389614559802685==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8216389614559802685== Content-Type: multipart/alternative; boundary=089e0158b8e2b1713304dd77158a --089e0158b8e2b1713304dd77158a Content-Type: text/plain; charset=ISO-8859-1 REMINDER: Xen Document Day is next TUESDAY due to holidays next Monday in multiple countries. ********************* * Xen Document Days * ********************* We have another Xen document day come up next *TUESDAY*. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO ). Of course, you can work on anything you like: the list just provides suggestions. How do I participate? ===================== - Join us on IRC: freenode channel #xendocs - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! --089e0158b8e2b1713304dd77158a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
REMINDER: Xen Document Day is next TUESDAY due to hol= idays next Monday
in multiple countries.

*********************
* Xen Document Days *
**********= ***********

We have another Xen document day come up next *TUESDAY*= . Xen Document Days=A0
are for people who care about Xen Document= ation and want to improve it.=A0
We introduced Documentation Days= , because working on documentation in=A0
parallel with like minded-people, is just more fun than working alone!= =A0
Everybody who can contribute is welcome to join!
For a list of items that need work, check out the community ma= intained=A0
work on anything you like: the list just provides suggestions.

How do I participate?
=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- Join us = on IRC: freenode channel #xendocs
- Tell people what you intend to work on (to avoid doing something som= ebody
=A0 =A0else is already working on)
- Fix some doc= umentation
- Help others
- And above all: have fun!
--089e0158b8e2b1713304dd77158a-- --===============8216389614559802685== 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 --===============8216389614559802685==-- From xen-arm-bounces@lists.xen.org Tue May 28 03:05:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 May 2013 03:05:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhAE4-0002Wd-Dr; Tue, 28 May 2013 03:05:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhAE2-0002WJ-9J; Tue, 28 May 2013 03:05:26 +0000 Received: from [85.158.138.51:30012] by server-4.bemta-3.messagelabs.com id 34/64-01776-4FE14A15; Tue, 28 May 2013 03:05:24 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1369710323!20734001!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8586 invoked from network); 28 May 2013 03:05:23 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 May 2013 03:05:23 -0000 Received: by mail-la0-f44.google.com with SMTP id fr10so7008438lab.31 for ; Mon, 27 May 2013 20:05:22 -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=tkkDdMHDs9uUXu6oQhQMRInUkORWU2VFmwX1J+2h8KA=; b=kjiQi9AQXouHBp1+2TtOTloEd8zwS54psPNPIG/0ilQixVxjSHdlvGxe0AIv/3FKjd 1fFql0vpvNOdZ7ngxDyJzTiE9p/tYb2osx4ybQBBu6xcvCGJOsqzbjjn7HIsFeVYij9I 183eTLvs59L8MtKITQco7oWxSqiyoUFEXj2jqR9/6dOPkEDYd+FrHHpAPcICIGvmtWCr hYPnG1d93/l1Lzi/pfpDU4qNfi1ZW2EwMIpwrRG01G2qc/FI6jXflWt7l7C2Y5j9TtvJ egbmxnXZF9hpHMGFN0VONtB3kbpxpKmZaNZL3JQ0bndtXwgXWNemw6ydW/wDbd77gwtv +SJw== MIME-Version: 1.0 X-Received: by 10.112.188.161 with SMTP id gb1mr4453040lbc.107.1369710321458; Mon, 27 May 2013 20:05:21 -0700 (PDT) Received: by 10.112.1.100 with HTTP; Mon, 27 May 2013 20:05:21 -0700 (PDT) Date: Mon, 27 May 2013 23:05:21 -0400 X-Google-Sender-Auth: MI8BOolqGqrDjvA9YgNyCECtTec Message-ID: From: Russ Pavlicek To: xen-api@lists.xen.org, xen-arm@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org Subject: [XenARM] Xen Document Day is Tuesday May 28 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="===============7560310050305932349==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============7560310050305932349== Content-Type: multipart/alternative; boundary=001a11c36dae27e2ad04ddbe8980 --001a11c36dae27e2ad04ddbe8980 Content-Type: text/plain; charset=ISO-8859-1 ********************* * Xen Document Days * ********************* Just a reminder that Xen Document Day is Tuesday May 28. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO ). Of course, you can work on anything you like: the list just provides suggestions. How do I participate? ===================== - Join us on IRC: freenode channel #xendocs - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! --001a11c36dae27e2ad04ddbe8980 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
*********************
* Xen Document Days *
*********************

Just a reminder that Xen Document Day is Tuesday May 28. =A0Xen Docume= nt Days=A0
are for people w= ho care about Xen Documentation and want to improve it.=A0
We introduced Documentatio= n Days, because working on documentation in=A0
parallel with li= ke minded-people, is just more fun than working alone!=A0
Everybody who can contribu= te is welcome to join!

For a list of items th= at need work, check out the community maintained=A0
<= div style=3D"font-family:arial,sans-serif;font-size:13px"><http://wik= i.xen.org/wiki/Xen_Document_Days/TODO>). Of course, you can=A0
work on anything= you like: the list just provides suggestions.

How do I participate?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /div>

<= div style=3D"font-family:arial,sans-serif;font-size:13px"> - Join us on IRC: freenode channel #xendocs
- Tell people what you intend to work on (= to avoid doing something somebody
=A0 =A0else is already working on)
- Fix some documentation
- Help others
- And above all: have fun!
--001a11c36dae27e2ad04ddbe8980-- --===============7560310050305932349== 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 --===============7560310050305932349==-- From xen-arm-bounces@lists.xen.org Tue May 28 03:05:31 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 28 May 2013 03:05:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhAE4-0002Wd-Dr; Tue, 28 May 2013 03:05:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhAE2-0002WJ-9J; Tue, 28 May 2013 03:05:26 +0000 Received: from [85.158.138.51:30012] by server-4.bemta-3.messagelabs.com id 34/64-01776-4FE14A15; Tue, 28 May 2013 03:05:24 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1369710323!20734001!1 X-Originating-IP: [209.85.215.44] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8586 invoked from network); 28 May 2013 03:05:23 -0000 Received: from mail-la0-f44.google.com (HELO mail-la0-f44.google.com) (209.85.215.44) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 28 May 2013 03:05:23 -0000 Received: by mail-la0-f44.google.com with SMTP id fr10so7008438lab.31 for ; Mon, 27 May 2013 20:05:22 -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=tkkDdMHDs9uUXu6oQhQMRInUkORWU2VFmwX1J+2h8KA=; b=kjiQi9AQXouHBp1+2TtOTloEd8zwS54psPNPIG/0ilQixVxjSHdlvGxe0AIv/3FKjd 1fFql0vpvNOdZ7ngxDyJzTiE9p/tYb2osx4ybQBBu6xcvCGJOsqzbjjn7HIsFeVYij9I 183eTLvs59L8MtKITQco7oWxSqiyoUFEXj2jqR9/6dOPkEDYd+FrHHpAPcICIGvmtWCr hYPnG1d93/l1Lzi/pfpDU4qNfi1ZW2EwMIpwrRG01G2qc/FI6jXflWt7l7C2Y5j9TtvJ egbmxnXZF9hpHMGFN0VONtB3kbpxpKmZaNZL3JQ0bndtXwgXWNemw6ydW/wDbd77gwtv +SJw== MIME-Version: 1.0 X-Received: by 10.112.188.161 with SMTP id gb1mr4453040lbc.107.1369710321458; Mon, 27 May 2013 20:05:21 -0700 (PDT) Received: by 10.112.1.100 with HTTP; Mon, 27 May 2013 20:05:21 -0700 (PDT) Date: Mon, 27 May 2013 23:05:21 -0400 X-Google-Sender-Auth: MI8BOolqGqrDjvA9YgNyCECtTec Message-ID: From: Russ Pavlicek To: xen-api@lists.xen.org, xen-arm@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org Subject: [XenARM] Xen Document Day is Tuesday May 28 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="===============7560310050305932349==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============7560310050305932349== Content-Type: multipart/alternative; boundary=001a11c36dae27e2ad04ddbe8980 --001a11c36dae27e2ad04ddbe8980 Content-Type: text/plain; charset=ISO-8859-1 ********************* * Xen Document Days * ********************* Just a reminder that Xen Document Day is Tuesday May 28. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO ). Of course, you can work on anything you like: the list just provides suggestions. How do I participate? ===================== - Join us on IRC: freenode channel #xendocs - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! --001a11c36dae27e2ad04ddbe8980 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
*********************
* Xen Document Days *
*********************

Just a reminder that Xen Document Day is Tuesday May 28. =A0Xen Docume= nt Days=A0
are for people w= ho care about Xen Documentation and want to improve it.=A0
We introduced Documentatio= n Days, because working on documentation in=A0
parallel with li= ke minded-people, is just more fun than working alone!=A0
Everybody who can contribu= te is welcome to join!

For a list of items th= at need work, check out the community maintained=A0
<= div style=3D"font-family:arial,sans-serif;font-size:13px"><http://wik= i.xen.org/wiki/Xen_Document_Days/TODO>). Of course, you can=A0
work on anything= you like: the list just provides suggestions.

How do I participate?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /div>

<= div style=3D"font-family:arial,sans-serif;font-size:13px"> - Join us on IRC: freenode channel #xendocs
- Tell people what you intend to work on (= to avoid doing something somebody
=A0 =A0else is already working on)
- Fix some documentation
- Help others
- And above all: have fun!
--001a11c36dae27e2ad04ddbe8980-- --===============7560310050305932349== 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 --===============7560310050305932349==-- From xen-arm-bounces@lists.xen.org Wed May 29 19:43:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 29 May 2013 19:43:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhmHO-0005xa-Ow; Wed, 29 May 2013 19:43:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhmHM-0005xG-Ok; Wed, 29 May 2013 19:43:24 +0000 Received: from [193.109.254.147:6384] by server-3.bemta-14.messagelabs.com id F2/95-06484-B5A56A15; Wed, 29 May 2013 19:43:23 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1369856594!10539246!1 X-Originating-IP: [209.85.215.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_18,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 871 invoked from network); 29 May 2013 19:43:22 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 May 2013 19:43:22 -0000 Received: by mail-la0-f52.google.com with SMTP id fo13so9127121lab.11 for ; Wed, 29 May 2013 12:43: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=+FGFTJIPdrUIMvKkj8ENzMapac8HQQ/9H3KVwMqRzt8=; b=0DOvYM3h8GDk311jHeiAUoPoWkxrFFIeOqxvIkoXgH8WNLpYUvbahZIGqI8Z+1nfN8 19kedICfL4j3DliZffg3VvLy7ALphurfsRFEGyW8HmR/gepa0f6jssBqz2ufKw+5zyqF bsU0G13thgk9EMop1lS5WgoYW4/OvlXQ+ZBawLJ6WZZdHPyfFHrX6EyA2wb8fNwvwPZ3 TON1A4/+Eoujuv5d9OjgNHJDl8xwN2rX32IXuZw246w41ynnrGtkFMOFP3NVa+HNd0C6 cGH2vwagh2tdryHPvDRt5TtEL9ihVwkzxV5HHs5no1ghaYjEUDXPQz539NhymO5ADM9g u+OA== MIME-Version: 1.0 X-Received: by 10.112.141.40 with SMTP id rl8mr2244928lbb.111.1369856584648; Wed, 29 May 2013 12:43:04 -0700 (PDT) Received: by 10.112.80.70 with HTTP; Wed, 29 May 2013 12:43:04 -0700 (PDT) Date: Wed, 29 May 2013 15:43:04 -0400 X-Google-Sender-Auth: 8cmY2jIRcT6dbfdSnHP0ofzBZZI Message-ID: From: Russ Pavlicek To: xen-users@lists.xen.org, xen-devel@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org Subject: [XenARM] Hear about Xen on The Linux Link Tech Show tonight at 8:30 PM EDT (GMT-4) 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="===============8827868148623292170==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8827868148623292170== Content-Type: multipart/alternative; boundary=001a11c268a61f0f0e04dde09732 --001a11c268a61f0f0e04dde09732 Content-Type: text/plain; charset=ISO-8859-1 Just a reminder that I will be talking about the Xen Project on The Linux Link Tech Show (TLLTS) tonight at 8:30 PM EDT (GMT-4). Streams and IRC info can be found here: http://tllts.org/livestreaminfo.php They do have a lively IRC channel during the show, so please join in and help answer questions about Xen as they arise! Also, Lars and I have another 4 speaking sessions in less than 2 weeks. If you are near Tokyo Japan, Austin Texas, or Charlotte North Carolina, we'd love to have you join us! http://blog.xen.org/index.php/2013/05/29/five-chances-to-hear-about-the-xen-project/ --001a11c268a61f0f0e04dde09732 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Just a reminder that I will be talking about the Xen Proje= ct on The Linux Link Tech Show (TLLTS) tonight at 8:30 PM EDT (GMT-4).
=
Streams and IRC info can be found here:=A0http://tllts.org/livestreaminfo.php=

They do have a lively IRC channel during th= e show, so please join in and help answer questions about Xen as they arise= !

Also, Lars and I have another 4 spea= king sessions in less than 2 weeks. =A0If you are near Tokyo Japan, Austin = Texas, or Charlotte North Carolina, we'd love to have you join us!

--001a11c268a61f0f0e04dde09732-- --===============8827868148623292170== 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 --===============8827868148623292170==-- From xen-arm-bounces@lists.xen.org Wed May 29 19:43:30 2013 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 29 May 2013 19:43:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhmHO-0005xa-Ow; Wed, 29 May 2013 19:43:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhmHM-0005xG-Ok; Wed, 29 May 2013 19:43:24 +0000 Received: from [193.109.254.147:6384] by server-3.bemta-14.messagelabs.com id F2/95-06484-B5A56A15; Wed, 29 May 2013 19:43:23 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1369856594!10539246!1 X-Originating-IP: [209.85.215.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_18,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 871 invoked from network); 29 May 2013 19:43:22 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 May 2013 19:43:22 -0000 Received: by mail-la0-f52.google.com with SMTP id fo13so9127121lab.11 for ; Wed, 29 May 2013 12:43: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=+FGFTJIPdrUIMvKkj8ENzMapac8HQQ/9H3KVwMqRzt8=; b=0DOvYM3h8GDk311jHeiAUoPoWkxrFFIeOqxvIkoXgH8WNLpYUvbahZIGqI8Z+1nfN8 19kedICfL4j3DliZffg3VvLy7ALphurfsRFEGyW8HmR/gepa0f6jssBqz2ufKw+5zyqF bsU0G13thgk9EMop1lS5WgoYW4/OvlXQ+ZBawLJ6WZZdHPyfFHrX6EyA2wb8fNwvwPZ3 TON1A4/+Eoujuv5d9OjgNHJDl8xwN2rX32IXuZw246w41ynnrGtkFMOFP3NVa+HNd0C6 cGH2vwagh2tdryHPvDRt5TtEL9ihVwkzxV5HHs5no1ghaYjEUDXPQz539NhymO5ADM9g u+OA== MIME-Version: 1.0 X-Received: by 10.112.141.40 with SMTP id rl8mr2244928lbb.111.1369856584648; Wed, 29 May 2013 12:43:04 -0700 (PDT) Received: by 10.112.80.70 with HTTP; Wed, 29 May 2013 12:43:04 -0700 (PDT) Date: Wed, 29 May 2013 15:43:04 -0400 X-Google-Sender-Auth: 8cmY2jIRcT6dbfdSnHP0ofzBZZI Message-ID: From: Russ Pavlicek To: xen-users@lists.xen.org, xen-devel@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org Subject: [XenARM] Hear about Xen on The Linux Link Tech Show tonight at 8:30 PM EDT (GMT-4) 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="===============8827868148623292170==" Sender: xen-arm-bounces@lists.xen.org Errors-To: xen-arm-bounces@lists.xen.org --===============8827868148623292170== Content-Type: multipart/alternative; boundary=001a11c268a61f0f0e04dde09732 --001a11c268a61f0f0e04dde09732 Content-Type: text/plain; charset=ISO-8859-1 Just a reminder that I will be talking about the Xen Project on The Linux Link Tech Show (TLLTS) tonight at 8:30 PM EDT (GMT-4). Streams and IRC info can be found here: http://tllts.org/livestreaminfo.php They do have a lively IRC channel during the show, so please join in and help answer questions about Xen as they arise! Also, Lars and I have another 4 speaking sessions in less than 2 weeks. If you are near Tokyo Japan, Austin Texas, or Charlotte North Carolina, we'd love to have you join us! http://blog.xen.org/index.php/2013/05/29/five-chances-to-hear-about-the-xen-project/ --001a11c268a61f0f0e04dde09732 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Just a reminder that I will be talking about the Xen Proje= ct on The Linux Link Tech Show (TLLTS) tonight at 8:30 PM EDT (GMT-4).
=
Streams and IRC info can be found here:=A0http://tllts.org/livestreaminfo.php=

They do have a lively IRC channel during th= e show, so please join in and help answer questions about Xen as they arise= !

Also, Lars and I have another 4 spea= king sessions in less than 2 weeks. =A0If you are near Tokyo Japan, Austin = Texas, or Charlotte North Carolina, we'd love to have you join us!

--001a11c268a61f0f0e04dde09732-- --===============8827868148623292170== 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 --===============8827868148623292170==--