kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Avi Kivity <avi@redhat.com>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>
Subject: Re: [PATCH] KVM: ia64: define kvm_lapic_enabled() to fix a compile error
Date: Mon, 27 Sep 2010 19:31:27 +0900	[thread overview]
Message-ID: <4CA0727F.1040507@oss.ntt.co.jp> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E1A90718200@shsmsx502.ccr.corp.intel.com>

>>> Hi,
>>>
>>> Isn't this a candidate for 2.6.36?
>>>
>>> Though ia64 kvm is in experimental stage and may not be working now,
>>> compile errors may be bad for other people who just want to compile
>>> ia64 linux.
>>>
>>
>> Maybe we should make ia64 kvm depend on CONFIG_BROKEN.
>>
>> It has been "experimental" for quite a while.
>
> I don't think the kvm/ia64 is broken in the upstream Linux, and it should work according to our last try. The big issue is about userspace support. Latest qemu maybe not work with latest kernel, but if you choose an old qemu, it should work!
> Xiantao
>

But without my patch, I failed to (cross-)compile kvm/ia64.

So for a few months, kvm/ia64 was broken in that sense, I guess.


I hope we would have more chance to know in which version kvm/ia64 works!
   From my side, I'm sometimes worried whether my patches made something
   bad for kvm/ia64, hopefully not of course.

Thanks,
   Takuya

  reply	other threads:[~2010-09-27 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02  8:55 [PATCH] KVM: ia64: define kvm_lapic_enabled() to fix a compile error Takuya Yoshikawa
2010-09-02  8:57 ` Avi Kivity
2010-09-27  6:51   ` Takuya Yoshikawa
2010-09-27  9:49     ` Avi Kivity
2010-09-27  9:52       ` Alexander Graf
2010-09-27 10:01       ` Zhang, Xiantao
2010-09-27 10:31         ` Takuya Yoshikawa [this message]
2010-09-28  9:27         ` Avi Kivity
2010-09-29 14:10           ` 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=4CA0727F.1040507@oss.ntt.co.jp \
    --to=yoshikawa.takuya@oss.ntt.co.jp \
    --cc=avi@redhat.com \
    --cc=kvm-ia64@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).