From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: christian.koenig@amd.com, helgaas@kernel.org,
xen-devel@lists.xen.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH v2] xen/balloon: Mark unallocated host memory as UNUSABLE
Date: Tue, 19 Dec 2017 11:08:25 +0100 [thread overview]
Message-ID: <334c80f2-92a6-7e24-8cf1-c6472194f813@suse.com> (raw)
In-Reply-To: <5A38E9A502000078001985CF@suse.com>
On 19/12/17 10:27, Jan Beulich wrote:
>>>> On 19.12.17 at 10:21, <jgross@suse.com> wrote:
>> On 19/12/17 09:23, Jan Beulich wrote:
>>>>>> On 18.12.17 at 23:22, <boris.ostrovsky@oracle.com> wrote:
>>>> +void __init arch_xen_balloon_init(struct resource *hostmem_resource)
>>>> +{
>>>> + struct xen_memory_map memmap;
>>>> + int rc;
>>>> + unsigned int i, last_guest_ram;
>>>> + phys_addr_t max_addr = max_pfn << PAGE_SHIFT;
>>>
>>> PFN_PHYS() as right now you still have an issue on 32-bit.
>>
>> Why? PFN_PHYS is defined as:
>>
>> #define PFN_PHYS(x) ((phys_addr_t)(x) << PAGE_SHIFT)
>
> Well, that's why I suggested its use (just like you did in your
> own review). IOW - now I'm confused.
Sorry, just got your answer wrong.
As I had already found the same issue somehow I assumked this remark
would be referencing my review. Sorry for the noise.
Juergen
prev parent reply other threads:[~2017-12-19 10:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 22:22 Boris Ostrovsky
2017-12-19 8:22 ` Juergen Gross
2017-12-19 8:23 ` [Xen-devel] " Jan Beulich
2017-12-19 14:25 ` Boris Ostrovsky
2017-12-19 14:40 ` Jan Beulich
2017-12-19 15:03 ` Boris Ostrovsky
2017-12-19 15:56 ` Jan Beulich
[not found] ` <5A38DA840200007800198579@suse.com>
2017-12-19 9:21 ` Juergen Gross
2017-12-19 9:27 ` Jan Beulich
[not found] ` <5A38E9A502000078001985CF@suse.com>
2017-12-19 10:08 ` 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=334c80f2-92a6-7e24-8cf1-c6472194f813@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=christian.koenig@amd.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®