From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762777AbYEVVeR (ORCPT ); Thu, 22 May 2008 17:34:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758137AbYEVVd6 (ORCPT ); Thu, 22 May 2008 17:33:58 -0400 Received: from sous-sol.org ([216.99.217.87]:46565 "EHLO sous-sol.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757184AbYEVVd5 (ORCPT ); Thu, 22 May 2008 17:33:57 -0400 Date: Thu, 22 May 2008 14:32:06 -0700 From: Chris Wright To: "H. Peter Anvin" Cc: Suresh Siddha , Mikael Pettersson , Andi Kleen , mingo@elte.hu, tglx@linutronix.de, torvalds@linux-foundation.org, akpm@linux-foundation.org, roland@redhat.com, drepper@redhat.com, Hongjiu.lu@intel.com, linux-kernel@vger.kernel.org, arjan@linux.intel.com, rmk+lkml@arm.linux.org.uk, dan@debian.org, asit.k.mallick@intel.com Subject: Re: [RFC] x86: xsave/xrstor support, ucontext_t extensions Message-ID: <20080522213201.GF4018@sequoia.sous-sol.org> References: <20080520015723.GD30034@linux-os.sc.intel.com> <4832A173.6020203@firstfloor.org> <18482.53246.642835.894623@harpo.it.uu.se> <4832E705.2010900@zytor.com> <18482.60491.764019.292031@harpo.it.uu.se> <20080520175325.GE30034@linux-os.sc.intel.com> <4834BE39.2000904@zytor.com> <18485.13663.51624.694435@harpo.it.uu.se> <20080522205619.GB7998@linux-os.sc.intel.com> <4835DF64.6080104@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4835DF64.6080104@zytor.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * H. Peter Anvin (hpa@zytor.com) wrote: > Suresh Siddha wrote: >> >> hpa, What is the virtualization problem? Are you referring to perf problem? >> As you noted, regular non-rt signal handlers won't need this cpuid check. It's >> needed only for those who manually look at non-rt signal frames and interpret it. >> And also, they can do this check only once and not everytime. >> > > No, relying on CPUID and vdso both have implications for virtualization. hmm, what implications? cpuid is dealt with already.