From: Janosch Frank <frankja@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: kvm@vger.kernel.org, david@redhat.com,
linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 3/6] s390x: uv: Add UV lib
Date: Tue, 18 May 2021 15:10:31 +0200 [thread overview]
Message-ID: <7a574791-f7c9-d8b4-fd5c-b4e941b199d1@linux.ibm.com> (raw)
In-Reply-To: <20210511181333.56e25c31.cohuck@redhat.com>
On 5/11/21 6:13 PM, Cornelia Huck wrote:
> On Mon, 10 May 2021 13:51:45 +0000
> Janosch Frank <frankja@linux.ibm.com> wrote:
>
>> Let's add a UV library to make checking the UV feature bit easier.
>> In the future this library file can take care of handling UV
>> initialization and UV guest creation.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
>> ---
>> lib/s390x/asm/uv.h | 4 ++--
>> lib/s390x/io.c | 2 ++
>> lib/s390x/uv.c | 45 +++++++++++++++++++++++++++++++++++++++++++++
>> lib/s390x/uv.h | 10 ++++++++++
>> s390x/Makefile | 1 +
>> 5 files changed, 60 insertions(+), 2 deletions(-)
>> create mode 100644 lib/s390x/uv.c
>> create mode 100644 lib/s390x/uv.h
>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
>>
>> diff --git a/lib/s390x/asm/uv.h b/lib/s390x/asm/uv.h
>> index 11f70a9f..b22cbaa8 100644
>> --- a/lib/s390x/asm/uv.h
>> +++ b/lib/s390x/asm/uv.h
>> @@ -9,8 +9,8 @@
>> * This code is free software; you can redistribute it and/or modify it
>> * under the terms of the GNU General Public License version 2.
>> */
>> -#ifndef UV_H
>> -#define UV_H
>> +#ifndef ASM_S390X_UV_H
>> +#define ASM_S390X_UV_H
>
> Completely unrelated, but this made me look at the various header
> guards, and they seem to be a bit all over the place.
>
> E.g. in lib/s390x/asm/, I see no prefix, ASM_S390X, _ASMS390X,
> __ASMS390X, ...
>
> Would consolidating this be worthwhile, or just busywork?
>
Good catch
Having a consolidated naming scheme would be good so new devs don't get
confused.
next prev parent reply other threads:[~2021-05-18 13:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 13:51 [kvm-unit-tests PATCH v2 0/6] s390x: uv: Extend guest test and add host test Janosch Frank
2021-05-10 13:51 ` [kvm-unit-tests PATCH v2 1/6] s390x: uv-guest: Add invalid share location test Janosch Frank
2021-05-10 13:51 ` [kvm-unit-tests PATCH v2 2/6] s390x: Add more Ultravisor command structure definitions Janosch Frank
2021-05-11 16:02 ` Cornelia Huck
2021-05-10 13:51 ` [kvm-unit-tests PATCH v2 3/6] s390x: uv: Add UV lib Janosch Frank
2021-05-11 16:13 ` Cornelia Huck
2021-05-18 13:10 ` Janosch Frank [this message]
2021-05-10 13:51 ` [kvm-unit-tests PATCH v2 4/6] s390x: Test for share/unshare call support before using them Janosch Frank
2021-05-11 16:15 ` Cornelia Huck
2021-05-10 13:51 ` [kvm-unit-tests PATCH v2 5/6] s390x: uv-guest: Test invalid commands Janosch Frank
2021-05-11 16:22 ` Cornelia Huck
2021-05-11 17:12 ` Claudio Imbrenda
2021-05-10 13:51 ` [kvm-unit-tests PATCH v2 6/6] s390x: Add UV host test Janosch Frank
2021-05-11 16:25 ` Cornelia Huck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a574791-f7c9-d8b4-fd5c-b4e941b199d1@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).