[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d114ae48-8ba5-a639-f220-b60f2cac67d2@linux.intel.com>
Date: Thu, 27 Oct 2022 05:30:51 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Kai Huang <kai.huang@...el.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Cc: linux-mm@...ck.org, seanjc@...gle.com, pbonzini@...hat.com,
dave.hansen@...el.com, dan.j.williams@...el.com,
rafael.j.wysocki@...el.com, kirill.shutemov@...ux.intel.com,
reinette.chatre@...el.com, len.brown@...el.com,
tony.luck@...el.com, peterz@...radead.org,
isaku.yamahata@...el.com, chao.gao@...el.com,
sathyanarayanan.kuppuswamy@...ux.intel.com, bagasdotme@...il.com,
sagis@...gle.com, imammedo@...hat.com
Subject: Re: [PATCH v6 19/21] x86/virt/tdx: Initialize all TDMRs
> + next = out.rdx;
> + /* Allow scheduling when needed */
> + if (need_resched())
> + cond_resched();
cond_resched already includes the need_resched check. That is why it is
called cond_
Powered by blists - more mailing lists