From: Razvan Cojocaru <rzvncj@gmail.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] libxc: Add xc_domain_hvm_get_mtrr_type() call
Date: Tue, 18 Dec 2012 19:24:01 +0200 [thread overview]
Message-ID: <50D0A6B1.30702@gmail.com> (raw)
In-Reply-To: <1355850255.14620.277.camel@zakaz.uk.xensource.com>
Thanks for the reply!
> Do you have a user in mind for this new functionality?
Yes. An (userspace) application that needs to look at this information
to decide if a set of pages are interesting for monitoring.
> This version seems to do a lot less than get_mtrr_type() in the
> hypervisor. Is that deliberate? Why isn't the fixed mtrr slot and
> overlap handling required here?
It does do less. It's somewhat deliberate :), ideally it should have
done everything that get_mtrr_type() does. It did work with my initial
test addresses, but clearly more is required if it is to provide the
full functionality of get_mtrr_type(). The code currently only iterates
through the var_ranges, not the fixed array, etc.
The overlap handling isn't there because there doesn't seem to be a
clear correspondence between struct mtrr_state and struct hvm_hw_mtrr.
I implemented as much of the get_mtrr_type() logic as was obvious using
what mapping was clear bewtween them.
Is having the full functionality in libxc feasible?
>> /**
>> + * This function returns information about the MTRR type of
>> + * a given guest physical address/
>
> ^ you mean . not / I think.
You're right, sorry for the typo.
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2012-12-18 17:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 11:38 [PATCH] libxc: Add xc_domain_hvm_get_mtrr_type() call Razvan Cojocaru
2012-12-18 17:04 ` Ian Campbell
2012-12-18 17:24 ` Razvan Cojocaru [this message]
2012-12-19 10:14 ` Ian Campbell
2012-12-19 10:42 ` Razvan Cojocaru
2012-12-19 11:28 ` Ian Campbell
2012-12-19 11:49 ` Razvan Cojocaru
2012-12-19 12:00 ` Razvan Cojocaru
2012-12-19 14:57 ` Razvan Cojocaru
2012-12-19 15:00 ` Ian Campbell
2012-12-19 15:10 ` Razvan Cojocaru
2012-12-19 15:27 ` Andrew Cooper
2012-12-19 15:54 ` Ian Campbell
2012-12-19 16:11 ` Andrew Cooper
2012-12-19 16:15 ` Ian Campbell
2012-12-19 16:29 ` Razvan Cojocaru
2012-12-19 17:46 ` Tim Deegan
2012-12-19 19:35 ` Razvan Cojocaru
2012-12-20 11:57 ` Tim Deegan
2012-12-20 13:40 ` Razvan Cojocaru
2012-12-19 15:43 ` Razvan Cojocaru
2012-12-20 11:54 ` Tim Deegan
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=50D0A6B1.30702@gmail.com \
--to=rzvncj@gmail.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.