linux-kernel - pci_lock and runtime resume

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>] [day] [month] [year] [list]

Message-ID: <CAPM=9tyyR2YkaFPHQGy_mU9YM87uaQ79Cgxvy=-ZfAAuxcSj+g@mail.gmail.com>
Date:	Mon, 4 Feb 2013 10:33:15 +1000
From:	Dave Airlie <airlied@...il.com>
To:	linux-pci@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: pci_lock and runtime resume

So I've just been looking a bit more at dynamic PM for graphics and
noticed that when userspace reads pci config space, the read happens
under the pci_lock which is a spinlock.
Now on most of the GPU drivers we'll be entering standard s/r paths
which don't have this restriction from what I can see, I get to see
lots of scheduling while atomic fun, that I'm not really sure I can
fix nicely.

Dave.
--
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/