From: Amit Shah <amit.shah@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
"H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org, kvm list <kvm@vger.kernel.org>
Subject: Re: [KVM paravirt issue?] Re: vsyscall=emulate regression
Date: Tue, 28 Feb 2012 16:38:23 +0530 [thread overview]
Message-ID: <20120228110823.GA9197@amit.redhat.com> (raw)
In-Reply-To: <4F4CA5C2.4050605@redhat.com>
On (Tue) 28 Feb 2012 [12:00:34], Avi Kivity wrote:
> On 02/24/2012 08:58 PM, Andy Lutomirski wrote:
> > On Thu, Feb 23, 2012 at 8:34 PM, H. Peter Anvin <hpa@zytor.com> 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?
I'm running this on a RHEL host, the version that fails is
2.6.32-220.4.1.el6.x86_64, but can't say when it got introduced,
haven't gone back and checked that.
Amit
prev parent reply other threads:[~2012-02-28 11:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 8:27 Amit Shah
2012-02-03 15:30 ` Andy Lutomirski
2012-02-03 17:32 ` Amit Shah
2012-02-14 12:22 ` Amit Shah
2012-02-14 16:26 ` Andy Lutomirski
2012-02-15 11:01 ` Amit Shah
2012-02-15 19:36 ` [KVM paravirt issue?] " Andy Lutomirski
2012-02-16 16:17 ` Avi Kivity
2012-02-16 16:45 ` Andy Lutomirski
2012-02-16 17:14 ` Avi Kivity
2012-02-16 17:35 ` Andy Lutomirski
2012-02-16 17:39 ` Avi Kivity
2012-02-24 4:34 ` H. Peter Anvin
2012-02-24 18:58 ` Andy Lutomirski
2012-02-28 10:00 ` Avi Kivity
2012-02-28 11:08 ` Amit Shah [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120228110823.GA9197@amit.redhat.com \
--to=amit.shah@redhat.com \
--cc=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome