All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Dmitry Adamushko <dmitry.adamushko@domain.hid>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [PATCH 5/7] Introduce ipipe_base.h (i386/x86_64)
Date: Fri, 27 Apr 2007 13:51:52 +0200	[thread overview]
Message-ID: <4631E3D8.4070400@domain.hid> (raw)
In-Reply-To: <b647ffbd0704270439h2a6e7ba2hee14be3a7a84e449@domain.hid>

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

Dmitry Adamushko wrote:
> On 26/04/07, Jan Kiszka <jan.kiszka@domain.hid> wrote:
>> These patches introduce minimalistic ipipe_base.h to be included by
>> every header out there in the kernel without any dependencies. That is
>> exploited here to move all *stall_root() related prototypes out off
>> irqflags.h, to following patches need ipipe_base.h as well.
> 
> So this file is supposed to extend with another generic stuff, isn't
> it? At the moment it's completely about the root domain, so one would
> think of ipipe_root.h as a more appropriate name.

Yes, when just looking at this particular patch. But then patch #7
extends the scope.

> 
> And this "minimalistic" and "without any dependencies" is due to the
> heaviness of linux/pipe.h?

Yep. Originally, I tried hard to drag central parts of struct
ipipe_domain into it. The goal was to work on a known root domain
structure instead of poking half-blind into it for the domain state. But
I already failed due to struct list_entry and IPIPE_NR_IRQS (would have
required something like asm/ipipe_base.h :-/). Not to speak of struct mutex.

Jan


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

  reply	other threads:[~2007-04-27 11:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 18:41 [Adeos-main] [PATCH 5/7] Introduce ipipe_base.h (i386/x86_64) Jan Kiszka
2007-04-27 11:39 ` Dmitry Adamushko
2007-04-27 11:51   ` Jan Kiszka [this message]
2007-04-27 11:53   ` Dmitry Adamushko

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=4631E3D8.4070400@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=dmitry.adamushko@domain.hid \
    /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.