From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH 4/4] xen: select grant interface version
Date: Fri, 15 Sep 2017 15:27:06 +0200 [thread overview]
Message-ID: <302b0b5f-34d2-07e8-ffd1-21b561daa6e2@suse.com> (raw)
In-Reply-To: <59BBEFFC020000780017B8EF@suse.com>
On 15/09/17 15:21, Jan Beulich wrote:
>>>> On 15.09.17 at 15:00, <jgross@suse.com> wrote:
>> So I've found the data I've searched in the hypervisor. The maximum
>> frame number to expect can be calculated from max_page, mem_hotplug
>> and the maximum physical address from cpuid node 0x80000008. If
>> CONFIG_BIGMEM isn't defined in Xen it is 16TB max.
>>
>> The question is how to present this value to a guest. IMHO something
>> like the maximum address width similar to cpuid node 0x80000008
>> would be fine. It could be above width for pv guests and the max.
>> memory address of the guest for HVM guests (adding a cap for those
>> wouldn't be the worst idea, I guess).
>>
>> What about a new subop of the xen_version hypercall?
>
> I don't see how that would be a good fit; instead, with the CPUID
> similarity you mention, why not provide the information in one of
> Xen's CPUID leaves? Otoh I wonder whether returning max_page
> from XENMEM_maximum_ram_page is really a good idea, if later
> on that value may increase, so perhaps that op should take
> mem_hotplug into account.
I think Andrew had concerns with the exact value being returned via
XENMEM_maximum_ram_page. Using a Xen CPUID leaf returning just the
number of address bits would be a better fit, I guess.
Juergen
prev parent reply other threads:[~2017-09-15 13:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 14:48 [PATCH 0/4] xen: grant table interface v2 support Juergen Gross
2017-09-08 14:48 ` [PATCH 1/4] xen: re-introduce support for grant v2 interface Juergen Gross
2017-09-12 15:41 ` [Xen-devel] " Boris Ostrovsky
2017-09-12 15:45 ` Juergen Gross
2017-09-08 14:48 ` [PATCH 2/4] xen: limit grant v2 interface to the v1 functionality Juergen Gross
2017-09-12 15:44 ` Boris Ostrovsky
2017-09-12 15:50 ` Juergen Gross
2017-09-12 16:05 ` Boris Ostrovsky
2017-09-12 16:09 ` Juergen Gross
2017-09-12 16:21 ` Boris Ostrovsky
2017-09-12 18:18 ` Juergen Gross
2017-09-13 13:22 ` Boris Ostrovsky
2017-09-13 13:38 ` Juergen Gross
2017-09-13 13:50 ` Boris Ostrovsky
2017-09-13 14:45 ` Juergen Gross
2017-09-13 16:20 ` Boris Ostrovsky
2017-09-14 8:13 ` Juergen Gross
2017-09-08 14:48 ` [PATCH 3/4] xen: add grant interface version dependent constants to gnttab_ops Juergen Gross
2017-09-12 16:02 ` Boris Ostrovsky
2017-09-08 14:48 ` [PATCH 4/4] xen: select grant interface version Juergen Gross
2017-09-12 16:21 ` [Xen-devel] " Boris Ostrovsky
2017-09-12 18:54 ` Andrew Cooper
2017-09-13 9:23 ` Juergen Gross
2017-09-15 13:00 ` Juergen Gross
2017-09-15 13:21 ` Jan Beulich
[not found] ` <59BBEFFC020000780017B8EF@suse.com>
2017-09-15 13:27 ` Juergen Gross [this message]
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=302b0b5f-34d2-07e8-ffd1-21b561daa6e2@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®