public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: struct exception_table_entry
Date: Wed, 15 Apr 2009 08:21:58 +0200	[thread overview]
Message-ID: <49E57D06.3020500@petalogix.com> (raw)
In-Reply-To: <200904141636.11676.arnd@arndb.de>

Arnd Bergmann wrote:
> On Thursday 09 April 2009, Michal Simek wrote:
>
>   
>> I am doing some cleanup things in MB MMU kernel and I looked at
>> exception_table_entry structure.
>> Only alpha use different types among others. Some arch use only
>> different names and types int/long.
>> I think that this structure could be moved to any generic location ->
>> asm-generic/uaccess.h folder.
>>
>> I think that this structure types should be acceptable for every archs?
>>
>> #ifndef exception_table_entry
>> struct exception_table_entry {
>>     unsigned long insn;
>>     unsigned long fixup;
>> };
>> #endif
>>
>> What do you think?
>>     
>
> Yes, sounds good to me. Have you tried using my generic version of
> uaccess.h on microblaze? It already contains a definition like this,
> though most of the header doesn't apply for MMU-based architectures.
>   
I haven't had time to look at it but it is on my list.
> I suppose it can be improved a bit, but should do the basic job.
>   
yes of course. That was just my idea. Use it only for MMU kernels +
#ifndef for structure
doesn't work I think.

Thanks,
Michal
> 	Arnd <><
>   


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663


      parent reply	other threads:[~2009-04-15  6:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 15:05 struct exception_table_entry Michal Simek
2009-04-14 14:36 ` Arnd Bergmann
2009-04-14 22:14   ` David Miller
2009-04-15  6:26     ` Michal Simek
2009-04-15  6:21   ` Michal Simek [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=49E57D06.3020500@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox