WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [PATCH] fix dirty_bit in xenivt.S (was Re: [Xen-ia64-devel] Fail toc

To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>, "You, Yongkang" <yongkang.you@xxxxxxxxx>
Subject: RE: [PATCH] fix dirty_bit in xenivt.S (was Re: [Xen-ia64-devel] Fail tocreate VTI domain in lates Cset 10143)
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Wed, 24 May 2006 15:04:27 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 24 May 2006 00:04:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZ+5f95mRWyzkSUSqu8Rec7J7imqgAGUCvQ
Thread-topic: [PATCH] fix dirty_bit in xenivt.S (was Re: [Xen-ia64-devel] Fail tocreate VTI domain in lates Cset 10143)
>From: Isaku Yamahata
>Sent: 2006年5月24日 11:56
>
>On Wed, May 24, 2006 at 06:10:53AM +0800, You, Yongkang wrote:
>
>> Well, I found a lot of bad address reported from serial port, no matter
>creating VTI or XenU domain.
>> (XEN) vcpu_translate: bad physical address: 0xa00000010000a0a0
>
>Does the attached patch fix it?
>I saw the same message, so I tracked it down.
>However I couldn't reproduce reliably, I don't know this patch solves it.
>If you know the way to reproduce, could you tell us?
>
>--

Hi, Isaku,
        I'm interesting why your patch can fix potential issue here. Ideally 
XEN_HYPER_ITC_D is only the fast path which should have the same 
effect as GP fault caused by itc.d. If your patch really helps, that means 
the two paths (slow/fast) are incompatible which need to be solved, right?

Thanks,
Kevin

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

<Prev in Thread] Current Thread [Next in Thread>