All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: big strong <fangtuo90@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: how to locate the hypercall address in memory?
Date: Tue, 14 Jul 2015 14:38:34 +0100	[thread overview]
Message-ID: <55A52CFA0200007800090BD2@mail.emea.novell.com> (raw)
In-Reply-To: <CAFnE1f1mhjmw=n2sJyL5T1gekpWaKucy4kC1CbSNMFEhANJ45A@mail.gmail.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
>>
>>

  reply	other threads:[~2015-07-14 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2015-07-14 14:02           ` Ian Campbell
2015-07-14 14:30             ` big strong
2015-07-14 14:30           ` big strong

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=55A52CFA0200007800090BD2@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=fangtuo90@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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 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.