From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sheng Yang <sheng@linux.intel.com>,
xen-devel <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Ian Pratt <Ian.Pratt@eu.citrix.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [Xen-devel] Re: [PATCH 7/7] xen: Make event channel work with PV extension of HVM
Date: Thu, 4 Mar 2010 19:22:08 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1003041910520.24752@kaball-desktop> (raw)
In-Reply-To: <4B8FFAD8.8090006@goop.org>
On Thu, 4 Mar 2010, Jeremy Fitzhardinge wrote:
>
> I think you need to expand this comment to explain the consequences of
> this change on SMP bringup and timers. I still don't see why there are
> (or should be) any differences from PV cpu bringup, aside from the tiny
> details of syscall setup (and MTRR I guess, but that's all a noop
> anyway, right?).
>
> Also, I think you can probably do the timer changes in a separate patch,
> as even with evtchns, an emulated timer device interrupt will still be
> delivered properly via VIRQ_EMUL_PIN_*.
>
One of the problems is that some VCPU initialization hypercalls at the
moment are PV specific and don't work with HVM guests, in particular I
find that VCPUOP_initialise doesn't work correctly for me.
But the timers shouldn't be an issue because you should be able to
receive the VIRQ_TIMER or the emulated timer interrupt anyway.
next prev parent reply other threads:[~2010-03-04 19:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 9:36 [PATCH 0/7][v5] PV extension of HVM (Hybrid) for Xen Sheng Yang
2010-03-04 9:36 ` [PATCH 1/7] xen: add support for hvm_op Sheng Yang
2010-03-04 9:36 ` [PATCH 2/7] xen: Import cpuid.h from Xen Sheng Yang
2010-03-04 9:36 ` [PATCH 3/7] xen: Make pv drivers only work with xen_pv_domain() Sheng Yang
2010-03-04 9:36 ` [PATCH 4/7] xen/hvm: Xen PV extension of HVM initialization Sheng Yang
2010-03-04 18:24 ` Jeremy Fitzhardinge
2010-03-04 9:36 ` [PATCH 5/7] x86/xen: The entrance for PV extension of HVM Sheng Yang
2010-03-04 9:36 ` [PATCH 6/7] xen: Enable PV clocksource for HVM Sheng Yang
2010-03-04 17:40 ` Jeremy Fitzhardinge
2010-03-04 20:25 ` Ian Campbell
2010-03-05 2:54 ` Sheng Yang
2010-03-05 9:31 ` Ian Campbell
2010-03-08 7:05 ` Sheng Yang
2010-03-04 9:36 ` [PATCH 7/7] xen: Make event channel work with PV extension of HVM Sheng Yang
2010-03-04 18:24 ` Jeremy Fitzhardinge
2010-03-04 19:22 ` Stefano Stabellini [this message]
2010-03-05 2:45 ` Sheng Yang
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=alpine.DEB.2.00.1003041910520.24752@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®