All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Alexander Graf <agraf@suse.de>, Sheng Yang <yasker@gmail.com>,
	KVM list <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>,
	Andrea Arcangeli <andrea@qumranet.com>
Cc: nikola.ciprich@linuxbox.cz
Subject: Re: Build failure w/o mmu notifiers
Date: Sat, 18 Oct 2008 07:21:11 +0000	[thread overview]
Message-ID: <20081018072110.GA5667@nik-comp.linuxbox.cz> (raw)
In-Reply-To: <20081017181727.GB24525@yukikaze>

[-- Attachment #1: Type: text/plain, Size: 2057 bytes --]

Hi,
I've been stumbling to same problems building kernel packages for our distro -
I've made small patches which allow enabling MMU notifier and also preempt notifiers
on kernel with KVM disabled (to allow building external always fresh KVM).
I'm attaching those, hope it helps.
Actually, Avi, do You thing souch patches could be pushed upstream? It doesn't
hurt anything to have such a choice no?
If so, I can send git style patches ;)
regards
nik

On Sat, Oct 18, 2008 at 02:17:27AM +0800, Sheng Yang wrote:
> On Fri, Oct 17, 2008 at 07:47:39PM +0200, Alexander Graf wrote:
> >
> > On 17.10.2008, at 19:25, Sheng Yang wrote:
> >
> >> On Fri, Oct 17, 2008 at 06:34:35PM +0200, Alexander Graf wrote:
> >>> Hi,
> >>>
> >>> I'm currently experiencing build failures when CONFIG_MMU_NOTIFIERS  
> >>> is
> >>> not set. Is this intended? If so, it might be nice to put a  
> >>> configure-
> >>> check or #error somewhere to tell the user that enabling mmu  
> >>> notifiers
> >>> became mandatory.
> >>
> >> Yeah, I think it's intended. In fact, it was selected by KVM
> >> , so if you compile a kernel with KVM, I think it would work...
> >
> > Well - it makes it pretty hard to build KVM as an external module (which 
> > I prefer due to many reasons) and I've actually had a problem to find the 
> > option in make menuconfig somewhere - is it even selectable?
> 
> CONFIG_MMU_NOITFIER? No... It's automatically selected, if you select KVM,
> either in-kernel or module. Please refer to arch/x86/kvm/Kconfig.
> --
> regards
> Yang, Sheng
> >
> > Alex
> >
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

[-- Attachment #2: linux-2.6.25-enable-preempt-notifiers.diff --]
[-- Type: text/plain, Size: 684 bytes --]

diff -Naur linux-2.6.25/init/Kconfig linux-2.6.25-enable-preempt-notifiers/init/Kconfig
--- linux-2.6.25/init/Kconfig	2008-06-10 02:51:26.000000000 -0400
+++ linux-2.6.25-enable-preempt-notifiers/init/Kconfig	2008-06-10 03:09:18.000000000 -0400
@@ -800,6 +800,11 @@
 	  /proc/kpagecount, and /proc/kpageflags. Disabling these
           interfaces will reduce the size of the kernel by approximately 4kb.
 
+config PREEMPT_NOTIFIERS
+	bool "Enable preempt notifiers"
+	help
+	  Enable preempt notifiers
+
 endmenu		# General setup
 
 config SLABINFO
@@ -913,9 +918,6 @@
 
 source "block/Kconfig"
 
-config PREEMPT_NOTIFIERS
-	bool
-
 config CLASSIC_RCU
 	def_bool !PREEMPT_RCU
 	help

[-- Attachment #3: linux-2.6.27-enable-mmu-notifier.diff --]
[-- Type: text/plain, Size: 373 bytes --]

diff -Naur linux-2.6.27/mm/Kconfig linux-2.6.27-enable-mmu-notifier/mm/Kconfig
--- linux-2.6.27/mm/Kconfig	2008-10-10 00:13:53.000000000 +0200
+++ linux-2.6.27-enable-mmu-notifier/mm/Kconfig	2008-10-12 15:10:21.000000000 +0200
@@ -207,4 +207,7 @@
 	depends on !ARCH_NO_VIRT_TO_BUS
 
 config MMU_NOTIFIER
-	bool
+	bool "Enable MMU notifier"
+	help
+	  Enable MMU notifier
+

  parent reply	other threads:[~2008-10-18  5:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 16:34 Build failure w/o mmu notifiers Alexander Graf
2008-10-17 17:25 ` Sheng Yang
2008-10-17 17:47   ` Alexander Graf
2008-10-17 18:17     ` Sheng Yang
2008-10-17 18:36       ` Alexander Graf
2008-10-17 19:25         ` Andrea Arcangeli
2008-10-18 10:51         ` Avi Kivity
2008-10-18 11:12           ` Alexander Graf
2008-10-19  8:57             ` Avi Kivity
2008-10-18  7:21       ` Nikola Ciprich [this message]
2008-10-18 10:52         ` 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=20081018072110.GA5667@nik-comp.linuxbox.cz \
    --to=extmaillist@linuxbox.cz \
    --cc=agraf@suse.de \
    --cc=andrea@qumranet.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    --cc=yasker@gmail.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.