On Wed, 2023-06-28 at 23:21 +0000, Huang, Kai wrote:
> > > + /* Need a stable CPU id for printing error message */
> > > + cpu = get_cpu();
> >
> > And that's important because?
> >
>
> I want to have a stable cpu for error message printing.
Sorry misunderstood your question.
I think having the CPU id on which the SEAMCALL failed in the dmesg would be
better? But it's not absolutely needed. I can remove it (thus remove
{get|put}_cpu()) if you prefer not to print?
