All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew D. Ball" <aball@us.ibm.com>
To: Ky Srinivasan <ksrinivasan@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: PV drivers for HVM guests
Date: Tue, 03 Oct 2006 18:19:55 -0400	[thread overview]
Message-ID: <1159913996.27206.37.camel@localhost> (raw)
In-Reply-To: <45229025.E57C.0030.0@novell.com>

Interesting!  Ideally, there would be better performance in the base HVM
device model.  I think I know of some people that are working hard on
that.

I'm curious to see what you've done for (1) and (2).

Peace.
Andrew

On Tue, 2006-10-03 at 16:31 -0400, Ky Srinivasan wrote:
> I am trying to build PV drivers for SLES9 HVM guests. SLES 9 is based on the 2.6.5 kernel. Since the PV driver code is really designed for the latest kernel release, I have had many issues/problems in building the PV drivers for older Linux OS targets - I have only been looking at the issues with 2.6.5 kernel base and I suspect the problem will be even worse if one were to look at older Linux kernels. This is unfortunate since PV drivers are so critical for HVM guests and there is considerable interest in supporting legacy Linux environments as HVM guests. The problems I have had to deal with can be broadly classified into:
> 
> a) Compiler related issues
> b) Missing functionality in the legacy kernel - this includes features as well as changed data structures
> c) Implementation differences of a given feature
> 
> These differences can be dealt with in a couple of different ways:
> 1) Modify the code in the PV drivers under appropriate compilation switches to deal with the differences in the base kernels.
> 2)  Introduce  a compatibility component that bridges the gap between the current PV code and a given Linux target and leave much of the PV driver  code untouched.
> 
> I have implemented both these schemes for the sles9 kernel and would like to get your input on your preference. I personally like option 2. Going forward, the evolution of PV drivers needs to be constrained by the required support for legacy Linux environments. 
> 
> Regards,
> 
> K. Y. Srinivasan 
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2006-10-03 22:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 20:31 PV drivers for HVM guests Ky Srinivasan
2006-10-03 22:19 ` Andrew D. Ball [this message]
2006-10-03 22:31 ` Steve Ofsthun
2006-10-04  7:56 ` Keir Fraser
2006-10-04  8:15   ` Muli Ben-Yehuda
2006-10-04  8:17     ` Keir Fraser
2006-10-04 11:02     ` Gerd Hoffmann
2006-10-04 15:54       ` Andi Kleen
2006-10-04 10:24 ` Steven Smith
2006-10-05 15:21 ` Ian Campbell
2006-10-05 16:47   ` Ky Srinivasan
2006-10-10  8:00   ` DOI Tsunehisa
2006-10-11 10:46     ` DOI Tsunehisa
2006-10-13  2:00       ` DOI Tsunehisa
2006-10-13  6:55         ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 18:40 Ky Srinivasan
2006-10-04 18:42 Ky Srinivasan
2006-10-05 14:59 ` Andrew D. Ball
2006-10-05 15:13   ` Ky Srinivasan
2006-10-04 18:45 Ky Srinivasan
2006-10-04 18:47 Ky Srinivasan
2006-10-04 18:50 Ky Srinivasan

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=1159913996.27206.37.camel@localhost \
    --to=aball@us.ibm.com \
    --cc=ksrinivasan@novell.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.