[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7fyh7qsx6guodh7vxs4luxrh25gdk4ze4cwlg4q2m7ukyqt5ht@t3a7hz2pohdt>
Date: Mon, 11 Mar 2024 14:00:17 +0200
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To:
Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...el.com, hpa@...or.com, seanjc@...gle.com, ele.reshetova@...el.com,
rick.p.edgecombe@...el.com, x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] x86/tdx: Introduce tdg_vm_wr()
On Sat, Mar 09, 2024 at 04:02:58PM -0800, Kuppuswamy Sathyanarayanan wrote:
> > + /* Old value */
> > + return args.r8;
>
> Since the update failure will panic, any use for returning the old value?
I don't have any immediate users for the old value, but I can imagine
situation when you need to do something else if your write result in
actual change of setting.
--
Kiryl Shutsemau / Kirill A. Shutemov
Powered by blists - more mailing lists