All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Ofsthun <sofsthun@virtualiron.com>
To: xen-devel@lists.xensource.com
Subject: [RFC] Hypercalls from HVM guests
Date: Thu, 06 Apr 2006 17:10:16 -0400	[thread overview]
Message-ID: <443583B8.3070008@virtualiron.com> (raw)

Hi,

I am currently working on hypercalls from HVM guests.  I started with a set
of Intel patches posted to xen-devel last September.  I currently have code
running for both 32-bit and 64-bit HVM guests running on a 64-bit hypervisor.

I am curious why none of the original patches were accepted, and what I might
need to do to make them acceptable.

Is other work being done in this area that hasn't been submitted?

Should I submit my version of the modified patches as is?

The following list summarizes the changes.

Hypervisor changes:

o Add vmexit handling for the VMCALL instruction.  This includes adjustments
   to hypercall arguments due to 32-bit vs. 64-bit calling conventions.

o Modify copy_to_user/copy_from_user to use hvm_copy for HVM guests.

o Modify grant table setup to properly map the grant table shared data for
   hvm guests.

o Provide alternate headers for compiling 32-bit HVM guest code to interface
   with a 64-bit hypervisor.  Many of the hypervisor structures used for
   hypercalls vary between 32-bit and 64-bit guests.

Dom 0 changes:

o Modify HVM building to properly map in a xen start info page and the shared
   info page for event channel notifications.

o Add a virtual PCI device to QEMU to facilitate event channel handling.

Dom U (HVM) driver changes:

o Modify grant table setup for HVM guest code.

o Modify event channel handling to interface with an unmodified Linux kernel
   running as an HVM guest.

o Make misc xen support available as a loadable module.

Steve
-- 
Steve Ofsthun - Virtual Iron Software, Inc.

             reply	other threads:[~2006-04-06 21:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 21:10 Steve Ofsthun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-07  2:32 [RFC] Hypercalls from HVM guests Yu, Ke
2006-04-07  8:47 Petersson, Mats
2006-04-07 17:06 ` Steve Ofsthun
2006-04-07 17:24 Petersson, Mats
2006-04-07 17:40 ` Keir Fraser
2006-04-07 17:56 Petersson, Mats
2006-04-07 19:30 ` Steve Ofsthun
2006-04-07 20:22   ` Anthony Liguori
2006-04-08  7:31   ` Keir Fraser
2006-04-08 14:12     ` Andi Kleen
2006-04-08 15:05       ` Keir Fraser
2006-04-08 23:33 Nakajima, Jun
2006-04-09  7:56 ` Keir Fraser
2006-04-09 13:56 Nakajima, Jun
2006-04-09 14:09 ` Keir Fraser
2006-04-12 15:58 ` Stephen C. Tweedie
2006-04-09 15:08 Nakajima, Jun

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=443583B8.3070008@virtualiron.com \
    --to=sofsthun@virtualiron.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.