From: Dexuan Cui <decui@microsoft.com>
To: "dave.hansen@intel.com" <dave.hansen@intel.com>,
Rik van Riel <riel@redhat.com>,
"H. Peter Anvin" <hpa@linux.intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: RE: Does slow_virt_to_phys() work with vmalloc() in the case of 32bit-PAE and 2MB page?
Date: Tue, 28 Oct 2014 08:50:34 +0000 [thread overview]
Message-ID: <F792CF86EFE20D4AB8064279AFBA51C610568754@HKNPRD3002MB017.064d.mgd.msft.net> (raw)
In-Reply-To: <F792CF86EFE20D4AB8064279AFBA51C610567A76@HKNPRD3002MB017.064d.mgd.msft.net>
> -----Original Message-----
> From: owner-linux-mm@kvack.org [mailto:owner-linux-mm@kvack.org] On
> Behalf Of Dexuan Cui
> Sent: Tuesday, October 28, 2014 15:08 PM
> To: Dave Hansen; Rik van Riel; H. Peter Anvin
> Cc: linux-kernel@vger.kernel.org; linux-mm@kvack.org
> Subject: Does slow_virt_to_phys() work with vmalloc() in the case of 32bit-
> PAE and 2MB page?
>
> Hi all,
> I suspect slow_virt_to_phys() may not work with vmalloc() in
> the 32-bit PAE case(when the pa > 4GB), probably due to 2MB page(?)
>
> Is there any known issue with slow_virt_to_phys() + vmalloc() +
> 32-bit PAE + 2MB page?
>
> From what I read the code of slow_virt_to_phys(), the variable 'psize' is
> assigned with a value but not used at all -- is this a bug?
After reading through the code, I think there is no issue here, though the
assignment of 'psize' should be unnecessary, I think.
Thanks,
-- Dexuan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-10-28 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 7:08 Dexuan Cui
2014-10-28 8:50 ` Dexuan Cui [this message]
2014-10-29 8:14 ` Dexuan Cui
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=F792CF86EFE20D4AB8064279AFBA51C610568754@HKNPRD3002MB017.064d.mgd.msft.net \
--to=decui@microsoft.com \
--cc=dave.hansen@intel.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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