[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4005b824-549a-094d-82f2-e921fcd22912@redhat.com>
Date: Fri, 24 Sep 2021 18:01:17 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Oleg Nesterov <oleg@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] KVM/rseq changes for Linux 5.15-rc3
On 24/09/21 17:13, Eric W. Biederman wrote:
> Does anyone have any idea what to call
> tracehook_notify_resume so that it describes it's current usage?
There isn't a more precise definition than "sundry slowpaths to be
invoked before returning to userspace". Whenever one of the triggering
conditions becomes true, set_notify_resume() is called and
tracehook_notify_resume() will execute them all.
Paolo
Powered by blists - more mailing lists