All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Backes <john.backes@adventiumlabs.org>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir.xen@gmail.com>
Subject: Re: Help With Custom Hyper Calls
Date: Mon, 15 Aug 2011 09:45:06 -0500	[thread overview]
Message-ID: <4E4930F2.3050903@adventiumlabs.org> (raw)
In-Reply-To: <CA6B1B19.1F29F%keir.xen@gmail.com>

So I greped through the s

I've altered the hypercall_table and hypercall_args_table to have an
additional entry in xen/arch/x86/x86_32/entry.S and in
xen/arch/x86/x86_64/entry.S:

to the hypercall_table:

...........................
         .long do_sysctl             /* 35 */
         .long do_domctl
         .long do_kexec_op
         .long do_tmem_op
         .long do_new_hyper          /* 39 */
...........................

to the hypercall_args_table:

...........................
         .byte 1 /* do_sysctl            */  /* 35 */
         .byte 1 /* do_domctl            */
         .byte 2 /* do_kexec_op          */
         .byte 1 /* do_tmem_op           */
         .byte 0 /* do_new_hyper         */  /* 39 */
...........................


I've also registered the name in xen/include/public/xen.h

...........................
#define __HYPERVISOR_new_hyper            39
...........................

and I've added the following function to xen/arch/x86/mm.c

...........................
void do_new_hyper ( void )
{
      printk("NEW HYPERCALL RECEIVED\n");
}
...........................

To test this, I am running a fedora 14 dom0 and I wrote the following
kernel module (so the code runs in ring 1):

...........................
#include <linux/init.h>
#include <linux/module.h>
#include <linux/fs.h>

MODULE_LICENSE("GPL");

#define SUCCESS 0

static int hyper_init(void){

  int output;

  printk(KERN_ALERT "Testing Hypercall\n");

  __asm__ ( "movl $39, %%eax;"
            "int $0x82;"
          : "=a" (output)
          );

  return SUCCESS;
}

static void hyper_exit(void){
  printk(KERN_ALERT "Removing Hypercall Module");


}

module_init(hyper_init);
module_exit(hyper_exit);
...........................

I then run "xm dmesg" to see if I can see the "NEW HYPERCALL RECEIVED"
message, but nothing appears.  Any thoughts?

- John


On 08/12/2011 12:02 PM, Keir Fraser wrote:
> On 12/08/2011 17:19, "John Backes" <john.backes@adventiumlabs.org> wrote:
> 
>> Hello,
>>
>> So I'm new to Xen development and want to play around with Xen
>> Hypercalls, but havn't been able to find a whole lot of documentation
>> related to creating custom Hypercalls.  I've found that to create a
>> custom Hypercall I need to define it with an unused Hypercall number in
>> "xen/include/public/xen.h", but then I am unsure of the next steps
>> (e.g., where to place the function to call with the Hypercall).
>>
>> Can anyone point more towards some documentation or at least towards the
>> correct locations for registering new Hypercalls?  Thanks in advance.
> 
> Pick the name of a hypercall, e.g., update_va_mapping has a nice distinctive
> name. Recursive grep for that name in the Xen and Linux source trees. Should
> give you a pretty good start on the few places you need to register in the
> hypervisor and in the guest kernel.
> 
>  -- Keir
> 
>> - John
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 
> 

  reply	other threads:[~2011-08-15 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 16:19 Help With Custom Hyper Calls John Backes
2011-08-12 17:02 ` Keir Fraser
2011-08-15 14:45   ` John Backes [this message]
2011-08-15 14:56     ` Tim Deegan
2011-08-15 15:00       ` John Backes
2011-08-15 15:10         ` 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=4E4930F2.3050903@adventiumlabs.org \
    --to=john.backes@adventiumlabs.org \
    --cc=keir.xen@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 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.