From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [KVM paravirt issue?] Re: vsyscall=emulate regression Date: Tue, 28 Feb 2012 12:00:34 +0200 Message-ID: <4F4CA5C2.4050605@redhat.com> References: <20120203082748.GB782@amit.redhat.com> <20120214122205.GA29418@amit.redhat.com> <20120215110122.GA3136@amit.redhat.com> <4F3D2C09.1020803@redhat.com> <4F3D395B.1000708@redhat.com> <4F3D3F59.80807@redhat.com> <4F471344.1010002@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "H. Peter Anvin" , Amit Shah , tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org, kvm list To: Andy Lutomirski Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 02/24/2012 08:58 PM, Andy Lutomirski wrote: > On Thu, Feb 23, 2012 at 8:34 PM, H. Peter Anvin wrote: > > On 02/16/2012 09:39 AM, Avi Kivity wrote: > >>> > >>> Yes, this is on purpose > > > > Why? > > I think the "this" refers to the PF_INSTR fault when executing at > 0xffffffffff600xxx. That's definitely intentional -- it's how > vsyscall emulation works. > > I think it's unintentional that some kvm versions apparently forget to > set the PF_INSTR bit. > Correct. Can you provide the version that failed, so we can fix it? -- error compiling committee.c: too many arguments to function