From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
jgross@suse.com, konrad.wilk@oracle.com
Cc: daniel.vetter@intel.com, dongwon.kim@intel.com,
matthew.d.roper@intel.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH 2/8] xen/balloon: Move common memory reservation routines to a module
Date: Thu, 31 May 2018 17:29:09 +0300 [thread overview]
Message-ID: <4d386f6f-5212-1e42-abf7-1913f6218f05@gmail.com> (raw)
In-Reply-To: <b9046572-8802-b213-a74f-68f58a58ae6a@gmail.com>
On 05/31/2018 10:51 AM, Oleksandr Andrushchenko wrote:
> On 05/30/2018 10:24 PM, Boris Ostrovsky wrote:
>> On 05/30/2018 01:46 PM, Oleksandr Andrushchenko wrote:
>>> On 05/30/2018 06:54 PM, Boris Ostrovsky wrote:
>>>>
>>>> BTW, I also think you can further simplify
>>>> xenmem_reservation_va_mapping_* routines by bailing out right away if
>>>> xen_feature(XENFEAT_auto_translated_physmap). In fact, you might even
>>>> make them inlines, along the lines of
>>>>
>>>> inline void xenmem_reservation_va_mapping_reset(unsigned long count,
>>>> struct page **pages)
>>>> {
>>>> #ifdef CONFIG_XEN_HAVE_PVMMU
>>>> if (!xen_feature(XENFEAT_auto_translated_physmap))
>>>> __xenmem_reservation_va_mapping_reset(...)
>>>> #endif
>>>> }
>>> How about:
>>>
>>> #ifdef CONFIG_XEN_HAVE_PVMMU
>>> static inline __xenmem_reservation_va_mapping_reset(struct page *page)
>>> {
>>> [...]
>>> }
>>> #endif
>>>
>>> and
>>>
>>> void xenmem_reservation_va_mapping_reset(unsigned long count,
>>> struct page **pages)
>>> {
>>> #ifdef CONFIG_XEN_HAVE_PVMMU
>>> if (!xen_feature(XENFEAT_auto_translated_physmap)) {
>>> int i;
>>>
>>> for (i = 0; i < count; i++)
>>> __xenmem_reservation_va_mapping_reset(pages[i]);
>>> }
>>> #endif
>>> }
>>>
>>> This way I can use __xenmem_reservation_va_mapping_reset(page);
>>> instead of xenmem_reservation_va_mapping_reset(1, &page);
>>
>> Sure, this also works.
> Could you please take look at the patch attached if this is what we want?
Please ignore it, it is ugly ;)
I have implemented this as you suggested:
static inline void
xenmem_reservation_va_mapping_update(unsigned long count,
struct page **pages,
xen_pfn_t *frames)
{
#ifdef CONFIG_XEN_HAVE_PVMMU
if (!xen_feature(XENFEAT_auto_translated_physmap))
__xenmem_reservation_va_mapping_update(count, pages, frames);
#endif
}
>> -boris
>>
> Thank you,
> Oleksandr
next prev parent reply other threads:[~2018-05-31 14:29 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 15:33 [PATCH 0/8] xen: dma-buf support for grant device Oleksandr Andrushchenko
2018-05-25 15:33 ` [PATCH 1/8] xen/grant-table: Make set/clear page private code shared Oleksandr Andrushchenko
2018-05-29 17:39 ` Boris Ostrovsky
2018-05-30 4:24 ` Juergen Gross
2018-05-30 5:27 ` Oleksandr Andrushchenko
2018-05-30 21:34 ` Dongwon Kim
2018-05-31 5:37 ` Oleksandr Andrushchenko
2018-05-25 15:33 ` [PATCH 2/8] xen/balloon: Move common memory reservation routines to a module Oleksandr Andrushchenko
2018-05-29 18:04 ` Boris Ostrovsky
2018-05-29 18:22 ` Oleksandr Andrushchenko
2018-05-29 20:03 ` Boris Ostrovsky
2018-05-30 8:29 ` Oleksandr Andrushchenko
2018-05-30 15:54 ` Boris Ostrovsky
2018-05-30 17:46 ` Oleksandr Andrushchenko
2018-05-30 19:24 ` Boris Ostrovsky
2018-05-31 7:51 ` Oleksandr Andrushchenko
2018-05-31 14:29 ` Oleksandr Andrushchenko [this message]
2018-05-29 18:24 ` Boris Ostrovsky
2018-05-29 18:23 ` Oleksandr Andrushchenko
2018-05-30 4:32 ` Juergen Gross
2018-05-30 5:30 ` Oleksandr Andrushchenko
2018-05-25 15:33 ` [PATCH 3/8] xen/grant-table: Allow allocating buffers suitable for DMA Oleksandr Andrushchenko
2018-05-29 19:10 ` Boris Ostrovsky
2018-05-30 6:34 ` Oleksandr Andrushchenko
2018-05-30 15:20 ` Boris Ostrovsky
2018-05-30 17:49 ` Oleksandr Andrushchenko
2018-05-30 19:25 ` Boris Ostrovsky
2018-05-25 15:33 ` [PATCH 4/8] xen/gntdev: Allow mappings for DMA buffers Oleksandr Andrushchenko
2018-05-29 21:52 ` Boris Ostrovsky
2018-05-30 6:47 ` Oleksandr Andrushchenko
2018-05-25 15:33 ` [PATCH 5/8] xen/gntdev: Add initial support for dma-buf UAPI Oleksandr Andrushchenko
2018-05-29 22:34 ` Boris Ostrovsky
2018-05-30 6:52 ` Oleksandr Andrushchenko
2018-05-30 6:52 ` Oleksandr Andrushchenko
2018-05-25 15:33 ` [PATCH 6/8] xen/gntdev: Implement dma-buf export functionality Oleksandr Andrushchenko
2018-05-30 23:10 ` Dongwon Kim
2018-05-31 5:55 ` Oleksandr Andrushchenko
2018-05-31 14:32 ` Oleksandr Andrushchenko
2018-05-25 15:33 ` [PATCH 7/8] xen/gntdev: Implement dma-buf import functionality Oleksandr Andrushchenko
2018-05-25 15:33 ` [PATCH 8/8] xen/gntdev: Expose gntdev's dma-buf API for in-kernel use Oleksandr Andrushchenko
2018-05-30 8:32 ` Oleksandr Andrushchenko
2018-05-31 1:46 ` [PATCH 0/8] xen: dma-buf support for grant device Boris Ostrovsky
2018-05-31 5:51 ` Oleksandr Andrushchenko
2018-05-31 14:41 ` Oleksandr Andrushchenko
2018-05-31 20:25 ` Boris Ostrovsky
2018-06-01 5:42 ` Oleksandr Andrushchenko
2018-05-31 19:36 ` Boris Ostrovsky
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=4d386f6f-5212-1e42-abf7-1913f6218f05@gmail.com \
--to=andr2000@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=daniel.vetter@intel.com \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matthew.d.roper@intel.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=xen-devel@lists.xenproject.org \
/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).