From: "Jan Beulich" Subject: Re: [PATCH] linux: prevent non-Xen modulesfromloading in Xen kernel Date: Fri, 18 Jan 2008 16:15:01 +0000 Message-ID: <4790DE95.76E4.0078.0@novell.com> References: <4790D851.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Zachary Amsden , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> Keir Fraser 18.01.08 17:07 >>> >I disagree. The xen interface version number is simply to allow downgradin= g >of the API exposed by the Xen public headers. And it *is* specifically = the >source API; *not* the ABI. Xen's ABIs are always backward compatible (old >guest driver; new Xen will always work), and for forward compatibility = (new >guest driver; old Xen) we expect the guest driver to gracefully degrade = its >functionality. Yeah, it really wasn't meant to cover that (which I know has been stable enough during a reasonably long time now), but rather to have a little = less coarse separation than with just "Xen ", but >This is orthogonal to what you are trying to achieve. So, can we just add >"Xen " to the magic string? ... sure we can. Jan