From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Matthew Wilcox <matthew@wil.cx>,
Jesse Barnes <jbarnes@virtuousgeek.org>, Martin Mares <mj@ucw.cz>,
LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
linux-arch@vger.kernel.org
Subject: Re: RFC: x86: cap iomem_resource to addressable physical memory
Date: Mon, 22 Jun 2009 00:54:14 -0700 [thread overview]
Message-ID: <4A3F38A6.80906@linux.intel.com> (raw)
In-Reply-To: <20090621205534.GA4324@elf.ucw.cz>
Pavel Machek wrote:
>
> Ok... and is there enough locking in there so that it is actually ok
> to change mask during hotplug? (Is it okay because it is single long
> and all the writers are somehow serialized by hotplug mechanism?)
> Pavel
Making it a locked reference probably would be a good idea (although I
personally think it will never actually matter in practice). Although
on 32 bits (PAE) it can be more than one long, it doesn't matter because
only the upper long can actually be modified. It does, however,
complicate the actual code somewhat... I'll look at it tomorrow.
-hpa
next prev parent reply other threads:[~2009-06-22 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 1:32 RFC: x86: cap iomem_resource to addressable physical memory H. Peter Anvin
2009-06-10 1:32 ` H. Peter Anvin
2009-06-11 19:17 ` Jesse Barnes
2009-06-11 19:17 ` Jesse Barnes
2009-06-11 20:43 ` Yinghai Lu
2009-06-11 20:46 ` H. Peter Anvin
2009-06-11 20:46 ` H. Peter Anvin
2009-06-21 6:42 ` Pavel Machek
2009-06-21 6:42 ` Pavel Machek
2009-06-21 7:40 ` H. Peter Anvin
2009-06-21 20:55 ` Pavel Machek
2009-06-21 20:55 ` Pavel Machek
2009-06-22 7:54 ` H. Peter Anvin [this message]
2009-06-22 7:54 ` 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=4A3F38A6.80906@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mj@ucw.cz \
--cc=pavel@ucw.cz \
--cc=x86@kernel.org \
--cc=yhlu.kernel@gmail.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