From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Tim Deegan <tim@xen.org>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: [RFC PATCH 11/16]: PVH xen: some misc changes like mtrr, intr, msi.
Date: Thu, 31 Jan 2013 16:05:30 -0800 [thread overview]
Message-ID: <20130131160530.6ce89e64@mantra.us.oracle.com> (raw)
In-Reply-To: <20130124164434.GK20551@ocelot.phlegethon.org>
On Thu, 24 Jan 2013 16:44:34 +0000
Tim Deegan <tim@xen.org> wrote:
> At 18:03 -0800 on 11 Jan (1357927436), Mukesh Rathor wrote:
> > diff -r 0a38c610f26b -r 33fc5356ad7c xen/arch/x86/time.c
> > --- a/xen/arch/x86/time.c Fri Jan 11 16:34:17 2013 -0800
> > +++ b/xen/arch/x86/time.c Fri Jan 11 16:35:48 2013 -0800
> > @@ -1923,7 +1923,7 @@ void tsc_set_info(struct domain *d,
> > break;
> > }
> > d->arch.incarnation = incarnation + 1;
> > - if ( is_hvm_domain(d) )
> > + if ( is_hvm_or_pvh_domain(d) )
> > hvm_set_rdtsc_exiting(d, d->arch.vtsc);
> > }
>
> The pvh vmexit handler in the last patch crashes the guest if it gets
> an RDTSC interception vmexit, so presumably either something should be
> added there or we need to make sure that d->arch.vtsc is never set on
> a PVH domain.
Fixed. For now, making sure vtsc is not set for PVH. But, I added an
action item for Phase II to investigate and add support for it. At
first glance, staring at tsc code for couple hours, I'm still clueless.
Thanks,
Mukesh
prev parent reply other threads:[~2013-02-01 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 2:03 [RFC PATCH 11/16]: PVH xen: some misc changes like mtrr, intr, msi Mukesh Rathor
2013-01-14 12:07 ` Jan Beulich
2013-01-16 1:02 ` Mukesh Rathor
2013-01-16 10:00 ` Jan Beulich
2013-02-06 0:31 ` Mukesh Rathor
2013-01-24 16:44 ` Tim Deegan
2013-02-01 0:05 ` Mukesh Rathor [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=20130131160530.6ce89e64@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=tim@xen.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;
as well as URLs for NNTP newsgroup(s).