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] GSI affinity and redirection

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] GSI affinity and redirection
From: "Ashish Bijlani" <ashish.bijlani@xxxxxxxxx>
Date: Tue, 30 Oct 2007 09:48:13 -0400
Delivery-date: Tue, 30 Oct 2007 06:48:56 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=qFoSDhXphafMbSHHFpSoNH5hWSmGbB4sTQ6fFhbQzNA=; b=Y2ZFw5pR+0dOnHL9sdztbCwpAungPHFXSMi+uUb4YWqfb7H2Xl3VWfPwCyVLy0vd3jbCdY+AYM8ivfXOOY3V9KqKgkEWDauq/JbkRSybeqxGV6JBcQqhia057z4ocXkAXYYbMxC0+OtJwMW9w5u3/oRHvCsP3uITv990h/YCXPU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=f+2TS2B8ny1fuOc92V4a7eqoya5TOhN325xPK8OVcTVZAtNDGiN+jOJM0z2hIc/qoFS5tNWMaXjy32SChfAqIirMG5Io9nakoKt5QuIFfalSdLGaEvmwcnyUa+KHDopJEzVILSvwUxFawV/9aUBzKb0BKR8eC6GMe657sXaGYm8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
folks...i've been trying to set affinity of PCI NIC GSI (irq=16) for core 1 (dual-core machine) and then upon receiving this interrupt on core 1, redirect it to core 0 (through IPI) to handle it. i'm able to set the affinity by invoking "set_affinity" operation on irq 16 but when I try to redirect it to core 0 through IPI, upon receiving this interrupt, the interrupt is somehow not handled and i'm not able to ping to this machine. i think i'm not doing something that needs to be done after sending IPI to core 0 to handle this interrupt, which is done from core 1 upon receiving this interrupt on it. as far as my understanding goes, when IPI is sent, the interrupt is delivered to a processor through local PIC, right? so does that mean that the processor that originally received the interrupt by IOAPIC should send EOI to IOAPIC and the processor that received the redirected interrupt by local PIC should send EOI to the local PIC and not IOAPIC. if that is the case, then in what order or sequence he two EOIs are sent? considering xen waits for virtual EOIs from guests before it can send actual EOI to the IOAPIC, which core should wait for EOIs from the guests in my case? thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] GSI affinity and redirection, Ashish Bijlani <=