WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] xen: make (set|get)_xen_guest_handle available

To: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen: make (set|get)_xen_guest_handle available
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Thu, 30 Jul 2009 05:41:33 -0700 (PDT)
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 30 Jul 2009 05:42:14 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1248957693; bh=CbalTF2g2lkxE6lLCTNDD5h/cVVSMUXLHj+073ah+B0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=5bu+HAI+hFdVH4BIQtNv2zZAUnvacpnLhRBXmQZDzX2eG2zmNoebuDehuZagHHcidxzLfzqL0UtTDRuL6Bg0w8No/ce7qEly4a+7qIAVGbBVFp5iFdcewKCBH3VApa7j4wWTB0+ezkEDkD7FcOOEHFapbVffAEzYnUlq6pVlrls=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=0yQwpWtTBE5Jj9Tzooh7zMi2GBTpHK/El9kU8nt2ia2f2ZyX/xWmXCsRkqcLNVpvswWz0qnrQd9RLqfidZFtWEOxZEMr8wyUb3FFqeZrHeHgaEAwc9DRGfFvI5Iu/91NcWEBy+0SCo9z7bAV3tP4ekvU/ObTjuSI+g/d9YEqYPY=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200907301355.33820.Christoph.Egger@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Christoph,

> NetBSD 5.0 got Xen 3.x support (both 32bit and 64bit), kept Xen 2 support

Sounds a bit strange for me. Like only 3.X  Xen Hypervisor could be connected via hypercalls from NetBSD 5.0 DomU xenified kernel.
( For instance Solaris Nevada until build 84(5)  ( or so)  required patch to work with Xen 3.2 and higher Linux Dom0 )

Would NetBSD 5.0 understand Xen 3.4.1 Dom0 on top
of Ubuntu 9.04 or F11 (64-bit environment) ?

Thanks.
Boris.

--- On Thu, 7/30/09, Christoph Egger <Christoph.Egger@xxxxxxx> wrote:

From: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen: make (set|get)_xen_guest_handle available
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Date: Thursday, July 30, 2009, 7:55 AM


Hi Boris,

this is the history:

NetBSD 2.0 got Xen 1.2 support (both Dom0 and DomU)
NetBSD 3.0 got Xen 2 support, dropped Xen 1.2 support (both Dom0 and DomU)
NetBSD 4.0 got Xen 3.0/3.1 support 32bit only, kept Xen 2 support (both Dom0
and DomU)
NetBSD 5.0 got Xen 3.x support (both 32bit and 64bit), kept Xen 2 support
(both Dom0 and DomU)
NetBSD-current dropped Xen 2 support, about to move to new interface.

Christoph

On Thursday 30 July 2009 13:16:00 Boris Derzhavets wrote:
> May the recent version of NetBSD run as PV guest ?
> Sorry, for stupid question.
> Boris.
>
> --- On Thu, 7/30/09, Christoph Egger <Christoph.Egger@xxxxxxx> wrote:
>
> From: Christoph Egger <Christoph.Egger@xxxxxxx>
> Subject: Re: [Xen-devel] [PATCH] xen: make (set|get)_xen_guest_handle
> available To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
> Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Date: Thursday, July 30, 2009, 6:34 AM
>
> On Thursday 30 July 2009 12:14:04 Keir Fraser wrote:
> > On 30/07/2009 10:12, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:
> > > Make (set|get)_xen_guest_handle() always available.
> > > This avoids code snippets in the guest like this:
> > >
> > > #if __XEN_ITNERFACE_VERSION__ >= 0x00030201
> > > set_xen_guest_handle(hnd, val);
> > > #else
> > > hnd = val;
> > > #endif
> >
> > Actually I don't see why you'd have code like this. *You*, the guest,
> > gets to specify __XEN_INTERFACE_VERSION__ -- that is the point of it --
> > so ifdef'ing based on it in the guest is stupid.
> >
> > Just specify __XEN_INTERFACE_VERSION__ to be recent enough to have the
> > guest handles, and then remove your ifdefs. Simple.
>
> The point is to keep backward compatibility. The patch makes Xen more
> friendly with using the old non-structured guest handler if the user wants.
>
> NetBSD offers both way to build & run it with either using the old or new
> interface. This allows a smooth migration.
>
> Christoph



--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632


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

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