All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Gerhard Wiesinger <lists@wiesinger.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Kevin Wolf <kwolf@redhat.com>
Subject: Re: DOS VM problem with QEMU-KVM and newer kernels
Date: Mon, 16 Apr 2012 15:03:05 +0300	[thread overview]
Message-ID: <4F8C0A79.3080702@redhat.com> (raw)
In-Reply-To: <20120416103026.GV2428@amd.com>

On 04/16/2012 01:30 PM, Roedel, Joerg wrote:
> On Mon, Apr 16, 2012 at 12:25:37PM +0200, Jan Kiszka wrote:
> > On 2012-04-15 11:44, Avi Kivity wrote:
> > > Jan, Joerg, was an AMD erratum published for the bug?
> > 
> > It wasn't an erratum but a documented feature limitation in the AMD
> > architecture that was simply ignored by the old code.
>
> Right. But there is an erratum on K8 (only) which Kevin ran into. It is
> documented as Erratum 701 and the bug is that no EXITINTINFO is stored
> on a task-switch intercept on K8.

Ah, so this could affect Gerhard.  Gerhard, what's your cpu
family/model/stepping from /proc/cpuinfo?

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2012-04-16 12:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 18:32 DOS VM problem with QEMU-KVM and newer kernels Gerhard Wiesinger
2012-04-15  9:44 ` Avi Kivity
2012-04-15 19:03   ` Gerhard Wiesinger
2012-04-16 10:11     ` Avi Kivity
2012-04-16 10:25   ` Jan Kiszka
2012-04-16 10:30     ` Roedel, Joerg
2012-04-16 12:03       ` Avi Kivity [this message]
2012-04-16 12:18         ` Gerhard Wiesinger
2012-04-16 12:28           ` Avi Kivity
2012-04-16 11:59     ` Avi Kivity
2012-04-17  6:04   ` Gerhard Wiesinger
2012-04-17  6:57     ` Gleb Natapov
2012-04-17  7:33       ` [Qemu-devel] " Avi Kivity

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=4F8C0A79.3080702@redhat.com \
    --to=avi@redhat.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=lists@wiesinger.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.