[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zfbczwz5.ffs@tglx>
Date: Tue, 02 Sep 2025 17:37:50 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Sean Christopherson <seanjc@...gle.com>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>
Cc: LKML <linux-kernel@...r.kernel.org>, Jens Axboe <axboe@...nel.dk>, Paolo
Bonzini <pbonzini@...hat.com>, Wei Liu <wei.liu@...nel.org>, Dexuan Cui
<decui@...rosoft.com>, Peter Zijlstra <peterz@...radead.org>, "Paul E.
McKenney" <paulmck@...nel.org>, Boqun Feng <boqun.feng@...il.com>,
x86@...nel.org, Arnd Bergmann <arnd@...db.de>, Heiko Carstens
<hca@...ux.ibm.com>, Christian Borntraeger <borntraeger@...ux.ibm.com>,
Sven Schnelle <svens@...ux.ibm.com>, Huacai Chen <chenhuacai@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt
<palmer@...belt.com>
Subject: Re: [patch V2 07/37] rseq, virt: Retrigger RSEQ after vcpu_run()
On Mon, Aug 25 2025 at 13:24, Sean Christopherson wrote:
> On Mon, Aug 25, 2025, Mathieu Desnoyers wrote:
>> > @@ -4466,6 +4467,8 @@ static long kvm_vcpu_ioctl(struct file *
>> > r = kvm_arch_vcpu_ioctl_run(vcpu);
>> > vcpu->wants_to_run = false;
>> > + rseq_virt_userspace_exit();
>
> I don't love bleeding even more entry/rseq details into KVM.
Neither do I.
> Rather than optimize KVM and then add TIF_RSEQ, what if we do the
> opposite?
I'm not optimizing KVM. I'm simplifying the RSEQ parts to ignore
TIF_NOTIFY_RESUME when invoked with @regs == NULL.
> I.e. add TIF_RSEQ to XFER_TO_GUEST_MODE_WORK as part of "rseq: Switch
> to TIF_RSEQ if supported", and then drop TIF_RSEQ from
> XFER_TO_GUEST_MODE_WORK in a new patch?
The problem is that I have to keep all the architectures which
- do not use the generic entry code
- therefore can't be switched trivially over to the TIF_RSEQ scheme
- have RSEQ support enabled
alive and working.
> That should make it easier to revert the KVM/virt change if it turns
> out PV setups are playing games with rseq,
I can't find a hint of such an insanity in kernel, so *shrug*.
If there is out of tree code which plays games with the vCPU's user
space thread::TLS::rseq, then it rightfully breaks. The update, which
happens today, is just coincidence and a kernel internal implementation
detail.
> and it would give the stragglers (arm64 in particular) some
> motiviation to implement TIF_RSEQ and/or switch to generic TIF bits.
There is enough motivation in this series to do so :)
Thanks,
tglx
Powered by blists - more mailing lists