From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: PVH questions
Date: Wed, 30 Jan 2013 15:58:26 +0100 [thread overview]
Message-ID: <20130130145826.GB6193@type.bordeaux.inria.fr> (raw)
In-Reply-To: <alpine.DEB.2.02.1301301412320.10432@kaball.uk.xensource.com>
Stefano Stabellini, le Wed 30 Jan 2013 14:28:39 +0000, a écrit :
> On Wed, 30 Jan 2013, Samuel Thibault wrote:
> > A couple more questions:
> >
> > - Does hvm_callback_vector flags designates routing events through
> > interrupt vector 0xf3?
>
> XENFEAT_hvm_callback_vector determins the hypervisor capability, while
> you need an HVMOP_set_param hypercall to set HVM_PARAM_CALLBACK_IRQ to
> enable it.
Ok, but I mean: does XENFEAT_hvm_callback_vector mean that
HVM_PARAM_CALLBACK_IRQ can be set?
> Actually the vector number can be chosen.
Ok.
> > - Is PIC/APIC I/O emulated by the hypervisor, as well as PIT?
>
> Yes (hvm_domain_initialise is called for PVH guests).
Ok, good!
> > And does hvm_callback_vector designates that fact?
>
> PVH implies it
I know, but there's not "PVH" flag in the hypervisor capabilities,
that's why I'm asking which flag advertises the capability.
Samuel
next prev parent reply other threads:[~2013-01-30 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 1:59 PVH questions Samuel Thibault
2013-01-28 2:00 ` Samuel Thibault
2013-01-30 14:00 ` Samuel Thibault
2013-01-30 14:28 ` Stefano Stabellini
2013-01-30 14:58 ` Samuel Thibault [this message]
2013-01-30 16:08 ` Stefano Stabellini
2013-01-30 16:19 ` Samuel Thibault
2013-01-30 16:22 ` Samuel Thibault
2013-01-28 15:09 ` Stefano Stabellini
2013-01-28 16:06 ` Konrad Rzeszutek Wilk
2013-01-28 16:20 ` Jan Beulich
2013-01-28 16:31 ` Stefano Stabellini
2013-01-28 16:17 ` Samuel Thibault
2013-01-29 2:42 ` Mukesh Rathor
2013-01-31 1:02 ` Samuel Thibault
2013-01-31 1:06 ` Samuel Thibault
2013-01-31 11:51 ` 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=20130130145826.GB6193@type.bordeaux.inria.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.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).