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 0/7][RFC] Enable kvm/ia-64 to build kvm components in userspace.
Date: Thu, 10 Jul 2008 17:52:40 +0300	[thread overview]
Message-ID: <48762238.9070906@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC0157079D@pdsmsx415.ccr.corp.intel.com>

Zhang, Xiantao wrote:
>>
>> I agree that for automatic testing it's more of a burden; but it needs
>> to be done, especially as some kvm features are only enabled on newer
>> kernels.
>>
>> The external module is convenient, but it's not a substitute for the
>> real thing.
>>     
>
> So, I have a question here, When will you drop external module support?
>   

I don't really know.

> You know, it blocks our auto-testing system now, we have to re-evaulate
> the effort without external module support. 
>   

I think it's very worthwhile to update the autotester to be able to 
build kernels. kvm will soon depend on core functionality (mmu 
notifiers) and since currently kvm is the only user (well, gru will be 
added soon, but ...) we need to test it ourselves.

> If it won't be dropped in a few weeks, we are eager to get its support
> for kvm-ia64.
>
>   

Okay, please send the patches, but with diff -M so they're readable.

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


  reply	other threads:[~2008-07-10 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  2:16 [PATCH 0/7][RFC] Enable kvm/ia-64 to build kvm components in userspace Zhang, Xiantao
2008-07-05  9:18 ` Avi Kivity
2008-07-05 10:02   ` Zhang, Xiantao
2008-07-05 10:21     ` Avi Kivity
2008-07-07  9:48       ` Zhang, Xiantao
2008-07-10 14:52         ` Avi Kivity [this message]
2008-07-11  0:43           ` Zhang, Xiantao

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=48762238.9070906@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