From: "H. Peter Anvin" <hpa@kernel.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Bernhard Walle <bwalle@suse.de>,
x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Always use 64 bit addresses for the firmware memory map
Date: Wed, 12 Nov 2008 17:16:57 -0800 [thread overview]
Message-ID: <491B8009.803@kernel.org> (raw)
In-Reply-To: <491B758E.5090902@goop.org>
Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> Jeremy Fitzhardinge wrote:
>>
>>> resource_size_t should always be 64-bit on PAE now.
>>>
>>>
>>
>> Yes, but this would affect non-PAE kernels too.
>>
>
> Yeah, I overlooked the comment about non-PAE. Should we just make
> resource_size_t 64 bits all the time? Or ignore inaccessible resources?
>
Ignore them, presumably (keeping in mind some of them may need to be
truncated.) We simply don't manage that space.
-hpa
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@kernel.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Bernhard Walle <bwalle@suse.de>,
x86@kernel.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Always use 64 bit addresses for the firmware memory map
Date: Wed, 12 Nov 2008 17:16:57 -0800 [thread overview]
Message-ID: <491B8009.803@kernel.org> (raw)
In-Reply-To: <491B758E.5090902@goop.org>
Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> Jeremy Fitzhardinge wrote:
>>
>>> resource_size_t should always be 64-bit on PAE now.
>>>
>>>
>>
>> Yes, but this would affect non-PAE kernels too.
>>
>
> Yeah, I overlooked the comment about non-PAE. Should we just make
> resource_size_t 64 bits all the time? Or ignore inaccessible resources?
>
Ignore them, presumably (keeping in mind some of them may need to be
truncated.) We simply don't manage that space.
-hpa
next prev parent reply other threads:[~2008-11-13 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 19:44 [PATCH] Always use 64 bit addresses for the firmware memory map Bernhard Walle
2008-11-12 19:44 ` Bernhard Walle
2008-11-12 19:59 ` H. Peter Anvin
2008-11-12 19:59 ` H. Peter Anvin
2008-11-12 21:11 ` Bernhard Walle
2008-11-12 21:11 ` Bernhard Walle
2008-11-12 23:35 ` H. Peter Anvin
2008-11-12 23:35 ` H. Peter Anvin
2008-11-13 8:04 ` Bernhard Walle
2008-11-13 8:04 ` Bernhard Walle
2008-11-12 20:16 ` Jeremy Fitzhardinge
2008-11-12 20:16 ` Jeremy Fitzhardinge
2008-11-12 23:34 ` H. Peter Anvin
2008-11-12 23:34 ` H. Peter Anvin
2008-11-13 0:32 ` Jeremy Fitzhardinge
2008-11-13 0:32 ` Jeremy Fitzhardinge
2008-11-13 1:16 ` H. Peter Anvin [this message]
2008-11-13 1:16 ` H. Peter Anvin
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=491B8009.803@kernel.org \
--to=hpa@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=jeremy@goop.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.