From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267957AbUHWW6M (ORCPT ); Mon, 23 Aug 2004 18:58:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267994AbUHWW43 (ORCPT ); Mon, 23 Aug 2004 18:56:29 -0400 Received: from x35.xmailserver.org ([69.30.125.51]:17039 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id S267957AbUHWWy2 (ORCPT ); Mon, 23 Aug 2004 18:54:28 -0400 X-AuthUser: davidel@xmailserver.org Date: Mon, 23 Aug 2004 15:54:23 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@bigblue.dev.mdolabs.com To: Linus Torvalds 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, Linus Torvalds wrote: > On Mon, 23 Aug 2004, Davide Libenzi wrote: > > > > The eventually double GPF would happen only on TSS-IObmp-lazy tasks, ie > > tasks using the I/O bitmap. > > You could also check for the error code (at least the low 16 bits) being > 0, I guess, just to cut down the noise. 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. - Davide