From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268257AbUHWXMM (ORCPT ); Mon, 23 Aug 2004 19:12:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268168AbUHWXKN (ORCPT ); Mon, 23 Aug 2004 19:10:13 -0400 Received: from fw.osdl.org ([65.172.181.6]:18309 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S268190AbUHWXJZ (ORCPT ); Mon, 23 Aug 2004 19:09:25 -0400 Date: Mon, 23 Aug 2004 16:09:17 -0700 (PDT) From: Linus Torvalds To: Davide Libenzi cc: Andi Kleen , Linux Kernel Mailing List , Andrew Morton Subject: Re: [patch] lazy TSS's I/O bitmap copy ... In-Reply-To: Message-ID: References: <20040823233249.09e93b86.ak@suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 23 Aug 2004, Davide Libenzi wrote: > > I think, not sure though (gonna test right now), that the "Segment > Selector Index" part of the error code might be the TSS selector index, > that will enable an even more selective reissue. I don't think so. Generally the error code is 0 for all normal GP cases. The error code tends to be non-zero only for the "load segment" things, when it shows what the incorrect segment was. So I bet you'll see a zero error code and that checking for it won't actually cut down _that_ much on the double GP faults. Linus