From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: jgross@suse.com, xen-devel@lists.xenproject.org,
david.vrabel@citrix.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] xen/gntdev: Use mempolicy instead of VM_IO flag to avoid NUMA balancing
Date: Thu, 17 Nov 2016 11:09:22 -0500 [thread overview]
Message-ID: <057d38c5-4e1a-21dd-c51d-010b1dfdc752@oracle.com> (raw)
In-Reply-To: <20161117160140.GB19761@aepfle.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 646 bytes --]
On 11/17/2016 11:01 AM, Olaf Hering wrote:
> On Thu, Nov 17, Boris Ostrovsky wrote:
>
>> On 11/17/2016 06:28 AM, Olaf Hering wrote:
>>> ERROR: "__mpol_dup" [drivers/xen/xen-gntdev.ko] undefined!
>>> ERROR: "get_task_policy" [drivers/xen/xen-gntdev.ko] undefined!
>> I just built 4.4.11 with this patch applied and haven't had any problems.
> Are these functions exported? How would the driver module call into the
> core kernel? Maybe the added functionality should be provided by an
> exported helper function.
You are right --- I didn't realize was building with grant device
built-in. So yes, this needs to be fixed.
-boris
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-17 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1479318378-595-1-git-send-email-boris.ostrovsky@oracle.com>
2016-11-17 11:28 ` [PATCH v2] xen/gntdev: Use mempolicy instead of VM_IO flag to avoid NUMA balancing Olaf Hering
[not found] ` <20161117112843.GA19761@aepfle.de>
2016-11-17 16:01 ` Boris Ostrovsky
2016-11-17 16:01 ` Olaf Hering
2016-11-17 16:09 ` Boris Ostrovsky [this message]
2016-11-16 17:46 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=057d38c5-4e1a-21dd-c51d-010b1dfdc752@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--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).