From: Michael Tokarev <mjt@tls.msk.ru>
To: Joerg Roedel <joro@8bytes.org>
Cc: Alec Joseph Rivera <eijhei@gmail.com>,
Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, Meric Mara <mmara@8layertech.com>,
Renan Mara <rmara@8layertech.com>
Subject: Re: 2.6.16 Guest Hangs on Boot
Date: Thu, 16 Sep 2010 15:35:17 +0400 [thread overview]
Message-ID: <4C9200F5.8000607@msgid.tls.msk.ru> (raw)
In-Reply-To: <20100916113255.GB15338@8bytes.org>
16.09.2010 15:32, Joerg Roedel пишет:
> On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote:
>> On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
>>
>> Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
>> time :-)
>>
>> Thanks, will update the list when either comes.
>
> Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem on
> 32 bit hosts.
What commit it is?
I swear I saw it in 2.6.32-stable somewhere. Is it this one (2.6.32.12):
From: Gleb Natapov <gleb@redhat.com>
Date: Fri, 19 Mar 2010 15:47:31 +0100
Subject: KVM: x86 emulator: fix memory access during x86 emulation
To: stable@kernel.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>, Avi Kivity <avi@redhat.com>, Gleb Natapov <gleb@redhat.com>
Message-ID: <1269010059-25309-4-git-send-email-stefan.bader@canonical.com>
From: Gleb Natapov <gleb@redhat.com>
commit 1871c6020d7308afb99127bba51f04548e7ca84e upstream
Currently when x86 emulator needs to access memory, page walk is done with
broadest permission possible, so if emulated instruction was executed
by userspace process it can still access kernel memory. Fix that by
providing correct memory access to page walker during emulation.
/mjt
next prev parent reply other threads:[~2010-09-16 11:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 16:53 2.6.16 Guest Hangs on Boot Alec Joseph Rivera
2010-09-15 17:28 ` Alexander Graf
2010-09-15 17:48 ` Alec Joseph Rivera
2010-09-15 17:51 ` Alexander Graf
2010-09-15 18:07 ` Alec Joseph Rivera
2010-09-15 18:15 ` Alexander Graf
2010-09-15 18:26 ` Alec Joseph Rivera
2010-09-16 1:55 ` Alec Joseph Rivera
2010-09-16 6:39 ` Gleb Natapov
2010-09-16 7:52 ` Alec Joseph Rivera
2010-09-16 7:56 ` Gleb Natapov
2010-09-16 8:03 ` Alec Joseph Rivera
2010-09-16 10:11 ` Alec Joseph Rivera
2010-09-16 10:14 ` Gleb Natapov
2010-09-16 11:13 ` Alec Joseph Rivera
2010-09-16 11:18 ` Gleb Natapov
2010-09-16 10:27 ` Alexander Graf
2010-09-16 11:02 ` Joerg Roedel
2010-09-16 11:11 ` Alec Joseph Rivera
2010-09-16 11:32 ` Joerg Roedel
2010-09-16 11:35 ` Michael Tokarev [this message]
2010-09-16 11:41 ` Gleb Natapov
2010-09-16 11:43 ` Joerg Roedel
2010-09-16 11:37 ` Alec Joseph Rivera
2010-09-16 11:41 ` Gleb Natapov
2010-09-16 11:51 ` Alec Joseph Rivera
2010-09-15 18:37 ` Michael Tokarev
2010-09-16 8:17 ` Alec Joseph Rivera
2010-09-16 8:32 ` Dave Young
2010-09-16 9:56 ` Alec Joseph Rivera
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=4C9200F5.8000607@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=agraf@suse.de \
--cc=eijhei@gmail.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=mmara@8layertech.com \
--cc=rmara@8layertech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox