From: Elizabeth Figura <zfigura@codeweavers.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
wine-devel@winehq.org, "André Almeida" <andrealmeid@igalia.com>,
"Wolfram Sang" <wsa@kernel.org>,
"Arkadiusz Hiler" <ahiler@codeweavers.com>,
"Andy Lutomirski" <luto@kernel.org>,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Randy Dunlap" <rdunlap@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Boqun Feng" <boqun.feng@gmail.com>
Subject: Re: [PATCH v5 00/28] NT synchronization primitive driver
Date: Mon, 10 Jun 2024 11:58:48 -0500 [thread overview]
Message-ID: <2325658.ElGaqSPkdT@uriel> (raw)
In-Reply-To: <20240519202454.1192826-1-zfigura@codeweavers.com>
On Sunday, May 19, 2024 3:24:26 PM CDT Elizabeth Figura wrote:
> This patch series implements a new char misc driver, /dev/ntsync, which is
> used to implement Windows NT synchronization primitives.
>
> NT synchronization primitives are unique in that the wait functions both are
> vectored, operate on multiple types of object with different behaviour
> (mutex, semaphore, event), and affect the state of the objects they wait
> on. This model is not compatible with existing kernel synchronization
> objects or interfaces, and therefore the ntsync driver implements its own
> wait queues and locking.
>
> This patch series is rebased against the "char-misc-next" branch of
> gregkh/char-misc.git.
Hi Peter,
Sorry to bother, but now that the Linux merge window is closed could I
request a review of this revision of the ntsync patch set, please (or a
review from another locking maintainer)?
I believe I've addressed all of the comments from the last review,
except those which would have changed the existing userspace API
(although since the driver isn't really functional yet, maybe this
would have been fine to do anyway?)
Thanks,
Zeb
next prev parent reply other threads:[~2024-06-10 17:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 20:24 [PATCH v5 00/28] NT synchronization primitive driver Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 01/28] ntsync: Introduce NTSYNC_IOC_WAIT_ANY Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 02/28] ntsync: Introduce NTSYNC_IOC_WAIT_ALL Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 03/28] ntsync: Introduce NTSYNC_IOC_CREATE_MUTEX Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 04/28] ntsync: Introduce NTSYNC_IOC_MUTEX_UNLOCK Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 05/28] ntsync: Introduce NTSYNC_IOC_MUTEX_KILL Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 06/28] ntsync: Introduce NTSYNC_IOC_CREATE_EVENT Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 07/28] ntsync: Introduce NTSYNC_IOC_EVENT_SET Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 08/28] ntsync: Introduce NTSYNC_IOC_EVENT_RESET Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 09/28] ntsync: Introduce NTSYNC_IOC_EVENT_PULSE Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 10/28] ntsync: Introduce NTSYNC_IOC_SEM_READ Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 11/28] ntsync: Introduce NTSYNC_IOC_MUTEX_READ Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 12/28] ntsync: Introduce NTSYNC_IOC_EVENT_READ Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 13/28] ntsync: Introduce alertable waits Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 14/28] selftests: ntsync: Add some tests for semaphore state Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 15/28] selftests: ntsync: Add some tests for mutex state Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 16/28] selftests: ntsync: Add some tests for NTSYNC_IOC_WAIT_ANY Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 17/28] selftests: ntsync: Add some tests for NTSYNC_IOC_WAIT_ALL Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 18/28] selftests: ntsync: Add some tests for wakeup signaling with WINESYNC_IOC_WAIT_ANY Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 19/28] selftests: ntsync: Add some tests for wakeup signaling with WINESYNC_IOC_WAIT_ALL Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 20/28] selftests: ntsync: Add some tests for manual-reset event state Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 21/28] selftests: ntsync: Add some tests for auto-reset " Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 22/28] selftests: ntsync: Add some tests for wakeup signaling with events Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 23/28] selftests: ntsync: Add tests for alertable waits Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 24/28] selftests: ntsync: Add some tests for wakeup signaling via alerts Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 25/28] selftests: ntsync: Add a stress test for contended waits Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 26/28] maintainers: Add an entry for ntsync Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 27/28] docs: ntsync: Add documentation for the ntsync uAPI Elizabeth Figura
2024-05-19 20:24 ` [PATCH v5 28/28] ntsync: No longer depend on BROKEN Elizabeth Figura
2024-06-10 16:58 ` Elizabeth Figura [this message]
2024-08-12 17:09 ` [PATCH v5 00/28] NT synchronization primitive driver Elizabeth Figura
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=2325658.ElGaqSPkdT@uriel \
--to=zfigura@codeweavers.com \
--cc=ahiler@codeweavers.com \
--cc=andrealmeid@igalia.com \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=longman@redhat.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=shuah@kernel.org \
--cc=will@kernel.org \
--cc=wine-devel@winehq.org \
--cc=wsa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).