From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>,
Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH xen-4.6] xen: Remove CONFIG_X86_SUPERVISOR_MODE_KERNEL as x86_32 builds are unsupported
Date: Mon, 5 Jan 2015 16:16:03 +0000 [thread overview]
Message-ID: <1420474563.28863.61.camel@citrix.com> (raw)
In-Reply-To: <54AAB6CF.7070404@citrix.com>
On Mon, 2015-01-05 at 16:07 +0000, Andrew Cooper wrote:
> >> What usecase was supervisor_mode_kernel developed for? It seems
> >> counter-intuitive, but I can't find anything in the history explaining
> >> its use.
> > It was a prototype from the pre-pvops days to see if it would be
> > feasible to have a single kernel binary which ran either on Xen or on a
> > stub hypervisor which ran it "as native" with little or no loss of
> > performance^TM (e.g. for distro's convenience to avoid the multiple
> > kernel issue).
> >
> > It never went beyond a prototype with Xen proper instead of the proposed
> > stub hypervisor and then pvops came along and was a much more sensible
> > idea...
>
> Considering the implications of running dom0 in ring0, pvops seems like
> a much more sensible idea.
It wouldn't have been a dom0, it would have just been a native system
which happened to use some Xen interfaces, the intention was never to be
able to run guests or anything, just to allow distros to only support
one binary.
Ian.
next prev parent reply other threads:[~2015-01-05 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 19:12 [PATCH xen-4.6] xen: Remove CONFIG_X86_SUPERVISOR_MODE_KERNEL as x86_32 builds are unsupported Andrew Cooper
2015-01-05 11:21 ` Tim Deegan
2015-01-05 15:16 ` Ian Campbell
2015-01-05 15:35 ` Andrew Cooper
2015-01-05 15:41 ` Ian Campbell
2015-01-05 16:07 ` Andrew Cooper
2015-01-05 16:16 ` Ian Campbell [this message]
2015-01-06 2:22 ` Mukesh Rathor
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=1420474563.28863.61.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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.