From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "Slutz, Donald Christopher" <dslutz@verizon.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [RFC PATCH v2 1/1] Add pci_hole_min_size
Date: Wed, 12 Mar 2014 11:29:53 -0400 [thread overview]
Message-ID: <53207D71.8040500@oracle.com> (raw)
In-Reply-To: <A3CD31A5D207064088A18AC2AF7B5DC68EB56F54@MIA20725MBX891A.apps.tmrk.corp>
On 03/12/2014 11:07 AM, Slutz, Donald Christopher wrote:
>
>> diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
>> index 5c06dfa..72842aa 100644
>> --- a/tools/libxl/libxl_dm.c
>> +++ b/tools/libxl/libxl_dm.c
>> @@ -656,6 +656,21 @@ static char ** libxl__build_device_model_args_new(libxl__gc *gc,
>> } else {
>> flexarray_append(dm_args, "xenfv");
>> }
>> + if (b_info->u.hvm.pci_hole_min_size) {
>> + unsigned long long max_ram_below_4g = (1ULL << 32) -
>> + b_info->u.hvm.pci_hole_min_size;
>> +
>> + if (max_ram_below_4g > 0xF0000000ULL)
> Is this '>' or '<'?
>
> '>' is right. This is the current value (I had issues getting the inculde file that defined this and so hard coded it.)
Then pci_hole_min_size is too small, not too big, isn't it?
-boris
>
>> + {
>> + LIBXL__LOG(ctx, LIBXL__LOG_WARNING,
>> + "pci_hole_min_size too big => max_ram_below_4g=%llu > %llu (new adjusted value)\n",
>> + max_ram_below_4g, 0xF0000000ULL);
>> + max_ram_below_4g = 0xF0000000ULL;
> Do you need to adjust pci_hole_min_size as well?
>
> The limiting in hvmloader/pci.c looks to be missing. I think that the auto correction of bad values needs to be done where they are used.
>
> Will add more in next version.
>
> -Don Slutz
>
>
> -boris
>
>> + }
>> + flexarray_append_pair(dm_args, "-global",
>> + GCSPRINTF("pc-memory-layout.max-ram-below-4g=%llu",
>> + max_ram_below_4g));
>> + }
>> for (i = 0; b_info->extra_hvm && b_info->extra_hvm[i] != NULL; i++)
>> flexarray_append(dm_args, b_info->extra_hvm[i]);
>> break;
>>
next prev parent reply other threads:[~2014-03-12 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 19:27 [RFC PATCH v2 0/1] Add pci_hole_min_size Don Slutz
2014-03-11 19:27 ` [RFC PATCH v2 1/1] " Don Slutz
2014-03-11 19:54 ` Boris Ostrovsky
2014-03-12 15:07 ` Slutz, Donald Christopher
2014-03-12 15:29 ` Boris Ostrovsky [this message]
2014-03-12 17:15 ` Don Slutz
2014-03-12 18:50 ` Boris Ostrovsky
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=53207D71.8040500@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=dslutz@verizon.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@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 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).