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

[Xen-ia64-devel] Re: [PATCH] Re: [Xen-devel] Re: [PATCH 2/2] PV framebuf

To: Markus Armbruster <armbru@xxxxxxxxxx>
Subject: [Xen-ia64-devel] Re: [PATCH] Re: [Xen-devel] Re: [PATCH 2/2] PV framebuffer
From: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Date: Thu, 14 Dec 2006 19:58:13 +0900
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 14 Dec 2006 02:59:35 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: (Your message of "Tue, 12 Dec 2006 13:23:18 +0100") <874ps1cngp.fsf@xxxxxxxxxxxxxxxxx>
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>
References: <87lkmjptqq.fsf@xxxxxxxxxxxxxxxxx> <874psydx6m.fsf@xxxxxxxxxxxxxxxxx> <200611221150.kAMBoeEX021723@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <87r6vv8ugo.fsf@xxxxxxxxxxxxxxxxx> <200611240501.kAO51Ctv001860@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <871wnt6za3.fsf@xxxxxxxxxxxxxxxxx> <200611281305.kASD5LMi024468@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <873b833cc0.fsf@xxxxxxxxxxxxxxxxx> <200612011236.kB1Car3M023008@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <87ac27wl15.fsf@xxxxxxxxxxxxxxxxx> <200612040847.kB48lEpR008524@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <87irgrqwe5.fsf@xxxxxxxxxxxxxxxxx> <200612051202.kB5C2GJI004049@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <874psap7ss.fsf@xxxxxxxxxxxxxxxxx> <200612070056.kB70u7XF027966@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <878xhkm928.fsf@xxxxxxxxxxxxxxxxx> <200612121155.kBCBtOXt000786@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <874ps1cngp.fsf@xxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi, Markus

  About SMP DomU VFB call trace problem.

 I searched the code and found
the code in smp_call_function line337@linux/arch/ia64/kernel/smp.c
   WARN_ON(irqs_disabled());

The call trace problem caused by spin_lock_irqsave()
in xenfb_update_screen@linux/drivers/xen/fbfront/xenfb.c

Why you need to use spin_lock_irqsave in xenfb_update()?
I understand the locking but why irqsave is required at this point?

Thanks
Atsushi SAKAI


>Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx> writes:
>
>> Hi, Markus
>>
>>  I am checking VFB with SMP
>> with xen-ia64-unstable cset 12886.
>>
>> But It seems strange behavior.
>> (call trace appeared from DomU xm console output)
>> Did you test it on SMP DomU? 
>> Of course UP DomU seems fine at this moment.
>>
>> Thanks
>> Atsushi SAKAI
>
>Please provide details, including xm console output.
>







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

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