From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Sergey Dyasli" <sergey.dyasli@citrix.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>,
"Suravee Suthikulpanit" <suravee.suthikulpanit@amd.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Brian Woods" <brian.woods@amd.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] x86/svm: Drop the suggestion of Long Mode Segment Limit support
Date: Tue, 24 Jul 2018 11:25:25 +0100 [thread overview]
Message-ID: <20180724102525.lzeavgmobasaias6@citrix.com> (raw)
In-Reply-To: <1532356957-1706-1-git-send-email-andrew.cooper3@citrix.com>
On Mon, Jul 23, 2018 at 03:42:37PM +0100, Andrew Cooper wrote:
> Because of a bug in 2010, LMSL support didn't functioned in Xen.
>
> c/s f2c608444 noticed but avoided fixing the issue for migration reasons. In
> addition to migration problems, changes to the segmentation logic for
> emulation would be needed before the feature could be enabled.
>
> This feature is entirely unused by operating systems (probably owing to its
> semantics which only cover half the segment registers), and no one has
> commented on its absence from Xen. As supporting it would involve a large
> amount of effort, it seems better to remove the code entirely.
>
> If someone finds a valid usecase, we can resurrecting the code and
> implementing the remaining parts, but I doubt anyone will.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-24 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 14:42 [PATCH] x86/svm: Drop the suggestion of Long Mode Segment Limit support Andrew Cooper
2018-07-23 22:02 ` Boris Ostrovsky
2018-07-23 22:04 ` Boris Ostrovsky
2018-07-24 10:15 ` Jan Beulich
2018-07-24 10:25 ` Wei Liu [this message]
2018-07-24 14:36 ` Roger Pau Monné
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=20180724102525.lzeavgmobasaias6@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=brian.woods@amd.com \
--cc=roger.pau@citrix.com \
--cc=sergey.dyasli@citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--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.