From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267726AbUHWWps (ORCPT ); Mon, 23 Aug 2004 18:45:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267951AbUHWWpp (ORCPT ); Mon, 23 Aug 2004 18:45:45 -0400 Received: from fw.osdl.org ([65.172.181.6]:18641 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S267726AbUHWW2N (ORCPT ); Mon, 23 Aug 2004 18:28:13 -0400 Date: Mon, 23 Aug 2004 15:27:57 -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: > > IMHO since the GPF path is not a fast path like a page fault, we shouldn't > be in bad shape with the current approach. No? I agree. Mostly. It might actually be a fairly critical path for some things, though. GP's happen with high frequency in emulation environments, ie I'd expect both vmware and dosemu to have just _tons_ of them. Of course, in those emulation environments you usually have other things going on too (ie signal handling costs will likely dwarf everything else). So who knows.. Linus