From: Petr Tesarik <ptesarik@suse.cz>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Proper place for an overview of Xen virtual space
Date: Fri, 27 Jul 2012 07:41:47 +0200 [thread overview]
Message-ID: <201207270741.47235.ptesarik@suse.cz> (raw)
In-Reply-To: <1343310813.6812.34.camel@zakaz.uk.xensource.com>
Dne Čt 26. července 2012 15:53:33 Ian Campbell napsal(a):
> On Thu, 2012-07-26 at 10:29 +0100, Petr Tesarik wrote:
> > Hello all,
> >
> > while working on makedumpfile support of Xen4, I made a side-by-side
> > comparison of the Xen3 and Xen4 virtual space on x86_64 (attached). I
> > believe that it can be useful to others as well, but I don't know what
> > would be an appropriate place for it.
>
> Somewhere on the wiki perhaps?
Sure, I can add a page there, but nobody will find it unless I link it from
somewhere, but I'm unable to find a good place for the link.
> BTW I don't think Xen3 and Xen4 are the right labels, perhaps 3.4 and
> 4.0? The 3->4 major number change was only a number change, it didn't
> signal a rearchitecting or anything like that (other than the normal
> development between a release). Labelling it Xen3 and Xen4 suggests it
> did.
And until now I've though this was indeed the case. At least many internal
structures used by the kdump infrastructure have changed substantially between
3.4 and 4.0, while they remained the same at least from 3.0.2 to 3.4.
Anyway, why wasn't 4.0 labelled 3.5 if there was no big change?
Petr Tesarik
SUSE Linux
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-07-27 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 9:29 Proper place for an overview of Xen virtual space Petr Tesarik
2012-07-26 13:53 ` Ian Campbell
2012-07-26 14:08 ` George Dunlap
2012-07-26 14:10 ` Ian Campbell
2012-07-27 5:41 ` Petr Tesarik [this message]
2012-07-27 7:15 ` Jan Beulich
2012-07-27 10:02 ` Ian Campbell
2012-07-26 13:54 ` Konrad Rzeszutek Wilk
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=201207270741.47235.ptesarik@suse.cz \
--to=ptesarik@suse.cz \
--cc=Ian.Campbell@citrix.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.