From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Version Detection Date: Tue, 19 Jun 2007 17:15:38 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0538655037==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Quang Ngo , "Petersson, Mats" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============0538655037== Content-type: multipart/alternative; boundary="B_3265118138_19715379" > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3265118138_19715379 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable On 19/6/07 16:47, "Quang Ngo" wrote: > Thanks for your response. It would be nice if there is some sort of vers= ion > info in the XEN vmlinuz image. Regular vmlinuz has signature at offset 0= x202 > ("HdrS") and kernel info at an offset (specified at 0x20e) + 0x200. > =20 > Also, I wish there is version info in /proc/xen. > =20 > If you find a way to find version info for a XEN vmlinuz image please let= me > know. We could add something quite easily for Xen itself, although bear in mind that both xen-syms and xen.gz are Elf files, so putting info at a fixed offset won=B9t work. We could put the info at a fixed offset into the text segment (e.g., immediately before or after the multiboot header). Doing the same for vmlinux files is a bit tricky. There are lots of Xen repositories maintained independently now, and getting everyone to agree on versioning information would likely be tricky. And soon enough Xen support will be in mainline, and discussions on image format and boot protocol are still in progress there. -- Keir --B_3265118138_19715379 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Re: [Xen-devel] Version Detection On 19= /6/07 16:47, "Quang Ngo" <quang4ngo@hotmail.com> wrote:

Thanks for your response.  It would be nice if the= re is some sort of version info in the XEN vmlinuz image.  Regular vmli= nuz has signature at offset 0x202 ("HdrS") and kernel info at an o= ffset (specified at 0x20e) + 0x200.
 
Also, I wish there is version info in /proc/xen.
 
If you find a way to find version info for a XEN vmlinuz image please let m= e know.

We could add something quite easily for Xen itself, although bear in mind t= hat both xen-syms and xen.gz are Elf files, so putting info at a fixed offse= t won’t work. We could put the info at a fixed offset into the text se= gment (e.g., immediately before or after the multiboot header).

Doing the same for vmlinux files is a bit tricky. There are lots of Xen rep= ositories maintained independently now, and getting everyone to agree on ver= sioning information would likely be tricky. And soon enough Xen support will= be in mainline, and discussions on image format and boot protocol are still= in progress there.

 -- Keir
 --B_3265118138_19715379-- --===============0538655037== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0538655037==--