All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] (2.4.x bk) efi_memmap_walk_uc
Date: Tue, 29 Jul 2003 20:41:51 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105951148111016@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105883467032028@msgid-missing>

>>>>> On Tue, 29 Jul 2003 11:34:07 -0700, Christopher Wedgwood <cw@sgi.com> said:

  Christopher> On Thu, Jul 24, 2003 at 06:15:42PM -0700, David Mosberger wrote:

  >> I really would like to see the code that's using
  >> efi_memmap_walk_uc() first.

  Christopher> I think Jack sent this to you already

If he did, I don't remember (and I don't have it in my inbox).

  >> Also, a check like this:

  Chris> if (md->attribute = EFI_MEMORY_UC)

  >> is almost certainly wrong (md->attribute is a bitmap).

  Christopher> I think the logic here seems to have been uncached ONLY
  Christopher> (ie. all other bits zero).

There are many bits in attribute, such as MEMORY_RUNTIME etc.  The
real problem is that the code you sent me makes little sense to me.
It creates a "node_fetchops" structure for _every_ uncached block of
address space?  Will there be problems if that address space/memory is
used for other purposes?

  Christopher> I guess this falls down if new attributes are added so
  Christopher> something like:

  Christopher> if ((md->attribute & SOME_MASK) = EFI_MEMORY_UC)
  Christopher> [...]

  Christopher> would then be required.  Since this is the only
  Christopher> consumer of this interface thus far I'm not sure it's
  Christopher> obvious how the function should best work.

I think what we really want here is two bitmasks: one telling us which
bits we care about and one telling us what values those bits should be
set to.  As it stands, efi_memmap_walk_uc() doesn't do what it
advertises to do and instead does something very specific to SN2.

  Christopher> The issue right now seems to be whether or not this or
  Christopher> some variation of this is useful and/or desirable in
  Christopher> the mainline kernel or whether for now it's best to
  Christopher> hide this in the driver until a later stage when the
  Christopher> EFI interfaces are abstracted out a little more to make
  Christopher> this easier?

Can you work with Tony on this?  Since he's Mr. MCA (you OK with this
title, Tony? ;-) and since we'll have to map the MINSTATE area UC, I
think we want to make sure that the interface can handle all of this.

	--david

  parent reply	other threads:[~2003-07-29 20:41 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
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 [this message]
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-105951148111016@msgid-missing \
    --to=davidm@napali.hpl.hp.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 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.