[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240424-e31c64bda7872b0be52e4c16@orel>
Date: Wed, 24 Apr 2024 09:50:28 +0200
From: Andrew Jones <ajones@...tanamicro.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Markus Elfring <Markus.Elfring@....de>,
Kunwu Chan <chentao@...inos.cn>, linux-kselftest@...r.kernel.org, kvm@...r.kernel.org,
kernel-janitors@...r.kernel.org, Muhammad Usama Anjum <usama.anjum@...labora.com>,
Paolo Bonzini <pbonzini@...hat.com>, Shuah Khan <shuah@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, Kunwu Chan <kunwu.chan@...mail.com>,
Anup Patel <anup@...infault.org>, Thomas Huth <thuth@...hat.com>,
Oliver Upton <oliver.upton@...ux.dev>
Subject: Re: [PATCH] KVM: selftests: Add 'malloc' failure check in
test_vmx_nested_state
On Tue, Apr 23, 2024 at 12:15:47PM -0700, Sean Christopherson wrote:
..
> I almost wonder if we should just pick a prefix that's less obviously connected
> to KVM and/or selftests, but unique and short.
>
How about kvmsft_ ? It's based on the ksft_ prefix of kselftest.h. Maybe
it's too close to ksft though and would be confusing when using both in
the same test? I'm not a huge fan of capital letters, but we could also
do something like MALLOC()/CALLOC(). Eh, I don't know. Naming is hard.
Thanks,
drew
Powered by blists - more mailing lists