From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jon Ludlam <jonathan.ludlam@eu.citrix.com>
Cc: Paul Durrant <Paul.Durrant@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Detecting PV drivers
Date: Thu, 4 Apr 2013 18:00:14 +0100 [thread overview]
Message-ID: <515DB19E.4090203@citrix.com> (raw)
In-Reply-To: <515DAAB2.5050107@eu.citrix.com>
On 04/04/13 17:30, Jon Ludlam wrote:
> Hi,
>
> I'm trying find out the best way of detecting whether PV drivers have
> loaded in an HVM guest. For example, this is so we can decide whether or
> not to wait for a response from the guest when suspending.
>
> I think the best way of doing this is to find out whether the hypercall
> page has been populated or not, as this is the first thing that any PV
> drivers will have to do, but I don't know how to detect this, or even if
> this is possible - is there any way of finding this out?
Not currently as far as I can tell, but intercepting
hvm_hypercall_page_initialise() and setting a boolean in struct domain
would be easy.
The better question would be how to get this information out of Xen.
Given that the memory claim hypercall has already bumped the hypercall
interface version, would it be acceptable to have another change to
struct xen_domctl_getdomaininfo ?
~Andrew
>
> At the moment we're currently thinking of looking at status of the
> callback IRQ, which is the second thing that the Citrix PV drivers
> currently do, but I'm not sure about any other drivers. Would this be a
> reasonable thing to do if we can't detect the hypercall page?
>
> Cheers,
>
> Jon
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-04-04 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 16:30 Detecting PV drivers Jon Ludlam
2013-04-04 17:00 ` Andrew Cooper [this message]
2013-04-05 8:53 ` Jan Beulich
2013-04-05 9:01 ` Paul Durrant
2013-04-05 1:01 ` James Harper
2013-04-05 10:14 ` Stefano Stabellini
2013-04-05 17:16 ` Jonathan Ludlam
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=515DB19E.4090203@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=jonathan.ludlam@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 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.