xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Ian Pratt <Ian.Pratt@eu.citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH][v5] PV extension of HVM(hybrid) in support in Xen
Date: Fri, 5 Mar 2010 10:01:11 +0800	[thread overview]
Message-ID: <201003051001.11627.sheng@linux.intel.com> (raw)
In-Reply-To: <20100304150431.GB25801@whitby.uk.xensource.com>

On Thursday 04 March 2010 23:04:31 Tim Deegan wrote:
> Hi,
> 
> Given that we now have a similar feature from Stefano I'd like to see
> them resolved into a single patchset.

I think Stefano's patch focused on pv_ops dom0? We are focused on upstream 
Linux as domU...

I think we can get dom0 approach step by step. 
> 
> At 09:37 +0000 on 04 Mar (1267695434), Sheng Yang wrote:
> > +	if (a.flags & HVM_PV_CLOCK) {
> > +		d->hvm_pv_enabled |= XEN_HVM_PV_CLOCK_ENABLED;
> > +		update_domain_wallclock_time(d);
> > +		/* Other vcpus are adjusted during the start-up */
> > +		hvm_funcs.set_tsc_offset(d->vcpu[0], 0);
> > +	}
> 
> This still makes no sense to me.  Either it should affect the calling
> vcpu (i.e., current) or it should affect all online vcpus.

Yeah... I would make it affect the calling vcpu.
> 
> Also, whatever the semantics, they should be documented in comments in
> the header file.

Sure.

-- 
regards
Yang, Sheng

  reply	other threads:[~2010-03-05  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  9:37 [PATCH][v5] PV extension of HVM(hybrid) in support in Xen Sheng Yang
2010-03-04 15:04 ` Tim Deegan
2010-03-05  2:01   ` Sheng Yang [this message]
2010-03-05 10:40     ` Ian Campbell
2010-03-05 11:19       ` Stefano Stabellini

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=201003051001.11627.sheng@linux.intel.com \
    --to=sheng@linux.intel.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=Tim.Deegan@citrix.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 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).