From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tomas Racek <tracek@redhat.com>, Borislav Petkov <bp@alien8.de>,
Alan Cox <alan@linux.intel.com>,
linux-kernel@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: x86, nops settings result in kernel crash
Date: Thu, 16 Aug 2012 14:30:18 -0700 [thread overview]
Message-ID: <502D666A.9080906@linux.intel.com> (raw)
In-Reply-To: <20120816195324.5356cba0@pyramind.ukuu.org.uk>
On 08/16/2012 11:53 AM, Alan Cox wrote:
>>
>> Yes, if I remove the break statement (introduced by this commit), it works fine.
>
> What version of qemu is this - do we have qemu bug here I wonder.
>
Also, is it 32 or 64 bits?
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: qemu-devel@nongnu.org, Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, Tomas Racek <tracek@redhat.com>,
Alan Cox <alan@linux.intel.com>
Subject: Re: [Qemu-devel] x86, nops settings result in kernel crash
Date: Thu, 16 Aug 2012 14:30:18 -0700 [thread overview]
Message-ID: <502D666A.9080906@linux.intel.com> (raw)
In-Reply-To: <20120816195324.5356cba0@pyramind.ukuu.org.uk>
On 08/16/2012 11:53 AM, Alan Cox wrote:
>>
>> Yes, if I remove the break statement (introduced by this commit), it works fine.
>
> What version of qemu is this - do we have qemu bug here I wonder.
>
Also, is it 32 or 64 bits?
-hpa
next prev parent reply other threads:[~2012-08-16 21:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1104118228.1760802.1345121009530.JavaMail.root@redhat.com>
2012-08-16 13:35 ` x86, nops settings result in kernel crash Tomas Racek
2012-08-16 13:35 ` [Qemu-devel] " Tomas Racek
2012-08-16 13:48 ` Borislav Petkov
2012-08-16 13:48 ` [Qemu-devel] " Borislav Petkov
2012-08-16 18:45 ` Tomas Racek
2012-08-16 18:45 ` [Qemu-devel] " Tomas Racek
2012-08-16 18:53 ` Alan Cox
2012-08-16 18:53 ` [Qemu-devel] " Alan Cox
2012-08-16 21:30 ` H. Peter Anvin [this message]
2012-08-16 21:30 ` H. Peter Anvin
2012-08-17 7:42 ` Tomas Racek
2012-08-17 7:42 ` [Qemu-devel] " Tomas Racek
2012-08-16 21:51 ` Anthony Liguori
2012-08-16 21:51 ` [Qemu-devel] " Anthony Liguori
2012-08-16 21:51 ` Anthony Liguori
2012-08-17 7:43 ` Tomas Racek
2012-08-17 7:43 ` [Qemu-devel] " Tomas Racek
2012-08-17 7:43 ` Tomas Racek
2012-08-17 8:09 ` Borislav Petkov
2012-08-17 8:09 ` [Qemu-devel] " Borislav Petkov
2012-08-17 8:09 ` Borislav Petkov
2012-08-20 17:13 ` Tomas Racek
2012-08-20 17:13 ` [Qemu-devel] " Tomas Racek
2012-08-20 17:13 ` Tomas Racek
2012-08-21 7:22 ` Michael Tokarev
2012-08-21 7:22 ` Michael Tokarev
2012-08-21 9:28 ` Tomas Racek
2012-08-21 9:28 ` [Qemu-devel] " Tomas Racek
2012-08-21 9:28 ` Tomas Racek
2012-08-22 9:54 ` Avi Kivity
2012-08-22 9:54 ` [Qemu-devel] " Avi Kivity
2012-08-22 9:54 ` Avi Kivity
2012-08-22 10:03 ` [PATCH] x86, alternative: fix p6 nops on non-modular kernels Avi Kivity
2012-08-22 10:03 ` [Qemu-devel] " Avi Kivity
2012-08-22 10:21 ` [tip:x86/urgent] x86/alternatives: Fix " tip-bot for Avi Kivity
2012-08-22 10:33 ` [PATCH] x86, alternative: fix " Tomas Racek
2012-08-22 10:33 ` [Qemu-devel] " Tomas Racek
2012-08-22 10:33 ` Tomas Racek
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=502D666A.9080906@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=tracek@redhat.com \
/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.