public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: kvm-ia64@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH]KVM: kvm/ia64: select ANON_INODES PREEMPT_NOTIFIERS, once
Date: Mon, 25 Aug 2008 16:39:24 +0300	[thread overview]
Message-ID: <48B2B60C.7070101@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC0188E570@pdsmsx415.ccr.corp.intel.com>

Zhang, Xiantao wrote:
> But if users don't configure it @ building kernel, they can't exercise
> kvm unless re-configure and re-build the host kernel.  Generally, we
> should allow users to build kvm in the form of modules, and insert to
> host kernels without other dependcies.   BTW, we often meet such fails
> and have to do rebuild.  :(


If users don't configure networking, they can't compile any drivers.

Sorry, that's how the kernel works.  btw, on x86 we manage to run even 
without preempt notifiers, but a lot of pain is involved.

In practice, I don't expect a problem.  Most users get their kernels 
from a distribution.  You should talk to ia64 distribution vendors to 
make sure they enable kvm in their ia64 2.6.26+ kernels.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-08-25 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23  2:44 [PATCH]KVM: kvm/ia64: select ANON_INODES PREEMPT_NOTIFIERS, once Zhang, Xiantao
2008-08-25  9:00 ` Jes Sorensen
2008-08-25  9:03 ` Avi Kivity
2008-08-25  9:28   ` Zhang, Xiantao
2008-08-25 10:15     ` Avi Kivity
2008-08-25 10:49       ` Zhang, Xiantao
2008-08-25 13:39         ` Avi Kivity [this message]
2008-08-26  1:22           ` Zhang, Xiantao
2008-08-26  8:13             ` 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=48B2B60C.7070101@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm-ia64@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=xiantao.zhang@intel.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