From: Ritu kaur <ritu.kaur.us@gmail.com>
To: xen-devel@lists.xensource.com
Subject: pci-passthrough and shared interrupts
Date: Wed, 25 Aug 2010 15:17:29 -0700 [thread overview]
Message-ID: <AANLkTin8j7gFkt3x_+QFrJJ+iaP7dk2q6RH5Sm8aoa1Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 552 bytes --]
Hello,
Couple of months back when we were testing xcp 0.1.1 and pci passthrough we
ran into issues when pci-passthrough enabled device shared interrupts with
another controller(in our case interrupt was shared between ide controller
and our nic). At that time Ian Campbell suggested backporting event-channel
changes from pvops to 2.6.27 kernel. Have two questions related to this
1. I am thinking of porting the changes now but wanted to check if it has
been addressed?
2. Will shared interrupts be a problem for pci-e slots as well?
Thanks
-Ritu
[-- Attachment #1.2: Type: text/html, Size: 590 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-08-25 22:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 22:17 Ritu kaur [this message]
2010-08-25 22:34 ` pci-passthrough and shared interrupts Konrad Rzeszutek Wilk
2010-08-25 22:48 ` Ritu kaur
2010-08-25 23:43 ` Konrad Rzeszutek Wilk
2010-08-26 22:58 ` Ritu kaur
2010-08-27 14:03 ` Konrad Rzeszutek Wilk
2010-09-30 2:14 ` Ritu kaur
2010-09-30 6:01 ` Pasi Kärkkäinen
2010-09-30 19:07 ` Ritu kaur
2010-10-01 13:45 ` Konrad Rzeszutek Wilk
2010-10-01 15:36 ` Ritu kaur
2010-10-01 15:58 ` Konrad Rzeszutek Wilk
2010-10-03 16:07 ` Ritu kaur
2010-10-03 16:41 ` Ritu kaur
2010-10-03 16:54 ` Pasi Kärkkäinen
2010-10-03 17:12 ` Ritu kaur
2010-10-03 17:18 ` Pasi Kärkkäinen
2010-10-03 16:42 ` Ritu kaur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTin8j7gFkt3x_+QFrJJ+iaP7dk2q6RH5Sm8aoa1Q@mail.gmail.com \
--to=ritu.kaur.us@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).