Re: [git pull] kgdb light, v5
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Sun, 10 Feb 2008 22:13:47 +0100
* Jan Kiszka <jan.kiszka@xxxxxx> wrote:
Maybe, maybe not. I followed the comment in the original code, saying
that we need word-wise access for I/O memory poking. Can I assume
across a all archs that __copy_to/from_user will not perform byte
accesses if count is 2, 4, or 8? I would be glad if we can kill other
couple of line.
those architectures should extend mm/maccess.c accordingly. It's now the
collector point for "weird kernel-owned memory access functionality".
Ingo, if you are close to an editor, please pick those up? Here are
some offline things cooking on my side...
yeah, fixed these in my tree.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [0/6] kgdb light
- From: Ingo Molnar
- Re: [0/6] kgdb light
- From: Sam Ravnborg
- [git pull] kgdb light, v5
- From: Ingo Molnar
- Re: [git pull] kgdb light, v5
- From: Ray Lee
- Re: [git pull] kgdb light, v5
- From: Jan Kiszka
- Re: [git pull] kgdb light, v5
- From: Linus Torvalds
- Re: [git pull] kgdb light, v5
- From: Jan Kiszka
- [0/6] kgdb light
- Prev by Date: [PATCH 2/8] drivers/block: Use FIELD_SIZEOF
- Next by Date: Re: [rft] s2ram wakeup moves to .c, could fix few machines
- Previous by thread: Re: [git pull] kgdb light, v5
- Next by thread: Re: [git pull] kgdb light, v5
- Index(es):