From: Henning Schild <henning.schild@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] [PATCH v3] ipipe x86 mm: handle huge pages in memory pinning
Date: Thu, 4 Feb 2016 12:53:57 +0100 [thread overview]
Message-ID: <20160204125357.7068aaa4@md1em3qc> (raw)
In-Reply-To: <20160203142448.GB32138@hermes.click-hack.org>
On Wed, 3 Feb 2016 15:24:48 +0100
Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> On Wed, Feb 03, 2016 at 01:59:25PM +0100, Henning Schild wrote:
> > In 4.1 huge page mapping of io memory was introduced, enable ipipe
> > to handle that when pinning kernel memory.
> >
> > change that introduced the feature
> > 0f616be120c632c818faaea9adcb8f05a7a8601f
>
> Could we have an assessment of whether avoiding the call to
> __ipipe_pin_range_mapping in upper layers makes the patch simpler?
I will have a look at that. Specifically why mainline does not run into
that. With the lazy nature of the mappings, when it comes to other
mm's, i still do not see why the vmalloc_fault path does not deal with
huge pages.
Henning
next prev parent reply other threads:[~2016-02-04 11:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 17:34 [Xenomai] ipipe x86_64 huge page ioremap Henning Schild
2016-01-15 8:32 ` Philippe Gerum
2016-01-15 12:34 ` Jan Kiszka
2016-02-02 17:43 ` Henning Schild
2016-02-03 15:07 ` Philippe Gerum
2016-02-03 15:48 ` Philippe Gerum
2016-02-04 11:43 ` Henning Schild
2016-01-26 15:20 ` [Xenomai] [PATCH] ipipe x86 mm: handle huge pages in memory pinning Henning Schild
2016-01-26 20:18 ` Jan Kiszka
2016-01-27 9:54 ` Henning Schild
2016-01-27 10:31 ` Jan Kiszka
2016-01-27 10:44 ` Philippe Gerum
2016-01-27 10:46 ` Philippe Gerum
2016-01-27 13:41 ` [Xenomai] [PATCH v2] " Henning Schild
2016-01-28 10:53 ` Philippe Gerum
2016-01-28 20:53 ` Henning Schild
2016-01-29 17:11 ` Philippe Gerum
2016-01-29 18:39 ` Gilles Chanteperdrix
2016-02-02 12:08 ` Henning Schild
2016-02-02 13:58 ` Philippe Gerum
2016-02-02 16:38 ` Henning Schild
2016-02-02 16:39 ` Jan Kiszka
2016-02-02 19:26 ` Gilles Chanteperdrix
2016-02-03 11:35 ` Henning Schild
2016-02-02 14:18 ` Philippe Gerum
2016-02-02 16:30 ` Henning Schild
2016-02-02 11:41 ` Henning Schild
2016-02-03 12:59 ` [Xenomai] [PATCH v3] " Henning Schild
2016-02-03 14:24 ` Gilles Chanteperdrix
2016-02-03 14:31 ` Jan Kiszka
2016-02-03 14:38 ` Gilles Chanteperdrix
2016-02-03 14:51 ` Jan Kiszka
2016-02-03 15:02 ` Gilles Chanteperdrix
2016-02-03 15:14 ` Jan Kiszka
2016-02-04 11:53 ` Henning Schild [this message]
2016-02-08 8:44 ` Henning Schild
2016-03-07 7:58 ` Henning Schild
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=20160204125357.7068aaa4@md1em3qc \
--to=henning.schild@siemens.com \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.