From: Jeffrey Melville <jmelville@mitre.org>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] rtdm_iomap_to_user caching followup
Date: Wed, 27 Aug 2014 16:59:33 -0400 [thread overview]
Message-ID: <53FE46B5.4010001@mitre.org> (raw)
In-Reply-To: <53F4F273.7090104@xenomai.org>
On 8/20/2014 3:09 PM, Gilles Chanteperdrix wrote:
> On 08/20/2014 04:46 PM, Jeffrey Melville wrote:
>> All,
>>
>> There was a patch applied back in January 2013 to disable caching with
>> memory areas mapped with rtdm_iomap_to_user.
>> (http://www.xenomai.org/pipermail/xenomai/2013-January/027370.html)
>>
>> Henri Roosen followed up in September 2013 to say that he still saw
>> caching behavior with rtdm_iomap_to_user. The original patch didn't
>> cover the ifdef LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,16) &&
>> defined(CONFIG_MMU). He submitted two patch options but I didn't see any
>> responses.
>> (http://www.xenomai.org/pipermail/xenomai/2013-September/029211.html)
>
>
> I believe this has been merged with commit
> http://git.xenomai.org/xenomai-2.6.git/commit/?id=1b8fb14e486ac0604e44067a0f1f89dc14153e95
>
> Could you try xenomai 2.6 git to see if you still have the issue?
>
Gilles,
Thanks for your response. My mistake, I thought I had already looked at
the 2.6 git head. The commit you mentioned is the right one. I tested
the 2.6 git on my hardware and didn't have any lockup issues. Yocto
actually still mistakenly applied my old patch against the kmem wrapper
(which I'm not using anywhere). I need to remove that from my build but
otherwise everything looks good for now.
Cheers,
Jeff
prev parent reply other threads:[~2014-08-27 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 14:46 [Xenomai] rtdm_iomap_to_user caching followup Jeffrey Melville
2014-08-20 19:09 ` Gilles Chanteperdrix
2014-08-27 20:59 ` Jeffrey Melville [this message]
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=53FE46B5.4010001@mitre.org \
--to=jmelville@mitre.org \
--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.