From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>,
Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: PV Autotranslate guests (are they used at all?)
Date: Wed, 7 Dec 2016 16:08:38 -0500 [thread overview]
Message-ID: <20161207210838.GB25789@char.us.oracle.com> (raw)
In-Reply-To: <5f9e0842-b6d7-5069-ec20-ae3b89fe9400@citrix.com>
On Wed, Dec 07, 2016 at 08:37:29PM +0000, Andrew Cooper wrote:
> Hello,
>
> While digging around, it looks like there is some major bitrot of the PV
> autotranslate code.
>
> When constructing an autotranslate domain, tools/libxc/xc_dom_x86.c:
> x86_shadow() sets refcount | translate on the domain.
>
> The combination of translate != external was excluded by c/s
> 92942fd3d469, which means that PV autotranslate guests can't boot on Xen
> 4.7 or later.
>
> The shadow emulation code for PV guests (which gets used one way or
> another if any of refcount|translate|external are set) always sets up
> emulation in the same mode as Xen's %cs. It appears to have had this
> behaviour since its introduction in c/s 1daf5e293b, and presumably means
> that noone has tried running a 32bit autotranslate guest on 64bit Xen in
> anger.
>
> Does anyone use PV autotranslate guests at all? I don't believe I have
> never come across one.
I ran it once I thing for fun. Just to see if dom0 could run. But that
was in .. Xen 4.1 days?
>
> The current shadow code excludes the translate without refcounts case,
> but the converse case (refcounts without translate) doesn't make sense.
> Without Xen performing translation, there are no shadow tables to
> reference count in the first place.
>
> This means that the only sensible shadow mode is refcount | translate |
> external, which allows PV emulation code in arch/x86/mm/shadow/ to be
> dropped, as PV guests necessarily can't be external. Doing so however
> would definitely be the end of autotranslate mode.
>
> Given that it hasn't booted on the past two releases of Xen, and doesn't
> appear to have ever worked in one common case, does anyone have any
> objection if I remove all vestigial pieces and permanently lay the
> feature to rest in SCM history?
No objection.
>
> ~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-07 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 20:37 PV Autotranslate guests (are they used at all?) Andrew Cooper
2016-12-07 21:08 ` Konrad Rzeszutek Wilk [this message]
2016-12-08 10:01 ` Tim Deegan
2016-12-14 3:23 ` George Dunlap
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=20161207210838.GB25789@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).