From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AEC9517C6B; Fri, 12 Jul 2024 17:14:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720804461; cv=none; b=gL48TlqY18tbd9Z9Cy99Ks1egSE+MHiiOm3Zoweogyoan2TSGSsy/QnvIDKcO7Vfy3pWX4x/Vo0XVKygbVJny8kvwjw+aOx3ZjtZ+gU8+rR5+jHEqOUQLQF6ajMzVKcYZlY1PFQxQjeamQBuRg8IxZAHso4ACrhtQqnjwq2gPeI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720804461; c=relaxed/simple; bh=fBPOV7zfczv29qyKM3eLeKNoHsGD5ay/fTO1h4n5yuk=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=s3Upr92oVVOBYWOh5IzFUoJ3ysz+Zr1TfE6fAsU1vneuhOtLEl1k89P9ZLFgzWIZseoal/ZCH9omCHKioi1QvkPMIBOLpbLwqGhTadKVp1eC76PtRi+7w3vuTGYLeHGZTYfl+rqQkPSi45zKX0JfuGvBzuUqVP4h5o1pwxiq7DY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3ECCDC32782; Fri, 12 Jul 2024 17:14:18 +0000 (UTC) Date: Fri, 12 Jul 2024 13:14:16 -0400 From: Steven Rostedt To: Sean Christopherson Cc: Joel Fernandes , Mathieu Desnoyers , Vineeth Remanan Pillai , Ben Segall , Borislav Petkov , Daniel Bristot de Oliveira , Dave Hansen , Dietmar Eggemann , "H . Peter Anvin" , Ingo Molnar , Juri Lelli , Mel Gorman , Paolo Bonzini , Andy Lutomirski , Peter Zijlstra , Thomas Gleixner , Valentin Schneider , Vincent Guittot , Vitaly Kuznetsov , Wanpeng Li , Suleiman Souhlal , Masami Hiramatsu , himadrics@inria.fr, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, graf@amazon.com, drjunior.org@gmail.com Subject: Re: [RFC PATCH v2 0/5] Paravirt Scheduling (Dynamic vcpu priority management) Message-ID: <20240712131416.78648a6e@rorschach.local.home> In-Reply-To: References: <20240403140116.3002809-1-vineeth@bitbyteword.org> <66912820.050a0220.15d64.10f5@mx.google.com> <19ecf8c8-d5ac-4cfb-a650-cf072ced81ce@efficios.com> <20240712122408.3f434cc5@rorschach.local.home> <66915ef3.050a0220.72f83.316b@mx.google.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: kvm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 12 Jul 2024 10:08:43 -0700 Sean Christopherson wrote: > > I am a bit confused by your statement Sean, because if a higher prio HOST > > thread wakes up on the vCPU thread's phyiscal CPU, then a VM-Exit should > > happen. That has nothing to do with IRQ delivery. What am I missing? > > Why does that require hooking VM-Exit? To do the lazy boosting. That's the time that the host can see the priority of the currently running task. -- Steve