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-devel

[Xen-devel] Re: nmi cache weirdness???

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: nmi cache weirdness???
From: Mukesh <mukesh.rathor@xxxxxxxxxx>
Date: Fri, 15 Aug 2008 05:45:57 +0000 (UTC)
Delivery-date: Thu, 14 Aug 2008 22:46:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <48A4E7EB.2080509@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Loom/3.14 (http://gmane.org/)
Mukesh Rathor <mukesh.rathor <at> oracle.com> writes:

.......
> However, in do_nmi(), nmi_callback still points to dummy (receiving cpus).
> What'sinteresting is, if I put two print lines back to back with nothing
> in between right at the beginning, then the first prints dummy but the
> second prints kdb_nmi_receive. I'm at a complete loss. Does NMI change
> cache protocol? I've been looking thru Intel/AMD manuals, but nothing....


I should clarify I made nmi_callback volatile before adding prints. 
Moreover, I also put wbinvd() after set_nmi_callback, still same behaviour.

thanks
mukesh



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

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