All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] pgprot_noncached for io-remapping?
Date: Sun, 16 Mar 2008 16:52:42 +0100	[thread overview]
Message-ID: <47DD424A.7040006@domain.hid> (raw)
In-Reply-To: <47DD3FB4.5080305@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> doesn't this patch [1] have some relevance for us as well? As we use
>> xnarch_remap_io_page_range also for non-IO memory, I'm hesitating to
>> suggest that we apply this unconditionally at xnarch level. Ideas welcome.
>>
> 
> Yes, I think it makes a lot of sense on powerpc at least, since doing so will
> set the PAGE_GUARDED bit as well, and we obviously want to avoid any
> out-of-order access of I/O memory.
> 
> (I don't see the reason to force the VM_RESERVED and VM_IO on the vma though,
> since remap_pfn_range will do it anyway.)

No, I was talking about cases where we may pass kmalloc'ed memory to
xnarch_remap_io_page_range. In that case, caching and out-of-order
access may be desired for performance reasons.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2008-03-16 15:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 15:25 [Xenomai-core] pgprot_noncached for io-remapping? Jan Kiszka
2008-03-16 15:41 ` Philippe Gerum
2008-03-16 15:52   ` Jan Kiszka [this message]
     [not found]     ` <47DD47F0.5020003@domain.hid>
2008-03-16 16:36       ` Jan Kiszka
2008-03-16 16:43         ` Philippe Gerum
2008-03-16 16:45           ` Philippe Gerum
2008-03-16 16:45           ` Philippe Gerum
2008-03-16 16:50           ` Jan Kiszka
2008-03-16 17:07             ` Philippe Gerum
2008-03-16 17:15               ` Jan Kiszka
2008-03-16 17:34                 ` Philippe Gerum
2008-03-16 17:54                   ` Jan Kiszka
2008-03-16 18:11                     ` Philippe Gerum

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=47DD424A.7040006@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Xenomai-core@domain.hid \
    --cc=rpm@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.