From xen-arm-bounces@lists.xen.org Tue Oct 01 13:13:19 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 13:13:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VQzlM-0005Ki-7Z; Tue, 01 Oct 2013 13:13:16 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anshulmakkar@gmail.com>) id 1VQzlL-0005Kc-CM
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 13:13:15 +0000
Received: from [85.158.139.211:59835] by server-16.bemta-5.messagelabs.com id
	A9/C1-03533-A6ACA425; Tue, 01 Oct 2013 13:13:14 +0000
X-Env-Sender: anshulmakkar@gmail.com
X-Msg-Ref: server-4.tower-206.messagelabs.com!1380633191!5720647!1
X-Originating-IP: [209.85.160.43]
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.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29458 invoked from network); 1 Oct 2013 13:13:13 -0000
Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com)
	(209.85.160.43)
	by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Oct 2013 13:13:13 -0000
Received: by mail-pb0-f43.google.com with SMTP id md4so7075441pbc.30
	for <xen-arm@lists.xen.org>; Tue, 01 Oct 2013 06:13:11 -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=5MNv372BfX68Y6U42iA9zx9D4i+0jg/TZGwe6Iwmmsg=;
	b=d6A6tXnOTcODfar1IfjYKJmL3ASm1BCVuLdBXZKdxZ4Iw0ETcb2Wokrdf3ONHkHa7i
	MJ26OCPs9zhzw84XwNSkoYlxg0cGMhEz9uqMK8liH+ZvMcsDPAIlTZtGbS0VkvyN+M2Q
	ErXCuqSGxnFidMy7KHz7FgOwBKnm1FVlFcRlPirV36l/WvSsLcWvDxEYpMxykVyZHBa/
	wiDDA/PUS4Wf0UGnxz9hkcUN4ISMvQkEuPSskt/H1NgcaFkDhsdS+85aosO2xfE31ntG
	5wP6otwiVAEtWrE8bzkcDj8tErPdn5fpCdAVikjLgkGNvP7AeAuLkH5Ci2O6QJs4vvgu
	JN3A==
MIME-Version: 1.0
X-Received: by 10.66.25.173 with SMTP id d13mr5461293pag.146.1380633191584;
	Tue, 01 Oct 2013 06:13:11 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 06:13:11 -0700 (PDT)
Date: Tue, 1 Oct 2013 18:43:11 +0530
Message-ID: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
From: anshul makkar <anshulmakkar@gmail.com>
To: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>
Subject: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2599710128200705697=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============2599710128200705697==
Content-Type: multipart/alternative; boundary=bcaec52bec09f319ec04e7adb69c

--bcaec52bec09f319ec04e7adb69c
Content-Type: text/plain; charset=ISO-8859-1

Hi,
Sorry for my ignorance here, but thus Xen port of  ARM (PV) (Cortex A9
without hardware virtualization) supports running unmodified Android as
guest or guest needs to be necessarily patched to be able to run.

I know paravirtualization does mean that guest needs to be modified, but I
am just confused as I remember I read somewhere that Xen also supports full
virtualization. But not sure whether that has been ported on ARM.
-- 
Thanks
Anshul Makkar
www.justkernel.com
<http://www.linkedin.com/just-kernel>
http://www.linkedin.com/groups/Just-Kernel-3033180

--bcaec52bec09f319ec04e7adb69c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,<br>Sorry for my ignorance here, but thus Xen port=
 of=A0 ARM (PV) (Cortex=20
A9 without hardware virtualization) supports running unmodified Android=20
as guest or guest needs to be necessarily patched to be able to run.<br cle=
ar=3D"all"><br></div>I know paravirtualization does mean that guest needs t=
o be modified, but I am just confused as I remember I read somewhere that X=
en also supports full virtualization. But not sure whether that has been po=
rted on ARM.<br>
<div>-- <br>Thanks<br>Anshul Makkar<br><a href=3D"http://www.justkernel.com=
" target=3D"_blank">www.justkernel.com</a><br><a href=3D"http://www.linkedi=
n.com/just-kernel" target=3D"_blank"></a><a href=3D"http://www.linkedin.com=
/groups/Just-Kernel-3033180" target=3D"_blank">http://www.linkedin.com/grou=
ps/Just-Kernel-3033180</a><br>

</div></div>

--bcaec52bec09f319ec04e7adb69c--


--===============2599710128200705697==
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

--===============2599710128200705697==--


From xen-arm-bounces@lists.xen.org Tue Oct 01 13:13:19 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 13:13:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VQzlM-0005Ki-7Z; Tue, 01 Oct 2013 13:13:16 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anshulmakkar@gmail.com>) id 1VQzlL-0005Kc-CM
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 13:13:15 +0000
Received: from [85.158.139.211:59835] by server-16.bemta-5.messagelabs.com id
	A9/C1-03533-A6ACA425; Tue, 01 Oct 2013 13:13:14 +0000
X-Env-Sender: anshulmakkar@gmail.com
X-Msg-Ref: server-4.tower-206.messagelabs.com!1380633191!5720647!1
X-Originating-IP: [209.85.160.43]
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.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29458 invoked from network); 1 Oct 2013 13:13:13 -0000
Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com)
	(209.85.160.43)
	by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Oct 2013 13:13:13 -0000
Received: by mail-pb0-f43.google.com with SMTP id md4so7075441pbc.30
	for <xen-arm@lists.xen.org>; Tue, 01 Oct 2013 06:13:11 -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=5MNv372BfX68Y6U42iA9zx9D4i+0jg/TZGwe6Iwmmsg=;
	b=d6A6tXnOTcODfar1IfjYKJmL3ASm1BCVuLdBXZKdxZ4Iw0ETcb2Wokrdf3ONHkHa7i
	MJ26OCPs9zhzw84XwNSkoYlxg0cGMhEz9uqMK8liH+ZvMcsDPAIlTZtGbS0VkvyN+M2Q
	ErXCuqSGxnFidMy7KHz7FgOwBKnm1FVlFcRlPirV36l/WvSsLcWvDxEYpMxykVyZHBa/
	wiDDA/PUS4Wf0UGnxz9hkcUN4ISMvQkEuPSskt/H1NgcaFkDhsdS+85aosO2xfE31ntG
	5wP6otwiVAEtWrE8bzkcDj8tErPdn5fpCdAVikjLgkGNvP7AeAuLkH5Ci2O6QJs4vvgu
	JN3A==
MIME-Version: 1.0
X-Received: by 10.66.25.173 with SMTP id d13mr5461293pag.146.1380633191584;
	Tue, 01 Oct 2013 06:13:11 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 06:13:11 -0700 (PDT)
Date: Tue, 1 Oct 2013 18:43:11 +0530
Message-ID: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
From: anshul makkar <anshulmakkar@gmail.com>
To: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>
Subject: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2599710128200705697=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============2599710128200705697==
Content-Type: multipart/alternative; boundary=bcaec52bec09f319ec04e7adb69c

--bcaec52bec09f319ec04e7adb69c
Content-Type: text/plain; charset=ISO-8859-1

Hi,
Sorry for my ignorance here, but thus Xen port of  ARM (PV) (Cortex A9
without hardware virtualization) supports running unmodified Android as
guest or guest needs to be necessarily patched to be able to run.

I know paravirtualization does mean that guest needs to be modified, but I
am just confused as I remember I read somewhere that Xen also supports full
virtualization. But not sure whether that has been ported on ARM.
-- 
Thanks
Anshul Makkar
www.justkernel.com
<http://www.linkedin.com/just-kernel>
http://www.linkedin.com/groups/Just-Kernel-3033180

--bcaec52bec09f319ec04e7adb69c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,<br>Sorry for my ignorance here, but thus Xen port=
 of=A0 ARM (PV) (Cortex=20
A9 without hardware virtualization) supports running unmodified Android=20
as guest or guest needs to be necessarily patched to be able to run.<br cle=
ar=3D"all"><br></div>I know paravirtualization does mean that guest needs t=
o be modified, but I am just confused as I remember I read somewhere that X=
en also supports full virtualization. But not sure whether that has been po=
rted on ARM.<br>
<div>-- <br>Thanks<br>Anshul Makkar<br><a href=3D"http://www.justkernel.com=
" target=3D"_blank">www.justkernel.com</a><br><a href=3D"http://www.linkedi=
n.com/just-kernel" target=3D"_blank"></a><a href=3D"http://www.linkedin.com=
/groups/Just-Kernel-3033180" target=3D"_blank">http://www.linkedin.com/grou=
ps/Just-Kernel-3033180</a><br>

</div></div>

--bcaec52bec09f319ec04e7adb69c--


--===============2599710128200705697==
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

--===============2599710128200705697==--


From xen-arm-bounces@lists.xen.org Tue Oct 01 15:18:43 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 15:18:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VR1ih-0008Nb-RQ; Tue, 01 Oct 2013 15:18:39 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <SrujanKotikela@my.unt.edu>) id 1VR1ih-0008NW-7S
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 15:18:39 +0000
Received: from [193.109.254.147:43021] by server-3.bemta-14.messagelabs.com id
	B1/BB-11293-EC7EA425; Tue, 01 Oct 2013 15:18:38 +0000
X-Env-Sender: SrujanKotikela@my.unt.edu
X-Msg-Ref: server-3.tower-27.messagelabs.com!1380640716!2627496!1
X-Originating-IP: [213.199.154.189]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15687 invoked from network); 1 Oct 2013 15:18:37 -0000
Received: from mail-db8lp0189.outbound.messaging.microsoft.com (HELO
	db8outboundpool.messaging.microsoft.com) (213.199.154.189)
	by server-3.tower-27.messagelabs.com with AES128-SHA encrypted SMTP;
	1 Oct 2013 15:18:37 -0000
Received: from mail189-db8-R.bigfish.com (10.174.8.239) by
	DB8EHSOBE012.bigfish.com (10.174.4.75) with Microsoft SMTP Server id
	14.1.225.22; Tue, 1 Oct 2013 15:18:36 +0000
Received: from mail189-db8 (localhost [127.0.0.1])	by
	mail189-db8-R.bigfish.com (Postfix) with ESMTP id 82138D00219;
	Tue,  1 Oct 2013 15:18:36 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:132.245.6.229; KIP:(null); UIP:(null); IPV:NLI;
	H:BN1PRD0113HT001.prod.exchangelabs.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: PS1(zz98dIc85dhzz1f42h1d77h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h17326ah18c673h1de097h186068h1954cbh18602eh8275bhz2dh2a8h839hbe3hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18deh18e1h1946h19b5h1ad9h1b0ah1bceh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h20f0h17ej1155h)
Received: from mail189-db8 (localhost.localdomain [127.0.0.1]) by mail189-db8
	(MessageSwitch) id 1380640644382708_13381;
	Tue,  1 Oct 2013 15:17:24 +0000 (UTC)
Received: from DB8EHSMHS015.bigfish.com (unknown [10.174.8.226])	by
	mail189-db8.bigfish.com (Postfix) with ESMTP id 59AED640233;
	Tue,  1 Oct 2013 15:17:24 +0000 (UTC)
Received: from BN1PRD0113HT001.prod.exchangelabs.com (132.245.6.229) by
	DB8EHSMHS015.bigfish.com (10.174.4.25) with Microsoft SMTP Server (TLS)
	id 14.16.227.3; Tue, 1 Oct 2013 15:17:22 +0000
Received: from BN1PRD0113MB696.prod.exchangelabs.com ([169.254.16.153]) by
	BN1PRD0113HT001.prod.exchangelabs.com ([10.242.220.34]) with mapi id
	14.16.0359.001; Tue, 1 Oct 2013 15:17:15 +0000
From: "Kotikela, Srujan" <SrujanKotikela@my.unt.edu>
To: anshul makkar <anshulmakkar@gmail.com>, "xen-arm@lists.xen.org"
	<xen-arm@lists.xen.org>
Thread-Topic: [XenARM] Support of unmodified guest
Thread-Index: AQHOvqgAa04AhjmBf0WrXvjfy8xNdZnf9U1h
Date: Tue, 1 Oct 2013 15:17:13 +0000
Message-ID: <245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
In-Reply-To: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [::]
MIME-Version: 1.0
X-OriginatorOrg: my.unt.edu
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============4462270653172065337=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============4462270653172065337==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_245u5sumqxcaomy3nun4pngl1380640648010emailandroidcom_"

--_000_245u5sumqxcaomy3nun4pngl1380640648010emailandroidcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Anshul,

Xen does support unmodified OS on arm. It is available in the upstream xen.=
 It is not a separate project.

Srujan

anshul makkar <anshulmakkar@gmail.com> wrote:



Hi,
Sorry for my ignorance here, but thus Xen port of  ARM (PV) (Cortex A9 with=
out hardware virtualization) supports running unmodified Android as guest o=
r guest needs to be necessarily patched to be able to run.

I know paravirtualization does mean that guest needs to be modified, but I =
am just confused as I remember I read somewhere that Xen also supports full=
 virtualization. But not sure whether that has been ported on ARM.
--
Thanks
Anshul Makkar
www.justkernel.com<http://www.justkernel.com>
<http://www.linkedin.com/just-kernel>http://www.linkedin.com/groups/Just-Ke=
rnel-3033180

--_000_245u5sumqxcaomy3nun4pngl1380640648010emailandroidcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body>
<pre style=3D"word-wrap:break-word; font-size:10.0pt; font-family:Tahoma; c=
olor:black">Hi Anshul,=0A=
=0A=
Xen does support unmodified OS on arm. It is available in the upstream xen.=
 It is not a separate project.=0A=
=0A=
Srujan =0A=
=0A=
anshul makkar &lt;anshulmakkar@gmail.com&gt; wrote:=0A=
=0A=
</pre>
<div>
<div dir=3D"ltr">
<div>Hi,<br>
Sorry for my ignorance here, but thus Xen port of&nbsp; ARM (PV) (Cortex A9=
 without hardware virtualization) supports running unmodified Android as gu=
est or guest needs to be necessarily patched to be able to run.<br clear=3D=
"all">
<br>
</div>
I know paravirtualization does mean that guest needs to be modified, but I =
am just confused as I remember I read somewhere that Xen also supports full=
 virtualization. But not sure whether that has been ported on ARM.<br>
<div>-- <br>
Thanks<br>
Anshul Makkar<br>
<a href=3D"http://www.justkernel.com" target=3D"_blank">www.justkernel.com<=
/a><br>
<a href=3D"http://www.linkedin.com/just-kernel" target=3D"_blank"></a><a hr=
ef=3D"http://www.linkedin.com/groups/Just-Kernel-3033180" target=3D"_blank"=
>http://www.linkedin.com/groups/Just-Kernel-3033180</a><br>
</div>
</div>
</div>
</body>
</html>

--_000_245u5sumqxcaomy3nun4pngl1380640648010emailandroidcom_--


--===============4462270653172065337==
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

--===============4462270653172065337==--


From xen-arm-bounces@lists.xen.org Tue Oct 01 15:18:43 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 15:18:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VR1ih-0008Nb-RQ; Tue, 01 Oct 2013 15:18:39 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <SrujanKotikela@my.unt.edu>) id 1VR1ih-0008NW-7S
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 15:18:39 +0000
Received: from [193.109.254.147:43021] by server-3.bemta-14.messagelabs.com id
	B1/BB-11293-EC7EA425; Tue, 01 Oct 2013 15:18:38 +0000
X-Env-Sender: SrujanKotikela@my.unt.edu
X-Msg-Ref: server-3.tower-27.messagelabs.com!1380640716!2627496!1
X-Originating-IP: [213.199.154.189]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15687 invoked from network); 1 Oct 2013 15:18:37 -0000
Received: from mail-db8lp0189.outbound.messaging.microsoft.com (HELO
	db8outboundpool.messaging.microsoft.com) (213.199.154.189)
	by server-3.tower-27.messagelabs.com with AES128-SHA encrypted SMTP;
	1 Oct 2013 15:18:37 -0000
Received: from mail189-db8-R.bigfish.com (10.174.8.239) by
	DB8EHSOBE012.bigfish.com (10.174.4.75) with Microsoft SMTP Server id
	14.1.225.22; Tue, 1 Oct 2013 15:18:36 +0000
Received: from mail189-db8 (localhost [127.0.0.1])	by
	mail189-db8-R.bigfish.com (Postfix) with ESMTP id 82138D00219;
	Tue,  1 Oct 2013 15:18:36 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:132.245.6.229; KIP:(null); UIP:(null); IPV:NLI;
	H:BN1PRD0113HT001.prod.exchangelabs.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: PS1(zz98dIc85dhzz1f42h1d77h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h17326ah18c673h1de097h186068h1954cbh18602eh8275bhz2dh2a8h839hbe3hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18deh18e1h1946h19b5h1ad9h1b0ah1bceh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h20f0h17ej1155h)
Received: from mail189-db8 (localhost.localdomain [127.0.0.1]) by mail189-db8
	(MessageSwitch) id 1380640644382708_13381;
	Tue,  1 Oct 2013 15:17:24 +0000 (UTC)
Received: from DB8EHSMHS015.bigfish.com (unknown [10.174.8.226])	by
	mail189-db8.bigfish.com (Postfix) with ESMTP id 59AED640233;
	Tue,  1 Oct 2013 15:17:24 +0000 (UTC)
Received: from BN1PRD0113HT001.prod.exchangelabs.com (132.245.6.229) by
	DB8EHSMHS015.bigfish.com (10.174.4.25) with Microsoft SMTP Server (TLS)
	id 14.16.227.3; Tue, 1 Oct 2013 15:17:22 +0000
Received: from BN1PRD0113MB696.prod.exchangelabs.com ([169.254.16.153]) by
	BN1PRD0113HT001.prod.exchangelabs.com ([10.242.220.34]) with mapi id
	14.16.0359.001; Tue, 1 Oct 2013 15:17:15 +0000
From: "Kotikela, Srujan" <SrujanKotikela@my.unt.edu>
To: anshul makkar <anshulmakkar@gmail.com>, "xen-arm@lists.xen.org"
	<xen-arm@lists.xen.org>
Thread-Topic: [XenARM] Support of unmodified guest
Thread-Index: AQHOvqgAa04AhjmBf0WrXvjfy8xNdZnf9U1h
Date: Tue, 1 Oct 2013 15:17:13 +0000
Message-ID: <245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
In-Reply-To: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [::]
MIME-Version: 1.0
X-OriginatorOrg: my.unt.edu
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============4462270653172065337=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============4462270653172065337==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_245u5sumqxcaomy3nun4pngl1380640648010emailandroidcom_"

--_000_245u5sumqxcaomy3nun4pngl1380640648010emailandroidcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Anshul,

Xen does support unmodified OS on arm. It is available in the upstream xen.=
 It is not a separate project.

Srujan

anshul makkar <anshulmakkar@gmail.com> wrote:



Hi,
Sorry for my ignorance here, but thus Xen port of  ARM (PV) (Cortex A9 with=
out hardware virtualization) supports running unmodified Android as guest o=
r guest needs to be necessarily patched to be able to run.

I know paravirtualization does mean that guest needs to be modified, but I =
am just confused as I remember I read somewhere that Xen also supports full=
 virtualization. But not sure whether that has been ported on ARM.
--
Thanks
Anshul Makkar
www.justkernel.com<http://www.justkernel.com>
<http://www.linkedin.com/just-kernel>http://www.linkedin.com/groups/Just-Ke=
rnel-3033180

--_000_245u5sumqxcaomy3nun4pngl1380640648010emailandroidcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body>
<pre style=3D"word-wrap:break-word; font-size:10.0pt; font-family:Tahoma; c=
olor:black">Hi Anshul,=0A=
=0A=
Xen does support unmodified OS on arm. It is available in the upstream xen.=
 It is not a separate project.=0A=
=0A=
Srujan =0A=
=0A=
anshul makkar &lt;anshulmakkar@gmail.com&gt; wrote:=0A=
=0A=
</pre>
<div>
<div dir=3D"ltr">
<div>Hi,<br>
Sorry for my ignorance here, but thus Xen port of&nbsp; ARM (PV) (Cortex A9=
 without hardware virtualization) supports running unmodified Android as gu=
est or guest needs to be necessarily patched to be able to run.<br clear=3D=
"all">
<br>
</div>
I know paravirtualization does mean that guest needs to be modified, but I =
am just confused as I remember I read somewhere that Xen also supports full=
 virtualization. But not sure whether that has been ported on ARM.<br>
<div>-- <br>
Thanks<br>
Anshul Makkar<br>
<a href=3D"http://www.justkernel.com" target=3D"_blank">www.justkernel.com<=
/a><br>
<a href=3D"http://www.linkedin.com/just-kernel" target=3D"_blank"></a><a hr=
ef=3D"http://www.linkedin.com/groups/Just-Kernel-3033180" target=3D"_blank"=
>http://www.linkedin.com/groups/Just-Kernel-3033180</a><br>
</div>
</div>
</div>
</body>
</html>

--_000_245u5sumqxcaomy3nun4pngl1380640648010emailandroidcom_--


--===============4462270653172065337==
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

--===============4462270653172065337==--


From xen-arm-bounces@lists.xen.org Tue Oct 01 17:55:41 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 17:55:41 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VR4Ab-0003Fl-6Z; Tue, 01 Oct 2013 17:55:37 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anshulmakkar@gmail.com>) id 1VR4AZ-0003Fg-U4
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 17:55:36 +0000
Received: from [85.158.143.35:16721] by server-2.bemta-4.messagelabs.com id
	33/A4-31802-79C0B425; Tue, 01 Oct 2013 17:55:35 +0000
X-Env-Sender: anshulmakkar@gmail.com
X-Msg-Ref: server-3.tower-21.messagelabs.com!1380650132!7934129!1
X-Originating-IP: [209.85.192.174]
X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28444 invoked from network); 1 Oct 2013 17:55:33 -0000
Received: from mail-pd0-f174.google.com (HELO mail-pd0-f174.google.com)
	(209.85.192.174)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Oct 2013 17:55:33 -0000
Received: by mail-pd0-f174.google.com with SMTP id y13so7616186pdi.33
	for <xen-arm@lists.xen.org>; Tue, 01 Oct 2013 10:55:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=SJ3c66uMdIKCUFHib+uHvva6nTsU8CJ591nK7jxz6Vk=;
	b=oOQNeqvIuemAy2x/I4bTu7C7TSNYskj7wLkIdxx+Iz821e/qFBbxpPv4NQqJaefVQ8
	GUVgS7JBa3fAeNdP+4Ga7X6Jfn8/YtEXwDXze/tUQLFoEmSqxf4ni/IzfLBSfFeb9/KU
	ovmpMMbSAAFdAHPvV7C3cJLfojoTW9F1lPIKQQtKUACArdGbbh1uTXVNDJozxLedpIou
	f1EPR1zFWUfaJYlELVI7xcGa7vz7GMSe3UTR+dwc5MZxFppI/iopKqh4qbmDNML4s8p6
	itkeA5WduWcvKhr/Tr8M+kn12QOxouuklwFLooJIW4ZgZz4ymkMxRd1K6Vqq1LLWRuom
	Inow==
MIME-Version: 1.0
X-Received: by 10.68.101.37 with SMTP id fd5mr10026157pbb.158.1380650131948;
	Tue, 01 Oct 2013 10:55:31 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 10:55:31 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 10:55:31 -0700 (PDT)
In-Reply-To: <CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
	<245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
	<CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
Date: Tue, 1 Oct 2013 23:25:31 +0530
Message-ID: <CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
From: anshul makkar <anshulmakkar@gmail.com>
To: Srujan Kotikela <SrujanKotikela@my.unt.edu>
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============3491580697857900083=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============3491580697857900083==
Content-Type: multipart/alternative; boundary=047d7b86f6fcac8bfc04e7b1a89e

--047d7b86f6fcac8bfc04e7b1a89e
Content-Type: text/plain; charset=ISO-8859-1

Hi srujan,  thanks for the reply.
So it means Xen provides full virtualization support as well.

Thanks
Anshul make
On 1 Oct 2013 20:49, "Kotikela, Srujan" <SrujanKotikela@my.unt.edu> wrote:

 Hi Anshul,

Xen does support unmodified OS on arm. It is available in the upstream
xen. It is not a separate project.

Srujan

anshul makkar <anshulmakkar@gmail.com> wrote:


 Hi,
Sorry for my ignorance here, but thus Xen port of  ARM (PV) (Cortex A9
without hardware virtualization) supports running unmodified Android as
guest or guest needs to be necessarily patched to be able to run.

 I know paravirtualization does mean that guest needs to be modified, but I
am just confused as I remember I read somewhere that Xen also supports full
virtualization. But not sure whether that has been ported on ARM.
-- 
Thanks
Anshul Makkar
www.justkernel.com
 <http://www.linkedin.com/just-kernel>
http://www.linkedin.com/groups/Just-Kernel-3033180

--047d7b86f6fcac8bfc04e7b1a89e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hi srujan,=A0 thanks for the reply.<br>
So it means Xen provides full virtualization support as well.=A0 </p>
<p dir=3D"ltr">Thanks<br>
Anshul make</p>
<div class=3D"gmail_quote">On 1 Oct 2013 20:49, &quot;Kotikela, Srujan&quot=
; &lt;<a href=3D"mailto:SrujanKotikela@my.unt.edu">SrujanKotikela@my.unt.ed=
u</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div>
<pre style=3D"font-size:10.0pt;font-family:Tahoma;word-wrap:break-word">Hi =
Anshul,

Xen does support unmodified OS on arm. It is available in the upstream xen.=
 It is not a separate project.

Srujan=20

anshul makkar &lt;<a href=3D"mailto:anshulmakkar@gmail.com" target=3D"_blan=
k">anshulmakkar@gmail.com</a>&gt; wrote:

</pre><div class=3D"elided-text">
<div>
<div dir=3D"ltr">
<div>Hi,<br>
Sorry for my ignorance here, but thus Xen port of=A0 ARM (PV) (Cortex A9 wi=
thout hardware virtualization) supports running unmodified Android as guest=
 or guest needs to be necessarily patched to be able to run.<br clear=3D"al=
l">

<br>
</div>
I know paravirtualization does mean that guest needs to be modified, but I =
am just confused as I remember I read somewhere that Xen also supports full=
 virtualization. But not sure whether that has been ported on ARM.<br>

<div>-- <br>
Thanks<br>
Anshul Makkar<br>
<a href=3D"http://www.justkernel.com" target=3D"_blank">www.justkernel.com<=
/a><br>
<a href=3D"http://www.linkedin.com/just-kernel" target=3D"_blank"></a><a hr=
ef=3D"http://www.linkedin.com/groups/Just-Kernel-3033180" target=3D"_blank"=
>http://www.linkedin.com/groups/Just-Kernel-3033180</a><br>
</div>
</div>
</div>
</div></div>

</blockquote></div>

--047d7b86f6fcac8bfc04e7b1a89e--


--===============3491580697857900083==
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

--===============3491580697857900083==--


From xen-arm-bounces@lists.xen.org Tue Oct 01 17:55:41 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 17:55:41 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VR4Ab-0003Fl-6Z; Tue, 01 Oct 2013 17:55:37 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anshulmakkar@gmail.com>) id 1VR4AZ-0003Fg-U4
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 17:55:36 +0000
Received: from [85.158.143.35:16721] by server-2.bemta-4.messagelabs.com id
	33/A4-31802-79C0B425; Tue, 01 Oct 2013 17:55:35 +0000
X-Env-Sender: anshulmakkar@gmail.com
X-Msg-Ref: server-3.tower-21.messagelabs.com!1380650132!7934129!1
X-Originating-IP: [209.85.192.174]
X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28444 invoked from network); 1 Oct 2013 17:55:33 -0000
Received: from mail-pd0-f174.google.com (HELO mail-pd0-f174.google.com)
	(209.85.192.174)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Oct 2013 17:55:33 -0000
Received: by mail-pd0-f174.google.com with SMTP id y13so7616186pdi.33
	for <xen-arm@lists.xen.org>; Tue, 01 Oct 2013 10:55:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=SJ3c66uMdIKCUFHib+uHvva6nTsU8CJ591nK7jxz6Vk=;
	b=oOQNeqvIuemAy2x/I4bTu7C7TSNYskj7wLkIdxx+Iz821e/qFBbxpPv4NQqJaefVQ8
	GUVgS7JBa3fAeNdP+4Ga7X6Jfn8/YtEXwDXze/tUQLFoEmSqxf4ni/IzfLBSfFeb9/KU
	ovmpMMbSAAFdAHPvV7C3cJLfojoTW9F1lPIKQQtKUACArdGbbh1uTXVNDJozxLedpIou
	f1EPR1zFWUfaJYlELVI7xcGa7vz7GMSe3UTR+dwc5MZxFppI/iopKqh4qbmDNML4s8p6
	itkeA5WduWcvKhr/Tr8M+kn12QOxouuklwFLooJIW4ZgZz4ymkMxRd1K6Vqq1LLWRuom
	Inow==
MIME-Version: 1.0
X-Received: by 10.68.101.37 with SMTP id fd5mr10026157pbb.158.1380650131948;
	Tue, 01 Oct 2013 10:55:31 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 10:55:31 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 10:55:31 -0700 (PDT)
In-Reply-To: <CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
	<245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
	<CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
Date: Tue, 1 Oct 2013 23:25:31 +0530
Message-ID: <CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
From: anshul makkar <anshulmakkar@gmail.com>
To: Srujan Kotikela <SrujanKotikela@my.unt.edu>
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============3491580697857900083=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============3491580697857900083==
Content-Type: multipart/alternative; boundary=047d7b86f6fcac8bfc04e7b1a89e

--047d7b86f6fcac8bfc04e7b1a89e
Content-Type: text/plain; charset=ISO-8859-1

Hi srujan,  thanks for the reply.
So it means Xen provides full virtualization support as well.

Thanks
Anshul make
On 1 Oct 2013 20:49, "Kotikela, Srujan" <SrujanKotikela@my.unt.edu> wrote:

 Hi Anshul,

Xen does support unmodified OS on arm. It is available in the upstream
xen. It is not a separate project.

Srujan

anshul makkar <anshulmakkar@gmail.com> wrote:


 Hi,
Sorry for my ignorance here, but thus Xen port of  ARM (PV) (Cortex A9
without hardware virtualization) supports running unmodified Android as
guest or guest needs to be necessarily patched to be able to run.

 I know paravirtualization does mean that guest needs to be modified, but I
am just confused as I remember I read somewhere that Xen also supports full
virtualization. But not sure whether that has been ported on ARM.
-- 
Thanks
Anshul Makkar
www.justkernel.com
 <http://www.linkedin.com/just-kernel>
http://www.linkedin.com/groups/Just-Kernel-3033180

--047d7b86f6fcac8bfc04e7b1a89e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hi srujan,=A0 thanks for the reply.<br>
So it means Xen provides full virtualization support as well.=A0 </p>
<p dir=3D"ltr">Thanks<br>
Anshul make</p>
<div class=3D"gmail_quote">On 1 Oct 2013 20:49, &quot;Kotikela, Srujan&quot=
; &lt;<a href=3D"mailto:SrujanKotikela@my.unt.edu">SrujanKotikela@my.unt.ed=
u</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div>
<pre style=3D"font-size:10.0pt;font-family:Tahoma;word-wrap:break-word">Hi =
Anshul,

Xen does support unmodified OS on arm. It is available in the upstream xen.=
 It is not a separate project.

Srujan=20

anshul makkar &lt;<a href=3D"mailto:anshulmakkar@gmail.com" target=3D"_blan=
k">anshulmakkar@gmail.com</a>&gt; wrote:

</pre><div class=3D"elided-text">
<div>
<div dir=3D"ltr">
<div>Hi,<br>
Sorry for my ignorance here, but thus Xen port of=A0 ARM (PV) (Cortex A9 wi=
thout hardware virtualization) supports running unmodified Android as guest=
 or guest needs to be necessarily patched to be able to run.<br clear=3D"al=
l">

<br>
</div>
I know paravirtualization does mean that guest needs to be modified, but I =
am just confused as I remember I read somewhere that Xen also supports full=
 virtualization. But not sure whether that has been ported on ARM.<br>

<div>-- <br>
Thanks<br>
Anshul Makkar<br>
<a href=3D"http://www.justkernel.com" target=3D"_blank">www.justkernel.com<=
/a><br>
<a href=3D"http://www.linkedin.com/just-kernel" target=3D"_blank"></a><a hr=
ef=3D"http://www.linkedin.com/groups/Just-Kernel-3033180" target=3D"_blank"=
>http://www.linkedin.com/groups/Just-Kernel-3033180</a><br>
</div>
</div>
</div>
</div></div>

</blockquote></div>

--047d7b86f6fcac8bfc04e7b1a89e--


--===============3491580697857900083==
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

--===============3491580697857900083==--


From xen-arm-bounces@lists.xen.org Tue Oct 01 18:00:58 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 18:00:58 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VR4Fj-0003WG-4g; Tue, 01 Oct 2013 18:00:55 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Stefano.Stabellini@eu.citrix.com>)
	id 1VR4Fh-0003W3-Ll
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 18:00:53 +0000
Received: from [85.158.143.35:46447] by server-2.bemta-4.messagelabs.com id
	80/58-31802-4DD0B425; Tue, 01 Oct 2013 18:00:52 +0000
X-Env-Sender: Stefano.Stabellini@eu.citrix.com
X-Msg-Ref: server-6.tower-21.messagelabs.com!1380650449!2863916!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.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26974 invoked from network); 1 Oct 2013 18:00:51 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Oct 2013 18:00:51 -0000
X-IronPort-AV: E=Sophos;i="4.90,1014,1371081600"; d="scan'208";a="56657177"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 01 Oct 2013 18:00:37 +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.4;
	Tue, 1 Oct 2013 14:00:36 -0400
Received: from kaball.uk.xensource.com ([10.80.2.59])	by
	ukmail1.uk.xensource.com with esmtp (Exim 4.69)	(envelope-from
	<stefano.stabellini@eu.citrix.com>)	id 1VR4FQ-00050C-W1;
	Tue, 01 Oct 2013 19:00:37 +0100
Date: Tue, 1 Oct 2013 18:59:54 +0100
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
X-X-Sender: sstabellini@kaball.uk.xensource.com
To: anshul makkar <anshulmakkar@gmail.com>
In-Reply-To: <CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1310011856483.26077@kaball.uk.xensource.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
	<245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
	<CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
	<CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="1342847746-1322536005-1380650394=:26077"
X-DLP: MIA1
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--1342847746-1322536005-1380650394=:26077
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: QUOTED-PRINTABLE

Anshul,
if you would like to know more about the Xen on ARM with virtualization
extensions project, give a look at:

http://www.xenproject.org/help/presentations-and-videos/video/latest/linaro=
-connect-introduction-to-xen-on-arm.html

the slides have been used during a Linaro presentation that has been
recorded, the video is available here:

www.youtube.com/watch?v=3DD0mTOKhAm6Y

Unfortunately the framing is very bad, but the audio might help you
better understand the slides.



On Tue, 1 Oct 2013, anshul makkar wrote:
> Hi srujan,=C2=A0 thanks for the reply.
> So it means Xen provides full virtualization support as well.=C2=A0
>=20
> Thanks
> Anshul make
>=20
> On 1 Oct 2013 20:49, "Kotikela, Srujan" <SrujanKotikela@my.unt.edu> wrote=
:
>=20
> Hi Anshul,
>=20
> Xen does support unmodified OS on arm. It is available in the upstream xe=
n. It is not a separate project.
>=20
> Srujan=20
>=20
> anshul makkar <anshulmakkar@gmail.com> wrote:
>=20
>       Hi,
>       Sorry for my ignorance here, but thus Xen port of=C2=A0 ARM (PV) (C=
ortex A9 without hardware virtualization) supports
>       running unmodified Android as guest or guest needs to be necessaril=
y patched to be able to run.
>=20
> I know paravirtualization does mean that guest needs to be modified, but =
I am just confused as I remember I read somewhere
> that Xen also supports full virtualization. But not sure whether that has=
 been ported on ARM.
> --
> Thanks
> Anshul Makkar
> www.justkernel.com
> http://www.linkedin.com/groups/Just-Kernel-3033180
>=20
>=20
>=20
--1342847746-1322536005-1380650394=:26077
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

--1342847746-1322536005-1380650394=:26077--


From xen-arm-bounces@lists.xen.org Tue Oct 01 18:00:58 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 18:00:58 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VR4Fj-0003WG-4g; Tue, 01 Oct 2013 18:00:55 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Stefano.Stabellini@eu.citrix.com>)
	id 1VR4Fh-0003W3-Ll
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 18:00:53 +0000
Received: from [85.158.143.35:46447] by server-2.bemta-4.messagelabs.com id
	80/58-31802-4DD0B425; Tue, 01 Oct 2013 18:00:52 +0000
X-Env-Sender: Stefano.Stabellini@eu.citrix.com
X-Msg-Ref: server-6.tower-21.messagelabs.com!1380650449!2863916!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.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26974 invoked from network); 1 Oct 2013 18:00:51 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Oct 2013 18:00:51 -0000
X-IronPort-AV: E=Sophos;i="4.90,1014,1371081600"; d="scan'208";a="56657177"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 01 Oct 2013 18:00:37 +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.4;
	Tue, 1 Oct 2013 14:00:36 -0400
Received: from kaball.uk.xensource.com ([10.80.2.59])	by
	ukmail1.uk.xensource.com with esmtp (Exim 4.69)	(envelope-from
	<stefano.stabellini@eu.citrix.com>)	id 1VR4FQ-00050C-W1;
	Tue, 01 Oct 2013 19:00:37 +0100
Date: Tue, 1 Oct 2013 18:59:54 +0100
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
X-X-Sender: sstabellini@kaball.uk.xensource.com
To: anshul makkar <anshulmakkar@gmail.com>
In-Reply-To: <CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1310011856483.26077@kaball.uk.xensource.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
	<245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
	<CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
	<CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="1342847746-1322536005-1380650394=:26077"
X-DLP: MIA1
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--1342847746-1322536005-1380650394=:26077
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: QUOTED-PRINTABLE

Anshul,
if you would like to know more about the Xen on ARM with virtualization
extensions project, give a look at:

http://www.xenproject.org/help/presentations-and-videos/video/latest/linaro=
-connect-introduction-to-xen-on-arm.html

the slides have been used during a Linaro presentation that has been
recorded, the video is available here:

www.youtube.com/watch?v=3DD0mTOKhAm6Y

Unfortunately the framing is very bad, but the audio might help you
better understand the slides.



On Tue, 1 Oct 2013, anshul makkar wrote:
> Hi srujan,=C2=A0 thanks for the reply.
> So it means Xen provides full virtualization support as well.=C2=A0
>=20
> Thanks
> Anshul make
>=20
> On 1 Oct 2013 20:49, "Kotikela, Srujan" <SrujanKotikela@my.unt.edu> wrote=
:
>=20
> Hi Anshul,
>=20
> Xen does support unmodified OS on arm. It is available in the upstream xe=
n. It is not a separate project.
>=20
> Srujan=20
>=20
> anshul makkar <anshulmakkar@gmail.com> wrote:
>=20
>       Hi,
>       Sorry for my ignorance here, but thus Xen port of=C2=A0 ARM (PV) (C=
ortex A9 without hardware virtualization) supports
>       running unmodified Android as guest or guest needs to be necessaril=
y patched to be able to run.
>=20
> I know paravirtualization does mean that guest needs to be modified, but =
I am just confused as I remember I read somewhere
> that Xen also supports full virtualization. But not sure whether that has=
 been ported on ARM.
> --
> Thanks
> Anshul Makkar
> www.justkernel.com
> http://www.linkedin.com/groups/Just-Kernel-3033180
>=20
>=20
>=20
--1342847746-1322536005-1380650394=:26077
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

--1342847746-1322536005-1380650394=:26077--


From xen-arm-bounces@lists.xen.org Tue Oct 01 18:06:01 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 18:06:01 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VR4Kc-0003lL-0J; Tue, 01 Oct 2013 18:05:58 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anshulmakkar@gmail.com>) id 1VR4Ka-0003lC-Hj
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 18:05:57 +0000
Received: from [85.158.137.68:62598] by server-6.bemta-3.messagelabs.com id
	58/A6-04812-30F0B425; Tue, 01 Oct 2013 18:05:55 +0000
X-Env-Sender: anshulmakkar@gmail.com
X-Msg-Ref: server-16.tower-31.messagelabs.com!1380650752!5985846!1
X-Originating-IP: [209.85.160.49]
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.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6462 invoked from network); 1 Oct 2013 18:05:53 -0000
Received: from mail-pb0-f49.google.com (HELO mail-pb0-f49.google.com)
	(209.85.160.49)
	by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Oct 2013 18:05:53 -0000
Received: by mail-pb0-f49.google.com with SMTP id xb4so7402389pbc.8
	for <xen-arm@lists.xen.org>; Tue, 01 Oct 2013 11:05:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=9IdyTKl0B8pKXoPGp1ZDGwYhS948NkMPtVXVHrjQASU=;
	b=cjd21qdncMOnaUD7iGpVEe4HcPMSCEgsUV+GmExOo9unWn9ZnqPEk8SFDtSkdBVqcb
	1l8+gImajWZW+G2fHHmsAzwjHvaMrXXuCS2lMUnet+AYEKp9ZZ0Mo1f5iJERYICotE6b
	fuh1teeD31iYr6cSJJAc1rHQFx6vyMyGP2KHde6Np2VCsr1k1vH1JE6sFRsrExeWRtEP
	40+rMPmoyZQ9cIyK9A8rRbEboNu3n1ZuNAPnZJlRrd6S6tGGtRpwJWwTuaD89GyTI0yN
	InMMkUtSqq8Nw/eVPPfSlsgDz+x+E9DEK7moUDlxT6MhjZkTRQnT+jXeH1h5ZCDwl6aq
	DZlA==
MIME-Version: 1.0
X-Received: by 10.68.189.229 with SMTP id gl5mr3020389pbc.195.1380650751824;
	Tue, 01 Oct 2013 11:05:51 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 11:05:51 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 11:05:51 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1310011856483.26077@kaball.uk.xensource.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
	<245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
	<CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
	<CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
	<alpine.DEB.2.02.1310011856483.26077@kaball.uk.xensource.com>
Date: Tue, 1 Oct 2013 23:35:51 +0530
Message-ID: <CACZDEvG3V-VMGh=oW1n+15s6J-1W020DTGEpvbe2X39fhrs7PA@mail.gmail.com>
From: anshul makkar <anshulmakkar@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0856015206176307911=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============0856015206176307911==
Content-Type: multipart/alternative; boundary=e89a8f642b529f17a604e7b1cd60

--e89a8f642b529f17a604e7b1cd60
Content-Type: text/plain; charset=ISO-8859-1

K. Thanks Stefano. Let me go through the videos. May be I will get my
answers.
On 1 Oct 2013 23:30, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
wrote:

> Anshul,
> if you would like to know more about the Xen on ARM with virtualization
> extensions project, give a look at:
>
>
> http://www.xenproject.org/help/presentations-and-videos/video/latest/linaro-connect-introduction-to-xen-on-arm.html
>
> the slides have been used during a Linaro presentation that has been
> recorded, the video is available here:
>
> www.youtube.com/watch?v=D0mTOKhAm6Y
>
> Unfortunately the framing is very bad, but the audio might help you
> better understand the slides.
>
>
>
> On Tue, 1 Oct 2013, anshul makkar wrote:
> > Hi srujan,  thanks for the reply.
> > So it means Xen provides full virtualization support as well.
> >
> > Thanks
> > Anshul make
> >
> > On 1 Oct 2013 20:49, "Kotikela, Srujan" <SrujanKotikela@my.unt.edu>
> wrote:
> >
> > Hi Anshul,
> >
> > Xen does support unmodified OS on arm. It is available in the upstream
> xen. It is not a separate project.
> >
> > Srujan
> >
> > anshul makkar <anshulmakkar@gmail.com> wrote:
> >
> >       Hi,
> >       Sorry for my ignorance here, but thus Xen port of  ARM (PV)
> (Cortex A9 without hardware virtualization) supports
> >       running unmodified Android as guest or guest needs to be
> necessarily patched to be able to run.
> >
> > I know paravirtualization does mean that guest needs to be modified, but
> I am just confused as I remember I read somewhere
> > that Xen also supports full virtualization. But not sure whether that
> has been ported on ARM.
> > --
> > Thanks
> > Anshul Makkar
> > www.justkernel.com
> > http://www.linkedin.com/groups/Just-Kernel-3033180
> >
> >
> >

--e89a8f642b529f17a604e7b1cd60
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">K. Thanks Stefano. Let me go through the videos. May be I wi=
ll get my answers. </p>
<div class=3D"gmail_quote">On 1 Oct 2013 23:30, &quot;Stefano Stabellini&qu=
ot; &lt;<a href=3D"mailto:stefano.stabellini@eu.citrix.com">stefano.stabell=
ini@eu.citrix.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
Anshul,<br>
if you would like to know more about the Xen on ARM with virtualization<br>
extensions project, give a look at:<br>
<br>
<a href=3D"http://www.xenproject.org/help/presentations-and-videos/video/la=
test/linaro-connect-introduction-to-xen-on-arm.html" target=3D"_blank">http=
://www.xenproject.org/help/presentations-and-videos/video/latest/linaro-con=
nect-introduction-to-xen-on-arm.html</a><br>

<br>
the slides have been used during a Linaro presentation that has been<br>
recorded, the video is available here:<br>
<br>
<a href=3D"http://www.youtube.com/watch?v=3DD0mTOKhAm6Y" target=3D"_blank">=
www.youtube.com/watch?v=3DD0mTOKhAm6Y</a><br>
<br>
Unfortunately the framing is very bad, but the audio might help you<br>
better understand the slides.<br>
<br>
<br>
<br>
On Tue, 1 Oct 2013, anshul makkar wrote:<br>
&gt; Hi srujan,=A0 thanks for the reply.<br>
&gt; So it means Xen provides full virtualization support as well.=A0<br>
&gt;<br>
&gt; Thanks<br>
&gt; Anshul make<br>
&gt;<br>
&gt; On 1 Oct 2013 20:49, &quot;Kotikela, Srujan&quot; &lt;<a href=3D"mailt=
o:SrujanKotikela@my.unt.edu">SrujanKotikela@my.unt.edu</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Anshul,<br>
&gt;<br>
&gt; Xen does support unmodified OS on arm. It is available in the upstream=
 xen. It is not a separate project.<br>
&gt;<br>
&gt; Srujan<br>
&gt;<br>
&gt; anshul makkar &lt;<a href=3D"mailto:anshulmakkar@gmail.com">anshulmakk=
ar@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 =A0 Hi,<br>
&gt; =A0 =A0 =A0 Sorry for my ignorance here, but thus Xen port of=A0 ARM (=
PV) (Cortex A9 without hardware virtualization) supports<br>
&gt; =A0 =A0 =A0 running unmodified Android as guest or guest needs to be n=
ecessarily patched to be able to run.<br>
&gt;<br>
&gt; I know paravirtualization does mean that guest needs to be modified, b=
ut I am just confused as I remember I read somewhere<br>
&gt; that Xen also supports full virtualization. But not sure whether that =
has been ported on ARM.<br>
&gt; --<br>
&gt; Thanks<br>
&gt; Anshul Makkar<br>
&gt; <a href=3D"http://www.justkernel.com" target=3D"_blank">www.justkernel=
.com</a><br>
&gt; <a href=3D"http://www.linkedin.com/groups/Just-Kernel-3033180" target=
=3D"_blank">http://www.linkedin.com/groups/Just-Kernel-3033180</a><br>
&gt;<br>
&gt;<br>
&gt; </blockquote></div>

--e89a8f642b529f17a604e7b1cd60--


--===============0856015206176307911==
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

--===============0856015206176307911==--


From xen-arm-bounces@lists.xen.org Tue Oct 01 18:06:01 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Oct 2013 18:06:01 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VR4Kc-0003lL-0J; Tue, 01 Oct 2013 18:05:58 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anshulmakkar@gmail.com>) id 1VR4Ka-0003lC-Hj
	for xen-arm@lists.xen.org; Tue, 01 Oct 2013 18:05:57 +0000
Received: from [85.158.137.68:62598] by server-6.bemta-3.messagelabs.com id
	58/A6-04812-30F0B425; Tue, 01 Oct 2013 18:05:55 +0000
X-Env-Sender: anshulmakkar@gmail.com
X-Msg-Ref: server-16.tower-31.messagelabs.com!1380650752!5985846!1
X-Originating-IP: [209.85.160.49]
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.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6462 invoked from network); 1 Oct 2013 18:05:53 -0000
Received: from mail-pb0-f49.google.com (HELO mail-pb0-f49.google.com)
	(209.85.160.49)
	by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Oct 2013 18:05:53 -0000
Received: by mail-pb0-f49.google.com with SMTP id xb4so7402389pbc.8
	for <xen-arm@lists.xen.org>; Tue, 01 Oct 2013 11:05:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=9IdyTKl0B8pKXoPGp1ZDGwYhS948NkMPtVXVHrjQASU=;
	b=cjd21qdncMOnaUD7iGpVEe4HcPMSCEgsUV+GmExOo9unWn9ZnqPEk8SFDtSkdBVqcb
	1l8+gImajWZW+G2fHHmsAzwjHvaMrXXuCS2lMUnet+AYEKp9ZZ0Mo1f5iJERYICotE6b
	fuh1teeD31iYr6cSJJAc1rHQFx6vyMyGP2KHde6Np2VCsr1k1vH1JE6sFRsrExeWRtEP
	40+rMPmoyZQ9cIyK9A8rRbEboNu3n1ZuNAPnZJlRrd6S6tGGtRpwJWwTuaD89GyTI0yN
	InMMkUtSqq8Nw/eVPPfSlsgDz+x+E9DEK7moUDlxT6MhjZkTRQnT+jXeH1h5ZCDwl6aq
	DZlA==
MIME-Version: 1.0
X-Received: by 10.68.189.229 with SMTP id gl5mr3020389pbc.195.1380650751824;
	Tue, 01 Oct 2013 11:05:51 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 11:05:51 -0700 (PDT)
Received: by 10.68.63.35 with HTTP; Tue, 1 Oct 2013 11:05:51 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1310011856483.26077@kaball.uk.xensource.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
	<245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
	<CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
	<CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
	<alpine.DEB.2.02.1310011856483.26077@kaball.uk.xensource.com>
Date: Tue, 1 Oct 2013 23:35:51 +0530
Message-ID: <CACZDEvG3V-VMGh=oW1n+15s6J-1W020DTGEpvbe2X39fhrs7PA@mail.gmail.com>
From: anshul makkar <anshulmakkar@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0856015206176307911=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============0856015206176307911==
Content-Type: multipart/alternative; boundary=e89a8f642b529f17a604e7b1cd60

--e89a8f642b529f17a604e7b1cd60
Content-Type: text/plain; charset=ISO-8859-1

K. Thanks Stefano. Let me go through the videos. May be I will get my
answers.
On 1 Oct 2013 23:30, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
wrote:

> Anshul,
> if you would like to know more about the Xen on ARM with virtualization
> extensions project, give a look at:
>
>
> http://www.xenproject.org/help/presentations-and-videos/video/latest/linaro-connect-introduction-to-xen-on-arm.html
>
> the slides have been used during a Linaro presentation that has been
> recorded, the video is available here:
>
> www.youtube.com/watch?v=D0mTOKhAm6Y
>
> Unfortunately the framing is very bad, but the audio might help you
> better understand the slides.
>
>
>
> On Tue, 1 Oct 2013, anshul makkar wrote:
> > Hi srujan,  thanks for the reply.
> > So it means Xen provides full virtualization support as well.
> >
> > Thanks
> > Anshul make
> >
> > On 1 Oct 2013 20:49, "Kotikela, Srujan" <SrujanKotikela@my.unt.edu>
> wrote:
> >
> > Hi Anshul,
> >
> > Xen does support unmodified OS on arm. It is available in the upstream
> xen. It is not a separate project.
> >
> > Srujan
> >
> > anshul makkar <anshulmakkar@gmail.com> wrote:
> >
> >       Hi,
> >       Sorry for my ignorance here, but thus Xen port of  ARM (PV)
> (Cortex A9 without hardware virtualization) supports
> >       running unmodified Android as guest or guest needs to be
> necessarily patched to be able to run.
> >
> > I know paravirtualization does mean that guest needs to be modified, but
> I am just confused as I remember I read somewhere
> > that Xen also supports full virtualization. But not sure whether that
> has been ported on ARM.
> > --
> > Thanks
> > Anshul Makkar
> > www.justkernel.com
> > http://www.linkedin.com/groups/Just-Kernel-3033180
> >
> >
> >

--e89a8f642b529f17a604e7b1cd60
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">K. Thanks Stefano. Let me go through the videos. May be I wi=
ll get my answers. </p>
<div class=3D"gmail_quote">On 1 Oct 2013 23:30, &quot;Stefano Stabellini&qu=
ot; &lt;<a href=3D"mailto:stefano.stabellini@eu.citrix.com">stefano.stabell=
ini@eu.citrix.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
Anshul,<br>
if you would like to know more about the Xen on ARM with virtualization<br>
extensions project, give a look at:<br>
<br>
<a href=3D"http://www.xenproject.org/help/presentations-and-videos/video/la=
test/linaro-connect-introduction-to-xen-on-arm.html" target=3D"_blank">http=
://www.xenproject.org/help/presentations-and-videos/video/latest/linaro-con=
nect-introduction-to-xen-on-arm.html</a><br>

<br>
the slides have been used during a Linaro presentation that has been<br>
recorded, the video is available here:<br>
<br>
<a href=3D"http://www.youtube.com/watch?v=3DD0mTOKhAm6Y" target=3D"_blank">=
www.youtube.com/watch?v=3DD0mTOKhAm6Y</a><br>
<br>
Unfortunately the framing is very bad, but the audio might help you<br>
better understand the slides.<br>
<br>
<br>
<br>
On Tue, 1 Oct 2013, anshul makkar wrote:<br>
&gt; Hi srujan,=A0 thanks for the reply.<br>
&gt; So it means Xen provides full virtualization support as well.=A0<br>
&gt;<br>
&gt; Thanks<br>
&gt; Anshul make<br>
&gt;<br>
&gt; On 1 Oct 2013 20:49, &quot;Kotikela, Srujan&quot; &lt;<a href=3D"mailt=
o:SrujanKotikela@my.unt.edu">SrujanKotikela@my.unt.edu</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Anshul,<br>
&gt;<br>
&gt; Xen does support unmodified OS on arm. It is available in the upstream=
 xen. It is not a separate project.<br>
&gt;<br>
&gt; Srujan<br>
&gt;<br>
&gt; anshul makkar &lt;<a href=3D"mailto:anshulmakkar@gmail.com">anshulmakk=
ar@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 =A0 Hi,<br>
&gt; =A0 =A0 =A0 Sorry for my ignorance here, but thus Xen port of=A0 ARM (=
PV) (Cortex A9 without hardware virtualization) supports<br>
&gt; =A0 =A0 =A0 running unmodified Android as guest or guest needs to be n=
ecessarily patched to be able to run.<br>
&gt;<br>
&gt; I know paravirtualization does mean that guest needs to be modified, b=
ut I am just confused as I remember I read somewhere<br>
&gt; that Xen also supports full virtualization. But not sure whether that =
has been ported on ARM.<br>
&gt; --<br>
&gt; Thanks<br>
&gt; Anshul Makkar<br>
&gt; <a href=3D"http://www.justkernel.com" target=3D"_blank">www.justkernel=
.com</a><br>
&gt; <a href=3D"http://www.linkedin.com/groups/Just-Kernel-3033180" target=
=3D"_blank">http://www.linkedin.com/groups/Just-Kernel-3033180</a><br>
&gt;<br>
&gt;<br>
&gt; </blockquote></div>

--e89a8f642b529f17a604e7b1cd60--


--===============0856015206176307911==
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

--===============0856015206176307911==--


From xen-arm-bounces@lists.xen.org Wed Oct 02 08:53:32 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 02 Oct 2013 08:53:32 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VRIBU-0007NF-9o; Wed, 02 Oct 2013 08:53:28 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1VRIBT-0007N4-0Y
	for xen-arm@lists.xen.org; Wed, 02 Oct 2013 08:53:27 +0000
Received: from [85.158.143.35:39876] by server-1.bemta-4.messagelabs.com id
	4E/A7-11076-60FDB425; Wed, 02 Oct 2013 08:53:26 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-11.tower-21.messagelabs.com!1380704004!8112538!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.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15102 invoked from network); 2 Oct 2013 08:53:25 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	2 Oct 2013 08:53:25 -0000
X-IronPort-AV: E=Sophos;i="4.90,1018,1371081600"; d="scan'208";a="59432546"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 02 Oct 2013 08:53:03 +0000
Received: from LONPEX01CL03.citrite.net (10.30.203.103) by
	FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server
	(TLS) id 14.2.342.4; Wed, 2 Oct 2013 04:53:03 -0400
Received: from [10.80.2.80] (10.30.203.1) by LONPEX01CL03.citrite.net
	(10.30.203.103) with Microsoft SMTP Server id 14.2.342.4;
	Wed, 2 Oct 2013 09:53:02 +0100
Message-ID: <1380703981.925.88.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: anshul makkar <anshulmakkar@gmail.com>
Date: Wed, 2 Oct 2013 09:53:01 +0100
In-Reply-To: <CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
	<245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
	<CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
	<CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.30.203.1]
X-DLP: MIA1
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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, 2013-10-01 at 23:25 +0530, anshul makkar wrote:
> So it means Xen provides full virtualization support as well.  

Unfortunately it does not.

The Xen port to ARM processors with virtualisation extensions[1] uses a
hybrid model which makes use of both hardware features and
paravirtualisation, it is not the same as either x86 PV or x86 HVM but
is somewhere in the middle, something like the in-progress x86 PVH mode.

So it does not support full virtualisation in the sense of providing an
environment to a guest which mimics a real hardware platform with
emulated devices etc. The guest hardware platform is a mixture of
hardware virtualisation features (e.g. timers, interrupt controller, two
stage paging) and software virtualisation (e.g. event channels and PV
I/O devices).

Ian.

[1] http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions
> 
> Thanks
> Anshul make
> 
> On 1 Oct 2013 20:49, "Kotikela, Srujan" <SrujanKotikela@my.unt.edu>
> wrote:
>         Hi Anshul,
>         
>         Xen does support unmodified OS on arm. It is available in the upstream xen. It is not a separate project.
>         
>         Srujan 
>         
>         anshul makkar <anshulmakkar@gmail.com> wrote:
>         
>         Hi,
>         Sorry for my ignorance here, but thus Xen port of  ARM (PV)
>         (Cortex A9 without hardware virtualization) supports running
>         unmodified Android as guest or guest needs to be necessarily
>         patched to be able to run.
>         
>         
>         I know paravirtualization does mean that guest needs to be
>         modified, but I am just confused as I remember I read
>         somewhere that Xen also supports full virtualization. But not
>         sure whether that has been ported on ARM.
>         -- 
>         Thanks
>         Anshul Makkar
>         www.justkernel.com
>         http://www.linkedin.com/groups/Just-Kernel-3033180
>         
> _______________________________________________
> Xen-arm mailing list
> Xen-arm@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm



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

From xen-arm-bounces@lists.xen.org Wed Oct 02 08:53:32 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 02 Oct 2013 08:53:32 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VRIBU-0007NF-9o; Wed, 02 Oct 2013 08:53:28 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1VRIBT-0007N4-0Y
	for xen-arm@lists.xen.org; Wed, 02 Oct 2013 08:53:27 +0000
Received: from [85.158.143.35:39876] by server-1.bemta-4.messagelabs.com id
	4E/A7-11076-60FDB425; Wed, 02 Oct 2013 08:53:26 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-11.tower-21.messagelabs.com!1380704004!8112538!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.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15102 invoked from network); 2 Oct 2013 08:53:25 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	2 Oct 2013 08:53:25 -0000
X-IronPort-AV: E=Sophos;i="4.90,1018,1371081600"; d="scan'208";a="59432546"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 02 Oct 2013 08:53:03 +0000
Received: from LONPEX01CL03.citrite.net (10.30.203.103) by
	FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server
	(TLS) id 14.2.342.4; Wed, 2 Oct 2013 04:53:03 -0400
Received: from [10.80.2.80] (10.30.203.1) by LONPEX01CL03.citrite.net
	(10.30.203.103) with Microsoft SMTP Server id 14.2.342.4;
	Wed, 2 Oct 2013 09:53:02 +0100
Message-ID: <1380703981.925.88.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: anshul makkar <anshulmakkar@gmail.com>
Date: Wed, 2 Oct 2013 09:53:01 +0100
In-Reply-To: <CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
References: <CACZDEvFQKJb1QzDyJ3fLZaHJCKwYAvpi3pHd4wVxpDBLKUq++g@mail.gmail.com>
	<245u5sumqxcaomy3nun4pngl.1380640648010@email.android.com>
	<CACZDEvHiOm-S6J0bfj88yadK866D-O=x_eyF=LH3wa_QuiG_6w@mail.gmail.com>
	<CACZDEvGrQOF=4=mCbikZH+ZZ6zD5mh7YRHfX5H7aMwxTwkzyjw@mail.gmail.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.30.203.1]
X-DLP: MIA1
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] Support of unmodified guest
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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, 2013-10-01 at 23:25 +0530, anshul makkar wrote:
> So it means Xen provides full virtualization support as well.  

Unfortunately it does not.

The Xen port to ARM processors with virtualisation extensions[1] uses a
hybrid model which makes use of both hardware features and
paravirtualisation, it is not the same as either x86 PV or x86 HVM but
is somewhere in the middle, something like the in-progress x86 PVH mode.

So it does not support full virtualisation in the sense of providing an
environment to a guest which mimics a real hardware platform with
emulated devices etc. The guest hardware platform is a mixture of
hardware virtualisation features (e.g. timers, interrupt controller, two
stage paging) and software virtualisation (e.g. event channels and PV
I/O devices).

Ian.

[1] http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions
> 
> Thanks
> Anshul make
> 
> On 1 Oct 2013 20:49, "Kotikela, Srujan" <SrujanKotikela@my.unt.edu>
> wrote:
>         Hi Anshul,
>         
>         Xen does support unmodified OS on arm. It is available in the upstream xen. It is not a separate project.
>         
>         Srujan 
>         
>         anshul makkar <anshulmakkar@gmail.com> wrote:
>         
>         Hi,
>         Sorry for my ignorance here, but thus Xen port of  ARM (PV)
>         (Cortex A9 without hardware virtualization) supports running
>         unmodified Android as guest or guest needs to be necessarily
>         patched to be able to run.
>         
>         
>         I know paravirtualization does mean that guest needs to be
>         modified, but I am just confused as I remember I read
>         somewhere that Xen also supports full virtualization. But not
>         sure whether that has been ported on ARM.
>         -- 
>         Thanks
>         Anshul Makkar
>         www.justkernel.com
>         http://www.linkedin.com/groups/Just-Kernel-3033180
>         
> _______________________________________________
> Xen-arm mailing list
> Xen-arm@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm



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

From xen-arm-bounces@lists.xen.org Wed Oct 02 09:07:22 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 02 Oct 2013 09:07:22 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VRIOs-0007qF-N0; Wed, 02 Oct 2013 09:07:18 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <sajid.hafeez@samsung.com>) id 1VRIOr-0007q9-Pw
	for xen-arm@lists.xen.org; Wed, 02 Oct 2013 09:07:17 +0000
Received: from [85.158.143.35:16649] by server-3.bemta-4.messagelabs.com id
	15/F3-24907-542EB425; Wed, 02 Oct 2013 09:07:17 +0000
X-Env-Sender: sajid.hafeez@samsung.com
X-Msg-Ref: server-2.tower-21.messagelabs.com!1380704836!8108299!1
X-Originating-IP: [210.118.77.12]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMjEwLjExOC43Ny4xMiA9PiAxODI3NDE=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19907 invoked from network); 2 Oct 2013 09:07:16 -0000
Received: from mailout2.w1.samsung.com (HELO mailout2.w1.samsung.com)
	(210.118.77.12) by server-2.tower-21.messagelabs.com with SMTP;
	2 Oct 2013 09:07:16 -0000
Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244])
	by mailout2.w1.samsung.com
	(Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit
	(built Nov
	17 2011)) with ESMTP id <0MU100KAAANCYU60@mailout2.w1.samsung.com> for
	xen-arm@lists.xen.org; Wed, 02 Oct 2013 10:07:01 +0100 (BST)
X-AuditID: cbfec7f4-b7f0a6d000007b1b-44-524be235a7b1
Received: from eusync2.samsung.com ( [203.254.199.212])
	by eucpsbgm1.samsung.com (EUCPMTA) with SMTP id E8.50.31515.532EB425;
	Wed, 02 Oct 2013 10:07:01 +0100 (BST)
Received: from ex1.seri.co.uk ([106.1.8.3])
	by eusync2.samsung.com (Oracle Communications Messaging Server
	7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011))
	with ESMTPA id <0MU1001ZBANPF360@eusync2.samsung.com> for
	xen-arm@lists.xen.org; Wed, 02 Oct 2013 10:07:01 +0100 (BST)
Received: from ex1.seri.co.uk ([2002:6a01:803::6a01:803])
	by ex1.seri.co.uk ([2002:6a01:803::6a01:803]) with mapi id
	14.01.0218.012; Wed, 02 Oct 2013 10:07:00 +0100
From: Sajid Hafeez <sajid.hafeez@samsung.com>
To: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>
Thread-topic: unsubscribe
Thread-index: Ac6/TsCDOXdfNUCVSP678RTkRgaV6w==
Date: Wed, 02 Oct 2013 09:07:00 +0000
Message-id: <A611441FD943B04690EB3542688F4C256AC66613@ex1.seri.co.uk>
Accept-Language: en-GB, en-US
Content-language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Originating-IP: [2002:6a01:90d::6a01:90d]
MIME-version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsVy+t/xK7qmj7yDDDZ1CFocu72E2YHR4+ju
	30wBjFFcNimpOZllqUX6dglcGU+fLWYuaBWoWLn7AnMD4xK+LkZODgkBE4npi7YwQthiEhfu
	rWfrYuTiEBJYyihxesMBdghnNpPE5buPoJwVjBKH7p8Ea2ET0JWYvGwDO4gtImAssb1zMjOI
	LSwgIrF/zzlmiLikxIzbS1kgbD2JvXMXAsU5OFgEVCVmrYgBCfMKuEps+n6JCcRmFJCV+NK4
	GqyVWUBcorn1JgvEdQISS/acZ4awRSVePv7HCmFrS/yccJIJoj5T4srROUwQMwUlfky+xzKB
	UXgWklGzkJTNQlIGEdeRWLD7ExuErS2xbOFrZhj7zIHHTMjiCxjZVzGKppYmFxQnpeca6hUn
	5haX5qXrJefnbmKERMuXHYyLj1kdYhTgYFTi4ZV46BUkxJpYVlyZe4hRgoNZSYS34rh3kBBv
	SmJlVWpRfnxRaU5q8SFGJg5OqQZGYyHteNvl4SE/WAL23TGWW6z4pHJfc7EJe8zl+qr111uz
	syafiE3edk08qaXcwSDO9V99PPfvguRtOVxJ3f7PLBJrBG83vFQTPvHq7KciVrvda1znTjFK
	8mR5uEb45wWdzZnTWkPbCrkiHrvd+C3WIGGvz7hbKbMw5lvtzTdZbK+PmX9+fVyJpTgj0VCL
	uag4EQBIG/PgdAIAAA==
Subject: [XenARM] unsubscribe
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6963891278031377511=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============6963891278031377511==
Content-language: en-US
Content-type: multipart/alternative;
 boundary=_000_A611441FD943B04690EB3542688F4C256AC66613ex1sericouk_

--_000_A611441FD943B04690EB3542688F4C256AC66613ex1sericouk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



--_000_A611441FD943B04690EB3542688F4C256AC66613ex1sericouk_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_A611441FD943B04690EB3542688F4C256AC66613ex1sericouk_--


--===============6963891278031377511==
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

--===============6963891278031377511==--


From xen-arm-bounces@lists.xen.org Wed Oct 02 09:07:22 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 02 Oct 2013 09:07:22 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VRIOs-0007qF-N0; Wed, 02 Oct 2013 09:07:18 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <sajid.hafeez@samsung.com>) id 1VRIOr-0007q9-Pw
	for xen-arm@lists.xen.org; Wed, 02 Oct 2013 09:07:17 +0000
Received: from [85.158.143.35:16649] by server-3.bemta-4.messagelabs.com id
	15/F3-24907-542EB425; Wed, 02 Oct 2013 09:07:17 +0000
X-Env-Sender: sajid.hafeez@samsung.com
X-Msg-Ref: server-2.tower-21.messagelabs.com!1380704836!8108299!1
X-Originating-IP: [210.118.77.12]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMjEwLjExOC43Ny4xMiA9PiAxODI3NDE=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19907 invoked from network); 2 Oct 2013 09:07:16 -0000
Received: from mailout2.w1.samsung.com (HELO mailout2.w1.samsung.com)
	(210.118.77.12) by server-2.tower-21.messagelabs.com with SMTP;
	2 Oct 2013 09:07:16 -0000
Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244])
	by mailout2.w1.samsung.com
	(Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit
	(built Nov
	17 2011)) with ESMTP id <0MU100KAAANCYU60@mailout2.w1.samsung.com> for
	xen-arm@lists.xen.org; Wed, 02 Oct 2013 10:07:01 +0100 (BST)
X-AuditID: cbfec7f4-b7f0a6d000007b1b-44-524be235a7b1
Received: from eusync2.samsung.com ( [203.254.199.212])
	by eucpsbgm1.samsung.com (EUCPMTA) with SMTP id E8.50.31515.532EB425;
	Wed, 02 Oct 2013 10:07:01 +0100 (BST)
Received: from ex1.seri.co.uk ([106.1.8.3])
	by eusync2.samsung.com (Oracle Communications Messaging Server
	7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011))
	with ESMTPA id <0MU1001ZBANPF360@eusync2.samsung.com> for
	xen-arm@lists.xen.org; Wed, 02 Oct 2013 10:07:01 +0100 (BST)
Received: from ex1.seri.co.uk ([2002:6a01:803::6a01:803])
	by ex1.seri.co.uk ([2002:6a01:803::6a01:803]) with mapi id
	14.01.0218.012; Wed, 02 Oct 2013 10:07:00 +0100
From: Sajid Hafeez <sajid.hafeez@samsung.com>
To: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>
Thread-topic: unsubscribe
Thread-index: Ac6/TsCDOXdfNUCVSP678RTkRgaV6w==
Date: Wed, 02 Oct 2013 09:07:00 +0000
Message-id: <A611441FD943B04690EB3542688F4C256AC66613@ex1.seri.co.uk>
Accept-Language: en-GB, en-US
Content-language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Originating-IP: [2002:6a01:90d::6a01:90d]
MIME-version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsVy+t/xK7qmj7yDDDZ1CFocu72E2YHR4+ju
	30wBjFFcNimpOZllqUX6dglcGU+fLWYuaBWoWLn7AnMD4xK+LkZODgkBE4npi7YwQthiEhfu
	rWfrYuTiEBJYyihxesMBdghnNpPE5buPoJwVjBKH7p8Ea2ET0JWYvGwDO4gtImAssb1zMjOI
	LSwgIrF/zzlmiLikxIzbS1kgbD2JvXMXAsU5OFgEVCVmrYgBCfMKuEps+n6JCcRmFJCV+NK4
	GqyVWUBcorn1JgvEdQISS/acZ4awRSVePv7HCmFrS/yccJIJoj5T4srROUwQMwUlfky+xzKB
	UXgWklGzkJTNQlIGEdeRWLD7ExuErS2xbOFrZhj7zIHHTMjiCxjZVzGKppYmFxQnpeca6hUn
	5haX5qXrJefnbmKERMuXHYyLj1kdYhTgYFTi4ZV46BUkxJpYVlyZe4hRgoNZSYS34rh3kBBv
	SmJlVWpRfnxRaU5q8SFGJg5OqQZGYyHteNvl4SE/WAL23TGWW6z4pHJfc7EJe8zl+qr111uz
	syafiE3edk08qaXcwSDO9V99PPfvguRtOVxJ3f7PLBJrBG83vFQTPvHq7KciVrvda1znTjFK
	8mR5uEb45wWdzZnTWkPbCrkiHrvd+C3WIGGvz7hbKbMw5lvtzTdZbK+PmX9+fVyJpTgj0VCL
	uag4EQBIG/PgdAIAAA==
Subject: [XenARM] unsubscribe
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6963891278031377511=="
Sender: xen-arm-bounces@lists.xen.org
Errors-To: xen-arm-bounces@lists.xen.org

--===============6963891278031377511==
Content-language: en-US
Content-type: multipart/alternative;
 boundary=_000_A611441FD943B04690EB3542688F4C256AC66613ex1sericouk_

--_000_A611441FD943B04690EB3542688F4C256AC66613ex1sericouk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



--_000_A611441FD943B04690EB3542688F4C256AC66613ex1sericouk_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_A611441FD943B04690EB3542688F4C256AC66613ex1sericouk_--


--===============6963891278031377511==
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

--===============6963891278031377511==--


From xen-arm-bounces@lists.xen.org Wed Oct 16 22:57:35 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 16 Oct 2013 22:57:35 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VWa1z-00030C-Oe; Wed, 16 Oct 2013 22:57:31 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <marc.ceeeee@gmail.com>)
	id 1VWa1y-000304-Eb; Wed, 16 Oct 2013 22:57:30 +0000
Received: from [193.109.254.147:25270] by server-4.bemta-14.messagelabs.com id
	81/00-27994-9D91F525; Wed, 16 Oct 2013 22:57:29 +0000
X-Env-Sender: marc.ceeeee@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1381964247!2580312!1
X-Originating-IP: [209.85.214.174]
X-SpamReason: INFO: max file limit 5000
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19950 invoked from network); 16 Oct 2013 22:57:28 -0000
Received: from mail-ob0-f174.google.com (HELO mail-ob0-f174.google.com)
	(209.85.214.174)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	16 Oct 2013 22:57:28 -0000
Received: by mail-ob0-f174.google.com with SMTP id wm4so1200334obc.5
	for <multiple recipients>; Wed, 16 Oct 2013 15:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:to:cc:subject:date:message-id;
	bh=UQ1V7VyxqlNV3TFMYy3I6byoBQ2ib8yoiLU4DvmDeCU=;
	b=SGOgUcjFZjfgwcJ8vY2lGUNm883AtSrEdT78ddRBWFiCRVrZg18T2KmyOUqfKl5gEO
	YXQu6HER22wek1lujQtsyzibD5Barl2JS8RhGERYu93iGan8Fc/heEJXrpTLakeTIbAa
	6a2fWoiQvtALfge2Z6Kid9jg1xbCGHhTe0aHbK0loK382PGrmQwaCCN8CyThqPG/5MxI
	1H57zGI1sSHL0Zgbw/2nuWeEGwhUf+fL0OmbNFGf70DGMi02deKREANf5AGiQesiwBk9
	BQbQDKQTF9jweYUmAHt1XvColVBLNUr+Flnw3xbdHv7UXrtT2aSTl2jGOu234pg3QY9c
	0bkg==
X-Received: by 10.182.44.134 with SMTP id e6mr8807748obm.14.1381964246829;
	Wed, 16 Oct 2013 15:57:26 -0700 (PDT)
Received: from ld-irv-0116.broadcom.com (5520-maca-inet1-outside.broadcom.com.
	[216.31.211.11]) by mx.google.com with ESMTPSA id
	tz10sm67261756obc.10.1969.12.31.16.00.00
	(version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 16 Oct 2013 15:57:26 -0700 (PDT)
From: marc.ceeeee@gmail.com
To: xen-devel@lists.xen.org
Date: Wed, 16 Oct 2013 15:57:06 -0700
Message-Id: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
X-Mailer: git-send-email 1.7.9.5
Cc: xen-arm@lists.xen.org, tim@xen.org, mcarino@broadcom.com
Subject: [XenARM] [PATCH] xen/arm: Add CPU ID for Broadcom Brahma-B15
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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 Carino <marc.ceeeee@gmail.com>

Let Xen recognize the Broadcom Brahma-B15 CPU by adding the appropriate
MIDR mask to the initialization phase. Further, ensure that the console
output properly reports the CPU manufacturer as "Broadcom Corporation".

Signed-off-by: Marc Carino <marc.ceeeee@gmail.com>
---
 xen/arch/arm/arm32/proc-v7.S |    8 ++++++++
 xen/arch/arm/setup.c         |    1 +
 2 files changed, 9 insertions(+)

diff --git a/xen/arch/arm/arm32/proc-v7.S b/xen/arch/arm/arm32/proc-v7.S
index 6577a89..2c8cb9c 100644
--- a/xen/arch/arm/arm32/proc-v7.S
+++ b/xen/arch/arm/arm32/proc-v7.S
@@ -43,6 +43,14 @@ __v7_ca7mp_proc_info:
         .long v7_init
         .size __v7_ca7mp_proc_info, . - __v7_ca7mp_proc_info
 
+        .section ".init.proc.info", #alloc, #execinstr
+        .type __v7_brahma15mp_proc_info, #object
+__v7_brahma15mp_proc_info:
+        .long 0x420F00F2             /* Broadcom Brahma-B15 */
+        .long 0xFF0FFFFF             /* Mask */
+        .long v7_init
+        .size __v7_brahma15mp_proc_info, . - __v7_brahma15mp_proc_info
+
 /*
  * Local variables:
  * mode: ASM
diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index 49f344c..7d6e596 100644
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -61,6 +61,7 @@ static void __init init_idle_domain(void)
 
 static const char * __initdata processor_implementers[] = {
     ['A'] = "ARM Limited",
+    ['B'] = "Broadcom Corporation",
     ['D'] = "Digital Equipment Corp",
     ['M'] = "Motorola, Freescale Semiconductor Inc.",
     ['Q'] = "Qualcomm Inc.",
-- 
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 Wed Oct 16 22:57:35 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 16 Oct 2013 22:57:35 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VWa1z-00030C-Oe; Wed, 16 Oct 2013 22:57:31 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <marc.ceeeee@gmail.com>)
	id 1VWa1y-000304-Eb; Wed, 16 Oct 2013 22:57:30 +0000
Received: from [193.109.254.147:25270] by server-4.bemta-14.messagelabs.com id
	81/00-27994-9D91F525; Wed, 16 Oct 2013 22:57:29 +0000
X-Env-Sender: marc.ceeeee@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1381964247!2580312!1
X-Originating-IP: [209.85.214.174]
X-SpamReason: INFO: max file limit 5000
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19950 invoked from network); 16 Oct 2013 22:57:28 -0000
Received: from mail-ob0-f174.google.com (HELO mail-ob0-f174.google.com)
	(209.85.214.174)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	16 Oct 2013 22:57:28 -0000
Received: by mail-ob0-f174.google.com with SMTP id wm4so1200334obc.5
	for <multiple recipients>; Wed, 16 Oct 2013 15:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:to:cc:subject:date:message-id;
	bh=UQ1V7VyxqlNV3TFMYy3I6byoBQ2ib8yoiLU4DvmDeCU=;
	b=SGOgUcjFZjfgwcJ8vY2lGUNm883AtSrEdT78ddRBWFiCRVrZg18T2KmyOUqfKl5gEO
	YXQu6HER22wek1lujQtsyzibD5Barl2JS8RhGERYu93iGan8Fc/heEJXrpTLakeTIbAa
	6a2fWoiQvtALfge2Z6Kid9jg1xbCGHhTe0aHbK0loK382PGrmQwaCCN8CyThqPG/5MxI
	1H57zGI1sSHL0Zgbw/2nuWeEGwhUf+fL0OmbNFGf70DGMi02deKREANf5AGiQesiwBk9
	BQbQDKQTF9jweYUmAHt1XvColVBLNUr+Flnw3xbdHv7UXrtT2aSTl2jGOu234pg3QY9c
	0bkg==
X-Received: by 10.182.44.134 with SMTP id e6mr8807748obm.14.1381964246829;
	Wed, 16 Oct 2013 15:57:26 -0700 (PDT)
Received: from ld-irv-0116.broadcom.com (5520-maca-inet1-outside.broadcom.com.
	[216.31.211.11]) by mx.google.com with ESMTPSA id
	tz10sm67261756obc.10.1969.12.31.16.00.00
	(version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 16 Oct 2013 15:57:26 -0700 (PDT)
From: marc.ceeeee@gmail.com
To: xen-devel@lists.xen.org
Date: Wed, 16 Oct 2013 15:57:06 -0700
Message-Id: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
X-Mailer: git-send-email 1.7.9.5
Cc: xen-arm@lists.xen.org, tim@xen.org, mcarino@broadcom.com
Subject: [XenARM] [PATCH] xen/arm: Add CPU ID for Broadcom Brahma-B15
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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 Carino <marc.ceeeee@gmail.com>

Let Xen recognize the Broadcom Brahma-B15 CPU by adding the appropriate
MIDR mask to the initialization phase. Further, ensure that the console
output properly reports the CPU manufacturer as "Broadcom Corporation".

Signed-off-by: Marc Carino <marc.ceeeee@gmail.com>
---
 xen/arch/arm/arm32/proc-v7.S |    8 ++++++++
 xen/arch/arm/setup.c         |    1 +
 2 files changed, 9 insertions(+)

diff --git a/xen/arch/arm/arm32/proc-v7.S b/xen/arch/arm/arm32/proc-v7.S
index 6577a89..2c8cb9c 100644
--- a/xen/arch/arm/arm32/proc-v7.S
+++ b/xen/arch/arm/arm32/proc-v7.S
@@ -43,6 +43,14 @@ __v7_ca7mp_proc_info:
         .long v7_init
         .size __v7_ca7mp_proc_info, . - __v7_ca7mp_proc_info
 
+        .section ".init.proc.info", #alloc, #execinstr
+        .type __v7_brahma15mp_proc_info, #object
+__v7_brahma15mp_proc_info:
+        .long 0x420F00F2             /* Broadcom Brahma-B15 */
+        .long 0xFF0FFFFF             /* Mask */
+        .long v7_init
+        .size __v7_brahma15mp_proc_info, . - __v7_brahma15mp_proc_info
+
 /*
  * Local variables:
  * mode: ASM
diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index 49f344c..7d6e596 100644
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -61,6 +61,7 @@ static void __init init_idle_domain(void)
 
 static const char * __initdata processor_implementers[] = {
     ['A'] = "ARM Limited",
+    ['B'] = "Broadcom Corporation",
     ['D'] = "Digital Equipment Corp",
     ['M'] = "Motorola, Freescale Semiconductor Inc.",
     ['Q'] = "Qualcomm Inc.",
-- 
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 Thu Oct 17 09:47:21 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Oct 2013 09:47:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VWkAn-0008BL-4n; Thu, 17 Oct 2013 09:47:17 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1VWkAl-0008BD-KP; Thu, 17 Oct 2013 09:47:15 +0000
Received: from [85.158.137.68:40974] by server-14.bemta-3.messagelabs.com id
	75/81-20312-222BF525; Thu, 17 Oct 2013 09:47:14 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-9.tower-31.messagelabs.com!1382003232!1981787!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: INFO: max file limit 5000
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22101 invoked from network); 17 Oct 2013 09:47:13 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Oct 2013 09:47:13 -0000
X-IronPort-AV: E=Sophos;i="4.93,513,1378857600"; d="scan'208";a="64499310"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 17 Oct 2013 09:47:11 +0000
Received: from LONPEX01CL01.citrite.net (10.30.203.101) by
	FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server
	(TLS) id 14.2.342.4; Thu, 17 Oct 2013 05:47:11 -0400
Received: from [10.80.2.80] (10.30.203.1) by LONPEX01CL01.citrite.net
	(10.30.203.101) with Microsoft SMTP Server id 14.2.342.4;
	Thu, 17 Oct 2013 10:47:10 +0100
Message-ID: <1382003230.18128.9.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: <marc.ceeeee@gmail.com>
Date: Thu, 17 Oct 2013 10:47:10 +0100
In-Reply-To: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
References: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.30.203.1]
X-DLP: MIA2
Cc: xen-arm@lists.xen.org, mcarino@broadcom.com, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [XenARM] [PATCH] xen/arm: Add CPU ID for Broadcom Brahma-B15
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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, 2013-10-16 at 15:57 -0700, marc.ceeeee@gmail.com wrote:
> From: Marc Carino <marc.ceeeee@gmail.com>
> 
> Let Xen recognize the Broadcom Brahma-B15 CPU by adding the appropriate
> MIDR mask to the initialization phase. Further, ensure that the console
> output properly reports the CPU manufacturer as "Broadcom Corporation".

Thanks for resending, I saw the original but somehow failed to add it to
my queue of things to look at, sorry!

> 
> Signed-off-by: Marc Carino <marc.ceeeee@gmail.com>
> ---
>  xen/arch/arm/arm32/proc-v7.S |    8 ++++++++
>  xen/arch/arm/setup.c         |    1 +
>  2 files changed, 9 insertions(+)
> 
> diff --git a/xen/arch/arm/arm32/proc-v7.S b/xen/arch/arm/arm32/proc-v7.S
> index 6577a89..2c8cb9c 100644
> --- a/xen/arch/arm/arm32/proc-v7.S
> +++ b/xen/arch/arm/arm32/proc-v7.S
> @@ -43,6 +43,14 @@ __v7_ca7mp_proc_info:
>          .long v7_init
>          .size __v7_ca7mp_proc_info, . - __v7_ca7mp_proc_info
>  
> +        .section ".init.proc.info", #alloc, #execinstr
> +        .type __v7_brahma15mp_proc_info, #object
> +__v7_brahma15mp_proc_info:
> +        .long 0x420F00F2             /* Broadcom Brahma-B15 */
> +        .long 0xFF0FFFFF             /* Mask */

This mask includes the revision field (last nibble). Is it intentional
too only support a single revision of this processor?

> +        .long v7_init

v7_init fiddles with the implementation defined ACTLR register in a
Cortex-A15/A7 specific manner. Is the B15 compatible with ARM's Cortex
A15 in this regard?

If not then I think this should be changed to:

ca7mp_init:
ca15mp_init:
        /* Set up the SMP bit in ACTLR */
        mrc   CP32(r0, ACTLR)
        orr   r0, r0, #(ACTLR_V7_SMP) /* enable SMP bit */
        mcr   CP32(r0, ACTLR)
v7_init: /* Generic v7 init */
        mov   pc, lr

and the A15/A7 entries updated to point to the new names.

Perhaps there isn't much point in listing a processor here which doesn't
need any init, but doing so will mean it'll get picked up if we ever add
some init for generic v7, or if we add new hooks etc.

Ian.

> +        .size __v7_brahma15mp_proc_info, . - __v7_brahma15mp_proc_info
> +
>  /*
>   * Local variables:
>   * mode: ASM
> diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
> index 49f344c..7d6e596 100644
> --- a/xen/arch/arm/setup.c
> +++ b/xen/arch/arm/setup.c
> @@ -61,6 +61,7 @@ static void __init init_idle_domain(void)
>  
>  static const char * __initdata processor_implementers[] = {
>      ['A'] = "ARM Limited",
> +    ['B'] = "Broadcom Corporation",
>      ['D'] = "Digital Equipment Corp",
>      ['M'] = "Motorola, Freescale Semiconductor Inc.",
>      ['Q'] = "Qualcomm Inc.",



_______________________________________________
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 Oct 17 09:47:21 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Oct 2013 09:47:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VWkAn-0008BL-4n; Thu, 17 Oct 2013 09:47:17 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1VWkAl-0008BD-KP; Thu, 17 Oct 2013 09:47:15 +0000
Received: from [85.158.137.68:40974] by server-14.bemta-3.messagelabs.com id
	75/81-20312-222BF525; Thu, 17 Oct 2013 09:47:14 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-9.tower-31.messagelabs.com!1382003232!1981787!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: INFO: max file limit 5000
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22101 invoked from network); 17 Oct 2013 09:47:13 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Oct 2013 09:47:13 -0000
X-IronPort-AV: E=Sophos;i="4.93,513,1378857600"; d="scan'208";a="64499310"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 17 Oct 2013 09:47:11 +0000
Received: from LONPEX01CL01.citrite.net (10.30.203.101) by
	FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server
	(TLS) id 14.2.342.4; Thu, 17 Oct 2013 05:47:11 -0400
Received: from [10.80.2.80] (10.30.203.1) by LONPEX01CL01.citrite.net
	(10.30.203.101) with Microsoft SMTP Server id 14.2.342.4;
	Thu, 17 Oct 2013 10:47:10 +0100
Message-ID: <1382003230.18128.9.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: <marc.ceeeee@gmail.com>
Date: Thu, 17 Oct 2013 10:47:10 +0100
In-Reply-To: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
References: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.30.203.1]
X-DLP: MIA2
Cc: xen-arm@lists.xen.org, mcarino@broadcom.com, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [XenARM] [PATCH] xen/arm: Add CPU ID for Broadcom Brahma-B15
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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, 2013-10-16 at 15:57 -0700, marc.ceeeee@gmail.com wrote:
> From: Marc Carino <marc.ceeeee@gmail.com>
> 
> Let Xen recognize the Broadcom Brahma-B15 CPU by adding the appropriate
> MIDR mask to the initialization phase. Further, ensure that the console
> output properly reports the CPU manufacturer as "Broadcom Corporation".

Thanks for resending, I saw the original but somehow failed to add it to
my queue of things to look at, sorry!

> 
> Signed-off-by: Marc Carino <marc.ceeeee@gmail.com>
> ---
>  xen/arch/arm/arm32/proc-v7.S |    8 ++++++++
>  xen/arch/arm/setup.c         |    1 +
>  2 files changed, 9 insertions(+)
> 
> diff --git a/xen/arch/arm/arm32/proc-v7.S b/xen/arch/arm/arm32/proc-v7.S
> index 6577a89..2c8cb9c 100644
> --- a/xen/arch/arm/arm32/proc-v7.S
> +++ b/xen/arch/arm/arm32/proc-v7.S
> @@ -43,6 +43,14 @@ __v7_ca7mp_proc_info:
>          .long v7_init
>          .size __v7_ca7mp_proc_info, . - __v7_ca7mp_proc_info
>  
> +        .section ".init.proc.info", #alloc, #execinstr
> +        .type __v7_brahma15mp_proc_info, #object
> +__v7_brahma15mp_proc_info:
> +        .long 0x420F00F2             /* Broadcom Brahma-B15 */
> +        .long 0xFF0FFFFF             /* Mask */

This mask includes the revision field (last nibble). Is it intentional
too only support a single revision of this processor?

> +        .long v7_init

v7_init fiddles with the implementation defined ACTLR register in a
Cortex-A15/A7 specific manner. Is the B15 compatible with ARM's Cortex
A15 in this regard?

If not then I think this should be changed to:

ca7mp_init:
ca15mp_init:
        /* Set up the SMP bit in ACTLR */
        mrc   CP32(r0, ACTLR)
        orr   r0, r0, #(ACTLR_V7_SMP) /* enable SMP bit */
        mcr   CP32(r0, ACTLR)
v7_init: /* Generic v7 init */
        mov   pc, lr

and the A15/A7 entries updated to point to the new names.

Perhaps there isn't much point in listing a processor here which doesn't
need any init, but doing so will mean it'll get picked up if we ever add
some init for generic v7, or if we add new hooks etc.

Ian.

> +        .size __v7_brahma15mp_proc_info, . - __v7_brahma15mp_proc_info
> +
>  /*
>   * Local variables:
>   * mode: ASM
> diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
> index 49f344c..7d6e596 100644
> --- a/xen/arch/arm/setup.c
> +++ b/xen/arch/arm/setup.c
> @@ -61,6 +61,7 @@ static void __init init_idle_domain(void)
>  
>  static const char * __initdata processor_implementers[] = {
>      ['A'] = "ARM Limited",
> +    ['B'] = "Broadcom Corporation",
>      ['D'] = "Digital Equipment Corp",
>      ['M'] = "Motorola, Freescale Semiconductor Inc.",
>      ['Q'] = "Qualcomm Inc.",



_______________________________________________
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 Oct 17 23:13:16 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Oct 2013 23:13:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VWwkj-0001z4-08; Thu, 17 Oct 2013 23:13:13 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <marc.ceeeee@gmail.com>)
	id 1VWwki-0001yw-EZ; Thu, 17 Oct 2013 23:13:12 +0000
Received: from [193.109.254.147:61171] by server-6.bemta-14.messagelabs.com id
	B8/A8-03516-70F60625; Thu, 17 Oct 2013 23:13:11 +0000
X-Env-Sender: marc.ceeeee@gmail.com
X-Msg-Ref: server-16.tower-27.messagelabs.com!1382051590!2838644!1
X-Originating-IP: [209.85.215.53]
X-SpamReason: INFO: max file limit 5000
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9125 invoked from network); 17 Oct 2013 23:13:10 -0000
Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com)
	(209.85.215.53)
	by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Oct 2013 23:13:10 -0000
Received: by mail-la0-f53.google.com with SMTP id eo20so64731lab.12
	for <multiple recipients>; Thu, 17 Oct 2013 16:13:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=1Q83Jr8AjHEFKDJzPv8hlQVGbBMCkYxu7W1TOZ9VwcI=;
	b=D188GdGV6JbqalKqffdQjGNlmwqYAChSko9hLo1Nun51tQoiHwTbjGTSuXmvBkWOns
	MFD07g1xvvr4yAQTL+FrUsJdNuWuTx8u7gRihV2RXLYGYhqYJkySDKNQ2yIq6OzINpVL
	mYxG+/QZ2SJOZ/aYGTi2SxXW1VDhw2uDc914nKPhjiVvPpgDg18Qkn3oiH7zBWvTjxcj
	12ltdtydgA/oZl5SBXvt+EsFCgd5YhZyrBXXDLbf5FqSAjoUiiNGFZMJ1rhJj0ELIz8j
	fL4zx/4LD+pMEQX3E4ZhnQvLh/NqPU0ktyJPrcDrSSTnuRq2VrmSWNBCBjFM1Ed7br5X
	nGAg==
MIME-Version: 1.0
X-Received: by 10.152.27.164 with SMTP id u4mr88952lag.82.1382051589874; Thu,
	17 Oct 2013 16:13:09 -0700 (PDT)
Received: by 10.112.55.202 with HTTP; Thu, 17 Oct 2013 16:13:09 -0700 (PDT)
In-Reply-To: <1382003230.18128.9.camel@kazak.uk.xensource.com>
References: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
	<1382003230.18128.9.camel@kazak.uk.xensource.com>
Date: Thu, 17 Oct 2013 16:13:09 -0700
Message-ID: <CAO1A-8DPA=sZLgsirMzNcdYrDEt5P=UeAYpAOodgN2BBXS=GiA@mail.gmail.com>
From: Marc C <marc.ceeeee@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-arm@lists.xen.org, mcarino@broadcom.com, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [XenARM] [PATCH] xen/arm: Add CPU ID for Broadcom Brahma-B15
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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

Hello Ian,

> Thanks for resending, I saw the original but somehow failed to add it to
> my queue of things to look at, sorry!

No problem. Thanks for taking the time to look at the patch!

>> +        .long 0x420F00F2             /* Broadcom Brahma-B15 */
>> +        .long 0xFF0FFFFF             /* Mask */
>
> This mask includes the revision field (last nibble). Is it intentional
> too only support a single revision of this processor?

Yes. At this time, supporting only this specific version of this CPU
is required.

>> +        .long v7_init
>
> v7_init fiddles with the implementation defined ACTLR register in a
> Cortex-A15/A7 specific manner. Is the B15 compatible with ARM's Cortex
> A15 in this regard?

Correct. The B15 will also require the SMP bit to be OR'ed in ACTLR,
so they can be considered compatible in this regard.

I could go ahead with refactoring the code in proc-v7.S, especially if
you expect there to be any future ARMv7 chips with unique
initialization requirements. I think going with your suggestion would
align the code with the Linux kernel's arch/arm/mm/proc-v7.S, which I
assume is a good thing!

Thanks,
Marc

On Thu, Oct 17, 2013 at 2:47 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Wed, 2013-10-16 at 15:57 -0700, marc.ceeeee@gmail.com wrote:
>> From: Marc Carino <marc.ceeeee@gmail.com>
>>
>> Let Xen recognize the Broadcom Brahma-B15 CPU by adding the appropriate
>> MIDR mask to the initialization phase. Further, ensure that the console
>> output properly reports the CPU manufacturer as "Broadcom Corporation".
>
> Thanks for resending, I saw the original but somehow failed to add it to
> my queue of things to look at, sorry!
>
>>
>> Signed-off-by: Marc Carino <marc.ceeeee@gmail.com>
>> ---
>>  xen/arch/arm/arm32/proc-v7.S |    8 ++++++++
>>  xen/arch/arm/setup.c         |    1 +
>>  2 files changed, 9 insertions(+)
>>
>> diff --git a/xen/arch/arm/arm32/proc-v7.S b/xen/arch/arm/arm32/proc-v7.S
>> index 6577a89..2c8cb9c 100644
>> --- a/xen/arch/arm/arm32/proc-v7.S
>> +++ b/xen/arch/arm/arm32/proc-v7.S
>> @@ -43,6 +43,14 @@ __v7_ca7mp_proc_info:
>>          .long v7_init
>>          .size __v7_ca7mp_proc_info, . - __v7_ca7mp_proc_info
>>
>> +        .section ".init.proc.info", #alloc, #execinstr
>> +        .type __v7_brahma15mp_proc_info, #object
>> +__v7_brahma15mp_proc_info:
>> +        .long 0x420F00F2             /* Broadcom Brahma-B15 */
>> +        .long 0xFF0FFFFF             /* Mask */
>
> This mask includes the revision field (last nibble). Is it intentional
> too only support a single revision of this processor?
>
>> +        .long v7_init
>
> v7_init fiddles with the implementation defined ACTLR register in a
> Cortex-A15/A7 specific manner. Is the B15 compatible with ARM's Cortex
> A15 in this regard?
>
> If not then I think this should be changed to:
>
> ca7mp_init:
> ca15mp_init:
>         /* Set up the SMP bit in ACTLR */
>         mrc   CP32(r0, ACTLR)
>         orr   r0, r0, #(ACTLR_V7_SMP) /* enable SMP bit */
>         mcr   CP32(r0, ACTLR)
> v7_init: /* Generic v7 init */
>         mov   pc, lr
>
> and the A15/A7 entries updated to point to the new names.
>
> Perhaps there isn't much point in listing a processor here which doesn't
> need any init, but doing so will mean it'll get picked up if we ever add
> some init for generic v7, or if we add new hooks etc.
>
> Ian.
>
>> +        .size __v7_brahma15mp_proc_info, . - __v7_brahma15mp_proc_info
>> +
>>  /*
>>   * Local variables:
>>   * mode: ASM
>> diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
>> index 49f344c..7d6e596 100644
>> --- a/xen/arch/arm/setup.c
>> +++ b/xen/arch/arm/setup.c
>> @@ -61,6 +61,7 @@ static void __init init_idle_domain(void)
>>
>>  static const char * __initdata processor_implementers[] = {
>>      ['A'] = "ARM Limited",
>> +    ['B'] = "Broadcom Corporation",
>>      ['D'] = "Digital Equipment Corp",
>>      ['M'] = "Motorola, Freescale Semiconductor Inc.",
>>      ['Q'] = "Qualcomm Inc.",
>
>

_______________________________________________
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 Oct 17 23:13:16 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Oct 2013 23:13:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VWwkj-0001z4-08; Thu, 17 Oct 2013 23:13:13 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <marc.ceeeee@gmail.com>)
	id 1VWwki-0001yw-EZ; Thu, 17 Oct 2013 23:13:12 +0000
Received: from [193.109.254.147:61171] by server-6.bemta-14.messagelabs.com id
	B8/A8-03516-70F60625; Thu, 17 Oct 2013 23:13:11 +0000
X-Env-Sender: marc.ceeeee@gmail.com
X-Msg-Ref: server-16.tower-27.messagelabs.com!1382051590!2838644!1
X-Originating-IP: [209.85.215.53]
X-SpamReason: INFO: max file limit 5000
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9125 invoked from network); 17 Oct 2013 23:13:10 -0000
Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com)
	(209.85.215.53)
	by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Oct 2013 23:13:10 -0000
Received: by mail-la0-f53.google.com with SMTP id eo20so64731lab.12
	for <multiple recipients>; Thu, 17 Oct 2013 16:13:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=1Q83Jr8AjHEFKDJzPv8hlQVGbBMCkYxu7W1TOZ9VwcI=;
	b=D188GdGV6JbqalKqffdQjGNlmwqYAChSko9hLo1Nun51tQoiHwTbjGTSuXmvBkWOns
	MFD07g1xvvr4yAQTL+FrUsJdNuWuTx8u7gRihV2RXLYGYhqYJkySDKNQ2yIq6OzINpVL
	mYxG+/QZ2SJOZ/aYGTi2SxXW1VDhw2uDc914nKPhjiVvPpgDg18Qkn3oiH7zBWvTjxcj
	12ltdtydgA/oZl5SBXvt+EsFCgd5YhZyrBXXDLbf5FqSAjoUiiNGFZMJ1rhJj0ELIz8j
	fL4zx/4LD+pMEQX3E4ZhnQvLh/NqPU0ktyJPrcDrSSTnuRq2VrmSWNBCBjFM1Ed7br5X
	nGAg==
MIME-Version: 1.0
X-Received: by 10.152.27.164 with SMTP id u4mr88952lag.82.1382051589874; Thu,
	17 Oct 2013 16:13:09 -0700 (PDT)
Received: by 10.112.55.202 with HTTP; Thu, 17 Oct 2013 16:13:09 -0700 (PDT)
In-Reply-To: <1382003230.18128.9.camel@kazak.uk.xensource.com>
References: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
	<1382003230.18128.9.camel@kazak.uk.xensource.com>
Date: Thu, 17 Oct 2013 16:13:09 -0700
Message-ID: <CAO1A-8DPA=sZLgsirMzNcdYrDEt5P=UeAYpAOodgN2BBXS=GiA@mail.gmail.com>
From: Marc C <marc.ceeeee@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-arm@lists.xen.org, mcarino@broadcom.com, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [XenARM] [PATCH] xen/arm: Add CPU ID for Broadcom Brahma-B15
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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

Hello Ian,

> Thanks for resending, I saw the original but somehow failed to add it to
> my queue of things to look at, sorry!

No problem. Thanks for taking the time to look at the patch!

>> +        .long 0x420F00F2             /* Broadcom Brahma-B15 */
>> +        .long 0xFF0FFFFF             /* Mask */
>
> This mask includes the revision field (last nibble). Is it intentional
> too only support a single revision of this processor?

Yes. At this time, supporting only this specific version of this CPU
is required.

>> +        .long v7_init
>
> v7_init fiddles with the implementation defined ACTLR register in a
> Cortex-A15/A7 specific manner. Is the B15 compatible with ARM's Cortex
> A15 in this regard?

Correct. The B15 will also require the SMP bit to be OR'ed in ACTLR,
so they can be considered compatible in this regard.

I could go ahead with refactoring the code in proc-v7.S, especially if
you expect there to be any future ARMv7 chips with unique
initialization requirements. I think going with your suggestion would
align the code with the Linux kernel's arch/arm/mm/proc-v7.S, which I
assume is a good thing!

Thanks,
Marc

On Thu, Oct 17, 2013 at 2:47 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Wed, 2013-10-16 at 15:57 -0700, marc.ceeeee@gmail.com wrote:
>> From: Marc Carino <marc.ceeeee@gmail.com>
>>
>> Let Xen recognize the Broadcom Brahma-B15 CPU by adding the appropriate
>> MIDR mask to the initialization phase. Further, ensure that the console
>> output properly reports the CPU manufacturer as "Broadcom Corporation".
>
> Thanks for resending, I saw the original but somehow failed to add it to
> my queue of things to look at, sorry!
>
>>
>> Signed-off-by: Marc Carino <marc.ceeeee@gmail.com>
>> ---
>>  xen/arch/arm/arm32/proc-v7.S |    8 ++++++++
>>  xen/arch/arm/setup.c         |    1 +
>>  2 files changed, 9 insertions(+)
>>
>> diff --git a/xen/arch/arm/arm32/proc-v7.S b/xen/arch/arm/arm32/proc-v7.S
>> index 6577a89..2c8cb9c 100644
>> --- a/xen/arch/arm/arm32/proc-v7.S
>> +++ b/xen/arch/arm/arm32/proc-v7.S
>> @@ -43,6 +43,14 @@ __v7_ca7mp_proc_info:
>>          .long v7_init
>>          .size __v7_ca7mp_proc_info, . - __v7_ca7mp_proc_info
>>
>> +        .section ".init.proc.info", #alloc, #execinstr
>> +        .type __v7_brahma15mp_proc_info, #object
>> +__v7_brahma15mp_proc_info:
>> +        .long 0x420F00F2             /* Broadcom Brahma-B15 */
>> +        .long 0xFF0FFFFF             /* Mask */
>
> This mask includes the revision field (last nibble). Is it intentional
> too only support a single revision of this processor?
>
>> +        .long v7_init
>
> v7_init fiddles with the implementation defined ACTLR register in a
> Cortex-A15/A7 specific manner. Is the B15 compatible with ARM's Cortex
> A15 in this regard?
>
> If not then I think this should be changed to:
>
> ca7mp_init:
> ca15mp_init:
>         /* Set up the SMP bit in ACTLR */
>         mrc   CP32(r0, ACTLR)
>         orr   r0, r0, #(ACTLR_V7_SMP) /* enable SMP bit */
>         mcr   CP32(r0, ACTLR)
> v7_init: /* Generic v7 init */
>         mov   pc, lr
>
> and the A15/A7 entries updated to point to the new names.
>
> Perhaps there isn't much point in listing a processor here which doesn't
> need any init, but doing so will mean it'll get picked up if we ever add
> some init for generic v7, or if we add new hooks etc.
>
> Ian.
>
>> +        .size __v7_brahma15mp_proc_info, . - __v7_brahma15mp_proc_info
>> +
>>  /*
>>   * Local variables:
>>   * mode: ASM
>> diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
>> index 49f344c..7d6e596 100644
>> --- a/xen/arch/arm/setup.c
>> +++ b/xen/arch/arm/setup.c
>> @@ -61,6 +61,7 @@ static void __init init_idle_domain(void)
>>
>>  static const char * __initdata processor_implementers[] = {
>>      ['A'] = "ARM Limited",
>> +    ['B'] = "Broadcom Corporation",
>>      ['D'] = "Digital Equipment Corp",
>>      ['M'] = "Motorola, Freescale Semiconductor Inc.",
>>      ['Q'] = "Qualcomm Inc.",
>
>

_______________________________________________
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 Oct 18 08:39:20 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 18 Oct 2013 08:39:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VX5aX-0003hc-1d; Fri, 18 Oct 2013 08:39:17 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1VX5aW-0003hU-0Z; Fri, 18 Oct 2013 08:39:16 +0000
Received: from [193.109.254.147:42009] by server-14.bemta-14.messagelabs.com
	id 4F/B9-20073-3B3F0625; Fri, 18 Oct 2013 08:39:15 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1382085553!2902642!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: INFO: max file limit 5000
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20899 invoked from network); 18 Oct 2013 08:39:14 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Oct 2013 08:39:14 -0000
X-IronPort-AV: E=Sophos;i="4.93,520,1378857600"; d="scan'208";a="64905378"
Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 18 Oct 2013 08:39:12 +0000
Received: from LONPEX01CL01.citrite.net (10.30.203.101) by
	FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server
	(TLS) id 14.2.342.4; Fri, 18 Oct 2013 04:39:12 -0400
Received: from [10.80.2.80] (10.30.203.1) by LONPEX01CL01.citrite.net
	(10.30.203.101) with Microsoft SMTP Server id 14.2.342.4;
	Fri, 18 Oct 2013 09:39:10 +0100
Message-ID: <1382085550.18128.81.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Marc C <marc.ceeeee@gmail.com>
Date: Fri, 18 Oct 2013 09:39:10 +0100
In-Reply-To: <CAO1A-8DPA=sZLgsirMzNcdYrDEt5P=UeAYpAOodgN2BBXS=GiA@mail.gmail.com>
References: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
	<1382003230.18128.9.camel@kazak.uk.xensource.com>
	<CAO1A-8DPA=sZLgsirMzNcdYrDEt5P=UeAYpAOodgN2BBXS=GiA@mail.gmail.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.30.203.1]
X-DLP: MIA2
Cc: xen-arm@lists.xen.org, mcarino@broadcom.com, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [XenARM] [PATCH] xen/arm: Add CPU ID for Broadcom Brahma-B15
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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-10-17 at 16:13 -0700, Marc C wrote:
> Hello Ian,
> 
> > Thanks for resending, I saw the original but somehow failed to add it to
> > my queue of things to look at, sorry!
> 
> No problem. Thanks for taking the time to look at the patch!
> 
> >> +        .long 0x420F00F2             /* Broadcom Brahma-B15 */
> >> +        .long 0xFF0FFFFF             /* Mask */
> >
> > This mask includes the revision field (last nibble). Is it intentional
> > too only support a single revision of this processor?
> 
> Yes. At this time, supporting only this specific version of this CPU
> is required.

Is there any harm in allowing all of them though?

> >> +        .long v7_init
> >
> > v7_init fiddles with the implementation defined ACTLR register in a
> > Cortex-A15/A7 specific manner. Is the B15 compatible with ARM's Cortex
> > A15 in this regard?
> 
> Correct. The B15 will also require the SMP bit to be OR'ed in ACTLR,
> so they can be considered compatible in this regard.
> 
> I could go ahead with refactoring the code in proc-v7.S,

Given the above it's not a requirement so I'll apply this patch as is,
but if you feel inclined to follow up with the refactoring that would be
wonderful.

Thanks,
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 Oct 18 08:39:20 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 18 Oct 2013 08:39:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VX5aX-0003hc-1d; Fri, 18 Oct 2013 08:39:17 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1VX5aW-0003hU-0Z; Fri, 18 Oct 2013 08:39:16 +0000
Received: from [193.109.254.147:42009] by server-14.bemta-14.messagelabs.com
	id 4F/B9-20073-3B3F0625; Fri, 18 Oct 2013 08:39:15 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1382085553!2902642!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: INFO: max file limit 5000
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20899 invoked from network); 18 Oct 2013 08:39:14 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Oct 2013 08:39:14 -0000
X-IronPort-AV: E=Sophos;i="4.93,520,1378857600"; d="scan'208";a="64905378"
Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 18 Oct 2013 08:39:12 +0000
Received: from LONPEX01CL01.citrite.net (10.30.203.101) by
	FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server
	(TLS) id 14.2.342.4; Fri, 18 Oct 2013 04:39:12 -0400
Received: from [10.80.2.80] (10.30.203.1) by LONPEX01CL01.citrite.net
	(10.30.203.101) with Microsoft SMTP Server id 14.2.342.4;
	Fri, 18 Oct 2013 09:39:10 +0100
Message-ID: <1382085550.18128.81.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Marc C <marc.ceeeee@gmail.com>
Date: Fri, 18 Oct 2013 09:39:10 +0100
In-Reply-To: <CAO1A-8DPA=sZLgsirMzNcdYrDEt5P=UeAYpAOodgN2BBXS=GiA@mail.gmail.com>
References: <1381964226-7853-1-git-send-email-marc.ceeeee@gmail.com>
	<1382003230.18128.9.camel@kazak.uk.xensource.com>
	<CAO1A-8DPA=sZLgsirMzNcdYrDEt5P=UeAYpAOodgN2BBXS=GiA@mail.gmail.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.30.203.1]
X-DLP: MIA2
Cc: xen-arm@lists.xen.org, mcarino@broadcom.com, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [XenARM] [PATCH] xen/arm: Add CPU ID for Broadcom Brahma-B15
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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-10-17 at 16:13 -0700, Marc C wrote:
> Hello Ian,
> 
> > Thanks for resending, I saw the original but somehow failed to add it to
> > my queue of things to look at, sorry!
> 
> No problem. Thanks for taking the time to look at the patch!
> 
> >> +        .long 0x420F00F2             /* Broadcom Brahma-B15 */
> >> +        .long 0xFF0FFFFF             /* Mask */
> >
> > This mask includes the revision field (last nibble). Is it intentional
> > too only support a single revision of this processor?
> 
> Yes. At this time, supporting only this specific version of this CPU
> is required.

Is there any harm in allowing all of them though?

> >> +        .long v7_init
> >
> > v7_init fiddles with the implementation defined ACTLR register in a
> > Cortex-A15/A7 specific manner. Is the B15 compatible with ARM's Cortex
> > A15 in this regard?
> 
> Correct. The B15 will also require the SMP bit to be OR'ed in ACTLR,
> so they can be considered compatible in this regard.
> 
> I could go ahead with refactoring the code in proc-v7.S,

Given the above it's not a requirement so I'll apply this patch as is,
but if you feel inclined to follow up with the refactoring that would be
wonderful.

Thanks,
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 Wed Oct 30 09:55:52 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 30 Oct 2013 09:55:52 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VbSVB-0006NT-OM; Wed, 30 Oct 2013 09:55:49 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <mj.embd@gmail.com>) id 1VbSV9-0006NM-Sz
	for xen-arm@lists.xen.org; Wed, 30 Oct 2013 09:55:47 +0000
Received: from [193.109.254.147:62570] by server-11.bemta-14.messagelabs.com
	id 36/84-08419-3A7D0725; Wed, 30 Oct 2013 09:55:47 +0000
X-Env-Sender: mj.embd@gmail.com
X-Msg-Ref: server-14.tower-27.messagelabs.com!1383126945!1555730!1
X-Originating-IP: [209.85.192.177]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31827 invoked from network); 30 Oct 2013 09:55:46 -0000
Received: from mail-pd0-f177.google.com (HELO mail-pd0-f177.google.com)
	(209.85.192.177)
	by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Oct 2013 09:55:46 -0000
Received: by mail-pd0-f177.google.com with SMTP id p10so732102pdj.36
	for <xen-arm@lists.xen.org>; Wed, 30 Oct 2013 02:55:44 -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=3iEh1bLfO/4/YLSNwWHAo/k4e1aM/T5tGAif4tlWby0=;
	b=lElwinBdPjw0eNyHMZb46BEeLcdfgLa0wnF7pMVZdbYamWXut6/owfBJCNiWsJtYTV
	Pq1+6aJGT6rq5cyJJNMCo8csnbMSfNoftPQSwXKdar7P66spZNA3aoccGzPWfNcktQe2
	8M6eNfWrN3q7x4n79a1CvEZTrQLwpbvGIr2QKAjspnKt9dVBtshsfIB3vxO14KBg1uIc
	En0Cw8WGCgcrzTptC644WfUah3GhTFzPQpM7gNs5EM+1v96iPUy1v2KI8J4fEEwgR+p4
	Hzvs3vN+jCPUc93DcqJVJmMO9sba7trpecz+T0xu8XYTtNQZNZiFACYW6NHFZWpQ7HVh
	sGug==
MIME-Version: 1.0
X-Received: by 10.68.105.35 with SMTP id gj3mr388901pbb.202.1383126944873;
	Wed, 30 Oct 2013 02:55:44 -0700 (PDT)
Received: by 10.70.135.106 with HTTP; Wed, 30 Oct 2013 02:55:44 -0700 (PDT)
Date: Wed, 30 Oct 2013 15:25:44 +0530
Message-ID: <CAPUj1ONAcOHS2Ze-djRC4wrct2ANV8WZc40u1SCYvGvajwh-2w@mail.gmail.com>
From: Mj Embd <mj.embd@gmail.com>
To: xen-arm@lists.xen.org
Subject: [XenARM] [query] gic_set_lr always uses maintenance Interrupt
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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,

As per section 5.2.2 of IHI0048B_b_gic_architecture_specification, If
hypervisor is injecting a VIRQ into guest, that is actually a HW IRQ,
and guest does EOI (provided conditions) the maintenance interrupt is
not needed.

In xen arch/arm/gic.c always while setting an LR using gic_set_lr ,
the maintenance_int is enabled.

Can some one clear the doubt on why it is done
a) is this because EOI by guest would result in control back to
hypervisor to replenish the LR for   inflight, as there is otherwise
no way to know in hypervisor that the LR is available.
or
b) some other reason ?

_______________________________________________
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 Oct 30 09:55:52 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 30 Oct 2013 09:55:52 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VbSVB-0006NT-OM; Wed, 30 Oct 2013 09:55:49 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <mj.embd@gmail.com>) id 1VbSV9-0006NM-Sz
	for xen-arm@lists.xen.org; Wed, 30 Oct 2013 09:55:47 +0000
Received: from [193.109.254.147:62570] by server-11.bemta-14.messagelabs.com
	id 36/84-08419-3A7D0725; Wed, 30 Oct 2013 09:55:47 +0000
X-Env-Sender: mj.embd@gmail.com
X-Msg-Ref: server-14.tower-27.messagelabs.com!1383126945!1555730!1
X-Originating-IP: [209.85.192.177]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31827 invoked from network); 30 Oct 2013 09:55:46 -0000
Received: from mail-pd0-f177.google.com (HELO mail-pd0-f177.google.com)
	(209.85.192.177)
	by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Oct 2013 09:55:46 -0000
Received: by mail-pd0-f177.google.com with SMTP id p10so732102pdj.36
	for <xen-arm@lists.xen.org>; Wed, 30 Oct 2013 02:55:44 -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=3iEh1bLfO/4/YLSNwWHAo/k4e1aM/T5tGAif4tlWby0=;
	b=lElwinBdPjw0eNyHMZb46BEeLcdfgLa0wnF7pMVZdbYamWXut6/owfBJCNiWsJtYTV
	Pq1+6aJGT6rq5cyJJNMCo8csnbMSfNoftPQSwXKdar7P66spZNA3aoccGzPWfNcktQe2
	8M6eNfWrN3q7x4n79a1CvEZTrQLwpbvGIr2QKAjspnKt9dVBtshsfIB3vxO14KBg1uIc
	En0Cw8WGCgcrzTptC644WfUah3GhTFzPQpM7gNs5EM+1v96iPUy1v2KI8J4fEEwgR+p4
	Hzvs3vN+jCPUc93DcqJVJmMO9sba7trpecz+T0xu8XYTtNQZNZiFACYW6NHFZWpQ7HVh
	sGug==
MIME-Version: 1.0
X-Received: by 10.68.105.35 with SMTP id gj3mr388901pbb.202.1383126944873;
	Wed, 30 Oct 2013 02:55:44 -0700 (PDT)
Received: by 10.70.135.106 with HTTP; Wed, 30 Oct 2013 02:55:44 -0700 (PDT)
Date: Wed, 30 Oct 2013 15:25:44 +0530
Message-ID: <CAPUj1ONAcOHS2Ze-djRC4wrct2ANV8WZc40u1SCYvGvajwh-2w@mail.gmail.com>
From: Mj Embd <mj.embd@gmail.com>
To: xen-arm@lists.xen.org
Subject: [XenARM] [query] gic_set_lr always uses maintenance Interrupt
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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,

As per section 5.2.2 of IHI0048B_b_gic_architecture_specification, If
hypervisor is injecting a VIRQ into guest, that is actually a HW IRQ,
and guest does EOI (provided conditions) the maintenance interrupt is
not needed.

In xen arch/arm/gic.c always while setting an LR using gic_set_lr ,
the maintenance_int is enabled.

Can some one clear the doubt on why it is done
a) is this because EOI by guest would result in control back to
hypervisor to replenish the LR for   inflight, as there is otherwise
no way to know in hypervisor that the LR is available.
or
b) some other reason ?

_______________________________________________
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 Oct 31 09:42:17 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 31 Oct 2013 09:42:17 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1Vbola-0001bw-Pv; Thu, 31 Oct 2013 09:42:14 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <mj.embd@gmail.com>) id 1VbolZ-0001br-Bj
	for xen-arm@lists.xen.org; Thu, 31 Oct 2013 09:42:13 +0000
Received: from [85.158.143.35:16547] by server-3.bemta-4.messagelabs.com id
	05/5F-19578-4F522725; Thu, 31 Oct 2013 09:42:12 +0000
X-Env-Sender: mj.embd@gmail.com
X-Msg-Ref: server-13.tower-21.messagelabs.com!1383212530!29894!1
X-Originating-IP: [209.85.220.48]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.13; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28469 invoked from network); 31 Oct 2013 09:42:12 -0000
Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com)
	(209.85.220.48)
	by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	31 Oct 2013 09:42:12 -0000
Received: by mail-pa0-f48.google.com with SMTP id kq14so2231980pab.7
	for <xen-arm@lists.xen.org>; Thu, 31 Oct 2013 02:42:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=Kd4HnLeSp7AL2l1NnU1Cp8Y5mqPR2I7TRxtdXPE3NJ4=;
	b=CjBTz+ndO00Ck4XMvamD/+FwQHaVNP3VQoQPph+/egYTHVOGEP8mxVe5QPsuV4n4x1
	mMt2in//APpMss1bgiKtvnTLyxJH+HVbdrDeWDHbCbs2SwkZ67ZMTlHr9bThvfCvykon
	mdHdKCUcoBydwrwNvlcyoR4tdQiLomhFWY/1iJXp75wgSqkUAjTY/KkTtfjWNammdIJ9
	fJXoDbgJLOFic+ybJQcZ4Uh2j8QZLnbX2/PkN+ETQiBXGDonMangCsgtQm0LWRs7Xbod
	Ckif136XTO5yxsk8pqk3zcyPoUJirYurdE8jFeV5+ygQa5QU2Y1zlpG7mkS8U46x19wp
	9+xg==
MIME-Version: 1.0
X-Received: by 10.66.155.36 with SMTP id vt4mr918557pab.93.1383212530041; Thu,
	31 Oct 2013 02:42:10 -0700 (PDT)
Received: by 10.70.135.106 with HTTP; Thu, 31 Oct 2013 02:42:09 -0700 (PDT)
In-Reply-To: <CAPUj1ONAcOHS2Ze-djRC4wrct2ANV8WZc40u1SCYvGvajwh-2w@mail.gmail.com>
References: <CAPUj1ONAcOHS2Ze-djRC4wrct2ANV8WZc40u1SCYvGvajwh-2w@mail.gmail.com>
Date: Thu, 31 Oct 2013 15:12:09 +0530
Message-ID: <CAPUj1ONQqa2DSFAtAXHCFSKheUCwgdn6Jbn+a6tfH23kik5Rzg@mail.gmail.com>
From: Mj Embd <mj.embd@gmail.com>
To: xen-arm@lists.xen.org, Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [XenARM] [query] gic_set_lr always uses maintenance Interrupt
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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,

Can you please comment...

On Wed, Oct 30, 2013 at 3:25 PM, Mj Embd <mj.embd@gmail.com> wrote:
> Hi,
>
> As per section 5.2.2 of IHI0048B_b_gic_architecture_specification, If
> hypervisor is injecting a VIRQ into guest, that is actually a HW IRQ,
> and guest does EOI (provided conditions) the maintenance interrupt is
> not needed.
>
> In xen arch/arm/gic.c always while setting an LR using gic_set_lr ,
> the maintenance_int is enabled.
>
> Can some one clear the doubt on why it is done
> a) is this because EOI by guest would result in control back to
> hypervisor to replenish the LR for   inflight, as there is otherwise
> no way to know in hypervisor that the LR is available.
> or
> b) some other reason ?



-- 
-mj

_______________________________________________
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 Oct 31 09:42:17 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 31 Oct 2013 09:42:17 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1Vbola-0001bw-Pv; Thu, 31 Oct 2013 09:42:14 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <mj.embd@gmail.com>) id 1VbolZ-0001br-Bj
	for xen-arm@lists.xen.org; Thu, 31 Oct 2013 09:42:13 +0000
Received: from [85.158.143.35:16547] by server-3.bemta-4.messagelabs.com id
	05/5F-19578-4F522725; Thu, 31 Oct 2013 09:42:12 +0000
X-Env-Sender: mj.embd@gmail.com
X-Msg-Ref: server-13.tower-21.messagelabs.com!1383212530!29894!1
X-Originating-IP: [209.85.220.48]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.13; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28469 invoked from network); 31 Oct 2013 09:42:12 -0000
Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com)
	(209.85.220.48)
	by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	31 Oct 2013 09:42:12 -0000
Received: by mail-pa0-f48.google.com with SMTP id kq14so2231980pab.7
	for <xen-arm@lists.xen.org>; Thu, 31 Oct 2013 02:42:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=Kd4HnLeSp7AL2l1NnU1Cp8Y5mqPR2I7TRxtdXPE3NJ4=;
	b=CjBTz+ndO00Ck4XMvamD/+FwQHaVNP3VQoQPph+/egYTHVOGEP8mxVe5QPsuV4n4x1
	mMt2in//APpMss1bgiKtvnTLyxJH+HVbdrDeWDHbCbs2SwkZ67ZMTlHr9bThvfCvykon
	mdHdKCUcoBydwrwNvlcyoR4tdQiLomhFWY/1iJXp75wgSqkUAjTY/KkTtfjWNammdIJ9
	fJXoDbgJLOFic+ybJQcZ4Uh2j8QZLnbX2/PkN+ETQiBXGDonMangCsgtQm0LWRs7Xbod
	Ckif136XTO5yxsk8pqk3zcyPoUJirYurdE8jFeV5+ygQa5QU2Y1zlpG7mkS8U46x19wp
	9+xg==
MIME-Version: 1.0
X-Received: by 10.66.155.36 with SMTP id vt4mr918557pab.93.1383212530041; Thu,
	31 Oct 2013 02:42:10 -0700 (PDT)
Received: by 10.70.135.106 with HTTP; Thu, 31 Oct 2013 02:42:09 -0700 (PDT)
In-Reply-To: <CAPUj1ONAcOHS2Ze-djRC4wrct2ANV8WZc40u1SCYvGvajwh-2w@mail.gmail.com>
References: <CAPUj1ONAcOHS2Ze-djRC4wrct2ANV8WZc40u1SCYvGvajwh-2w@mail.gmail.com>
Date: Thu, 31 Oct 2013 15:12:09 +0530
Message-ID: <CAPUj1ONQqa2DSFAtAXHCFSKheUCwgdn6Jbn+a6tfH23kik5Rzg@mail.gmail.com>
From: Mj Embd <mj.embd@gmail.com>
To: xen-arm@lists.xen.org, Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [XenARM] [query] gic_set_lr always uses maintenance Interrupt
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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,

Can you please comment...

On Wed, Oct 30, 2013 at 3:25 PM, Mj Embd <mj.embd@gmail.com> wrote:
> Hi,
>
> As per section 5.2.2 of IHI0048B_b_gic_architecture_specification, If
> hypervisor is injecting a VIRQ into guest, that is actually a HW IRQ,
> and guest does EOI (provided conditions) the maintenance interrupt is
> not needed.
>
> In xen arch/arm/gic.c always while setting an LR using gic_set_lr ,
> the maintenance_int is enabled.
>
> Can some one clear the doubt on why it is done
> a) is this because EOI by guest would result in control back to
> hypervisor to replenish the LR for   inflight, as there is otherwise
> no way to know in hypervisor that the LR is available.
> or
> b) some other reason ?



-- 
-mj

_______________________________________________
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 Oct 31 16:41:24 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 31 Oct 2013 16:41:24 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VbvJA-000545-Rw; Thu, 31 Oct 2013 16:41:20 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1VbvJ9-00053t-F7
	for xen-arm@lists.xen.org; Thu, 31 Oct 2013 16:41:19 +0000
Received: from [193.109.254.147:4563] by server-9.bemta-14.messagelabs.com id
	B2/AB-08751-E2882725; Thu, 31 Oct 2013 16:41:18 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-9.tower-27.messagelabs.com!1383237676!1934300!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.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28873 invoked from network); 31 Oct 2013 16:41:17 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	31 Oct 2013 16:41:17 -0000
X-IronPort-AV: E=Sophos;i="4.93,609,1378857600"; d="scan'208";a="69402049"
Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 31 Oct 2013 16:41:16 +0000
Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com
	(10.13.107.78) with Microsoft SMTP Server id 14.2.342.4;
	Thu, 31 Oct 2013 12:41:15 -0400
Received: from gateway-cbg.eng.citrite.net ([10.80.16.17] helo=[127.0.0.1])	by
	ukmail1.uk.xensource.com with esmtp (Exim 4.69)	(envelope-from
	<Ian.Campbell@citrix.com>)	id 1VbvJ5-0007F9-Gz;
	Thu, 31 Oct 2013 16:41:15 +0000
Message-ID: <1383237675.25018.137.camel@dagon.hellion.org.uk>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Mj Embd <mj.embd@gmail.com>
Date: Thu, 31 Oct 2013 16:41:15 +0000
In-Reply-To: <CAPUj1ONQqa2DSFAtAXHCFSKheUCwgdn6Jbn+a6tfH23kik5Rzg@mail.gmail.com>
References: <CAPUj1ONAcOHS2Ze-djRC4wrct2ANV8WZc40u1SCYvGvajwh-2w@mail.gmail.com>
	<CAPUj1ONQqa2DSFAtAXHCFSKheUCwgdn6Jbn+a6tfH23kik5Rzg@mail.gmail.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-4+b1 
MIME-Version: 1.0
X-DLP: MIA1
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] [query] gic_set_lr always uses maintenance Interrupt
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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-10-31 at 15:12 +0530, Mj Embd wrote:
> Hi Ian,
> 
> Can you please comment...

I think I commented on the version on xen-devel.

FYI xen-arm@ is for the discussion of the (mostly moribund) PV port of
Xen to ARM[0], discussion of the mainline port to ARM with virt
extensions[1] happens on xen-devel@. Yes, this is confusing.

Ian.

[0] http://wiki.xenproject.org/wiki/Xen_ARM_%28PV%29
[1] http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions


_______________________________________________
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 Oct 31 16:41:24 2013
Return-path: <xen-arm-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 31 Oct 2013 16:41:24 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-arm-bounces@lists.xen.org>)
	id 1VbvJA-000545-Rw; Thu, 31 Oct 2013 16:41:20 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1VbvJ9-00053t-F7
	for xen-arm@lists.xen.org; Thu, 31 Oct 2013 16:41:19 +0000
Received: from [193.109.254.147:4563] by server-9.bemta-14.messagelabs.com id
	B2/AB-08751-E2882725; Thu, 31 Oct 2013 16:41:18 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-9.tower-27.messagelabs.com!1383237676!1934300!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.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28873 invoked from network); 31 Oct 2013 16:41:17 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	31 Oct 2013 16:41:17 -0000
X-IronPort-AV: E=Sophos;i="4.93,609,1378857600"; d="scan'208";a="69402049"
Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 31 Oct 2013 16:41:16 +0000
Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com
	(10.13.107.78) with Microsoft SMTP Server id 14.2.342.4;
	Thu, 31 Oct 2013 12:41:15 -0400
Received: from gateway-cbg.eng.citrite.net ([10.80.16.17] helo=[127.0.0.1])	by
	ukmail1.uk.xensource.com with esmtp (Exim 4.69)	(envelope-from
	<Ian.Campbell@citrix.com>)	id 1VbvJ5-0007F9-Gz;
	Thu, 31 Oct 2013 16:41:15 +0000
Message-ID: <1383237675.25018.137.camel@dagon.hellion.org.uk>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Mj Embd <mj.embd@gmail.com>
Date: Thu, 31 Oct 2013 16:41:15 +0000
In-Reply-To: <CAPUj1ONQqa2DSFAtAXHCFSKheUCwgdn6Jbn+a6tfH23kik5Rzg@mail.gmail.com>
References: <CAPUj1ONAcOHS2Ze-djRC4wrct2ANV8WZc40u1SCYvGvajwh-2w@mail.gmail.com>
	<CAPUj1ONQqa2DSFAtAXHCFSKheUCwgdn6Jbn+a6tfH23kik5Rzg@mail.gmail.com>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-4+b1 
MIME-Version: 1.0
X-DLP: MIA1
Cc: xen-arm@lists.xen.org
Subject: Re: [XenARM] [query] gic_set_lr always uses maintenance Interrupt
X-BeenThere: xen-arm@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: List for Xen ARM developers and users <xen-arm.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-arm@lists.xen.org>
List-Help: <mailto:xen-arm-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm>,
	<mailto:xen-arm-request@lists.xen.org?subject=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-10-31 at 15:12 +0530, Mj Embd wrote:
> Hi Ian,
> 
> Can you please comment...

I think I commented on the version on xen-devel.

FYI xen-arm@ is for the discussion of the (mostly moribund) PV port of
Xen to ARM[0], discussion of the mainline port to ARM with virt
extensions[1] happens on xen-devel@. Yes, this is confusing.

Ian.

[0] http://wiki.xenproject.org/wiki/Xen_ARM_%28PV%29
[1] http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions


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