From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Priyanka Tembey <tembey.priyanka@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Passing information from HVM to Xen hypervisor
Date: Thu, 16 Sep 2010 16:04:49 +0100 [thread overview]
Message-ID: <AANLkTinzxdCmOKfmDi3RtbyaCqqt1QMH3Tp92DQOGNLw@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim+P8qwXV1Zwf9aSwATQfH2oe8fV8X+fE0j4Ce9@mail.gmail.com>
It depends on what information you want to pass. Shared pages are
good to pass information to Xen if it's updated frequently, but Xen
doesn't necessarily need to know about each update. (Paravirtualized
TPR would be a good example of this -- updated somtimes thoundands of
times per second, but only important if Xen is delivering an
interrupt.)
For simplicity, I'd probably say start with a hypercall, and switch to
a shared page only if the overhead of making the VMEXITs is causing a
measurable performance problem.
Are you doing scheduler work?
-George
On Thu, Sep 16, 2010 at 3:51 PM, Priyanka Tembey
<tembey.priyanka@gmail.com> wrote:
> hello,
>
> I want to pass some information about the HVM guest kernel from the HVM
> guest to the hypervisor (specifically, the scheduler). What is the best way
> to implement this and how should I go about it (hypercall vs. shared page)?
> I was taking a look at an old post related to a similar issue
> [http://xen.1045712.n5.nabble.com/Hypercall-from-HVM-guest-td2525175.html],
> but it wasn't very conclusive.
>
> thanks,
> Priyanka
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2010-09-16 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 14:51 Passing information from HVM to Xen hypervisor Priyanka Tembey
2010-09-16 15:04 ` George Dunlap [this message]
2010-09-17 19:49 ` Priyanka Tembey
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=AANLkTinzxdCmOKfmDi3RtbyaCqqt1QMH3Tp92DQOGNLw@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=tembey.priyanka@gmail.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).