* How to recognize which guest issues the hypercall?
@ 2015-11-25 7:18 Big Strong
2015-11-25 10:44 ` George Dunlap
0 siblings, 1 reply; 4+ messages in thread
From: Big Strong @ 2015-11-25 7:18 UTC (permalink / raw)
To: xen-users, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 173 bytes --]
I write a program to intercept all hypercalls happend on a xen hypervisor.
How can I know which domain called the hypercall? Is it possible to obtain
it from the registers?
[-- Attachment #1.2: Type: text/html, Size: 420 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to recognize which guest issues the hypercall?
2015-11-25 7:18 How to recognize which guest issues the hypercall? Big Strong
@ 2015-11-25 10:44 ` George Dunlap
2015-11-25 13:23 ` Big Strong
0 siblings, 1 reply; 4+ messages in thread
From: George Dunlap @ 2015-11-25 10:44 UTC (permalink / raw)
To: Big Strong; +Cc: xen-devel
On Wed, Nov 25, 2015 at 7:18 AM, Big Strong <fangtuo90@gmail.com> wrote:
> I write a program to intercept all hypercalls happend on a xen hypervisor.
> How can I know which domain called the hypercall? Is it possible to obtain
> it from the registers?
Why are you cross-posting this to both xen-users and xen-devel? This
is obviously a development question.
At any given time, "current" will point to the vcpu struct of the
currently-running vcpu; current->domain will point to the domain
struct. That should get you started.
-George
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to recognize which guest issues the hypercall?
2015-11-25 10:44 ` George Dunlap
@ 2015-11-25 13:23 ` Big Strong
2015-11-25 14:05 ` George Dunlap
0 siblings, 1 reply; 4+ messages in thread
From: Big Strong @ 2015-11-25 13:23 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 771 bytes --]
Thanks for your replying and sorry for the behavior. Can I get that using
libxc? Because I can't access the structure directly from dom0.
2015-11-25 18:44 GMT+08:00 George Dunlap <dunlapg@umich.edu>:
> On Wed, Nov 25, 2015 at 7:18 AM, Big Strong <fangtuo90@gmail.com> wrote:
> > I write a program to intercept all hypercalls happend on a xen
> hypervisor.
> > How can I know which domain called the hypercall? Is it possible to
> obtain
> > it from the registers?
>
> Why are you cross-posting this to both xen-users and xen-devel? This
> is obviously a development question.
>
> At any given time, "current" will point to the vcpu struct of the
> currently-running vcpu; current->domain will point to the domain
> struct. That should get you started.
>
> -George
>
[-- Attachment #1.2: Type: text/html, Size: 1280 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to recognize which guest issues the hypercall?
2015-11-25 13:23 ` Big Strong
@ 2015-11-25 14:05 ` George Dunlap
0 siblings, 0 replies; 4+ messages in thread
From: George Dunlap @ 2015-11-25 14:05 UTC (permalink / raw)
To: Big Strong; +Cc: xen-devel
On Wed, Nov 25, 2015 at 1:23 PM, Big Strong <fangtuo90@gmail.com> wrote:
> Thanks for your replying and sorry for the behavior. Can I get that using
> libxc? Because I can't access the structure directly from dom0.
Also, please don't top-post. :-)
Hypercalls are made from the guest to the hypervisor; it's in the
hypervisor that "current" is available.
-George
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-11-25 14:05 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-11-25 7:18 How to recognize which guest issues the hypercall? Big Strong
2015-11-25 10:44 ` George Dunlap
2015-11-25 13:23 ` Big Strong
2015-11-25 14:05 ` George Dunlap
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.