Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756554AbYGNAAb (ORCPT ); Sun, 13 Jul 2008 20:00:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754497AbYGNAAQ (ORCPT ); Sun, 13 Jul 2008 20:00:16 -0400 Received: from terminus.zytor.com ([198.137.202.10]:59818 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754462AbYGNAAO (ORCPT ); Sun, 13 Jul 2008 20:00:14 -0400 Message-ID: <487A963E.6040307@kernel.org> Date: Sun, 13 Jul 2008 16:56:46 -0700 From: "H. Peter Anvin" Organization: Linux Kernel Organization, Inc. User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Jeremy Fitzhardinge CC: Ingo Molnar , Linux Kernel Mailing List , the arch/x86 maintainers Subject: Re: [PATCH 1/3] x86_64: further cleanup of 32-bit compat syscall mechanisms References: <487877B8.8010505@goop.org> In-Reply-To: <487877B8.8010505@goop.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 782 Lines: 20 Jeremy Fitzhardinge wrote: > AMD only supports "syscall" from 32-bit compat usermode. > Intel and Centaur(?) only support "sysenter" from 32-bit compat usermode. > > Set the X86 feature bits accordingly, and set up the vdso in > accordance with those bits. On the offchance we run on in a 64-bit > environment which supports neither syscall nor sysenter from 32-bit > mode, then fall back to the int $0x80 vdso. > > Signed-off-by: Jeremy Fitzhardinge Acked-by: H. Peter Anvin -hpa -- 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/