Replay Interrupts

Replay Interrupts

[Jingwei Tan]

[-- Attachment #1.1: Type: text/plain, Size: 1355 bytes --]

Hey guys,

What do I want to achieve...
I have 3 identical DomU. Typically only the active DomU will receive
interrupts from my device (keyboard and mouse). Because all DomU are
identical, I might not want to repeat my keyboard and mouse action 3 times.
Thus, I want to modify my Xen such that all my DomU will receive the same
interrupt when I just do it on one of them.
There isn't seems to be any tools that can do that, thus, I know I will have
to change the source and build my own version of Xen.

What I understand from the source code of Xen regarding Interrupt is... ...
When there's an interrupt, do_IRQ_guest() (from /arch/x86/irq.c) will be
called... And the interrupt will be sent by calling sent_guest_pirq() (from
/common/event_channel.c) that will creates an event channel and sets the
pending flag of this event channel by calling evtchn_set_pending() (from
/common/event_channel.c). Finally, Xen will notify the domain regarding the
interrupt.

My question is...
1. How Xen determine which domainU is the one who should be receiving the
interrupt?
2. Is it possible to make all my domainU to be the receipent of the
interrupt?

Am I on the right track?
I need not definite answer. Tips and hints are welcome too!

I've not made any progress regarding this for weeks.
Help needed urgently and is definitely appreciated!

-- 
Regards,
Tan

[-- Attachment #1.2: Type: text/html, Size: 1461 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Replay Interrupts

[Emil Tan]

Hey guys, 

I'm still stuck with the same old situation. 
I'm playing with the source of Xen 3.3.1. My situation is -- I have 3
identical HVM (Windows), I want to the other two HVM to receive the same
interrupt when I'm controlling one of them. The purpose of this is that I'm
doing a research about keyloggers. 

I'm still a beginner in playing with Open Source application, and
programming. 
I really need help over here. It would be a bonus if developer from
XenSource can have a little help over here. 

After some read-up about how Xen handles interrupt calls, I think I should
be playing around with do_IRQ() and __do_IRQ_guest() of xen/arch/x86/irq.c?

Help needed urgently. Thanks in advance!



Emil Tan wrote:
> 
> Hey guys,
> 
> What do I want to achieve...
> I have 3 identical DomU. Typically only the active DomU will receive
> interrupts from my device (keyboard and mouse). Because all DomU are
> identical, I might not want to repeat my keyboard and mouse action 3
> times.
> Thus, I want to modify my Xen such that all my DomU will receive the same
> interrupt when I just do it on one of them.
> There isn't seems to be any tools that can do that, thus, I know I will
> have
> to change the source and build my own version of Xen.
> 
> What I understand from the source code of Xen regarding Interrupt is...
> ...
> When there's an interrupt, do_IRQ_guest() (from /arch/x86/irq.c) will be
> called... And the interrupt will be sent by calling sent_guest_pirq()
> (from
> /common/event_channel.c) that will creates an event channel and sets the
> pending flag of this event channel by calling evtchn_set_pending() (from
> /common/event_channel.c). Finally, Xen will notify the domain regarding
> the
> interrupt.
> 
> My question is...
> 1. How Xen determine which domainU is the one who should be receiving the
> interrupt?
> 2. Is it possible to make all my domainU to be the receipent of the
> interrupt?
> 
> Am I on the right track?
> I need not definite answer. Tips and hints are welcome too!
> 
> I've not made any progress regarding this for weeks.
> Help needed urgently and is definitely appreciated!
> 
> -- 
> Regards,
> Tan
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/Replay-Interrupts-tp23514592p23825595.html
Sent from the Xen - Dev mailing list archive at Nabble.com.