All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <dev@sw.ru>
To: devel@openvz.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Containers@lists.osdl.org, video4linux-list@redhat.com,
	kraxel@bytesex.org, linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [Devel] Re: [PATCH] kthread: saa7134-tvaudio.c
Date: Wed, 30 Aug 2006 20:35:33 +0400	[thread overview]
Message-ID: <44F5BE55.2010904@sw.ru> (raw)
In-Reply-To: <44F5BA6F.2070900@fr.ibm.com>

Cedric Le Goater wrote:
> Eric W. Biederman wrote:
> 
> [ ... ]
> 
> 
>>>>That plus the obvious bit.  For the pid namespace we have to declare
>>>>war on people storing a pid_t values.  Either converting them to
>>>>struct pid * or removing them entirely.  Doing the kernel_thread to
>>>>kthread conversion removes them entirely.
>>>
>>>we've started that war, won a few battles but some drivers need more work
>>>that a simple replace. If we could give some priorities, it would help to
>>>focus on the most important ones. check out the list bellow.
>>
>>Sure, I think I can help.
>>
>>There are a couple of test I can think of that should help.
>>1) Is the pid value stored.  If not a pid namespace won't affect
>>   it's normal operation.
> 
> 
> I've extracted this list from a table which includes a pid cache column.
> this pid cache column is not complete yet. I'd be nice if we could use a
> wiki to maintain this table, the existing openvz or vserver wiki ?
feel free to use http://wiki.openvz.org
we will create a 'Developement' category then for such pages.
I think we can help with the patches soon as well.

[...]
>>I do agree from what I have seen, that changing idioms to the kthread way of
>>doing things isn't simply a matter of substitute and replace which is
>>unfortunate.  Although the biggest hurdle seems to be to teach kernel threads
>>to communicate with something besides signals.  Which is a general help anyway.
>>
>>Unfortunately I'm distracted at the moment so I haven't gone through the entire
>>list but I hope this helps.
If we have some list on the wiki, people could assign the issues to themself and
prepare the patches. Thus work could be paralleled a bit.

Thanks,
Kirill

  reply	other threads:[~2006-08-30 16:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 21:15 [PATCH] kthread: saa7134-tvaudio.c Sukadev Bhattiprolu
2006-08-29 21:22 ` Dave Hansen
2006-08-29 21:39 ` Andrew Morton
2006-08-29 22:39   ` Eric W. Biederman
2006-08-30 12:39     ` Eric W. Biederman
2006-08-30 14:07       ` Cedric Le Goater
2006-08-30 15:43         ` Eric W. Biederman
2006-08-30 16:18           ` Cedric Le Goater
2006-08-30 16:35             ` Kirill Korotaev [this message]
2006-08-30 16:38             ` [Devel] " Kir Kolyshkin
2006-08-30 16:30   ` Cedric Le Goater
2006-08-30 16:49     ` Andrew Morton
2006-08-30 17:36       ` Mauro Carvalho Chehab
2006-08-31  1:02         ` Sukadev Bhattiprolu
2006-08-31  1:05         ` [PATCH] kthread: tvaudio.c Sukadev Bhattiprolu

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=44F5BE55.2010904@sw.ru \
    --to=dev@sw.ru \
    --cc=Containers@lists.osdl.org \
    --cc=devel@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=video4linux-list@redhat.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 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.