From: Arjan van de Ven <arjan@infradead.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [RFC] i386: per-cpu mmconfig map
Date: Sun, 24 Dec 2006 18:16:17 +0100 [thread overview]
Message-ID: <1166980577.3281.1396.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <87lkkxz0k5.fsf@duaron.myhome.or.jp>
On Mon, 2006-12-25 at 02:05 +0900, OGAWA Hirofumi wrote:
> Hi,
>
> [ Alternatively, we could make a per-cpu mapping area or something. Not
> that it's probably worth it, but if we wanted to avoid all locking and
> instead just disable preemption, that would be the way to go. --Linus ]
>
> This patch is a draft of Linus's suggestion. This seems work for me.
> And this removes pci_config_lock in mmconfig access path, I think we
> don't need lock on this path, although we need to disable IRQ.
>
> Comment?
Hi,
I like the idea and the implementation, I have just one concern:
Does your schema still work if the Non-Maskable-Interrupt code uses
config space? It may do that I suspect to deal with ECC memory errors ;(
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2006-12-24 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 17:05 OGAWA Hirofumi
2006-12-24 17:16 ` Arjan van de Ven [this message]
2006-12-24 17:38 ` OGAWA Hirofumi
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=1166980577.3281.1396.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®