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] Determining the CPU at which interrupts arrive in the VMM by

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Determining the CPU at which interrupts arrive in the VMM bypass case
From: "Devdutt Patnaik" <xendevid@xxxxxxxxx>
Date: Mon, 30 Jun 2008 01:33:14 -0400
Delivery-date: Sun, 29 Jun 2008 22:33:37 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=ecWOsCY+w/sFsTHTEsfZnHYKWi+2ZJoDcEk4jlWcvWM=; b=j5ylbDkfLEN10JY/aIzkS0vVNb1XK5QsWdoykUd6/P/movjU08yMNZq4d+8m2wAlZt vnxp6acSTBAiB+TOKa7245vMHdLfGqfzI9oMNuR/U27uZDQCTPJJ5UhrHTg1xzRuzMoW J4GOgkmKzqIC+z8isfzkNYOeOJL2HEBvo+q5Q=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=RQfUUQocacm69n1JDIDIy+UP5WqzCnG7sa2FrtnhpCis1lJd+wjBqZ0UzZueHWetNN nqh1JnctNUEVdZoZXZbOLYz17GZekhibfRusbJrf5ctpLyvqgo3S0SbJW9uv+7aKS7aX ImOBecX5k2B4mffHmRl8wqYtVq/Afg49dPQ4s=
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I have set up a VM to bypass Dom0 and talk directly to my second NIC card.
When I view /proc/interrupts on the guest VM is see a single CPU ie. CPU0 as I have given it 1 VCPU.
It shows IRQ16 being serviced on that CPU.

However, this does not indicate which physical CPU the interrupts are actually arriving at.
On Dom0 /proc/interrupts does not show eth1 which is expected as the device is hidden from Dom0.
I have an 8 core server.

Any pointers on how I can determine the CPU or core # where the interrupts for eth1 arrive ?

Thanks,
Devdutt.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Determining the CPU at which interrupts arrive in the VMM bypass case, Devdutt Patnaik <=