From: Andrew Morton <akpm@linux-foundation.org>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: tzanussi@gmail.com, penberg@cs.helsinki.fi,
torvalds@linux-foundation.org, compudj@krystal.dyndns.org,
vegard.nossum@gmail.com, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 3/3] relay: Add buffer-only channels; useful for early logging.
Date: Wed, 2 Jul 2008 23:06:36 -0700 [thread overview]
Message-ID: <20080702230636.66e484bb.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080623153104.50549291@linux360.ro>
On Mon, 23 Jun 2008 15:31:04 +0300 Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> wrote:
> Allows one to create and use a channel with no associated files. Files
> can be initialized later. This is useful in scenarios such as logging
> in early code, before VFS is up. Therefore, such channels can be
> created and used as soon as kmem_cache_init() completed.
>
> This is needed by kmemtrace to do tracing in early kernel code.
This breaks on sparc64.
> + err = smp_call_function_single(i,
> + __relay_set_buf_dentry,
> + &disp, 0, 1);
Because that ain't implemented.
There's a call in net/iucv/iucv.c, but that's s390-only.
There's a call in virt/kvm/kvm_main.c.
There's a call in kernel/time/tick-broadcast.c, so I assume that the
intersection between CONFIG_GENERIC_CLOCKEVENTS_BROADCAST and
non-smp_call_function_single() architectures is presently empty.
I guess all SMP-capable architectures should now implement this,
please. It is presently defined on all architectures for CONFIG_SMP=n
and it is declared in include/linux/smp.h.
next prev parent reply other threads:[~2008-07-03 7:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 12:31 [PATCH 3/3] relay: Add buffer-only channels; useful for early logging Eduard - Gabriel Munteanu
2008-07-03 6:06 ` Andrew Morton [this message]
2008-07-05 4:14 ` Eduard - Gabriel Munteanu
2008-07-05 6:32 ` Andrew Morton
2008-08-06 17:32 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2008-06-21 14:11 Eduard - Gabriel Munteanu
2008-06-22 19:24 ` Pekka Enberg
2008-06-22 19:29 ` Pekka Enberg
2008-06-22 20:51 ` Eduard - Gabriel Munteanu
2008-06-15 15:05 Eduard - Gabriel Munteanu
2008-06-17 14:35 ` Mathieu Desnoyers
2008-06-13 1:10 Eduard - Gabriel Munteanu
2008-06-13 7:04 ` Pekka Enberg
2008-06-13 15:54 ` Eduard - Gabriel Munteanu
2008-06-16 12:30 ` Mathieu Desnoyers
2008-06-16 13:37 ` Eduard - Gabriel Munteanu
2008-06-17 13:53 ` Mathieu Desnoyers
2008-06-14 16:10 ` Eduard - Gabriel Munteanu
2008-06-16 12:35 ` Mathieu Desnoyers
2008-06-16 13:30 ` Eduard - Gabriel Munteanu
2008-06-12 20:26 Eduard - Gabriel Munteanu
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=20080702230636.66e484bb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.org \
--cc=tzanussi@gmail.com \
--cc=vegard.nossum@gmail.com \
/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