From: Ciprian Barbu <ciprian.barbu@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, aarcange@redhat.com
Subject: CONFIG_TRANSPARENT_HUGEPAGE with PREEMPT_RT_FULL
Date: Wed, 02 Oct 2013 13:59:00 +0300 [thread overview]
Message-ID: <524BFC74.6060401@linaro.org> (raw)
Hello Thomas,
(resending due to HTML formatting)
I am looking into using CONFIG_TRANSPARENT_HUGEPAGE with PREEMPT_RT_FULL
but currently the latest rt patch has it disabled.
What I managed to find on the mailing list so far is that Yong Zhang
reported a crash on rt_spin_lock for which you suggested to disable
CONFIG_TRANSPARENT_HUGEPAGE until further notice. That was on Jul 24,
2011 so I was wondering if you have any more news on that. Is there any
hope to get transparent hugepages working with preempt_rt? Any estimate
on how difficult a fix for that will be?
Also, we ran some basic ltp mm and ltp hugetlb on an rt image with
transparent hugepages, on an ARM arndale, and didn't get any problems.
Do you think it's possible that the problem got fixed somewhere along
the way?
Thanks and regards,
Ciprian
reply other threads:[~2013-10-02 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=524BFC74.6060401@linaro.org \
--to=ciprian.barbu@linaro.org \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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