All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ky Srinivasan" <ksrinivasan@novell.com>
To: Ian Campbell <Ian.Campbell@XenSource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: PV drivers for HVM guests
Date: Thu, 05 Oct 2006 10:47:28 -0600	[thread overview]
Message-ID: <4524FEB2.E57C.0030.0@novell.com> (raw)
In-Reply-To: <1160061687.3755.101.camel@localhost.localdomain>

Thanks Ian. I am currently testing my implementation on sles9. I will certainly look at how I can leverage your work.

Regards,

K. Y

>>> On Thu, Oct 5, 2006 at 11:21 AM, in message
<1160061687.3755.101.camel@localhost.localdomain>, Ian Campbell
<Ian.Campbell@XenSource.com> wrote: 
> On Tue, 2006- 10- 03 at 16:31 - 0400, Ky Srinivasan wrote:
>> 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 
> 
> FWIW I have a half complete implementation (compile tested only) of such
> a scheme which I've attached, perhaps you can crib something useful from
> it ;- ).
> 
> Basically it adds a compat- include directory to the end of the include
> search path which contains compatibility versions of headers which may
> not present in older kernels and adds compat.h which defines other
> missing bits where necessary.
> 
> It covers most of the issues compiling against a RHEL4 (2.6.9) or SLES9
> (2.6.5) kernel, although compatibility shims for
> schedule_timeout_interruptible() and nonseekable_open() are still
> missing and the versions used for triggering compatibility code are
> certainly totally wrong (just right for RHEL4 and SLES9 though ;- )).
> 
> I'm fairly unhappy about the number of ifdef's in xenbus_probe.c. I
> reckon some function reordering could coalesce a lot of them. Perhaps
> they are candidates for splitting into a separate file.
> 
> This work will also be useful for the fully PV vendor kernel ports which
> is why I'm interested.
> 
> Ian.

  reply	other threads:[~2006-10-05 16:47 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
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 [this message]
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=4524FEB2.E57C.0030.0@novell.com \
    --to=ksrinivasan@novell.com \
    --cc=Ian.Campbell@XenSource.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.