From: Pierre Morel <pmorel@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com, cohuck@redhat.com,
imbrenda@linux.ibm.com, drjones@redhat.com, pbonzini@redhat.com
Subject: Re: [kvm-unit-tests PATCH v4 2/3] s390x: define UV compatible I/O allocation
Date: Thu, 21 Jan 2021 14:47:57 +0100 [thread overview]
Message-ID: <ab6a5d6d-29e1-4ccd-64dd-6e39888cb439@linux.ibm.com> (raw)
In-Reply-To: <0a46a299-c52d-2c7f-bb38-8d58afe053e0@redhat.com>
On 1/21/21 2:43 PM, Thomas Huth wrote:
> On 21/01/2021 14.02, Pierre Morel wrote:
>>
>>
>> On 1/21/21 10:46 AM, Janosch Frank wrote:
>>> On 1/21/21 10:13 AM, Pierre Morel wrote:
>>>> To centralize the memory allocation for I/O we define
>>>> the alloc_io_page/free_io_page functions which share the I/O
>>>> memory with the host in case the guest runs with
>>>> protected virtualization.
>>>>
>>>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>>>> ---
>>>> MAINTAINERS | 1 +
>>>> lib/s390x/malloc_io.c | 70
>>>> +++++++++++++++++++++++++++++++++++++++++++
>>>> lib/s390x/malloc_io.h | 45 ++++++++++++++++++++++++++++
>>>> s390x/Makefile | 1 +
>>>> 4 files changed, 117 insertions(+)
>>>> create mode 100644 lib/s390x/malloc_io.c
>>>> create mode 100644 lib/s390x/malloc_io.h
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index 54124f6..89cb01e 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -82,6 +82,7 @@ M: Thomas Huth <thuth@redhat.com>
>>>> M: David Hildenbrand <david@redhat.com>
>>>> M: Janosch Frank <frankja@linux.ibm.com>
>>>> R: Cornelia Huck <cohuck@redhat.com>
>>>> +R: Pierre Morel <pmorel@linux.ibm.com>
>>>
>>> If you're ok with the amount of mails you'll get then go ahead.
>>> But I think maintainer file changes should always be in a separate
>>> patch.
>>>
>>>> L: kvm@vger.kernel.org
>>>> L: linux-s390@vger.kernel.org
>>>> F: s390x/*
>>>> diff --git a/lib/s390x/malloc_io.c b/lib/s390x/malloc_io.c
>>>> new file mode 100644
>>>> index 0000000..bfe8c6a
>>>> --- /dev/null
>>>> +++ b/lib/s390x/malloc_io.c
>>>> @@ -0,0 +1,70 @@
>>>> +// SPDX-License-Identifier: GPL-2.0
>>>
>>> I think we wanted to use:
>>
>> @Janosch , @Thomas
>>
>>> /* SPDX-License-Identifier: GPL-2.0-or-later */
>>
>> or
>>
>> // SPDX-License-Identifier: GPL-2.0-only
>>
>> later or only ?
>
> If it's a new file, it's up to the author. I personally prefer -later,
> but I think IBM's preference is normally -only instead. Please check
> with your colleagues.
> Most s390x-related files in the kvm-unit-tests currently use
> "GPL-2.0-only", so that should be ok anyway.
>
>> /* or // ?
>
> I don't mind. // seems to be kernel style for .c files, but so far we've
> only used /* with SPDX in the kvm-unit-tests, so both should be fine, I
> think.
>
>> Just to : Why are you people not using the Linux style code completely
>> instead of making new exceptions.
>>
>> i.e. SPDX license and MAINTAINERS
>
> Actually, I wonder why the Linux documentation still recommends the
> identifiers that are marked as deprecated on the SPDX website. The
> deprecated "GPL-2.0" can be rather confusing, since it IMHO can easily
> be mistaken as "GPL-2.0+", so the newer identifiers are better, indeed.
>
> Not sure what you mean with MAINTAINERS, though.
Thanks for the explanations :)
For MAINTAINERS, the Linux kernel checkpatch warns that we should use
TABS instead of SPACES between item and names.
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2021-01-21 13:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 9:13 [kvm-unit-tests PATCH v4 0/3] s390x: css: pv: css test adaptation for PV Pierre Morel
2021-01-21 9:13 ` [kvm-unit-tests PATCH v4 1/3] s390x: pv: implement routine to share/unshare memory Pierre Morel
2021-01-21 9:20 ` Janosch Frank
2021-01-21 9:49 ` Janosch Frank
2021-01-21 9:52 ` Pierre Morel
2021-01-21 9:13 ` [kvm-unit-tests PATCH v4 2/3] s390x: define UV compatible I/O allocation Pierre Morel
2021-01-21 9:32 ` Thomas Huth
2021-01-22 7:55 ` Pierre Morel
2021-01-21 9:46 ` Janosch Frank
2021-01-21 9:57 ` Pierre Morel
2021-01-21 13:02 ` Pierre Morel
2021-01-21 13:43 ` Thomas Huth
2021-01-21 13:47 ` Pierre Morel [this message]
2021-01-21 13:56 ` Thomas Huth
2021-01-21 15:47 ` Pierre Morel
2021-01-21 13:48 ` Janosch Frank
2021-01-21 15:48 ` Pierre Morel
2021-01-21 13:33 ` Pierre Morel
2021-01-21 9:13 ` [kvm-unit-tests PATCH v4 3/3] s390x: css: pv: css test adaptation for PV Pierre Morel
2021-01-21 9:35 ` Thomas Huth
2021-01-21 13:25 ` Pierre Morel
2021-01-21 9:57 ` Janosch Frank
2021-01-21 13:25 ` Pierre Morel
2021-01-21 12:48 ` Cornelia Huck
2021-01-21 13:25 ` Pierre Morel
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=ab6a5d6d-29e1-4ccd-64dd-6e39888cb439@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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).