All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arch@vger.kernel.org,
	Parisc List <linux-parisc@vger.kernel.org>,
	linux-ia64@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Correct printk %pF to work on all architectures
Date: Wed, 03 Sep 2008 18:00:53 -0500	[thread overview]
Message-ID: <1220482853.3254.47.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.1.10.0809031546310.3515@nehalem.linux-foundation.org>

On Wed, 2008-09-03 at 15:54 -0700, Linus Torvalds wrote:
> > Anyway, it's easy to do (if a slightly larger diff) ... I have to move
> > the prototype from include/kernel.h to include/module.h because I need
> > an assured asm/xxx include before it to get the override.
> 
> I don't really see what this has to do with module.h, though.
> 
> Why do this in <linux/module.h>?  Why not just do it in lib/vsptintf.c 
> which is the only place that cares? None of this needs to pollute the 
> generic header files that simply don't care.

You want me to pull the elf header files into lib/vsprintf.c and have
something like

static inline void *dereference_function_descritpor(void *ptr)
{
#if defined(CONFIG_IA64) || defined(CONFIG_PPC64)
	void *p;
	if (!probe_kernel_address(ptr, p))
		ptr = p;
#elif defined(CONFIG_PARISC) && defined(CONFIG_64BITS)
	Elf64_Fptr *desc = ptr;
	void *p;
	if (!probe_kernel_address(&desc->addr, p))
		ptr = p;
#endif
	...

?

Because it just looks rather tacky ...

James



WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arch@vger.kernel.org,
	Parisc List <linux-parisc@vger.kernel.org>,
	linux-ia64@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Correct printk %pF to work on all architectures
Date: Wed, 03 Sep 2008 23:00:53 +0000	[thread overview]
Message-ID: <1220482853.3254.47.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.1.10.0809031546310.3515@nehalem.linux-foundation.org>

On Wed, 2008-09-03 at 15:54 -0700, Linus Torvalds wrote:
> > Anyway, it's easy to do (if a slightly larger diff) ... I have to move
> > the prototype from include/kernel.h to include/module.h because I need
> > an assured asm/xxx include before it to get the override.
> 
> I don't really see what this has to do with module.h, though.
> 
> Why do this in <linux/module.h>?  Why not just do it in lib/vsptintf.c 
> which is the only place that cares? None of this needs to pollute the 
> generic header files that simply don't care.

You want me to pull the elf header files into lib/vsprintf.c and have
something like

static inline void *dereference_function_descritpor(void *ptr)
{
#if defined(CONFIG_IA64) || defined(CONFIG_PPC64)
	void *p;
	if (!probe_kernel_address(ptr, p))
		ptr = p;
#elif defined(CONFIG_PARISC) && defined(CONFIG_64BITS)
	Elf64_Fptr *desc = ptr;
	void *p;
	if (!probe_kernel_address(&desc->addr, p))
		ptr = p;
#endif
	...

?

Because it just looks rather tacky ...

James



WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, linuxppc-dev@ozlabs.org,
	linux-ia64@vger.kernel.org,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] Correct printk %pF to work on all architectures
Date: Wed, 03 Sep 2008 18:00:53 -0500	[thread overview]
Message-ID: <1220482853.3254.47.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.1.10.0809031546310.3515@nehalem.linux-foundation.org>

On Wed, 2008-09-03 at 15:54 -0700, Linus Torvalds wrote:
> > Anyway, it's easy to do (if a slightly larger diff) ... I have to move
> > the prototype from include/kernel.h to include/module.h because I need
> > an assured asm/xxx include before it to get the override.
> 
> I don't really see what this has to do with module.h, though.
> 
> Why do this in <linux/module.h>?  Why not just do it in lib/vsptintf.c 
> which is the only place that cares? None of this needs to pollute the 
> generic header files that simply don't care.

You want me to pull the elf header files into lib/vsprintf.c and have
something like

static inline void *dereference_function_descritpor(void *ptr)
{
#if defined(CONFIG_IA64) || defined(CONFIG_PPC64)
	void *p;
	if (!probe_kernel_address(ptr, p))
		ptr = p;
#elif defined(CONFIG_PARISC) && defined(CONFIG_64BITS)
	Elf64_Fptr *desc = ptr;
	void *p;
	if (!probe_kernel_address(&desc->addr, p))
		ptr = p;
#endif
	...

?

Because it just looks rather tacky ...

James

  reply	other threads:[~2008-09-03 23:00 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 20:18 [PATCH] Correct printk %pF to work on all architectures James Bottomley
2008-09-03 20:18 ` James Bottomley
2008-09-03 20:18 ` James Bottomley
2008-09-03 21:22 ` Linus Torvalds
2008-09-03 21:22   ` Linus Torvalds
2008-09-03 21:22   ` Linus Torvalds
2008-09-03 22:42   ` James Bottomley
2008-09-03 22:42     ` James Bottomley
2008-09-03 22:42     ` James Bottomley
2008-09-03 22:42     ` James Bottomley
2008-09-03 22:54     ` Linus Torvalds
2008-09-03 22:54       ` Linus Torvalds
2008-09-03 22:54       ` Linus Torvalds
2008-09-03 23:00       ` James Bottomley [this message]
2008-09-03 23:00         ` James Bottomley
2008-09-03 23:00         ` James Bottomley
2008-09-03 23:15         ` Linus Torvalds
2008-09-03 23:15           ` Linus Torvalds
2008-09-03 23:15           ` Linus Torvalds
2008-09-03 23:33           ` James Bottomley
2008-09-03 23:33             ` James Bottomley
2008-09-03 23:33             ` James Bottomley
2008-09-04  0:01             ` Linus Torvalds
2008-09-04  0:01               ` Linus Torvalds
2008-09-04  0:01               ` Linus Torvalds
2008-09-04  1:43               ` James Bottomley
2008-09-04  1:43                 ` James Bottomley
2008-09-04  1:43                 ` James Bottomley
2008-09-04 22:36                 ` Benjamin Herrenschmidt
2008-09-04 22:36                   ` Benjamin Herrenschmidt
2008-09-04 22:36                   ` Benjamin Herrenschmidt
2008-09-04 23:07                   ` Luck, Tony
2008-09-04 23:07                     ` Luck, Tony
2008-09-04 23:07                     ` Luck, Tony
2008-09-09 14:12                     ` James Bottomley
2008-09-09 14:12                       ` James Bottomley
2008-09-09 14:12                       ` James Bottomley
2008-09-09 18:08                       ` Kyle McMartin
2008-09-09 18:08                         ` Kyle McMartin
2008-09-09 18:08                         ` Kyle McMartin
2008-09-09 22:05                         ` Benjamin Herrenschmidt
2008-09-09 22:05                           ` Benjamin Herrenschmidt
2008-09-09 22:05                           ` Benjamin Herrenschmidt

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=1220482853.3254.47.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=torvalds@linux-foundation.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.