From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Sheng Yang <sheng@linux.intel.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Yaozu (Eddie) Dong" <eddie.dong@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ian Pratt <Ian.Pratt@eu.citrix.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH][v9 4/6] xen/hvm: Xen PV extension of HVM initialization
Date: Tue, 16 Mar 2010 10:29:23 -0700 [thread overview]
Message-ID: <4B9FBFF3.4090806@goop.org> (raw)
In-Reply-To: <1268760010.10129.31253.camel@zakaz.uk.xensource.com>
On 03/16/2010 10:20 AM, Ian Campbell wrote:
> I don't think a new hypercall is required. Xen should simply pre-account
> for the TSC offset which HVM guests are subject to in
> __update_vcpu_system_time.
>
Yes, that would work too.
J
next prev parent reply other threads:[~2010-03-16 17:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 2:57 [PATCH][v9 0/6] PV extension of HVM (Hybrid) for Xen Sheng Yang
2010-03-12 2:57 ` Sheng Yang
2010-03-12 2:57 ` [PATCH][v9 1/6] xen: add support for hvm_op Sheng Yang
2010-03-12 2:57 ` [PATCH][v9 2/6] xen: Import cpuid.h from Xen Sheng Yang
2010-03-12 2:57 ` [PATCH][v9 3/6] xen: Make pv drivers only work with xen_pv_domain() Sheng Yang
2010-03-12 2:57 ` [PATCH][v9 4/6] xen/hvm: Xen PV extension of HVM initialization Sheng Yang
2010-03-12 20:35 ` [Xen-devel] " Jeremy Fitzhardinge
2010-03-15 1:45 ` Sheng Yang
2010-03-15 12:04 ` Stefano Stabellini
2010-03-15 22:59 ` Jeremy Fitzhardinge
2010-03-16 1:51 ` Sheng Yang
2010-03-16 17:12 ` Jeremy Fitzhardinge
2010-03-16 17:20 ` Ian Campbell
2010-03-16 17:29 ` Jeremy Fitzhardinge [this message]
2010-03-12 2:57 ` [PATCH][v9 5/6] x86/xen: The entrance for PV extension of HVM Sheng Yang
2010-03-12 2:57 ` [PATCH][v9 6/6] xen: Enable PV clocksource for HVM Sheng Yang
2010-03-12 20:37 ` [Xen-devel] " Jeremy Fitzhardinge
2010-03-12 20:37 ` Jeremy Fitzhardinge
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=4B9FBFF3.4090806@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=eddie.dong@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sheng@linux.intel.com \
--cc=xen-devel@lists.xensource.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.