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

[Xen-merge] General xen question on send_IPI_self

To: xen-merge <xen-merge@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-merge] General xen question on send_IPI_self
From: "Martin J. Bligh" <mbligh@xxxxxxxxxx>
Date: Sun, 07 Aug 2005 14:35:22 -0700
Delivery-date: Sun, 07 Aug 2005 21:33:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-merge-request@lists.xensource.com?subject=help>
List-id: xen-merge <xen-merge.lists.xensource.com>
List-post: <mailto:xen-merge@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=unsubscribe>
Reply-to: "Martin J. Bligh" <mbligh@xxxxxxxxxx>
Sender: xen-merge-bounces@xxxxxxxxxxxxxxxxxxx
This looks dangerous to me, instintively, though I don't know what
you're doing in this space, or why. How can you get away with a no-op
for send_IPI_self?

#ifndef CONFIG_SMP
void fastcall send_IPI_self(int vector)
{
#ifndef CONFIG_XEN
        unsigned int cfg;

        /*
         * Wait for idle.
         */
        apic_wait_icr_idle();
        cfg = APIC_DM_FIXED | APIC_DEST_SELF | vector | APIC_DEST_LOGICAL;
        /*
         * Send the IPI. The write to APIC_ICR fires this off.
         */
        apic_write_around(APIC_ICR, cfg);
#endif
}
#endif /* !CONFIG_SMP */


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

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