From: Pierre Morel <pmorel@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, frankja@linux.ibm.com,
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: Fri, 22 Jan 2021 08:55:48 +0100 [thread overview]
Message-ID: <ff1f7e69-6962-5d1d-d7be-51089c735993@linux.ibm.com> (raw)
In-Reply-To: <a50c9d35-4a67-4adc-4647-98df14300ada@redhat.com>
On 1/21/21 10:32 AM, Thomas Huth wrote:
...snip...
>> +#include <asm/facility.h>
>> +
>> +static int share_pages(void *p, int count)
>> +{
>> + int i = 0;
>> +
>> + for (i = 0; i < count; i++, p += PAGE_SIZE)
>> + if (uv_set_shared((unsigned long)p))
>> + return i;
>
> Just a matter of taste, but you could replace the "return i" here also
> with a "break" since you're returning i below anyway.
right a single out point is always better.
>
>> + return i;
>> +}
>> +
>> +static void unshare_pages(void *p, int count)
>> +{
>> + int i;
>> +
>> + for (i = count; i > 0; i--, p += PAGE_SIZE)
>> + uv_remove_shared((unsigned long)p);
>> +}
>> +
>> +void *alloc_io_pages(int size, int flags)
>
> I still think the naming or size parameter is confusing here. If I read
> something like alloc_io_pages(), I'd expect a "num_pages" parameter. So
> if you want to keep the "size" in bytes, I'd suggest to rename the
> function to "alloc_io_mem" instead.
OK, I rename the function, allowing the user to keep a simple interface
without having to calculate the page order.
>
>> +{
>> + int order = (size >> PAGE_SHIFT);
>
> I think this is wrong. According to the description of alloc_pages_flag,
> it allocates "1ull << order" pages.
> So you likely want to do this instead here:
>
> int order = get_order(size >> PAGE_SHIFT);
you are absolutely right.
>
>> + void *p;
>> + int n;
>> +
>> + assert(size);
>> +
>> + p = alloc_pages_flags(order, AREA_DMA31 | flags);
>> + if (!p || !test_facility(158))
>> + return p;
>> +
>> + n = share_pages(p, 1 << order);
>> + if (n == 1 << order)
>> + return p;
>> +
>> + unshare_pages(p, n);
>> + free_pages(p);
>> + return NULL;
>> +}
>> +
>> +void free_io_pages(void *p, int size)
>> +{
>> + int order = size >> PAGE_SHIFT;
>
> dito?
yes :(
>
>> + assert(IS_ALIGNED((uintptr_t)p, PAGE_SIZE));
>> +
>> + if (test_facility(158))
>> + unshare_pages(p, 1 << order);
>> + free_pages(p);
>> +}
>> diff --git a/lib/s390x/malloc_io.h b/lib/s390x/malloc_io.h
>> new file mode 100644
>> index 0000000..494dfe9
>> --- /dev/null
>> +++ b/lib/s390x/malloc_io.h
>> @@ -0,0 +1,45 @@
>> +/* SPDX-License-Identifier: GPL-2.0 */
>
> GPL-2.0-only please.
almmost... I use:
/* SPDX-License-Identifier: GPL-2.0-or-later */
as in other files updated by janosch if this is not a problem.
>
>> +/*
>> + * I/O allocations
>> + *
>> + * Copyright (c) 2021 IBM Corp
>> + *
>> + * Authors:
>> + * Pierre Morel <pmorel@linux.ibm.com>
>> + *
>> + */
>> +#ifndef _S390X_MALLOC_IO_H_
>> +#define _S390X_MALLOC_IO_H_
>> +
>> +/*
>> + * Allocates a page aligned page bound range of contiguous real or
>> + * absolute memory in the DMA31 region large enough to contain size
>> + * bytes.
>> + * If Protected Virtualization facility is present, shares the pages
>> + * with the host.
>> + * If all the pages for the specified size cannot be reserved,
>> + * the function rewinds the partial allocation and a NULL pointer
>> + * is returned.
>> + *
>> + * @size: the minimal size allocated in byte.
>> + * @flags: the flags used for the underlying page allocator.
>> + *
>> + * Errors:
>> + * The allocation will assert the size parameter, will fail if the
>> + * underlying page allocator fail or in the case of protected
>> + * virtualisation if the sharing of the pages fails.
>
> I think "virtualization" (with an z) is more common than "virtualisation".
OK
Thanks,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2021-01-22 7:56 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 [this message]
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
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=ff1f7e69-6962-5d1d-d7be-51089c735993@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