From: veerasena reddy <veeruyours@gmail.com>
To: xen-devel@lists.xensource.com
Subject: how to route interrupts directly to HVM guest from hypervisor
Date: Sun, 5 Jun 2011 19:05:53 +0530 [thread overview]
Message-ID: <BANLkTi=JZX1+vJvoDegpxi2tBj1ZY+dFJA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 379 bytes --]
Hi,
I want to customize my XEN-4.0 hypervisor to directly pass interrupts from
an IO device to HVM guest driver directly without involving dom0. Means,
when the hypervisor receives real interrupts from IO device and then i want
to send virtual interrupt to HVM guest without involving dom0.
Could you please advice where can i start for this?
Thanks in advance.
Regards,
VSR.
[-- Attachment #1.2: Type: text/html, Size: 410 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:[~2011-06-05 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 13:35 veerasena reddy [this message]
2011-06-06 8:47 ` how to route interrupts directly to HVM guest from hypervisor Tim Deegan
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='BANLkTi=JZX1+vJvoDegpxi2tBj1ZY+dFJA@mail.gmail.com' \
--to=veeruyours@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).