public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christopher Wedgwood <cw@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] (2.4.x bk) efi_memmap_walk_uc
Date: Tue, 22 Jul 2003 02:58:30 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105884272104553@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105883467032028@msgid-missing>

On Mon, Jul 21, 2003 at 08:16:04PM -0600, Bjorn Helgaas wrote:

> I sort of object to adding a parallel function just to extract
> regions with a different attribute.

As do I.

> I'd rather rework efi_memmap_walk to call the callback for *every*
> memory descriptor, and make the callback responsible for filtering
> out the regions of interest.

I'd prefer we cleaned up the entire EFI code to do this and a few
other things differently --- however, given the status of 2.4.x I'm
not sure this is desirable?

> The only problem is that the existing callbacks would have to be
> changed.  Plus, all the trimming that's currently in efi_memmap_walk
> to make sure all the granules with WB memory are completely WB,
> would have to be reworked or pulled out into its own function.  I
> kind of like the idea of factoring it out anyway.

Given that is this acceptable for 2.4.x as-is or should I move the
code into the driver as distasteful as that is.

I'm not convinced that massive EFI API changes right now are a good
idea (not to mention I certainly have no time for them myself).



Thanks,
  --cw

  parent reply	other threads:[~2003-07-22  2:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22  0:43 [PATCH] (2.4.x bk) efi_memmap_walk_uc Christopher Wedgwood
2003-07-22  2:16 ` Bjorn Helgaas
2003-07-22  2:58 ` Christopher Wedgwood [this message]
2003-07-22  3:08 ` Bjorn Helgaas
2003-07-22  4:43 ` Christopher Wedgwood
2003-07-25  1:15 ` David Mosberger
2003-07-29 18:34 ` Christopher Wedgwood
2003-07-29 18:45 ` Luck, Tony
2003-07-29 19:03 ` Christopher Wedgwood
2003-07-29 20:41 ` David Mosberger
2003-07-29 21:15 ` Christopher Wedgwood
2003-07-29 21:31 ` David Mosberger
2003-07-29 21:34 ` Luck, Tony
2003-07-29 22:05 ` Jack Steiner
2003-07-29 22:07 ` Christopher Wedgwood
2003-07-29 22:26 ` Luck, Tony
2003-07-29 22:30 ` David Mosberger
2003-07-29 22:35 ` Christopher Wedgwood
2003-07-29 22:37 ` Christopher Wedgwood
2003-07-29 22:47 ` Luck, Tony
2003-07-29 22:48 ` David Mosberger
2003-07-29 22:54 ` David Mosberger
2003-07-29 23:49 ` Jack Steiner
2003-07-29 23:54 ` Christopher Wedgwood
2003-07-29 23:56 ` Jack Steiner
2003-07-30  0:00 ` Christopher Wedgwood
2003-07-30  0:02 ` Christopher Wedgwood
2003-07-30  0:05 ` David Mosberger
2003-07-30  0:12 ` David Mosberger
2003-07-30  0:22 ` Jack Steiner
2003-07-30  9:21 ` Christoph Hellwig

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=marc-linux-ia64-105884272104553@msgid-missing \
    --to=cw@sgi.com \
    --cc=linux-ia64@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox