From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: mmotm 2013-01-11-15-47 (trouble starting kvm)
Date: Sat, 12 Jan 2013 16:47:32 +0100 [thread overview]
Message-ID: <50F18594.7070004@iskon.hr> (raw)
In-Reply-To: <20130111234813.170A620004E@hpza10.eem.corp.google.com>
On 12.01.2013 00:48, akpm@linux-foundation.org wrote:
> A git tree which contains the memory management portion of this tree is
> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> by Michal Hocko. It contains the patches which are between the
The last commit I see in this tree is:
commit a0d271cbfed1dd50278c6b06bead3d00ba0a88f9
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Sep 30 16:47:46 2012 -0700
Linux 3.6
Is it dead? Or am I doing something wrong?
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release. Individual mmotm releases are tagged. The master branch always
> points to the latest release, so it's constantly rebasing.
>
> http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary
>
> This mmotm tree contains the following patches against 3.8-rc3:
> (patches marked "*" will be included in linux-next)
>
> * lockdep-rwsem-provide-down_write_nest_lock.patch
> * mm-mmap-annotate-vm_lock_anon_vma-locking-properly-for-lockdep.patch
Had to revert the above two patches to start KVM (win7) successfully.
Otherwise it would livelock on some semaphore, it seems. Couldn't kill
it, ps output would stuck, even reboot didn't work (had to use SysRQ).
--
Zlatko
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-12 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 23:48 mmotm 2013-01-11-15-47 uploaded akpm
2013-01-12 1:43 ` mmotm 2013-01-11-15-47 uploaded (x86 asm-offsets broken) Randy Dunlap
2013-01-12 2:17 ` Stephen Rothwell
2013-01-12 2:29 ` Joe Perches
2013-01-12 10:13 ` Sedat Dilek
2013-01-12 11:12 ` Sedat Dilek
2013-01-12 16:52 ` Joe Perches
2013-01-14 4:03 ` Stephen Rothwell
2013-01-12 15:47 ` Zlatko Calusic [this message]
2013-01-15 18:46 ` mmotm 2013-01-11-15-47 (trouble starting kvm) Jiri Kosina
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=50F18594.7070004@iskon.hr \
--to=zlatko.calusic@iskon.hr \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mm-commits@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