From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: About arm32 address translation Date: Wed, 16 Oct 2013 11:24:47 +0100 Message-ID: <1381919087.21901.64.camel@kazak.uk.xensource.com> References: <1381915521.21901.54.camel@kazak.uk.xensource.com> <2D233787-D3A5-48D2-9398-C122CB57C187@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2D233787-D3A5-48D2-9398-C122CB57C187@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Chen Baozi Cc: List Developer Xen List-Id: xen-devel@lists.xenproject.org On Wed, 2013-10-16 at 18:02 +0800, Chen Baozi wrote: > On Oct 16, 2013, at 5:25 PM, Ian Campbell wrote: > > > On Wed, 2013-10-16 at 17:20 +0800, Chen Baozi wrote: > >> Hi Ian, > >> > >> I am trying to add supporting dumping 32-bit guest on arm32 to see > >> what happened in my dom0 kernel when booting. It seems > >> gvirt_to_maddr() is not workable under arm32. > > > > What makes you say that, it should work, or else it is buggy and we've > > not noticed, but it is used in copy to/from user routines so I doubt > > that. > > Ok, I'll look into it. The output shows me "Failed to convert stack to > physical address". In this case, it must be gvirt_to_maddr to return > -EFAULT. That suggests that the guest's SP doesn't have a mapping in the guest's PTs. What's the full trace? Ian