Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755123AbaDKSuO (ORCPT ); Fri, 11 Apr 2014 14:50:14 -0400 Received: from mail-ve0-f174.google.com ([209.85.128.174]:43665 "EHLO mail-ve0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754547AbaDKSuL (ORCPT ); Fri, 11 Apr 2014 14:50:11 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 11 Apr 2014 11:50:10 -0700 X-Google-Sender-Auth: n18GPGWUcy151ug-5A6VHUfWuqA Message-ID: Subject: Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels From: Linus Torvalds To: Brian Gerst Cc: Ingo Molnar , "H. Peter Anvin" , Linux Kernel Mailing List , Thomas Gleixner , stable , "H. Peter Anvin" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 11, 2014 at 11:45 AM, Brian Gerst wrote: > > I haven't tested it recently but I do know it has worked on 64-bit > kernels. There is no reason for it not to, the only thing not > supported in long mode is vm86. 16-bit protected mode is unchanged. Afaik 64-bit windows doesn't support 16-bit binaries, so I just assumed Wine wouldn't do it either on x86-64. Not for any real technical reasons, though. HOWEVER. I'd like to hear something more definitive than "I haven't tested recently". The "we don't break user space" is about having actual real *users*, not about test programs. Are there people actually using 16-bit old windows programs under wine? That's what matters. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/