From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Francis Moreau <francis.moro@gmail.com>, kvm@vger.kernel.org
Subject: Re: 2.6.38-rc6: general protection error inside KVM 64 bits guest
Date: Wed, 09 Mar 2011 11:26:27 +0200 [thread overview]
Message-ID: <4D7747C3.1070807@redhat.com> (raw)
In-Reply-To: <20110309092520.GC10151@redhat.com>
On 03/09/2011 11:25 AM, Gleb Natapov wrote:
> On Wed, Mar 09, 2011 at 08:05:54AM +0100, Francis Moreau wrote:
> > Hi,
> >
> > On Sun, Mar 6, 2011 at 4:08 PM, Avi Kivity<avi@redhat.com> wrote:
> > > On 03/06/2011 05:02 PM, Avi Kivity wrote:
> > >>
> > >> (for #TS we need additional logic... will this arch never end?)
> > >>
> > >
> > > Actually these instructions don't generate #TS.
> > >
> >
> > I just wanted to know if this issue is going to be fixed before 2.6.38 is out ?
> >
> I posted updated patches. It is up to maintainers to decide if the
> patches should be included in 2.6.38 at such late rc stage.
Probably not. The problematic case is not very mainstream.
We'll merge it into 2.6.39 and backport into 2.6.38.1.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-03-09 9:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 9:40 2.6.38-rc6: general protection error inside KVM 64 bits guest Francis Moreau
2011-03-06 12:42 ` Gleb Natapov
2011-03-06 12:55 ` Avi Kivity
2011-03-06 14:35 ` Gleb Natapov
2011-03-06 15:02 ` Avi Kivity
2011-03-06 15:08 ` Avi Kivity
2011-03-09 7:05 ` Francis Moreau
2011-03-09 9:25 ` Gleb Natapov
2011-03-09 9:26 ` Avi Kivity [this message]
2011-03-09 9:28 ` Francis Moreau
2011-03-09 9:29 ` Avi Kivity
2011-03-09 9:30 ` Francis Moreau
2011-03-09 9:32 ` Gleb Natapov
2011-03-09 10:03 ` Avi Kivity
2011-03-09 10:07 ` Francis Moreau
2011-05-27 10:22 ` Francis Moreau
2011-05-27 12:48 ` Gleb Natapov
2011-05-27 14:30 ` Francis Moreau
2011-03-06 19:36 ` Francis Moreau
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=4D7747C3.1070807@redhat.com \
--to=avi@redhat.com \
--cc=francis.moro@gmail.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.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