* how to locate the hypercall address in memory?
@ 2015-07-14 7:10 big strong
2015-07-14 11:56 ` Jan Beulich
0 siblings, 1 reply; 9+ messages in thread
From: big strong @ 2015-07-14 7:10 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 101 bytes --]
As syscalls can be located with the help of symbol files, is it possible to
do it to hypercalls too?
[-- Attachment #1.2: Type: text/html, Size: 122 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] 9+ messages in thread
* Re: how to locate the hypercall address in memory?
2015-07-14 7:10 how to locate the hypercall address in memory? big strong
@ 2015-07-14 11:56 ` Jan Beulich
2015-07-14 11:59 ` big strong
0 siblings, 1 reply; 9+ messages in thread
From: Jan Beulich @ 2015-07-14 11:56 UTC (permalink / raw)
To: big strong; +Cc: xen-devel
>>> On 14.07.15 at 09:10, <fangtuo90@gmail.com> wrote:
> As syscalls can be located with the help of symbol files, is it possible to
> do it to hypercalls too?
Sure.
Jan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: how to locate the hypercall address in memory?
2015-07-14 11:56 ` Jan Beulich
@ 2015-07-14 11:59 ` big strong
2015-07-14 12:36 ` Jan Beulich
0 siblings, 1 reply; 9+ messages in thread
From: big strong @ 2015-07-14 11:59 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 492 bytes --]
could you explain that in detail? As syscall tracing, we usually locate the
kernel module first, then find the address of specific syscall function in
that module with the help of symbol files. How could this be applied to
hypercalls then?
2015-07-14 19:56 GMT+08:00 Jan Beulich <JBeulich@suse.com>:
> >>> On 14.07.15 at 09:10, <fangtuo90@gmail.com> wrote:
> > As syscalls can be located with the help of symbol files, is it possible
> to
> > do it to hypercalls too?
>
> Sure.
>
> Jan
>
>
[-- Attachment #1.2: Type: text/html, Size: 948 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] 9+ messages in thread
* Re: how to locate the hypercall address in memory?
2015-07-14 11:59 ` big strong
@ 2015-07-14 12:36 ` Jan Beulich
2015-07-14 13:31 ` big strong
0 siblings, 1 reply; 9+ messages in thread
From: Jan Beulich @ 2015-07-14 12:36 UTC (permalink / raw)
To: big strong; +Cc: xen-devel
>>> On 14.07.15 at 13:59, <fangtuo90@gmail.com> wrote:
> could you explain that in detail? As syscall tracing, we usually locate the
> kernel module first, then find the address of specific syscall function in
> that module with the help of symbol files. How could this be applied to
> hypercalls then?
You'd do whatever you do with the kernel binary with the hypervisor
one instead (plus you don't even need to care about modules there).
Jan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: how to locate the hypercall address in memory?
2015-07-14 12:36 ` Jan Beulich
@ 2015-07-14 13:31 ` big strong
2015-07-14 13:38 ` Jan Beulich
0 siblings, 1 reply; 9+ messages in thread
From: big strong @ 2015-07-14 13:31 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 644 bytes --]
All right, what is the base address of hypercalls table? And which file
contains the offset of each hypercall?
2015-07-14 20:36 GMT+08:00 Jan Beulich <JBeulich@suse.com>:
> >>> On 14.07.15 at 13:59, <fangtuo90@gmail.com> wrote:
> > could you explain that in detail? As syscall tracing, we usually locate
> the
> > kernel module first, then find the address of specific syscall function
> in
> > that module with the help of symbol files. How could this be applied to
> > hypercalls then?
>
> You'd do whatever you do with the kernel binary with the hypervisor
> one instead (plus you don't even need to care about modules there).
>
> Jan
>
>
[-- Attachment #1.2: Type: text/html, Size: 1121 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] 9+ messages in thread
* Re: how to locate the hypercall address in memory?
2015-07-14 13:31 ` big strong
@ 2015-07-14 13:38 ` Jan Beulich
2015-07-14 14:02 ` Ian Campbell
2015-07-14 14:30 ` big strong
0 siblings, 2 replies; 9+ messages in thread
From: Jan Beulich @ 2015-07-14 13:38 UTC (permalink / raw)
To: big strong; +Cc: xen-devel
>>> On 14.07.15 at 15:31, <fangtuo90@gmail.com> wrote:
> All right, what is the base address of hypercalls table? And which file
> contains the offset of each hypercall?
Did you at least _try_ to find the answer yourself, e.g. by
grep-ing the hypervisor source for some obvious strings?
Jan
> 2015-07-14 20:36 GMT+08:00 Jan Beulich <JBeulich@suse.com>:
>
>> >>> On 14.07.15 at 13:59, <fangtuo90@gmail.com> wrote:
>> > could you explain that in detail? As syscall tracing, we usually locate
>> the
>> > kernel module first, then find the address of specific syscall function
>> in
>> > that module with the help of symbol files. How could this be applied to
>> > hypercalls then?
>>
>> You'd do whatever you do with the kernel binary with the hypervisor
>> one instead (plus you don't even need to care about modules there).
>>
>> Jan
>>
>>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: how to locate the hypercall address in memory?
2015-07-14 13:38 ` Jan Beulich
@ 2015-07-14 14:02 ` Ian Campbell
2015-07-14 14:30 ` big strong
2015-07-14 14:30 ` big strong
1 sibling, 1 reply; 9+ messages in thread
From: Ian Campbell @ 2015-07-14 14:02 UTC (permalink / raw)
To: Jan Beulich; +Cc: big strong, xen-devel
On Tue, 2015-07-14 at 14:38 +0100, Jan Beulich wrote:
> >>> On 14.07.15 at 15:31, <fangtuo90@gmail.com> wrote:
> > All right, what is the base address of hypercalls table? And which file
> > contains the offset of each hypercall?
>
> Did you at least _try_ to find the answer yourself, e.g. by
> grep-ing the hypervisor source for some obvious strings?
big strong,
I would recommend that you read
http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions
Ian.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: how to locate the hypercall address in memory?
2015-07-14 13:38 ` Jan Beulich
2015-07-14 14:02 ` Ian Campbell
@ 2015-07-14 14:30 ` big strong
1 sibling, 0 replies; 9+ messages in thread
From: big strong @ 2015-07-14 14:30 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1462 bytes --]
I've read the hypercall related code, such as entry.S hypervisor.h ,etc.
But the problem is that hypercall functions are implemented in different
files while linux package syscalls into glibc and windows ntoskrnl. There
is a hypercall table defined in entry.S. But I havn't found any offsets
related information. Besides, I've learned that hypercall page is mapped to
a fixed address when the guest is initialized, but which address it is and
is this address the base address of hypercall table?
2015-07-14 21:38 GMT+08:00 Jan Beulich <JBeulich@suse.com>:
> >>> On 14.07.15 at 15:31, <fangtuo90@gmail.com> wrote:
> > All right, what is the base address of hypercalls table? And which file
> > contains the offset of each hypercall?
>
> Did you at least _try_ to find the answer yourself, e.g. by
> grep-ing the hypervisor source for some obvious strings?
>
> Jan
>
> > 2015-07-14 20:36 GMT+08:00 Jan Beulich <JBeulich@suse.com>:
> >
> >> >>> On 14.07.15 at 13:59, <fangtuo90@gmail.com> wrote:
> >> > could you explain that in detail? As syscall tracing, we usually
> locate
> >> the
> >> > kernel module first, then find the address of specific syscall
> function
> >> in
> >> > that module with the help of symbol files. How could this be applied
> to
> >> > hypercalls then?
> >>
> >> You'd do whatever you do with the kernel binary with the hypervisor
> >> one instead (plus you don't even need to care about modules there).
> >>
> >> Jan
> >>
> >>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2248 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] 9+ messages in thread
* Re: how to locate the hypercall address in memory?
2015-07-14 14:02 ` Ian Campbell
@ 2015-07-14 14:30 ` big strong
0 siblings, 0 replies; 9+ messages in thread
From: big strong @ 2015-07-14 14:30 UTC (permalink / raw)
To: Ian Campbell; +Cc: Jan Beulich, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 630 bytes --]
http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions The page cannot open
2015-07-14 22:02 GMT+08:00 Ian Campbell <ian.campbell@citrix.com>:
> On Tue, 2015-07-14 at 14:38 +0100, Jan Beulich wrote:
> > >>> On 14.07.15 at 15:31, <fangtuo90@gmail.com> wrote:
> > > All right, what is the base address of hypercalls table? And which file
> > > contains the offset of each hypercall?
> >
> > Did you at least _try_ to find the answer yourself, e.g. by
> > grep-ing the hypervisor source for some obvious strings?
>
> big strong,
>
> I would recommend that you read
> http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions
>
> Ian.
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 1307 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] 9+ messages in thread
end of thread, other threads:[~2015-07-14 14:30 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-14 7:10 how to locate the hypercall address in memory? big strong
2015-07-14 11:56 ` Jan Beulich
2015-07-14 11:59 ` big strong
2015-07-14 12:36 ` Jan Beulich
2015-07-14 13:31 ` big strong
2015-07-14 13:38 ` Jan Beulich
2015-07-14 14:02 ` Ian Campbell
2015-07-14 14:30 ` big strong
2015-07-14 14:30 ` big strong
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.