From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: Alexander Graf <agraf@suse.de>, Sheng Yang <yasker@gmail.com>,
KVM list <kvm@vger.kernel.org>,
Andrea Arcangeli <andrea@qumranet.com>,
nikola.ciprich@linuxbox.cz
Subject: Re: Build failure w/o mmu notifiers
Date: Sat, 18 Oct 2008 12:52:12 +0200 [thread overview]
Message-ID: <48F9BFDC.6080108@redhat.com> (raw)
In-Reply-To: <20081018072110.GA5667@nik-comp.linuxbox.cz>
Nikola Ciprich wrote:
> 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?
>
More choices to confuse users; and these choices aren't helpful for
ordinary builds (which don't have external modules).
You can always select KVM and ignore the modules generated.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2008-10-18 10:52 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
2008-10-18 10:52 ` Avi Kivity [this message]
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=48F9BFDC.6080108@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=andrea@qumranet.com \
--cc=extmaillist@linuxbox.cz \
--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.