Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1654261 > unrolled thread

Re: espfix and 5-level paging

Started byAndy Lutomirski <luto@kernel.org>
First post2017-05-31 16:00 +0200
Last post2017-05-31 16:00 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: espfix and 5-level paging Andy Lutomirski <luto@kernel.org> - 2017-05-31 16:00 +0200

#1654261 — Re: espfix and 5-level paging

FromAndy Lutomirski <luto@kernel.org>
Date2017-05-31 16:00 +0200
SubjectRe: espfix and 5-level paging
Message-ID<tNcki-5yl-23@gated-at.bofh.it>
On Sat, May 27, 2017 at 2:30 PM, Yuhong Bao <YuhongBao_386@hotmail.com> wrote:
> I don't like espfix of course, and would probably manually fix it to N in the kernel config unless I really had to run buggy DPMI apps.
> Win8 decided to just disable NTVDM by default instead.
> ________________________________________
> From: Yuhong Bao
> Sent: Saturday, May 13, 2017 2:39:59 AM
> To: kirill.shutemov@linux.intel.com; linux-kernel@vger.kernel.org
> Subject: espfix and 5-level paging
>
> Instead of porting espfix to 5-level paging, why not fix the IRET instruction?
> It probably should not require even a CR4 flag to enable.

I have no context here.  It would be great if Intel and/or AMD were to
fix IRET.  Meanwhile, we can work around it in the kernel, which we do
if MODIFY_LDT is on and configured to allow 16-bit segments.  If you
don't want 16-bit segments, you can turn them off.

(This has nothing to do with buggy DPMI apps.  It affects pretty much
all 16-bit code.)

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web