To: linux-kernel@vger.kernel.org
From: hpa@zytor.com (H. Peter Anvin)
Subject: Re: Calling syscalls from x86-64 kernel results in a crash on Opteron
 machines
Date: Mon, 13 Sep 2004 19:39:04 +0000 (UTC)
Organization: Transmeta Corporation, Santa Clara CA
Message-ID: <ci4t0o$244$1@terminus.zytor.com>
References: <4145A8E1.8010409@qlusters.com> <200409131644.54441.arnd@arndb.de> <4145BA28.5020702@qlusters.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
NNTP-Posting-Date: Mon, 13 Sep 2004 19:39:04 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 819
Lines: 21

Followup to:  <4145BA28.5020702@qlusters.com>
By author:    Constantine Gavrilov <constg@qlusters.com>
In newsgroup: linux.dev.kernel
> 
> I can implement differently what I want, though it will be somewhat 
> kludgy and kernel depenedent (depends on a version and distribution). I 
> wanted to avoid that. Since what I write is really an application and 
> not interface, it was very "native" to use application syscall approach.
> 
> My real problem is not how to implement it. I want to understand this 
> specific x86_64 problem.
> 

Put it in userspace.  Really.

	-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/