linux-kernel - Re: [RFC] i386: per-cpu mmconfig map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 25 Dec 2006 02:38:20 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: [RFC] i386: per-cpu mmconfig map

Hi,

Arjan van de Ven <arjan@...radead.org> writes:

>>     [ 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?
>
> 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 ;(

I didn't notice the problem of NMI at all. However if NMI path use it,
pci_config_lock would be deadlock already. So I think NMI can't access
to PCI config... Hm...
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/