Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753447Ab0ATRsf (ORCPT ); Wed, 20 Jan 2010 12:48:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752915Ab0ATRse (ORCPT ); Wed, 20 Jan 2010 12:48:34 -0500 Received: from terminus.zytor.com ([198.137.202.10]:57388 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752452Ab0ATRsd (ORCPT ); Wed, 20 Jan 2010 12:48:33 -0500 Message-ID: <4B5740CD.4020005@zytor.com> Date: Wed, 20 Jan 2010 09:43:41 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0 MIME-Version: 1.0 To: Gleb Natapov CC: Peter Zijlstra , kvm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, avi@redhat.com, mingo@elte.hu, tglx@linutronix.de, riel@redhat.com, cl@linux-foundation.org Subject: Re: [PATCH v3 04/12] Add "handle page fault" PV helper. References: <1262700774-1808-5-git-send-email-gleb@redhat.com> <1263490267.4244.340.camel@laptop> <20100117144411.GI31692@redhat.com> <4B541D08.9040802@zytor.com> <20100118085022.GA30698@redhat.com> <4B5510B1.9010202@zytor.com> <20100119065537.GF14345@redhat.com> <4B55E5D8.1070402@zytor.com> <20100119174438.GA19450@redhat.com> <4B5611A9.4050301@zytor.com> <20100120100254.GC5238@redhat.com> In-Reply-To: <20100120100254.GC5238@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1374 Lines: 31 On 01/20/2010 02:02 AM, Gleb Natapov wrote: > >> You can have the guest OS take an exception on a vector above 31 just >> fine; you just need it to tell the hypervisor which vector it, the OS, >> assigned for this purpose. >> > VMX doesn't allow to inject hardware exception with vector greater then 31. > SDM 3B section 23.2.1.3. > OK, you're right. I had missed that... I presume it was done for implementation reasons. > I can inject the event as HW interrupt on vector greater then 32 but not > go through APIC so EOI will not be required. This sounds non-architectural > and I am not sure kernel has entry point code for this kind of event, it > has one for exception and one for interrupts that goes through __do_IRQ() > which assumes that interrupts should be ACKed. You can also just emulate the state transition -- since you know you're dealing with a flat protected-mode or long-mode OS (and just make that a condition of enabling the feature) you don't have to deal with all the strange combinations of directions that an unrestricted x86 event can take. Since it's an exception, it is unconditional. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/