From: Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>
To: Christoph Hellwig <hch@infradead.org>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"marmarek@invisiblethingslab.com"
<marmarek@invisiblethingslab.com>
Subject: Re: [Xen-devel] xen/mem-reservation API and out-of-tree kernel modules
Date: Fri, 1 Feb 2019 08:38:43 +0000 [thread overview]
Message-ID: <735816a7-897a-61ad-e70b-8d683c94d8ac@epam.com> (raw)
In-Reply-To: <20190201082710.GA7437@infradead.org>
On 2/1/19 10:27 AM, Christoph Hellwig wrote:
> On Thu, Jan 31, 2019 at 01:44:15PM -0800, Stefano Stabellini wrote:
>> The alternative would be to turn xenmem_reservation_scrub_page into a
>> regular function (not a static inline)?
> All that is a moot point until said currently out of tree module gets
> submitted for inclusion anyway.
Indeed this is a moot point, so I can't argue here.
But this is how it is and unfortunately we have to live
with those modules and depend on 3rd parties willing or not
to disclose their sources to public...
next prev parent reply other threads:[~2019-02-01 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 14:02 [Xen-devel] xen/mem-reservation API and out-of-tree kernel modules Oleksandr Andrushchenko
2019-01-31 21:44 ` Stefano Stabellini
2019-02-01 8:27 ` Christoph Hellwig
2019-02-01 8:38 ` Oleksandr Andrushchenko [this message]
2019-02-01 8:45 ` Christoph Hellwig
2019-02-01 8:39 ` Oleksandr Andrushchenko
2019-02-01 9:14 ` Juergen Gross
2019-02-01 9:40 ` Oleksandr Andrushchenko
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=735816a7-897a-61ad-e70b-8d683c94d8ac@epam.com \
--to=oleksandr_andrushchenko@epam.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hch@infradead.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--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).