public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yang, Sheng" <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Carlo Marcelo Arenas Belon
	<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: [RFC][PATCH 0/2]In-kernel PIT model
Date: Tue, 22 Jan 2008 09:12:31 +0800	[thread overview]
Message-ID: <200801220912.31687.sheng.yang@intel.com> (raw)
In-Reply-To: <20080121111708.GA26072@tapir>

On Monday 21 January 2008 19:17:08 Carlo Marcelo Arenas Belon wrote:
> On Mon, Jan 21, 2008 at 05:18:21PM +0800, Yang, Sheng wrote:
> > The patch works well on IA32e host(passed 2.6.22, 2.6.20, 2.6.18, 2.6.16
> > with hpet=disable, 2.6.9 with clock=pit),
>
> slightly off-topic but how you got around on building KVM and loading it
> with the undefined symbols from hpet (hrtimer_{cancel,start,init}) and smp
> (cpu_online_map) with < 2.6.18? or you patched and enabled it statically
> into the kernel?
>
> Carlo

Oh, sorry to cause confusion. The versions I mentioned is the guest kernel 
version, and the host kernel is 2.6.22, both in IA32e and PAE.

-- 
Thanks
Yang, Sheng

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-01-22  1:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21  9:18 [RFC][PATCH 0/2]In-kernel PIT model Yang, Sheng
     [not found] ` <200801211718.21688.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2008-01-21 11:17   ` Carlo Marcelo Arenas Belon
2008-01-22  1:12     ` Yang, Sheng [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=200801220912.31687.sheng.yang@intel.com \
    --to=sheng.yang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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