xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
	George.Dunlap@eu.citrix.com, tim@xen.org,
	ian.jackson@eu.citrix.com, julien.grall@arm.com,
	jbeulich@suse.com
Subject: Re: [PATCH v11 0/3] xen: better grant v2 support
Date: Fri, 29 Sep 2017 06:33:41 +0200	[thread overview]
Message-ID: <9e3921fb-1f9a-afa1-384a-64b01500ff32@suse.com> (raw)
In-Reply-To: <86b0e6e2-e742-f6dc-39b6-9c3cfbfc7f05@citrix.com>

On 28/09/17 21:02, Andrew Cooper wrote:
> On 28/09/17 11:02, Juergen Gross wrote:
>> Currently Linux has no support for grant v2 as this would reduce the
>> maximum number of active grants by a factor of 2 compared to v1,
>> because the number of possible grants are limited by the allowed number
>> of grant frames and grant entries of v2 need twice as much bytes as
>> those of v1.
>>
>> Unfortunately grant v2 is the only way to support either guests with
>> more than 16TB memory size or PV guests with memory above the 16TB
>> border, as grant v1 limits the frame number to be 32 bits wide.
>>
>> In order to remove the disadvantage of grant v2 this patch series
>> adds support for setting per-domain values regarding grant limits.
>> Additionally the default limit of grant frames is doubled in case
>> of hosts with potential memory above the 16TB border.
>>
>> Changes in V11:
>> - dropped patches 1-8, as already committed
>> - patch 1: add comment in include/asm-arm/grant_table.h (Julien Grall)
>> - patch 2: return max. subleaf number in EAX (Andrew Cooper)
>> - patch 2: use flsl() instead of generic_flsl() (Jan Beulich)
> 
> Jan: You appear to have committed v10 of this series, which amongst
> other things, is missing the max subleaf assignment.

While not stating it explicitly, the subleaf stuff is okay: res->a
isn't touched, so it will be 0. The address width is put into res->b.

> Juergen: Would you mind rebasing v11 over staging, just to see what else
> got missed?

As this was the only modification in v11 regarding the applied patches
we are fine.


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-09-29  4:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 10:02 [PATCH v11 0/3] xen: better grant v2 support Juergen Gross
2017-09-28 10:02 ` [PATCH v11 1/3] xen: make grant resource limits per domain Juergen Gross
2017-10-03 13:33   ` Julien Grall
2017-09-28 10:02 ` [PATCH v11 2/3] xen: add new Xen cpuid node for max address width info Juergen Gross
2017-09-28 10:02 ` [PATCH v11 3/3] xen: add some comments in include/public/arch-x86/cpuid.h Juergen Gross
2017-09-28 19:02 ` [PATCH v11 0/3] xen: better grant v2 support Andrew Cooper
2017-09-29  4:33   ` 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=9e3921fb-1f9a-afa1-384a-64b01500ff32@suse.com \
    --to=jgross@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --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;
as well as URLs for NNTP newsgroup(s).