All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <aarcange@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Sheng Yang <yasker@gmail.com>, KVM list <kvm@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>
Subject: Re: Build failure w/o mmu notifiers
Date: Fri, 17 Oct 2008 21:25:06 +0200	[thread overview]
Message-ID: <20081017192506.GU26399@duo.random> (raw)
In-Reply-To: <16F9B349-9566-445E-9FF8-A1254AAFDA4F@suse.de>

Hi Alexander,

On Fri, Oct 17, 2008 at 08:36:08PM +0200, Alexander Graf wrote:
> So if I don't select kvm in the kernel (either as module or compiled in) I 
> can't build an external module providing kvm's functionality? That doesn't 
> seem really useful to me...

The external module is supposed to still build against older kernels
that don't have mmu notifier functionality at all regardless of their
build config. So it should build on latest kernel with kvm disabled
too (as mentioned here, MMU_NOTIFIER isn't explicitly selectable, it
gets set implicitly if kvm is selected), if it doesn't it's probably
some glitch that needs fixing. Or perhaps if it's not a vanilla kernel
you're building against and a third party patch interfering, just
wondering. I'll try to reproduce with vanilla mainline to see if
something broke, in any case you can post the build failure if the
problem persists.

Thanks!
Andrea

  reply	other threads:[~2008-10-18 10:56 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 [this message]
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
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=20081017192506.GU26399@duo.random \
    --to=aarcange@redhat.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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.