[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Determining the CPU at which interrupts arrive in the VMM bypass case

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Devdutt Patnaik" <xendevid@xxxxxxxxx>
  • Date: Mon, 30 Jun 2008 01:33:14 -0400
  • Delivery-date: Sun, 29 Jun 2008 22:33:37 -0700
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


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 ?

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.