public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 64-bit struct resource fields
Date: 01 Dec 2002 21:46:11 -0700	[thread overview]
Message-ID: <m1of85xc30.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3DE2AE04.5030209@us.ibm.com>

Dave Hansen <haveblue@us.ibm.com> writes:

> We need some way to replicate the e820 tables for kexec.  This modifies struct
> resource to use u64's for its start and end fields. This way we can export the
> whole e820 table on PAE machines.
> 
> resource->flags seems to be used often to mask out things in
> resource->start/end, so I think it needs to be u64 too.  

I don't see this in the parts of the kernel your patch changes, I will
have to look a little more and see if this is really true.  If it
is you probably should append ULL to the flag constants.

>But, Is it all right to
> 
> let things like pcibios_update_resource() truncate the resource addresses like
> they do?

The type of addresses for resources will always be equal or larger
than the resources they actually represent.  Until someone modifies
the pcibios_xxxx code to handle 64bit BARs it should only be
truncation of zeros and thus safe.  

I will see if I can scrutinize this carefully, and try it in the next
little while.  For now I am placing it on the back burner and going
to bed.  It looks like a good start though.

Eric

      parent reply	other threads:[~2002-12-02  4:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 23:11 [PATCH] 64-bit struct resource fields Dave Hansen
2002-11-26 16:49 ` Matt Porter
2002-12-02  4:26   ` Eric W. Biederman
2002-12-04 18:57     ` Matt Porter
2002-12-02  4:46 ` Eric W. Biederman [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=m1of85xc30.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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