From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCH 3/5] booke: define reset and shutdown hcalls
Date: Wed, 17 Jul 2013 12:09:28 -0500
Message-ID: <1374080968.8183.359@snotra>
References: <20130716063555.GG11772@redhat.com> <1374015874.8183.344@snotra>
	<20130717110032.GV11772@redhat.com>
	<10FE6A8C-161E-404C-AEA0-715C72F2B2FE@suse.de>
	<9F6FE96B71CF29479FF1CDC8046E150364EA85@039-SN1MPN1-004.039d.mgd.msft.net>
	<8F816921-FB5A-476D-8633-2574A517AEED@suse.de>
	<9F6FE96B71CF29479FF1CDC8046E150364EAD2@039-SN1MPN1-004.039d.mgd.msft.net>
	<9105925A-44D7-49DF-98DE-252E5FCD0B54@suse.de>
	<6A3DF150A5B70D4F9B66A25E3F7C888D070D5E4E@039-SN2MPN1-013.039d.mgd.msft.net>
	<BB948474-FE57-499B-86FE-D678CC976BA2@suse.de>
	<6A3DF150A5B70D4F9B66A25E3F7C888D070D5EBE@039-SN2MPN1-013.039d.mgd.msft.net>
	<BF328B5D-FBE6-4A02-A14C-036D20E1C287@suse.de> <1374080360.8183.357@snotra>
	<D29DB244-11F3-44F0-BE2A-1B3450124116@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed
Content-Transfer-Encoding: 8BIT
Cc: Bhushan Bharat-R65777 <R65777@freescale.com>,
	Yoder Stuart-B08248 <B08248@freescale.com>,
	Wood Scott-B07421 <B07421@freescale.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
	Gleb Natapov <gleb@redhat.com>
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-ppc-owner@vger.kernel.org>
In-Reply-To: <D29DB244-11F3-44F0-BE2A-1B3450124116@suse.de> (from
	agraf@suse.de on Wed Jul 17 12:05:41 2013)
Content-Disposition: inline
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On 07/17/2013 12:05:41 PM, Alexander Graf wrote:
> 
> On 17.07.2013, at 18:59, Scott Wood wrote:
> 
> > On 07/17/2013 11:04:08 AM, Alexander Graf wrote:
> >> On 17.07.2013, at 17:59, Bhushan Bharat-R65777 wrote:
> >> > Ah, so we can choose any address range in ccsr space of a PV  
> machine (-M ppce500 / e500plat).
> >> No, we don't put it in CCSR space. It'd just be orthogonal to CCSR.
> >
> > I'd rather we put it in CCSR, especially if/when we implement LAWs  
> and CCSRBAR which gives the guest control of its address space.
> 
> Do we have space in CCSR?

Sure.  Even on real hardware there are gaps, and on the paravirt  
platform we have loads of space. :-)

This does raise the question of what compatible the ccsr node should  
have on the paravirt platform.  Currently it's still labelled  
"fsl,mpc8544-immr", which is clearly wrong.  If we add CCSRBAR support,  
should the paravirt platform have it as well?  If so, what is the size  
of CCSR on the paravirt platform?

-Scott