All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Smith <sos22-xen@srcf.ucam.org>
To: xen-devel@lists.xensource.com
Cc: sos22@srcf.ucam.org
Subject: Re: Paravirtualised drivers for fully virtualised domains
Date: Wed, 26 Jul 2006 16:34:52 +0100	[thread overview]
Message-ID: <20060726153452.GA6211@cam.ac.uk> (raw)
In-Reply-To: <20060718125106.GA4727@cam.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1263 bytes --]

I've just put an updated version of these patches up at
http://www.cl.cam.ac.uk/~sos22/pv-on-hvm/rev2 .  There's also an
equivalent single big patch at
http://www.cl.cam.ac.uk/~sos22/pv-on-hvm/rev2.combined .  Thank you to
everyone who gave feedback on the previous version.

The main changes since last time are:

-- Support for SMP guests
-- Support for 64 bit guests on a 64 bit hypervisor
-- Partial support for 32 bit guests on a 64 bit hypervisor: the network
   interface works, but the block device doesn't.

The block device can be made to work by #define'ing ALIEN_INTERFACES
in blkif.h, but drivers compiled in that way won't work with 32 on 32.
The problem here is that blkif_request_t contains extra padding in 64
bit builds, and so is a different size, and so the block ring layout
is different.

Other structures with similar problems are handled either by run time
tests in the drivers (shared_info_t) or translation wrappers in the
hypervisor (xen_feature_info_t, xen_add_to_physmap_t), but trying to
do this for the block rings would require far more painful and
extensive surgery.  I'm inclined to stick with multiply compiling the
frontend drivers in the short term, although it'll obviously need
doing in a slightly less grotty way.

Steven.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2006-07-26 15:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 12:51 Paravirtualised drivers for fully virtualised domains Steven Smith
2006-07-18 13:45 ` Ben Thomas
2006-07-18 16:00 ` Steve Ofsthun
2006-07-18 16:23   ` Mark Williamson
2006-07-18 20:34   ` Steven Smith
2006-07-18 23:24     ` Steve Ofsthun
2006-07-19  6:50       ` Gerd Hoffmann
2006-07-26 15:34 ` Steven Smith [this message]
2006-08-08  9:42   ` Steven Smith
2006-08-09 18:05     ` Steve Dobbelstein
2006-08-10 11:08     ` Paravirtualised drivers for fully virtualised domains, rev9 Steven Smith
2006-08-10 21:48       ` Steve Dobbelstein
2006-08-11 10:17         ` Steven Smith
2006-08-11 10:31           ` Harry Butterworth
2006-08-14  9:12             ` Steven Smith
2006-08-11 17:04           ` Steve Dobbelstein
2006-08-12  8:32             ` Steven Smith
2006-08-14 21:22               ` Steve Dobbelstein
2006-08-15  7:27                 ` Steven Smith
2006-08-15 22:05                   ` Steve Dobbelstein
2006-08-16 13:36         ` Steven Smith
2006-08-16 13:33       ` Paravirtualised drivers for fully virtualised domains, rev11 sos22-xen
  -- strict thread matches above, loose matches on Subject: below --
2006-07-19  4:14 Paravirtualised drivers for fully virtualised domains Ian Pratt
2006-07-26 22:35 Nakajima, Jun
2006-08-02  8:01 He, Qing
2006-08-02  9:30 ` Steven Smith
2006-08-02  8:23 Zhao, Yunfeng
2006-08-02  8:56 ` Steven Hand
2006-08-02  9:37   ` Steven Smith
2006-08-02  9:49 He, Qing
2006-08-02 10:35 He, Qing
2006-08-03  6:59 ` Himanshu Raj
2006-08-03  9:35   ` Steven Smith
2006-08-04  6:13     ` Himanshu Raj

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=20060726153452.GA6211@cam.ac.uk \
    --to=sos22-xen@srcf.ucam.org \
    --cc=sos22@srcf.ucam.org \
    --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.