From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268410AbUHWXe3 (ORCPT ); Mon, 23 Aug 2004 19:34:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268497AbUHWXe1 (ORCPT ); Mon, 23 Aug 2004 19:34:27 -0400 Received: from x35.xmailserver.org ([69.30.125.51]:29071 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id S268410AbUHWXdS (ORCPT ); Mon, 23 Aug 2004 19:33:18 -0400 X-AuthUser: davidel@xmailserver.org Date: Mon, 23 Aug 2004 16:33:12 -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: > > > > 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. Indeed, zero is. - Davide